Step 8 · Billing
Credits & estimates
Credits are honesty. Estimates are respect.
Heft meters background AI work — visibility checks, foundation harvest, scene compile — not a flat “per report” price.
Dry-run estimate
3 moments × 3 engines × P1–P3
~7,500
credits (planning range)
Contrast
Why teams switch
Without Heft
- ✕Opaque “AI tokens”
- ✕Surprise overages
- ✕Marketing promises a fixed per-check price
With Heft
- ✓Background AI metering with line items
- ✓Dry-run before checks and heavy harvests
- ✓Monthly pool first, boost last — in-app guide
In the app
What you do
- ✓See balance and credit log under project billing settings.
- ✓Read the in-app credits guide (/visibility/guides/credits).
- ✓Use dry-run estimates before starting checks or long foundation jobs.
- ✓Choose monthly plan + boost packs on the pricing page when usage is bursty.
/visibility/guides/credits
Visual proof
Screenshots & assets
Placeholders below — drop in product UI captures, workshop photos, or client-safe redactions.
Persuasion layer
Why this step closes deals
Every product page uses the same tactics we teach — specificity, contrast, proof, transparency, and shared language for brand and SEO.
Transparency
Debits when work completes — not when you save a textarea.
Control
Dry-run default — update estimate, then go live.
Objections
Straight answers
Is 200k credits enough?+
Depends on program cadence. Pricing page ranges are planning guides — your estimate is scope-specific.
What if we spike one month?+
Boost packs do not expire while active — built for bursty research waves.