Billing, products, and seats

GTM Engine uses a product SKU and credit model rather than a single monolithic plan. Your organization owns specific product engines (such as Core, Pipeline Engine, Campaign Engine, Prospecting Engine, Content Engine, Enrichment Engine, and Workspace Admin), each with its own seat capacity, alongside a shared credit balance that powers AI generation, enrichment, and automation. For the full breakdown of what spends credits, see Credits and usage.

How product SKUs work

Every product SKU defines:

Feature and workflow access — each engine unlocks a specific set of pages, workflows, and capabilities across the workspace.
Seat capacity — seats are tracked per SKU (seats_assigned out of seats_entitled), so you can give revenue reps, marketers, or admins access to only the engines they need.

When a feature is locked because your organization is missing an entitlement, GTM Engine shows the required SKU in the locked page, inline card, prompt, or navigation tooltip so admins know which engine unlocks access.

Your owned products, seat usage, credit balance, and usage breakdown are visible to admins and RevOps users under Settings → Billing. The Usage Detail tab defaults its usage selector to Charged usage for credit balance consumption, with included seat-bundled usage available from the same selector. Included system workflow activity can show AI cost without reducing your credit balance. Usage Detail also separates Historical record backfill (10 credits per opportunity, contact, or account record enqueued when configured as credit-billed), Custom field backfill (10 credits per successfully processed record when configured as credit-billed), Mailbox warmup (prorated for the activation month, then 350 credits per mailbox/month), Domain warmup (prorated for the activation month, then 2,000 credits per domain/month), and Inbox placement checks (50 credits per mailbox checked). Selected custom AI/Research field tasks can also produce their own AI Prompt or Research usage entries.

Free vs. paid engines

New workspaces start with limited trial access so you can explore GTM Engine before purchasing seats. Once your organization purchases a paid engine SKU or credit tier, paid capabilities and included out-of-the-box field processing are unlocked for assigned users.

If all paid Stripe subscriptions terminate, GTM Engine removes the Stripe-backed paid entitlements and returns the workspace to default free limits without re-granting one-time signup credits.

Seats and adding engines

Seats are counted per product SKU and assigned to active and invited users. On Settings → Billing → Overview:

Your products shows each SKU your organization owns, how many seats are assigned vs. entitled, how many seats are still available, the subscription status, and the next renewal or expiration date.
Seats are assigned by giving a teammate a role under Settings → Team → Members. Every active or invited teammate holds a Core workspace seat, and each role uses a seat on the product it belongs to (for example, Sales User uses a Sales Engine seat); a teammate only uses one seat per product no matter how many roles they hold for it. Executive Admin uses one engine seat in addition to Core: a Sales Engine seat if your organization owns Sales Engine, otherwise Campaign Engine, then Customer Success Engine, then Content Engine. The Free plan includes one Campaign Engine seat for the signup Executive Admin. Executive Admins can still see every product your organization owns; seats only count usage. Seats update automatically when your products change: adding Sales Engine moves the Executive Admin from the Campaign seat to a Sales seat, and seats on cancelled or expired products are released. The role picker shows how many seats each role will use and how many are left; if a product is out of seats, the role is grayed out with a link to buy more. Removing a role frees its seat once no remaining role needs that product, and deactivating or removing a teammate frees all of their seats (reactivating them requires those seats to be available). Assign via roles on a product card takes you there.
Click Buy seats on an owned product (or Add seats on Settings → Team → Members) to preview the prorated Stripe cost and add or reduce seats.
Add more engines lists product SKUs your workspace does not own yet, along with what each engine unlocks and per-seat pricing. Admins can click Add to workspace to buy seats through self-serve Stripe checkout, Learn more to inspect everything the SKU unlocks, or Talk to sales to have Genie connect them with the team.

Getting more credits

When you need more credits for AI workflows, prospecting, or enrichment, you can subscribe to a recurring monthly credit tier or purchase a one-time credit pack from the Credits card on Settings → Billing. The purchase dialog groups recurring monthly tiers (highlighting your current tier) separately from one-time top-up packs. See Getting credits for the details.

Managing billing

Billing is admin and RevOps only. From Settings → Billing, eligible users can:

Review owned product SKUs, seat utilization, credit balance, and period usage on Overview.
Buy additional seats for owned and unowned SKUs (seats are assigned through roles on Settings → Team → Members).
Subscribe to recurring credit tiers or buy one-time credit packs.
Open the Stripe billing portal via Manage to update payment methods, manage subscriptions, and download invoices.

Self-serve purchase options are limited to active customer-visible Stripe catalog items. Legacy, test, hidden, custom, and admin-only catalog entries are not shown in customer purchase selectors. Some Stripe changes (such as seat reductions) take effect at the next billing period instead of immediately; GTM Engine records those scheduled changes when submitted and applies them automatically at the end of the billing cycle.

When an organization already has an active recurring credit tier, choosing a different tier updates the existing credit-tier subscription instead of starting a second one. The replacement tier sets the recurring credit balance for that tier rather than stacking with the previous tier.

Recurring Stripe-backed SKUs renew automatically; no manual renewal action is required from the Billing page. Stripe checkouts return to /settings/billing with a confirmation banner and refresh your entitlements once payment is confirmed.

If a payment fails, there's a short grace period before access degrades — resolving billing here restores full access. See Running low or out.

Organizations on Stripe-backed contracts are managed by GTM Engine admins instead of self-serve checkout. Contract entitlements grant when Stripe finalizes the contract invoice, preserve negative credit overage across renewals, and clear grace metadata when the invoice is paid. Super admins can inspect a contract-backed organization's Billing & Usage snapshot from Billing Contracts when helping with amendments.