Sculptor
Sign inRegister

Roadmap: Horizons, dependencies, and release sequencing

By Sculptor team

Sequence ROAD-001 and IM-001 milestones with dependency and risk notes—for startup release planning and enterprise multi-quarter programs.

  • startup strategy
  • strategy pack
  • roadmap
  • ROAD-001
  • IM-001
  • milestones
  • dependencies
  • release planning

If you are building a company and feel lost about strategy roadmap milestones, you are not alone. This phase exists so your Strategy Pack stays honest—not pretty.

What this phase is really about

Roadmap sequences when initiatives land across horizons—now, next, later—with dependency clarity. It connects backlog and OKRs to calendar reality. Startups communicate runway-aware plans; enterprises align cross-team milestones before resourcing fights begin.

In Sculptor, RoadmapAgent keeps the conversation anchored to Roadmap so you do not mix this work with other phases. That separation is how consultants run engagements: one room, one decision set, one artefact pack.

Why teams skip this (and regret it later)

Spreadsheets with dates feel like roadmaps but hide dependencies. Skipping ROAD-001 pushes arguments into standups. Teams ship out of order and wonder why GTM and support were surprised.

Questions this phase must answer

  • What customer-visible milestone proves MVP first?
  • Which dependencies are external (partners, regulators, data)?
  • Where do we need parallel paths vs strict sequencing?
  • What scope moves if a milestone slips one quarter?
  • Which milestones unlock funding or sales motions?
  • How do horizons map to OBJ ids?
  • What kill criteria pause a horizon?
  • Who owns integration milestones between squads?

Deliverables you should leave with

Roadmap artefacts lay out horizons, milestones (IM ids), dependencies, and explicit risks—bridging OKRs to executable timing without pretending dates are guarantees.

  • ROAD-001 horizon map (now / next / later)
  • IM-001 dated milestones with owners
  • Dependency graph with critical path highlighted
  • Risk register hooks for /risks phase

What to prepare before you start

  • OKR set and backlog MVP boundaries
  • Known blackout dates (holidays, fiscal close)
  • Partner or vendor lead times

Who should own the answers

Product or program management owns the roadmap artifact; engineering validates dependencies; GTM marks launch-sensitive milestones. Sponsors arbitrate horizon shifts with explicit trade-offs.

How this connects to the rest of your pack

This phase sits in the Plan and commit group on the Strategy Pack journey.

Previous: Earlier phase

Next: Next phase

See the complete phase guide for all specialists.

Examples from the real world (names changed)

A fintech app tied IM-001 to partner certification, preventing a public launch date that compliance could not support.

A B2B SaaS vendor sequenced admin and SSO milestones before enterprise SKUs, saving sales from promising integrations that ROAD-001 flagged as Q3.

Use this in Sculptor tomorrow

  1. Open Sculptor and create or open a workspace project.
  2. In Chat, type /road or pick Roadmap from the command palette—the same rules apply as the slash.
  3. For breadth, start an Agentic Strategy Pack run; the phase executes in journey order and saves library assets.
  4. Read From specialist chat to a library-ready Strategy Pack for how chat and Agentic runs fit together.

Keyword focus: strategy roadmap milestones, Strategy Pack coach, startup strategy planning, AI strategy specialist.