How do you build a product roadmap from goals?

Start with the outcomes you want, group the work into a few themes that serve them, then sequence the themes by what delivers the most value soonest. A roadmap is not a list of features with dates — it is a short story about what you are chasing and in what order.

Can AI write a product roadmap?

AI can draft a strong first version. Give it your goals, the themes you are considering, and your constraints, and it will group the work, propose an order, and flag dependencies. You still make the calls on priority and timing — the AI organizes, you decide.

Should a roadmap have dates?

Prefer order over exact dates. Now, next, and later beats a Gantt chart of promises you cannot keep. Use rough horizons — this quarter, next quarter — and let the sequence carry the plan. Hard dates are for launches, not for the whole roadmap.

Product roadmap prompt (copy-paste, from goals to plan)

A free, copy-paste product roadmap prompt that turns your goals and themes into a clear, honest roadmap — paste it into a sfora post or hand it to your agent.

Here is a copy-paste product roadmap prompt you can use right now. Paste it into a sfora post, or hand it to your AI agent, give it your goals and a few themes, and you get back a clear roadmap — grouped into now, next, and later, with the reasoning behind the order. The output is a markdown file on your board, not a slide you screenshot and lose.

This is one of the prompts in our AI prompts guide. Once the roadmap points you at the next thing to build, draft its spec with the PRD prompt and break it down with the user story prompt. For the background on writing product docs with AI, see the AI PRDs guide.

The prompt

Copy this block, paste it where you draft, and replace the bracketed parts.

Product roadmap prompt

You are helping me draft a product roadmap. I want a plan organized by outcome
and order, not a list of features with fake deadlines.

Here is what I have:

- **Goals:** <the outcomes we want, e.g. "grow weekly active teams," "cut churn">
- **Themes:** <the big areas of work we are considering>
- **Constraints:** <team size, deadlines, tech limits, anything that shapes order>
- **What we already know we're doing:** <anything already committed>

Write the roadmap with this shape:

1. **The bet** — one paragraph: the single most important outcome this roadmap
   chases and why.
2. **Now** — the 2–4 things we start on immediately. For each: the theme, the goal
   it serves, and why it comes first.
3. **Next** — the work that follows, and what has to be true before we start it
   (dependencies).
4. **Later** — bigger or less certain bets we are naming but not committing to.
5. **Not now** — things we are explicitly choosing not to do, and why. This
   section matters most.

Rules:
- Order by what delivers the most value soonest, not by what is easiest.
- Use horizons (this quarter / next quarter), not exact dates, unless I gave you a
  hard launch date.
- Tie every item to a goal. If something serves no goal, flag it.
- Do not pad the roadmap. A short, honest plan beats a long wish list.
- If two items compete for the same slot, say so and recommend one.

Run it:paste into a sfora postorhand it to your agent · CLI + MCP

Running it in sfora

You do not have to leave your workspace to use this. In sfora, a post is a markdown file, so the roadmap lives in the same place as the work it plans.

There are two ways to run it:

Paste it into a post. Open a new post, paste the block, fill in your goals and themes, and hand it to the agent in that thread. It replies with the drafted roadmap, right there.
Hand it to your agent over the CLI. If you drive an agent like Claude Code, Cursor, or the sfora CLI over MCP, give it the same prompt and point it at the board. It writes the roadmap as a file you can open, edit, and share.

Either way, the result is a real markdown roadmap on your board — one a person can edit and revisit as things change, not a static slide that goes stale the day you make it.

What the output looks like

Feed the prompt a couple of goals and themes, and you get back something like this:

# Roadmap: H2 — grow weekly active teams

## The bet

Teams that invite a second and third member stick around; solo trials churn. So
the whole roadmap points at one thing: get more teams past the "three active
members" line in their first two weeks.

## Now (this quarter)

- **Faster onboarding** — theme: activation. Serves "grow weekly active teams."
  First because nothing else matters if new teams stall on day one.
- **Invite flow rework** — theme: activation. The single biggest drop-off is at
  invites; fixing it feeds every other goal.

## Next

- **Shared templates** — helps a new team fill their board fast. Depends on the
  onboarding rework landing first, so the template shows up at the right moment.

## Later

- **Team analytics dashboard** — useful, but it serves retention, not activation.
  Named, not committed.

## Not now

- **Custom themes / white-label.** Real requests, but they serve no current goal
  and would eat the quarter. Revisit when activation is solved.

Notice the discipline: one clear bet, a short Now list tied to the goal, honest dependencies in Next, and a Not now section that says out loud what is being left on the floor. That last section is where roadmaps usually go soft, and it is the one the prompt refuses to skip.

Now, next, later beats dates

The prompt pushes you toward horizons instead of hard dates on purpose. A roadmap full of specific deadlines is a roadmap full of promises you will break, and every broken date costs trust. Order carries the plan better than dates do:

Now is what you are actually working on. Keep it short.
Next is what you have decided but not started — with the dependencies named, so nobody starts it too early.
Later is honest about uncertainty. Naming a bet is not the same as committing to it.
Not now protects the plan. Every "not now" is a fight you do not have to have when someone asks why their pet feature slipped.

Save hard dates for launches, where the date is the point. For the plan itself, sequence beats schedule.

How to get a sharper roadmap

The roadmap is only as good as the goals you feed it. To get more from the prompt:

Give real goals, not themes disguised as goals. "Grow weekly active teams" is a goal. "Improve onboarding" is a theme — it serves a goal but is not one. Name both and the AI can tie work to outcomes.
List your constraints. Team size and deadlines change the order more than anything. Leave them out and you get a roadmap for a team you do not have.
Say what is already committed. The AI should plan around your fixed points, not pretend the slate is blank.

Where sfora fits

sfora is a project workspace where humans and AI agents are members of the same team, and everything — tasks, docs, posts — is a markdown file. That is what makes this prompt more than a chat trick.

When you run the roadmap prompt in sfora, the plan is a real file on your board. A person edits it as priorities shift; an agent that is a member of the same workspace can read it, understand what comes next, and pick up the tasks that flow from it. The roadmap is not a slide that drifts out of date — it lives next to the work, so the plan and the doing stay in the same place.

Once the roadmap tells you what to build next, draft its spec with the PRD prompt, break it into work with the user story prompt, and browse the full set in the AI prompts guide.