Stop maintaining three versions of the same roadmap.
Your squad needs owners and status. Your director needs five bars and a quarter. Keep one roadmap, save a view for each, and change an item once: every view is current. Export any view as a sharp image for your slides.
Built for the product manager who maintains the roadmap alone, reshapes it for each audience, and needs it in a deck, not behind a login.
One set of items. As many views as you have audiences.
Table to maintain it, board to discuss it, timeline to present it. Every view reads the same items; nothing is copied between them.
| Name | Stage | Status |
|---|---|---|
Billing rework | Now | Doing |
Card payments | Now | Doing |
Invoicing | Next | To do |
Board approval | Now | To do |
Data migration | Next | At risk |
Discovery interviews | Now | Done |
Search relevance | Now | Doing |
Onboarding revamp | Next | To do |
Public launch | Later | To do |
Single sign-on | Next | To do |
Audit log export | Later | To do |
Partner API | Later | To do |
Hide what they don’t need. The data stays in the file.
Each view picks which fields it shows. Hidden fields stay in the file, so send the image, not the file, to anyone who shouldn’t see them.
| Name | Status | Owner | Area | Start | End |
|---|---|---|---|---|---|
Card payments | Doing | Rosa | Payments | Q3 2026 | Q3 2026 |
Instant payouts | To do | Rosa | Payments | Q4 2026 | Q4 2026 |
Single sign-on | Blocked | Dev | Identity | Q3 2026 | Q3 2026 |
Directory sync | To do | Dev | Identity | Q4 2026 | Q4 2026 |
Audit log | To do | Dev | Identity | Q1 2027 | Q1 2027 |
Usage dashboards | Doing | Kai | Reporting | Q3 2026 | Q3 2026 |
Scheduled exports | To do | Kai | Reporting | Q1 2027 | Q1 2027 |
Board review | To do | — | Reporting | Q4 2026 | — |
Change an item once and every view is current. What to show each audience, field by field.
Export at the size your slide actually is.
Pick PowerPoint 16:9 and you get a 4K PNG, 3840 × 2160, that fills the frame without cropping. It’s always drawn in the light theme, so it looks sharp on any projector.
- PNG
- SVG
- CSV
- Markdown
- JSON
- 4:3
- Document width
PowerPoint 16:9 · 3840 × 2160 PNG · fits the frame, nothing cropped
Your roadmap is a file you own.
One .roadmap.json file. Open it in any text editor, email it, keep it in version control.
{
"schemaVersion": 1,
"title": "Product roadmap",
"properties": [
{ "id": "stage", "label": "Stage", "type": "select",
"options": [{ "id": "now", "label": "Now", "color": "blue" }] }
],
"items": [
{ "id": "k3n8fq2p", "parentId": null,
"values": { "title": "Card payments", "stage": "now",
"start": "2026-01-01", "end": "2026-03-31" } }
],
"views": [{ "name": "All items", "type": "table" }]
}- No accountNo email, no login, no sign-up screen.
- Works offlineOnce loaded, the editor needs nothing from the network.
- Opens in any text editorPlain JSON with readable field names, so a diff makes sense.
The file format is published, so the file stays readable whether or not you keep using this editor.
Where to start
Field-by-field advice for each audience, 20 editable templates, and how RoadmapStar compares with other roadmap tools.
Who made this
I’m Ethan, a product manager in Singapore. I built RoadmapStar because I was tired of keeping a Confluence page and a PowerPoint slide in sync. It’s the tool I wanted: one roadmap, a view for each audience, and a clean image for the deck.
Questions or ideas? Get in touch.