# Prospect vote required before feature promise

> Make sales attach the prospect as a voter on the request before the team starts feature-promise discussions.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/prospect-vote-required-before-feature-promise/
- Source: [canny.io](https://canny.io/case-studies/hapily)
- GrowthDex source hub: [Canny Case Study: hapily](/sources/canny-case-study-hapily-canny-io/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: free
- Channels: Sales, Product, Customer Success
- Stages: sales assist, feature requests, pipeline quality, b2b


## Why this can grow

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

1. Define one narrow startup segment where prospect vote required before feature promise can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Sales and Product channel.
3. Use the evidence from canny.io to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. 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.

## Adjacent tactics in the same lane

- [Canny seed known requests before opening the board](/growth-ideas/canny-seed-known-requests-before-opening-the-board/) - same source, 1 shared channel
- [Trial feedback board with frontline teams before full rollout](/growth-ideas/trial-feedback-board-with-frontline-teams-before-full-rollout/) - 3 shared channels, 1 shared stage
- [Segment-filtered voter list with opportunity value](/growth-ideas/segment-filtered-voter-list-with-opportunity-value/) - 3 shared channels, 1 shared stage
- [Customer page sorted by important and in-progress work](/growth-ideas/customer-page-sorted-by-important-and-in-progress-work/) - 3 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The feedback queue should carry revenue before volume](/blog/the-feedback-queue-should-carry-revenue-before-volume/) - product ops, feedback systems, revenue prioritization

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.