Sign in

Optimization Retainer

Compound small monthly gains on an asset you already own, with every change measured and every result reported.

Pro simple Service Offers

What it adds

The builder uses your test records, analytics history, and reporting templates to define an ongoing engagement focused on iterative improvement of an existing asset rather than new construction. It converts by selling accumulation: a defined monthly test cadence with measured outcomes, where the reporting itself becomes the proof that justifies renewal.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Read the past test records and change logs in the source files, and calculate how many meaningful changes were shipped and measured per month. That throughput sets the cadence this offer may promise.

  2. 2

    State the promise as ongoing measured improvement of a named asset, explicitly excluding new builds so the boundary against project work is clear from the first sentence.

  3. 3

    Publish the monthly loop: how opportunities are identified, how changes are prioritized, how many are shipped, how each is measured, and when results are reported.

  4. 4

    Describe the measurement standard — what counts as a result, the minimum observation period, and how inconclusive outcomes are recorded — because credibility here rests on admitting what did not work.

  5. 5

    Define the reporting artifact in detail: its sections, its cadence, and the fact that it records both improvements and inconclusive tests, with no claimed figures invented for the page.

  6. 6

    Explain pricing as a monthly fee for a sustained cadence, and note that results compound across months while any single month's outcome is not promised.

  7. 7

    Handle layout: on mobile present the monthly loop as a circular-stage list rendered vertically with a sticky monthly-fee action; on tablet show the loop beside the reporting sample in two columns; on desktop render the loop as a horizontal cycle diagram with a live-scrolling reporting sample panel to its right.

  8. 8

    Close with one action — start the first cycle — and state the minimum number of cycles needed before results are meaningfully readable, drawn from the source files.

Edge cases it handles

5

The things an agent skips when you only say "build a optimization retainer".
  • The asset has insufficient traffic or volume for reliable measurement — state the qualification threshold and recommend a different engagement below it.
  • A month's tests all return inconclusive results — describe how that month is reported and what the buyer receives.
  • The buyer changes the asset independently and contaminates measurement — define the change-coordination requirement.
  • Improvement plateaus after early gains — state honestly that gains diminish and describe how the focus shifts.
  • The buyer wants a redesign rather than optimization — direct them to the build engagement rather than reshaping this one.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • The offer explicitly excludes new builds and names the asset being optimized.
  • Monthly throughput is stated and grounded in real change-log history.
  • The measurement standard including minimum observation period is published.
  • The reporting artifact is described as recording inconclusive results as well as improvements.
  • No performance figures appear unless they exist in the source files.
  • Mobile vertical loop, tablet two-column, and desktop cycle-diagram layouts each function as described.
  • The builder reports which source files set the cadence and qualification thresholds, 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.