Growth idea action plan
Prospect vote required before feature promise
Make sales attach the prospect as a voter on the request before the team starts feature-promise discussions.
Why this can grow a startup
A lot of feature-selling goes wrong because the request gets discussed long before the buyer is attached to a visible record. hapily made the sales motion stricter: if a prospect asks for a feature, the rep adds that person as a voter on the idea before the conversation continues. That rule improves more than tracking. It introduces the buyer to the request forum, shows shipped and planned work in context, and forces the sales team to ground the promise in a live thread rather than in hallway memory. The result is a cleaner signal for product and a better look for the buyer.
Ian's take
From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.
Action plan
- Define one narrow startup segment where prospect vote required before feature promise can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Sales and Product channel.
- Use the evidence from canny.io to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
Source-backed example
hapily requires reps to add a prospect as a voter on an idea during a sales deal before continuing the feature conversation, so the buyer can see what has shipped, what is planned, and how the team responds.
Source: Canny Case Study: hapily (canny.io)
GrowthDex source hub: Canny Case Study: hapily
Last checked: 2026-05-29
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Canny seed known requests before opening the board same source · 1 shared channel
- Trial feedback board with frontline teams before full rollout 3 shared channels · 1 shared stage
- Segment-filtered voter list with opportunity value 3 shared channels · 1 shared stage
- Customer page sorted by important and in-progress work 3 shared channels
Related GrowthDex essays
- The feedback queue should carry revenue before volume product ops, feedback systems, revenue prioritization
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory