Enablement sequence · 1 of 4
Diagnose the gap before you pitch the retainer
This page should help studios and developers structure a pre-sales audit that proves one thing clearly: launch created value, but launch did not finish the growth job.
Use this page when
You need to surface the growth gap clearly before discussing offer structure or pricing.
Core outcome
A client should leave understanding what launch solved, what remains, and why the next 90 days matter.
Do not use it for
Closing price, debating packages, or answering diligence questions before the gap is visible.
Fast audit summary
What should a good audit prove before you pitch the retainer?
The page works best when it does three things in order: honor what the launch achieved, show what it did not solve, and translate that gap into a believable next-quarter roadmap.
Protect trust
Acknowledge the project value first so recurring support does not sound like a reversal.
Show the unfinished work
Name discoverability, authority, corroboration, and reporting gaps in plain English.
Advance the sequence
Route into packaging next, not directly into pricing or objection handling.
What this page owns
How should this page surface the before-state cleanly?
This is the diagnosis page. It should help you show what launch solved, what it did not solve, and where ongoing support creates the next layer of value.
What it should not do
Why shouldn’t this page try to close pricing?
The audit creates urgency and clarity. Packaging and pricing happen next. If this page tries to jump ahead, the story gets muddy fast.
Best next move
What should happen after diagnosis is clear?
Once the gap is visible, the next page should explain how to package it for the specific buyer sitting across from you.
| Audit block | What to inspect | Why it matters commercially |
|---|---|---|
| What launch solved | Design, technical baseline, foundational structure, brand presence | Shows the build was valuable and creates trust for the next recommendation |
| What launch did not solve | Authority gaps, discoverability gaps, weak corroboration, thin reporting logic | Creates the bridge into recurring support without implying the original project failed |
| What the next 90 days could improve | Priority fixes, momentum plays, authority building, GEO readiness | Turns the audit into a believable monthly roadmap |
| What success would look like | Visible progress markers, proof checkpoints, reporting signals | Makes the recurring offer feel concrete instead of abstract |
Simple audit flow
How should you structure a repeatable pre-sales audit without sounding canned?
1. Confirm what is working
Start by protecting trust. Acknowledge where the build or launch already created value.
2. Show what still needs support
Point to the gaps a website alone does not solve: authority, visibility, corroboration, and momentum.
3. Translate that into a roadmap
Give the client a next-90-days lens so the offer sounds staged and believable.
4. Define what progress means
Name the metrics, proof points, and reporting signals the client can later recognize.
Next step
What should happen once the gap is visible?
The audit should create clarity. The next page should decide how to frame that clarity for different client types so the offer feels like the natural continuation of the project.
Audit FAQ
What else should a pre-sales audit answer before the offer gets packaged?
What should a pre-sales audit prove before you pitch recurring work?
It should prove what launch solved, what it did not solve, and why the next 90 days of recurring work are the logical continuation.
Why shouldn’t this page try to close pricing?
Because diagnosis creates urgency and clarity first. Packaging and pricing become easier to accept after the gap is visible.
What should happen after the diagnosis is clear?
Move into offer packaging for the specific buyer or run the live GEO audit if you still need sharper inputs.
Leave audit mode when
The gap is clear
Move into packaging if the client now needs the right story for their buyer type.
The conversation is post-launch
Use the handoff page if the website is already live and momentum is the issue.
You need raw inputs first
Use the live GEO audit when you still need sharper diagnostic inputs before packaging anything.