Step 4 · Measure
Visibility checks
See the bill before the engines run.
Run live probes across AI engines — with a dry-run credit estimate before you commit.
Dry-run estimate
3 moments × 3 engines × P1–P3
~7,500
credits (planning range)
Contrast
Why teams switch
Without Heft
- ✕Surprise invoice after a “quick check”
- ✕Single engine theater
- ✕Mention-only victory laps
With Heft
- ✓Dry-run credit estimate (default on)
- ✓Multi-engine panel with variance exposed
- ✓P1 + P2 + P3 — mention, survive conversation, harvest gaps
In the app
What you do
- ✓Select buyer situations and engines from your charter.
- ✓Choose programs P1 (baseline), P2 (conversation), P3 (gap harvest) — typically all three for a full check.
- ✓Review the credit estimate (dry run on by default), then start the live harvest.
- ✓Track progress; open the report when the run completes.
/visibility/runs
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.
Loss aversion
Know credit gap to top-up before you start — not after.
Contrast
Recommend rate beside mention rate — footnote vs guide exposed.
Consistency
Same prompts, locked programs — comparable wave over wave.
Objections
Straight answers
How many credits is one check?+
Depends on moments × engines × programs. Use the estimate — we do not publish a single fixed number.
Can we test cheaply?+
Fixture replay for QA; live engines debit real credits.