Your feature requests aren't a roadmap
Why a list of every customer ask isn't the same as knowing what to ship — and the 4 questions that close the gap.
Your feature requests aren't a roadmap
If you're a solo founder shipping a B2B SaaS, you almost certainly have a Notion doc, an Airtable, or a spreadsheet of every feature request a customer has ever made. Mine had 247 entries last time I counted.
You also, almost certainly, have not looked at it in two months.
The reason isn't laziness. The reason is that a list of feature requests is not a roadmap, and reading it linearly doesn't produce one. It produces guilt. The list reminds you of everyone you said "we'll consider that" to. It doesn't tell you what to do on Monday.
A roadmap is the answer to four questions. A list of feature requests answers zero of them.
The four questions a real roadmap answers
1. What's actually happening, by the numbers?
Your gut tells you "people want SSO." Your spreadsheet has 12 mentions of SSO and 28 mentions of CSV import. You should be building CSV import.
But you keep building SSO, because the last person who asked for it was on a sales call that almost closed and your brain weighted that conversation more than the previous 28 tickets it didn't read.
A roadmap starts with honest counts. Not "many users." Not "several customers." Twelve users. Twenty-eight users. With dates. With dollar values attached if you can join to Stripe.
2. Which signals are about retention vs. acquisition?
Not all feedback is equal. A churn-survey response is worth ~10 trial-signup gripes, because churn is revenue you've already won and lost. A sales-call ask is worth ~5 free-tier complaints, because sales-call asks come from people willing to pay.
Most founders apply this weighting accidentally and inconsistently. A real roadmap applies it explicitly:
- Critical: tied to revenue or retention. SOC2 blocker, churned-customer reason, sales-call dealbreaker.
- High: friction at the moment of value. Onboarding step that drops 30% of users. Feature missing that makes someone manually export data every day.
- Medium: nice-to-have that compounds. UI polish. A second-tier integration.
- Low: weak signal. One person said it once and you happen to remember it.
Most spreadsheets give every row equal visual weight. That's the bug.
3. What's the smallest thing I could ship that would meaningfully move the signal?
A real roadmap pairs each priority with an action, not a category. "Improve onboarding" is not an action. "Add a 3-step setup wizard with sample data" is an action.
This sounds obvious. But the failure mode is everywhere: open any indie founder's roadmap doc and 80% of the entries are nouns ("CSV import," "mobile app," "API"), not verbs.
Verbs force commitment. They expose the actual cost. "Add bulk CSV import for contacts up to 50K rows" is a 3-day project; "CSV import" sounds like an afternoon.
4. What am I not doing, and why?
The thing that separates roadmaps from idea lists is that roadmaps require omission. You can build A or B in the next two weeks, not both. The reason is always: B is more important because of [X].
If you can't articulate the X, you don't have a roadmap. You have a list of things you'd like to build someday.
What the gap looks like in practice
Here's the loop I was stuck in for most of 2025:
- Customer pings me on Intercom with a feature request.
- I respond ("good idea, we'll consider it") and add it to a Notion doc.
- Two weeks later, I pick what to build based on the most recent customer conversation I remember.
- Goto 1.
The Notion doc grew to 247 entries. I shipped maybe 15 of them.
The fix was not "be more disciplined." The fix was admitting that no one is going to read 247 entries with fresh eyes every Monday morning. Even an excellent founder.
The fix was synthesis: collapse the 247 entries into 6 themes, with honest counts, ranked by severity, with the smallest shippable action for each. That's a roadmap. It fits on one page. You can re-read it in 90 seconds. You actually look at it.
How Omentoo closes the gap
Omentoo does this loop for you. Paste your feature requests, churn survey responses, support tickets, or sales call notes. Get back the four answers above, structured:
- A one-line headline of the most important signal
- Themes with honest mention counts and severity ratings
- Quoted text from the source (not paraphrased)
- Prioritized actions (P1–P5) with effort and confidence estimates
- A watchlist of weak signals to track
The free demo on the home page runs once on whatever you paste. Pro runs continuously and emails you a fresh roadmap every Monday morning.
If your spreadsheet has been untouched for more than a month, that's the signal that the format isn't working — not that you need more discipline. Try the demo, paste a week of feedback, and see if the synthesis surfaces something you weren't already weighing.