Sign in

Build Sprint

Ship a working, usable version of the thing in one concentrated build window, demonstrated live at the end.

Pro simple Service Offers

What it adds

From your technical specifications, past build logs, and demo recordings, the builder assembles an offer that produces functioning software or systems inside a compressed window, ending in a live demonstration and a handover. It converts because the deliverable is a working artifact rather than a document, and because the demo date is fixed before any money changes hands.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inspect the technical specifications and past build logs in the source files, and identify the smallest end-to-end slice that is genuinely usable rather than a collection of unfinished parts.

  2. 2

    Define the promise as a working artifact the buyer can operate themselves, and name what "working" means for it in observable terms.

  3. 3

    Publish the thin-slice principle explicitly: one complete path built to production quality, with the additional paths named as the next sprint rather than quietly implied to be included.

  4. 4

    Lay out the build week structure — environment setup, core build days, integration, hardening, and the demo — with a stated buyer touchpoint on each.

  5. 5

    Define the technical prerequisites the buyer must supply before day one: accounts, credentials, environments, data, and design assets, each with the format required.

  6. 6

    Describe the handover: repository or system access, deployment state, documentation, and what the buyer's team needs in order to continue independently after the sprint ends.

  7. 7

    Set layout expectations: on mobile show the build week as a day-by-day accordion with the demo day highlighted and a sticky prerequisite-check action; on tablet render the week as a horizontal five-column strip with the scope slice diagram below; on desktop show the slice diagram and the build week side by side with the handover contents fixed in a lower panel.

  8. 8

    Close with one action — reserve a build window — and state the prerequisite deadline as a number of days before the window opens.

Edge cases it handles

5

The things an agent skips when you only say "build a build sprint".
  • Prerequisites arrive late and consume build days — state the policy: the demo date holds, and scope reduces.
  • Integration with a third-party system fails outside the provider's control — define the fallback and how it is communicated.
  • The artifact works but the buyer expected more surface area — the thin-slice principle must be stated prominently enough to prevent this.
  • The buyer's environment cannot host the build — name the environment requirements as a prerequisite, not a discovery.
  • The buyer has no team to continue after handover — point to the maintenance or retainer path rather than extending the sprint informally.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • The thin-slice scope principle is stated explicitly and prominently.
  • "Working" is defined in observable, checkable terms.
  • A day-by-day build week structure with buyer touchpoints is published.
  • Technical prerequisites are listed with required formats and a deadline before the window.
  • Handover contents and post-sprint independence requirements are itemized.
  • Mobile accordion, tablet five-column strip, and desktop side-by-side layouts each render as specified.
  • The builder reports which source files were used to size the slice, and lists any technical assumption left unresolved.

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.