Strategy & Planning

How to build a product roadmap as Chief of Staff and Founder's Office

Strategy & PlanningFor Chief of Staff and Founder's Office4 apps12 steps~24 min to set up

You're the person who turns 'we should have a roadmap' into an actual artifact that 12 different stakeholders will argue about in the next all-hands. Right now that means pulling feature requests out of Slack threads from six months ago, cross-referencing OKR progress from a Notion doc someone last updated in January, chasing engineering leads for effort estimates over Gmail, and then building a Google Slides deck that's already out of date by the time the CEO presents it. The roadmap isn't a product problem — it's a coordination and synthesis problem. And that coordination currently lives entirely in your head and your inbox.

Build this on Starch → See the apps used

Strategy & PlanningFor Chief of Staff and Founder's Office4 apps12 steps~24 min to set up

Outcome

What you'll set up

A living product roadmap dashboard that pulls initiative status from Notion, deal signals from HubSpot, and headcount constraints from your calendar data — updated automatically, not by you manually refreshing tabs

A meeting capture workflow that turns your roadmap planning sessions into structured action items, decision logs, and owner assignments without anyone playing scribe

A board-ready presentation built directly from your roadmap data, so the 'make it look like slides' step takes minutes, not Sunday night

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Knowledge Management Meeting Notes Task Manager Presentation Agent

Data sources & config

Starch syncs your Notion workspace and Google Calendar data on a schedule, so initiative docs and exec meeting history are always current. HubSpot is connected from Starch's integration catalog and queried live when the roadmap dashboard needs to surface deals waiting on product features. Slack is synced on a schedule for surfacing relevant threads during roadmap reviews. Gmail is synced on a schedule for pulling stakeholder feedback threads into the knowledge base. The Presentation Agent (currently in development — request beta access) builds slides from the live roadmap data when you're ready to go to the board.

Prompts to copy

Build me a product roadmap tracker that shows each initiative with status (not started / in progress / shipped), owning team, linked OKR, estimated quarter, and a confidence score from 1–5. Pull existing initiative names and owners from our Notion workspace and let me add new ones manually.

After each roadmap planning meeting, extract every decision made, every initiative that changed status, and every action item with the person responsible and deadline. Archive it with the meeting date and link it to the relevant initiative in the roadmap tracker.

Build me a weekly digest that summarizes roadmap changes since last Monday — what moved, what got deprioritized, what's newly blocked — and Slack it to me every Monday at 8am.

Create a 12-slide board update presentation showing our roadmap against Q3 OKRs, with an executive summary, a slide per product pillar, and a risks and dependencies section. Pull initiative statuses from the roadmap tracker.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Notion to Starch (scheduled sync) — Starch pulls your existing pages, databases, and initiative docs so the roadmap tracker starts pre-populated with what your team already wrote down, not a blank slate.

2 Connect Slack and Gmail (both scheduled sync) — Starch surfaces historical threads and email chains where feature requests, customer feedback, and exec decisions about roadmap priorities were made but never formally recorded.

3 Connect HubSpot from Starch's integration catalog — the agent queries it live to show which open deals are blocked waiting on specific product capabilities, so the roadmap isn't disconnected from revenue reality.

4 Install the Knowledge Management app from the App Store and tell Starch: 'Build me a product roadmap tracker that shows each initiative with status, owning team, linked OKR, estimated quarter, and a confidence score. Pull existing initiative names from Notion and let me add new rows.' Starch assembles the app from your connected data.

5 Add a second prompt layer: 'Flag any initiative marked In Progress that has no owner assigned or no target quarter set.' Now the tracker enforces basic hygiene without you auditing it row by row.

6 Install the Meeting Notes app and configure it for your recurring roadmap planning sessions — weekly with the product lead, monthly with the exec team. It transcribes, summarizes, and extracts action items automatically after each session.

7 Tell Starch: 'After each roadmap planning meeting, link every decision and status change back to the relevant initiative in the roadmap tracker.' Now your meeting history and your roadmap stay in sync without a manual reconciliation step.

8 Set up the weekly Slack digest automation: 'Every Monday at 8am, summarize what changed on the roadmap since last Monday — initiatives that moved status, new items added, items deprioritized — and post it to #chiefs-of-staff.' Anyone who needs to stay current can, without asking you.

9 Add a Task Manager app for your own roadmap-coordination to-dos: 'Remind me to collect Q3 effort estimates from engineering by the 15th of each month' or 'Flag this as P1 due Friday.' Keep your coordination work out of your email inbox.

10 When it's time for the board prep, prompt the Presentation Agent (beta): 'Build a 12-slide board update on our product roadmap against Q3 OKRs. Include an executive summary, one slide per product pillar, a shipped initiatives section, and a risks and dependencies slide.' It pulls from the live roadmap tracker — you're not rebuilding the deck from scratch.

11 Run a one-time synthesis prompt before each board cycle: 'Identify any initiative on the roadmap that was mentioned in an investor update in the last two quarters but isn't marked Shipped or In Progress — flag it with the date it was last committed to.' This is the check you currently do manually by rereading old investor memos.

12 Share a read-only view of the roadmap dashboard with the CEO, CPO, and any board members who want live visibility — they stop asking you for the latest version because there's only one version and it's always current.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Q3 2026 Roadmap Planning Cycle — June

Sample numbers from a real run

Initiatives tracked	34
Initiatives with no owner (flagged by Starch)	6
HubSpot deals blocked on product features	8
Action items extracted from June planning meetings	41
Hours saved vs. manual prep	9

It's the first week of June and you're running the Q3 roadmap planning cycle for a 150-person company with four product pillars. Historically this has taken you two weeks: two days pulling initiative status from Notion, one day chasing owners for updates over email, half a day reading back through Slack to find the decisions that never made it into a doc, and a full weekend building the board slides. This time, the roadmap tracker in Starch already shows all 34 active initiatives pulled from Notion, with statuses current as of this morning's sync. Starch flagged 6 initiatives with no assigned owner — you send one Slack message instead of auditing the whole list. It also surfaced 8 open HubSpot deals whose notes explicitly mention waiting on a product feature that maps to a Q3 initiative — you bring that list into the planning meeting with the CPO rather than making her look it up separately. The June planning sessions are captured by Meeting Notes: 41 action items extracted, each with an owner and due date, each linked back to the relevant initiative row in the tracker. By the time you sit down to build the board deck, the Presentation Agent has a live, accurate dataset to pull from. You describe the structure you want in one prompt and spend 45 minutes refining rather than 8 hours building. The CEO reviews it the day before the board call and it has current numbers — not the ones from two weeks ago when you first exported the spreadsheet.

Measurement

How you'll know it's working

% of roadmap initiatives with a named owner and target quarter (hygiene metric — Starch flags gaps automatically)

Number of open deals in HubSpot waiting on a specific product capability (shows roadmap-to-revenue alignment)

Time from planning session to distributed action items (target: same day, not three days later)

Roadmap accuracy rate: % of initiatives committed to in investor updates that shipped on schedule

Exec time spent in status-update meetings per month (proxy for whether the tracker is actually reducing sync overhead)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Notion + manual consolidation

Notion is where the docs live, but it has no way to query HubSpot deals, surface stale initiatives, or auto-generate a board presentation — you are still the connective tissue between every data source.

Linear or Jira for roadmapping

Strong for engineering ticket management but not designed for the exec-facing, cross-functional, narrative-plus-data artifact that a chief of staff actually needs to produce; board decks still get built in Slides separately.

Dedicated roadmap tools (Productboard, Roadmunk)

Purpose-built for product managers maintaining a single source of truth for features, but doesn't connect to your financial data, your calendar, your investor updates, or your board deck workflow — you still assemble everything by hand for exec audiences.

Manual deck + spreadsheet cycle

Total control over the output, zero setup cost — but it's 8–12 hours of your time every planning cycle, and the artifact is already stale the moment you export it.

On Starch RECOMMENDED

One platform — knowledge management, meeting notes, task manager all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

We keep our roadmap in Notion today. Does Starch replace Notion or sit on top of it?

Starch sits on top of it. Starch syncs your Notion workspace on a schedule — pages, databases, the works. Your team keeps working in Notion. Starch reads what's there and lets you build a roadmap tracker, digest automations, and board presentations on top of that data without asking anyone to change their workflow.

Our roadmap is tied to OKRs that live in a mix of Notion docs and a shared Google Sheet. Can Starch pull from both?

Notion syncs on a schedule directly. Google Sheets is reachable from Starch's integration catalog and queried live when your roadmap app needs the data. You describe the connection in plain language — 'pull OKR targets from this sheet and match them to initiatives by name' — and Starch handles the join.

What happens to roadmap history? If an initiative gets cut, can I see when and why?

Yes, with one caveat. Starch keeps a record of changes captured through meeting notes and automation logs, and the Knowledge Management app archives decisions. What Starch doesn't do is act as a long-horizon data warehouse — it's a live data surface, not a years-long audit trail. For most roadmap purposes (quarters, not decades) this is not a constraint.

The Presentation Agent and Task Manager are listed as in development. When can I use them?

Both are currently in development. You can request beta access on the Starch site to get notified when they launch. Everything else in this workflow — the roadmap tracker, meeting notes, weekly digest automations, and the knowledge base — is available today.

We use Linear for engineering tickets. Can the roadmap tracker pull status from Linear?

Linear is reachable from Starch's integration catalog, so the agent can query it live when your roadmap app runs. You'd describe what you want — 'show me the count of open Linear tickets tagged to each roadmap initiative' — and Starch builds the view. No API work required on your end.

Is Starch SOC 2 certified? Our board will ask.

Not yet — Starch is not SOC 2 Type II certified as of today. If that's a hard requirement for your security review, that's an honest constraint worth knowing now rather than after you've built on it.

How do I handle stakeholders who want to edit the roadmap directly rather than just view it?

You control who can prompt Starch to update records vs. who gets a read-only dashboard view. The most common setup for a chief of staff is: you and the CPO can edit; the CEO, board observers, and functional leads get a live read-only view. That way the roadmap has one owner (you) but full visibility across the org.