Up to 70% off kits30% off services
Product Roadmap Template
Pick what you are building and what it needs. You get a week-by-week timeline from discovery to launch, with dates, and a Now, Next, Later roadmap filled with typical items you can edit, move and download. Nothing leaves your browser.
Launch in about
12 weeks
Launch timeline
Discovery and strategy
Weeks 1–2 ·2 wks
UX and UI design
Weeks 3–5 ·3 wks
Build
Weeks 6–11 ·6 wks
Test and launch
Week 12 ·1 wk
A planning estimate for one small team working in parallel. Mobile phases include app store review.
Roadmap: Now, Next, Later
Now: launch (5)
In version one. Built in the timeline above.
Next (3)
The first months after launch, once real users arrive.
Later (3)
Worth doing when usage proves it. Not promised.
Want a real plan with a fixed price?30% OFF
Our $1,680$2,400 Discovery Sprint turns this into a week-by-week launch plan: customer interviews, every feature scored, a clickable prototype tested with 5 people and one fixed build price, in two weeks.
How long does it take to build an app?
Typical timelines from first workshop to launch, for one small team that designs and builds in parallel:
| Product | Discovery | Design | Build | Launch | Total |
|---|---|---|---|---|---|
| Web app (SaaS, portal or dashboard) | 2 wks | 3 wks | 6 wks | 1 wk | 12 wks |
| Mobile app (iOS and Android) | 2 wks | 3 wks | 7 wks | 2 wks | 14 wks |
| Web app and mobile apps | 2 wks | 4 wks | 9 wks | 2 wks | 17 wks |
| Custom e-commerce store | 2 wks | 3 wks | 6 wks | 1 wk | 12 wks |
| AI feature in an existing product | 1 wk | 2 wks | 4 wks | 1 wk | 8 wks |
Each of these adds build time: subscriptions or marketplace payments (about 1 week), ai features (about 2 weeks), two or more integrations (crm, erp, data) (about 2 weeks), teams, roles and permissions (about 1 week).
What makes a good product roadmap
- It starts from a problem, not a feature list. Write down who it is for and why first; the free lean canvas template does this on one page.
- Version one is small. Rank features with the RICE score calculator and launch with the few that matter most.
- Only Now gets dates. Next and Later are an order, not a promise. Real users will change them.
- Design comes before build. A tested prototype is the cheapest place to change your mind.
- It gets revisited every month. A roadmap that never changes is not being used.
Frequently asked questions
Product roadmaps, app timelines and how to use the template.
A product roadmap is a plan of what a product will do and roughly when. A good one for a new product has two parts: a timeline to launch (discovery, design, build, testing) and a short list of what comes after, grouped as Now, Next and Later instead of promising exact dates for everything.
For a focused web product, about 12 weeks from the first workshop to launch: 2 weeks of discovery, 3 of design, 6 of build and 1 of testing and launch. A mobile app for iOS and Android usually takes 3 to 4 months, partly because of app store review. A web app plus mobile apps takes 4 to 5 months. Payments, AI features, integrations and team permissions each add time.
It is a planning estimate based on the timelines we see on typical projects, with one small, senior team working in parallel. Your real timeline depends on scope, how fast decisions get made and how much is already designed. A Discovery Sprint turns it into a week-by-week plan with a fixed price.
Because the order matters more than the date once you launch. Real usage changes what is worth building, so promising a date for a feature six months out sets a trap. Now is what ships in version one. Next is the first few months. Later is a list of bets you will revisit.
Yes. Download the CSV and open it in Excel, Google Sheets or Numbers. It includes every phase with its start and end date, and every roadmap item with its lane.
No. The template runs in your browser and nothing is stored or sent. Download or copy your roadmap before closing the tab.