Pricing themes

A sales motion where a human at the vendor must engage to close the deal — typically tied to custom quotes and committed contracts.

Pricing plans designed for large organisations — typically custom-quoted, with SSO, SCIM, audit logs, and committed-use discounts.

A sales motion where customers can sign up, pay, and use the product without ever speaking to a human at the vendor.

Pricing plans aimed at small and medium businesses — typically self-serve, with team features and modest per-user fees.

Pricing plans aimed at mid-market companies — typically a hybrid of self-serve onboarding and sales-assisted upgrades, with SSO and advanced admin.

A sales motion where the product itself drives acquisition, expansion, and retention — typically anchored in a free or low-friction tier.

A billing unit where the vendor charges a fixed fee per named user, regardless of how much each user consumes.

A pricing model that combines a permanently free tier with paid upgrade plans, used to drive product-led growth and self-serve acquisition.

Pricing for general-purpose AI platforms — model APIs, inference services, and multi-model hosting providers.

A pricing model that charges a flat recurring fee — monthly or annual — with no usage component meaningful to the bill.

Pricing for AI agent platforms — products that perform multi-step autonomous tasks on the user's behalf.

A pricing model that combines a fixed recurring fee with variable usage-based charges, both meaningful to the bill.

Pricing plans designed for developers — typically pure-usage, self-serve, and credit-card billed, with free tiers and API-first access.

A billing unit where customers pre-purchase or are allocated a pool of credits that deplete as they use the product, often at variable rates per feature.

Pricing plans designed for individual users — typically priced low, self-serve, and credit-card billed.

Pricing for AI model inference services — APIs and platforms that run trained models on user inputs, typically billed per token, per request, or per GPU-hour.

A pricing model where the customer pays only for what they consume, with no fixed recurring fee beyond a possible minimum.

Pricing models used by tools sold to developers — IDEs, CLIs, libraries, voice-to-code, and adjacent products.

A pricing model where the primary billing dimension is the number of named users, regardless of their consumption.

Pricing for AI products whose core job is analytics — querying, evaluating, and reporting on data, models, or market signals.

A billing unit common in LLM and AI products, where customers are charged per input and output token processed.

Pricing for vertical SaaS products — AI software purpose-built for a specific industry (legal, healthcare, sales, marketing).

A pricing model where the customer commits to a minimum spend over a period (typically annual) in exchange for a discounted rate.

Pricing for horizontal AI SaaS — productivity and workflow products sold across industries rather than to one vertical.

A billing unit where customers are charged per API request, regardless of payload size or processing time.

Pricing for AI marketing products — content generation, ad creative, outbound campaigns, and sales-marketing automation.

A billing unit where customers are charged per request served — the generic meter for inference endpoints, search, scraping, and browser infrastructure.

Pricing for AI compute infrastructure — GPU clouds, serverless inference, and training platforms.

A billing unit where customers are charged per minute of audio or video processed — used by speech, voice, and video AI vendors.

Pricing for data collection, scraping, and pipeline services — platforms that extract, transform, and deliver web data, typically billed per request, per GB, or per record.

Pricing for AI products that automate customer service — chatbots, ticket triage, and autonomous resolution agents.

Pricing for data platforms — scraping, enrichment, search API, and knowledge-graph vendors.

A subset of hybrid pricing where a per-user seat fee is combined with usage-based charges that typically dominate the bill at scale.

A billing unit where customers are charged per gigabyte of data stored on the platform per month.

Pricing for AI-native developer tools — code editors, completion engines, and agent platforms that write or modify code.

Pricing for AI services whose primary output is generated source code, typically measured in tokens, requests, or completed tasks.

A billing unit where customers are charged for GPU time consumed, typically measured per-second or per-hour by GPU type.

A pricing model where the customer is charged per business outcome — a resolved support ticket, a converted lead, a closed sale — rather than per unit of input.

Pricing for products that monitor AI systems and software — LLM observability, evaluation in production, and security monitoring.

Pricing for products whose primary surface is AI-assisted coding — IDEs, completion engines, and review agents.

Pricing for customer service software platforms — ticketing, chat, automation, and AI agent products.

A billing unit where customers are charged per event ingested — the native meter of observability and billing-infrastructure platforms.

Pricing for usage-billing and metering platforms — the vendors that meter, rate, and invoice usage for other companies.

Pricing for AI-era fintech products — billing infrastructure, accounting automation, and financial operations platforms.

A billing unit where customers are charged per monthly or daily active user rather than per provisioned seat.

A billing unit where customers are charged for the CPU time their workloads consume, typically measured in vCPU-seconds or vCPU-hours.

A billing unit where customers are charged per document processed or generated — common in AI writing, SEO, and document-intelligence tools.

A billing unit unique to AI customer-support products, where the vendor charges only when an AI agent resolves a customer issue without escalation.

Pricing for AI-enabled billing and payment infrastructure platforms that help software companies meter usage, generate invoices, and collect revenue.

A billing unit used by robotics, hardware AI, and some SaaS companies where the metered object is a physical or abstract 'unit' — a robot deployed, a device sold, or a defined deliverable.

Pricing for platforms that host web applications, typically billed across multiple dimensions — bandwidth, requests, compute, and storage.

A billing unit where customers are charged per financial or billing transaction processed — the meter of billing and accounting platforms.

Pricing for LLM and ML observability platforms — tracing, evaluation, and monitoring of model behavior in production.

A billing unit where customers are charged per character of text processed — the standard meter for text-to-speech and translation.

A billing unit where each end-to-end workflow or automation run is metered and billed, regardless of the compute steps it contains.

A billing unit where customers are charged per gigabyte of data transferred out of the platform.

A billing unit where each individual message or reply in a conversation is metered, common in AI chat and voice platforms.

A billing unit where customers are charged per page crawled, parsed, or rendered — the meter for web scraping and document parsing.

A billing unit where customers are charged per task an automation or agent executes — Zapier's historical unit, now spreading to AI agents.

A billing unit where customers are charged for vectors stored or indexed — the storage dimension of vector database pricing.

A billing unit where customers are charged for the memory their workloads consume over time, measured in gigabyte-hours.

A billing unit where each contact or lead in the database is metered, common in AI sales development and outbound automation platforms.

A billing unit where each discrete action taken by an AI agent or automation is metered — common in browser automation and agentic workflow tools.

A billing unit where each complete customer conversation — from first message to resolution — is metered as a single chargeable event.

A billing unit where each AI-generated image is metered, common in image generation APIs and multimodal AI platforms.

A billing unit used by billing infrastructure platforms where each invoice generated or processed is metered as the primary cost driver.

Pricing for serverless function platforms, billed per invocation plus compute time consumed.

A billing unit where each data record processed, labeled, or extracted is metered — common in data platforms and web scraping services.

A billing unit common in translation and localization platforms where the metered object is the word count of content processed.

A pricing structure where access to proprietary datasets or data assets is licensed separately from the software or services, common in AI training data and clinical data platforms.

A billing unit used in drug discovery and biotech AI where payment is tied to achieving defined research milestones rather than time or compute consumed.

A billing unit where each individual data measurement or signal ingested is metered — common in cloud cost intelligence and ML evaluation platforms.

A billing unit where each AI-generated creative asset — image, video, or design — is counted as a 'generation' and metered accordingly.

A billing unit where each patient-agent or user-agent interaction is metered, common in healthcare AI and customer engagement platforms.

A billing unit where payment is triggered by verified outcomes delivered — distinct from outcome-based pricing models, this refers specifically to 'outcomes' as a countable billing unit.

A billing unit where each AI-generated video is metered, common in video generation and synthetic media platforms.

Pricing for AI-powered security products — covering code security, voice fraud detection, SOC automation, and threat analysis.

Pricing for AI products that generate UI components or full pages from prompts — typically billed per credit or generation.

A billing unit where each hour of headless browser compute time is metered, common in web scraping and browser automation platforms.

Pricing for platform-as-a-service products that abstract away the underlying infrastructure and bill for higher-level units.

A billing unit where each LLM request log ingested or stored is metered — common in AI observability and evaluation platforms.

A billing unit where each connected email mailbox or sending account is metered, common in AI outbound sales and email automation platforms.

A billing unit where each customer support ticket handled by an AI agent is metered — common in AI customer service platforms.

A billing unit where each distributed trace — a complete record of an LLM request chain — is metered, common in AI observability platforms.

A billing unit where each hour a robot or autonomous system operates is metered — the robotics equivalent of a GPU-hour.

Pricing for platforms that track, analyze, and optimize AI API spending — the observability layer for AI infrastructure costs.

Pricing for platforms purpose-built to observe, debug, and optimize LLM application behavior — logging prompts, responses, latency, and cost.

A sales motion where the vendor's primary go-to-market route runs through resellers, system integrators, or strategic partners rather than direct sales.

A billing unit used in legal AI platforms where each case or matter processed by the AI is metered.

A billing unit where each hardware device or endpoint connected to the AI platform is metered.

A billing unit where customers are charged per serverless function invocation, often combined with a separate compute-time charge.

A billing unit where each IP address or proxy endpoint allocated is metered — used by web scraping proxy providers.

A billing unit where each AI-generated report or analysis document is metered as a discrete output.