Skip to main content
Sample deliverable

This is what the Proposal Teardown Sprint actually gives the buyer.

Not a vague audit call. Not a generic strategy deck. A clear read on the live proposal motion, the biggest leaks, and what should change first if the goal is to recover close rate.

Use this page when someone asks what they really get for the $750 sprint before they decide whether to book it.

Example input

Business

Small design studio selling custom website and brand retainers

Current format

3-page PDF proposal sent after a discovery call

Current CTA

Reply if you want to move forward

Deal range

$6k-$18k custom projects

Turnaround

72 hours

Fast enough to keep a sales conversation moving instead of drifting into another week of indecision.

What comes back

Priority-ranked teardown with the clearest conversion leaks first

Annotated guidance on packaging, recommendation framing, and CTA order

A better send and next-step motion for the live proposal path

A final recommendation: leave it alone, run the conversion upgrade, or scope the bigger system

First-fix recommendations
Rewrite the proposal opening so the recommendation lands before the total cost.
Turn one flat quote into a clearer good / better / best package frame.
Replace the single reply CTA with action-specific next steps.
Refactor the send email so the proposal feels like a guided decision, not paperwork.

Sample findings

A teardown should make the first priorities painfully obvious.

Priority

P1

The buyer hits price before recommendation

What the teardown flags

The current PDF opens with scope and total cost, so the buyer has not yet been told which path is best or why it exists.

First fix

Lead with a short recommendation summary, then show the package ladder after the buyer understands the suggested path.

Priority

P1

There is no clear decision path

What the teardown flags

Reply-by-email leaves approval, revisions, questions, and scheduling bundled into one vague action.

First fix

Split the next move into a tighter CTA stack: approve, request changes, ask a question, or book the next call.

Priority

P2

The package ladder is hard to compare

What the teardown flags

Options are listed, but the buyer has to infer what is actually different and where the recommended value sits.

First fix

Use a comparison frame that makes the recommended tier visually and narratively easier to justify.

Priority

P2

Follow-up is still calendar-based

What the teardown flags

The proposal is sent, then the team guesses when to follow up because the delivery surface itself is not helping.

First fix

Tighten the send flow and next-step language so follow-up starts from clearer buyer behavior and stronger intent signals.

Best use for this page

Send this when someone wants proof of the deliverable, not just the idea.

This is the page that helps the teardown sprint feel tangible in outreach, follow-up, and referral chains. It answers the buyer's quiet question: what would I actually receive?

Send after the buyer says the idea sounds good but they are not ready for a bigger build yet.
Use in outreach when you want to show the $750 sprint is a real deliverable, not a fuzzy audit call.
Pair with the before-and-after page for conceptual proof and the ProJobCalc page for product proof.
Next step

If this preview feels useful, the actual sprint is the next move.

The point is speed and clarity: one current proposal in, one clear diagnosis out, and a better decision about whether to stop there or roll into the larger Proposal OS build.

FAQ

A few quick clarifiers.

Is this a real client teardown?

No. It is a realistic sample built to show the structure of the deliverable without relying on private client material.

Will every teardown look exactly like this?

No. The format is stable, but the findings and recommendations change based on the proposal, the sales motion, and the business model.

What should happen after the teardown?

Either the buyer implements the recommendations alone, or the teardown rolls into a Proposal Conversion Upgrade if the opportunity is strong enough.