Sign in

Audit Plus Implementation Offer

Pair the diagnosis with the cure in one engagement, with a decision gate between them so nothing is bought blind.

Free moderate Service Offers

What it adds

The builder combines your audit deliverables, implementation scopes, and past conversion patterns into a two-phase offer where findings lead directly into fixes, separated by an explicit go/no-go point. It converts by removing the awkward gap where buyers receive a report and never act, while the decision gate keeps the commitment feeling reversible.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inspect the past audit outputs and their follow-on implementation scopes in the source files, and identify which recommendations most consistently converted into implementation work. Those define phase two's likely contents.

  2. 2

    Present the offer as two clearly labeled phases with the decision gate rendered as a visible structural element between them, not as fine print.

  3. 3

    Specify phase one exactly as an audit: methodology, deliverable, and turnaround, with findings prioritized by expected impact and effort.

  4. 4

    Define the gate: what the buyer decides, what information they hold when deciding, how long they have, and the fact that stopping after phase one is a complete and acceptable outcome.

  5. 5

    Specify phase two as scoped implementation, and state how its scope is derived from phase one's findings, including how its price is determined — a stated range, a fixed fee per finding category, or a quote produced at the gate, based on what the source files support.

  6. 6

    Describe the fee relationship between the phases exactly as the source files show it — whether phase one's fee applies toward phase two, or whether they are priced independently — and invent nothing.

  7. 7

    Set layout expectations: on mobile show the two phases as sequential full-width sections with the decision gate as a distinct interstitial card and a sticky start-phase-one action; on tablet show phases side by side with the gate as a vertical divider element; on desktop render a horizontal two-phase flow with the gate as a central node and phase details expanding beneath the selected phase.

  8. 8

    Close with one action — start phase one — and state plainly beside it that phase two is decided later, not now.

Edge cases it handles

5

The things an agent skips when you only say "build a audit plus implementation offer".
  • The audit finds nothing significant enough to implement — state that this is a valid outcome and that phase two simply does not proceed.
  • Findings fall outside the provider's implementation capability — commit to saying so and to scoping only what can be delivered.
  • The buyer wants to implement only part of the findings — describe how partial scope is selected and priced at the gate.
  • The buyer wants to skip the audit and go straight to implementation — point to the standalone implementation offer with its prerequisite requirements.
  • Time passes between phases and conditions change — state any validity window on the phase-two scope.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Two labeled phases with a structurally visible decision gate are presented.
  • Stopping after phase one is explicitly framed as a complete, acceptable outcome.
  • Phase two's scoping and pricing method is stated, not left as "to be discussed."
  • Any fee-credit relationship between phases matches the source files exactly, with nothing invented.
  • Findings are described as prioritized by impact and effort.
  • Mobile sequential, tablet side-by-side, and desktop two-phase-flow layouts each render as specified.
  • The builder reports which source files informed the phase contents and pricing relationship, and lists unresolved assumptions.

Related offer files

How it works

  1. 1

    Copy the link

    Grab the Markdown blueprint URL for this offer type.

  2. 2

    Give it to your builder

    Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.

  3. 3

    It maps, then builds

    Your agent reads the blueprint first, then builds the offer into your app around the product, audience, and stack.

Works with your stack

These blueprints are written to adapt. They tell the agent to detect your framework, match your existing design system, and use your source files instead of guessing the offer.

Need it tighter than that? Customize the offer file and tell it exactly which source docs and stack to use.