Sign in

Roadmap Package

Sequence the next ninety days into a dependency-ordered plan your team can execute without you in the room.

Pro involved Service Offers

What it adds

The builder draws on your planning documents, prioritization frameworks, and past roadmaps to produce an offer whose deliverable is an ordered, dependency-aware execution plan with owners, estimates, and decision points. It converts by selling sequence over ideas — buyers rarely lack initiatives, they lack the confidence to know what comes first and what must wait.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Open the past roadmaps and prioritization worksheets in the source files, and extract the criteria used to rank initiatives and the way dependencies were represented. This becomes the offer's methodology.

  2. 2

    Frame the promise around the decision the buyer keeps deferring: what to do first, what to do next, and what to consciously not do this quarter.

  3. 3

    Publish the prioritization criteria openly — the factors weighed and how they trade off — so the roadmap reads as a defensible method rather than an opinion.

  4. 4

    Describe the roadmap artifact in detail: time horizon, granularity of each item, whether each carries an owner, an estimate, a dependency link, and a defined completion signal.

  5. 5

    Include a decision-point layer — the moments in the sequence where results determine which branch is taken next — since a roadmap without branch logic becomes obsolete on contact with reality.

  6. 6

    Define the discovery inputs required to produce it: which stakeholders are interviewed, what documents are reviewed, and how long that phase takes before the roadmap is drafted.

  7. 7

    Handle layout: on mobile show the roadmap sample as a vertical phase list with dependencies indicated by inline labels and a sticky booking bar; on tablet render a compressed two-track timeline; on desktop present a horizontal multi-track timeline with dependency connectors and a side panel detailing the selected item.

  8. 8

    Close with a single action — book the roadmap engagement — and state the total elapsed time from kickoff to delivered roadmap.

Edge cases it handles

5

The things an agent skips when you only say "build a roadmap package".
  • Stakeholders disagree on priorities — describe how the criteria are agreed before sequencing begins, so the roadmap arbitrates rather than the provider.
  • The buyer's capacity is unknown — state that the roadmap is sequenced against a declared capacity and that the declaration is required input.
  • Conditions change and the sequence breaks — describe the built-in review cadence or re-sequencing trigger.
  • The roadmap concludes that a current initiative should stop — state that removal recommendations are part of the deliverable.
  • The buyer wants the provider to execute the roadmap — name the separate execution engagement without bundling it here.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • Prioritization criteria are published, not implied.
  • Each roadmap item is specified as carrying owner, estimate, dependency, and completion signal.
  • Decision points with branch logic are part of the described artifact.
  • Discovery inputs, stakeholders, and phase duration are all stated.
  • Total elapsed time from kickoff to delivery is stated and grounded in past engagements.
  • Mobile vertical list, tablet two-track, and desktop multi-track timeline layouts are all implemented.
  • The builder reports which source files supplied the prioritization criteria and artifact structure, 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.