Sign in

Implementation Package

Install an already-approved plan into the buyer's business with a fixed scope, a fixed date, and no strategy detour.

Pro moderate Service Offers

What it adds

Working from the buyer's existing specifications, plans, or prior audit outputs, the builder creates an offer that executes a defined blueprint end to end and stops there. It converts by removing execution risk for buyers who already know what they want built: the deliverable is a working, verified system with a documented acceptance test rather than another round of recommendations.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inspect the specification and acceptance documents in the source files first, and determine what a complete, buildable input looks like — the exact artifacts a buyer must already have before this package can start.

  2. 2

    State the prerequisite gate near the top: this package executes an existing plan, and here is the checklist of what the buyer must already possess. Buyers without those artifacts should be pointed to the planning offer instead.

  3. 3

    Describe the build phases with concrete milestones and dates measured from the start date, ending in a verification milestone rather than a delivery milestone.

  4. 4

    Publish the acceptance test — the specific, checkable conditions under which the implementation is considered complete — drawn from the source files' acceptance checklist. This is the offer's proof mechanism and its scope boundary simultaneously.

  5. 5

    Define change handling: what happens when the plan turns out to be wrong mid-build, how change requests are priced, and what does not require a change request.

  6. 6

    State the pricing model as a fixed fee against the fixed specification, with the explicit note that scope changes are quoted separately, so the price is credible rather than optimistic.

  7. 7

    Apply layout rules: on mobile display milestones as a vertical progress list with the acceptance test in a collapsible panel and a sticky "check my prerequisites" action; on tablet show milestones and acceptance criteria side by side; on desktop render a horizontal milestone bar above a two-column detail region with acceptance criteria fixed in view while phases scroll.

  8. 8

    Provide one next action — submit the plan for a fit check — and describe what the buyer receives back from that check and how long it takes.

Edge cases it handles

5

The things an agent skips when you only say "build a implementation package".
  • The supplied plan is incomplete or internally contradictory — define the pre-build reconciliation step and whether it is billed.
  • Dependencies outside the provider's control block a milestone — state how the timeline shifts and who is notified.
  • The buyer requests strategy changes mid-build — route them through the named change process rather than absorbing them.
  • Acceptance criteria are subjective in the source files — rewrite them as observable conditions before publishing.
  • Access or credentials arrive late — tie the start date to access receipt, not to purchase date.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • A prerequisite checklist gates the offer above the primary action.
  • Milestones are dated relative to a defined start trigger, not to purchase.
  • A published, observable acceptance test defines completion.
  • The change-request process and its pricing treatment are stated.
  • The fixed-fee-against-fixed-spec logic is explained in plain language.
  • Mobile vertical list, tablet side-by-side, and desktop pinned-criteria layouts all behave as specified.
  • The builder reports which source files supplied the specification and acceptance conditions, and lists any requirement left unverified as an unresolved assumption.

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.