Back to GrowthDex
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.

rare tacticfree budget

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.

Company 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 and metric

Source: Canny Case Study: hapily

hapily's board had 340+ votes after its first year on Canny, and the team explicitly requires prospect votes during feature-led deals.

Source discovered: May 29, 2026

SalesProductCustomer Successsales assistfeature requestspipeline qualityb2b
GrowthDex operator note

When to use it

Use this when Sales, Product, Customer Success is relevant to sales assist, feature requests, pipeline quality and you can run a bounded test with a free budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

Founder checklist

  1. Read Canny Case Study: hapily and identify what is directly supported.
  2. Choose one channel context: Sales, Product, Customer Success.
  3. Define the test around hapily's board had 340+ votes after its first year on Canny, and the team explicitly requires prospect votes during feature-led deals..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Referral and Retention GrowthSalesProductCustomer Success

Related tactics

Segment-filtered voter list with opportunity value

Filter voters by segment and pair the request with open opportunities so the team can tell who wants the feature and what revenue is tied to it.

rareProduct, Sales, Customer Success

Trial feedback board with frontline teams before full rollout

Pilot the feedback system with the teams closest to customers first so the workflow proves itself before the whole company is asked to trust it.

rareProduct, Customer Success, Sales

Customer page sorted by important and in-progress work

Use the customer page as a live account view that groups important and in-progress requests, so the team can see what matters to that customer without rebuilding the story in a slide deck.

uncommonProduct, Customer Success, Sales

Canny renewal date and account owner view before roadmap promise

Review request clusters by renewal date and account owner before making roadmap promises that ignore who has to save the account.

rareProduct, Customer Success, Sales

Customer email-domain auto-mapping for feedback identity

Map incoming support requests to the right customer record by email domain so product sees account context without a cleanup pass.

rareSupport, Product, Customer Success

Customer requests report by company spend and renewal risk

Review requests in a company-level report that includes spend, renewal risk, and opportunity value instead of treating every vote like the same customer.

rareProduct, Customer Success, Sales
Advisory bridge

Apply this with an operator

Connect activation, customer value, retention, and referral into one measurable loop.

Work with Ian