Credits and usage

Credits are the unit GTM Engine uses to bill value-generating work — AI generation, data discovery, enrichment, research, and domain purchases. Most everyday usage of the app is free; credits are only spent on a specific, bounded set of actions.

A key conversion to remember: 100 credits = $1.00 of underlying cost. AI-powered actions pass the real model cost through at that rate (rounded up), so a single Genie question is usually worth a few cents in credits, not a large fixed block.

How AI is metered: pass-through plus compute

GTM Engine acts as a utility for AI. We meter the exact token consumption reported by the model provider and pass that cost through to you without markup, converted to credits at 100 credits = $1.00. The token cost of every AI action is reported transparently on your Billing & Usage page, so you can see precisely what was consumed and why.

For workflows and background jobs that run AI, there is a small flat compute charge in credits on top of the pass-through token cost. This covers the orchestration, retries, and infrastructure required to run the job reliably. So a billable AI workflow task is:

• Pass-through token cost (provider cost, no markup, at 100 credits = $1), plus
• A flat compute charge in credits (configurable; often small or zero for individual tasks).

Pure data operations (enrichment, prospect search, LinkedIn scrape, domain purchase) are billed at a flat rate instead, since they don't consume model tokens.

What does not consume credits

These are free and unlimited within your plan:

• Signing in, browsing the app, and viewing records, dashboards, and reports.
• CRM data syncs (HubSpot / Salesforce import and export) and any ongoing background sync.
• Webhooks, call-recorder transcript ingestion, and email / calendar sync.
• Out-of-the-box field processing on paid plans — processing your emails and transcripts to populate GTM Engine's built-in fields (health scoring, forecasting, deal gaps, MEDDIC-style sales-methodology scoring, tracking each contact involved, and the other standard fields) is included with your plan. See Included fields vs. custom fields below.
• Saving and editing reports, filters, fields, and settings.
• Adding seats and other billing or admin actions.
• Viewing existing AI output — only the original generation is charged, never re-viewing it.

What consumes credits

Flat rates are current defaults and can be adjusted, so treat them as planning estimates rather than contractual figures. Token-based actions (Genie, AI tasks) are billed at the provider's metered cost with no markup, plus any flat compute charge, and scale with the size of the prompt and response and the model used.

Example: a single Genie question

You ask Genie "show me open deals over $50k grouped by stage." Genie sends your prompt and CRM schema to the model and gets back a structured query. If that call costs roughly $0.03 of model spend, you are charged about 3 credits. Re-opening or re-running the resulting report does not cost anything more.

Example: a bulk enrichment workflow

You run a workflow over 200 contacts that enriches each contact's email. At ~30 credits per contact, that single run consumes about 6,000 credits. This is why bulk runs — not individual questions — are where credits add up fastest.

Included fields vs. custom fields

On paid plans, GTM Engine continuously processes your emails and transcripts to populate a set of out-of-the-box fields at no credit cost — this is included with your plan. If you ask GTM Engine to automatically track additional custom fields beyond that standard set, those custom field tasks consume credits the same way an ad-hoc AI workflow task does (pass-through token cost plus a flat compute charge).

This applies to ongoing processing and to one-time backfills. A targeted custom field backfill has a base charge of 10 credits per successfully processed record. The selected custom AI Prompt and/or Research field tasks can also create their own usage entries based on their pricing. Included system-default fields remain free on paid plans.

Historical record backfill during onboarding is a separate charge for processing existing CRM records after historical call transcripts are imported: 10 credits for every opportunity, contact, or account record enqueued. Transcript import itself does not consume credits. System-default field tasks remain included on paid plans, while any custom field tasks triggered for those records may consume additional credits.

Where credits add up fastest

The biggest spenders are bulk and background automations — bulk enrichment, bulk prospecting or enrollment jobs, and workflows that run AI tasks across many records. A single workflow run multiplied across hundreds of records consumes far more than individual Genie questions.

Getting credits

Credits arrive in a few ways:

• Monthly plan credits. Your plan includes a credit allotment that refreshes each billing period. These are granted automatically when your subscription invoice is paid, so a healthy paid subscription tops your balance back up every month. Enterprise annual contracts are different — those credits are granted upfront for the contract term rather than monthly.
• One-time credit packs. Admins can buy a credit pack at any time for a one-off top-up. The credits are added to your balance as soon as the purchase completes.
• Recurring credit-pack subscriptions. If you regularly need more than your plan includes, a credit pack can be set up as a recurring subscription so it's purchased and added on a schedule. Admins can cancel a recurring pack at any time.

Auto top-up

Admins can enable auto top-up and choose a credit pack. When your balance runs low, GTM Engine automatically purchases that pack so long-running automations and bulk jobs don't stall mid-run. Auto top-up is an admin-only setting and can be turned off at any time.

Running low or out

GTM Engine doesn't hard-stop the instant your balance hits zero. Billable work keeps running until you reach your organization's negative credit floor (default around −1,000 credits). Once you cross that floor, new billable tasks are blocked while free actions — signing in, browsing, viewing records and reports, CRM syncs — keep working normally. Topping up (or auto top-up) lifts the block immediately.

Separately, if a subscription payment fails, there's a short grace period (currently 7 days) before access begins to degrade. Resolving the payment under Settings → Organization → Billing & Usage restores full access. See Billing and plans for how plans, seats, and invoices work.

Guardrails

• Pre-flight balance check — billable workflows check your credit balance before billable tasks start.
• Negative floor — organizations can run to a configurable negative credit floor (default around −1,000 credits) before new billable work is blocked, so you can't silently blow far past your allotment.
• System-default field tasks are free — on paid plans, the built-in fields GTM Engine ships are processed at no credit cost (recorded for analytics only). Only custom fields your team configures consume credits. See Included fields vs. custom fields.

Monitor your usage

Admins and RevOps users can see the current credit balance and a usage breakdown under Settings → Organization → Billing & Usage. In Usage Detail, Historical record backfill shows the 10-credit per-enqueued-record onboarding charge, while Custom field backfill shows the 10-credit base charge per successfully processed record. AI Prompt and Research charges from selected custom field tasks appear as their own usage entries rather than being folded into one custom-backfill line item. Plan changes, credit-pack purchases, invoices, and billing portal access remain admin-only.

See also

• Tasks — the workflow steps that can consume credits.
• Build an outbound prospecting workflow — a bulk flow where credit usage is worth planning for.