For founders
Decide which customer requests belong on your roadmap.
Early on, every request sounds urgent because it comes from someone you cannot afford to lose. Helpful BoB keeps the feedback together so you can see whether one prospect is asking or several customers are.
BoB organises and helps you assess. You decide what your small team builds next.
- 01
One prospect or a repeated need
Group similar comments and see how many companies raised the same problem before you commit engineering time to it.
- 02
Work from actual feedback
Add what customers said in their own words, or connect a Slack channel, so the roadmap argument is not decided from memory.
- 03
Reasons to say yes or wait
Each theme comes with arguments for acting now and arguments against, so a 'not yet' has something behind it.
Example
One prospect asked. Four customers described something else.
Read how it works, or use our guide to saying no to feature requests.
- Customer request
- “We would need per-user notification settings before we sign.” Raised by a prospect on a sales call.
- What the feedback shows
- Four existing customers describe the same underlying problem: routine email hides the updates they need. Only the prospect asked for per-user switches.
- What the team could do
- Consider a daily digest with quieter defaults, which may address the four existing customers, and tell the prospect what is being assessed rather than promising a date.
Start with the request from your last sales call.
Add it alongside your existing feedback and see what it connects to.