Validate demand before you build
Put three candidates in front of real accounts and read the revenue behind each.
Ask “which should we build next?” with a Vote list of candidate features. Each vote carries the account and its MRR: revenue at stake before you commit.
Set it up
Put the candidates on a board
One request per candidate, each with a one-line summary of what it would do.
Settings → Boards
Make a short list
A Vote list with a title like “What should we build next?”, manual order, counts on. Keep it to three to five.
Settings → Vote lists → New list
Show it to signed-in accounts
Inline on your home screen or in onboarding. Signed in through SSO, each vote carries the account, plan and MRR.
<div data-theyasked-list="next-up"></div>Read it by revenue and segment
Rank by revenue at stake, filter to Source: Vote list, compare plans. Every figure is recomputed for the segment.
Insights → Demand
What you learn
- Revenue at stake
- The MRR behind each candidate, each account once.
- Unique accounts
- Breadth: twenty people from one customer are one account’s ask.
- Over-index
- “Enterprise wants this 2.9× more than everyone else.”
- Opportunity
- Demand, revenue, momentum and critical votes in one score, with the reasons shown.
Who it's for
- B2B product managers
- Before a quarterly planning meeting.
- Founders
- Before committing an engineer for a month.
- Pricing and packaging
- Which add-on would accounts pay for.