A hand-raiser is a lead who asks for a sales conversation directly. The request can be a demo form, a pricing page inquiry, a contact-sales submission, or a reply to an email asking to talk. What defines the category is that the buyer stated intent instead of a model inferring it from behavior.
Why the category deserves its own field
Scoring models exist because most leads never say what they want. Hand-raisers already said it, so putting them through the same accumulation logic wastes the only clear signal in the funnel. Create an explicit flag at lead creation, set by the form or channel that produced the request, and make that flag independent of the lead score. Routing, service levels, and reporting all key off that flag afterward.
Route on minutes
The value of a hand-raiser decays fast, because a buyer who requested a demo is usually requesting demos from several vendors in the same session. Route these records instantly to a named owner with a response commitment measured in minutes, and page a backup when the owner does not respond. Every routing rule that adds a queue, an enrichment wait, or an overnight batch job spends the advantage the request created.
Track the volume separately in the plan
Hand-raiser volume behaves differently from total lead volume. It tracks active demand in the market, so it moves with buying conditions rather than with content output. A month where total leads rise and hand-raisers fall usually means the content program is reaching people earlier in their process, which changes the timing of the pipeline it produces. Keep the two series apart and forecast them apart. Hand-raiser counts multiplied by their own create rate and average deal size give a much tighter estimate of near-term pipeline than a blended lead number does, and they carry a materially different win rate that belongs in the model explicitly.
Where the count gets corrupted
Two things break the series. Consolidating a demo form into a general contact form erases the distinction in the data, and no downstream analysis can recover it. Automated submissions add records that inflate volume without adding buyers, which is why the raw form count should be filtered before it feeds any planning number. Keep a dedicated request path, filter non-human submissions, and the hand-raiser series stays usable as an input to the sales forecast quarter after quarter.
Frequently Asked Questions
How is a hand-raiser different from an MQL?
An MQL is a model's inference that someone is ready. A hand-raiser is the buyer stating it. The distinction matters for routing, because a scoring model tolerates a delay while a demo request does not. Split the two in reporting and compare their conversion rates directly, since a blended lead-to-opportunity rate averages a stated request together with an inferred one.
Should hand-raisers go through lead scoring at all?
Run them through fit checks, not readiness scoring. A demo request from an account outside the addressable market still needs to be filtered. What should never happen is a hand-raiser sitting in a nurture track because a scoring model has not accumulated enough points to release it.
What ruins hand-raiser counts?
Form consolidation and automated submissions. When a company merges its demo request form into a general contact form, hand-raisers stop being identifiable in the data and the historical series breaks. Automated form fills inflate the count with records no human submitted, so filter them before the number reaches a forecast.
Can hand-raiser volume be forecast?
Yes, and it is one of the more stable demand series because it tracks active buying interest rather than content consumption. Build it from trailing volume adjusted for seasonality and any change in traffic to the pages that carry the request forms, then hold it separate from total lead volume in the plan.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like hand-raiser lead into prescriptive action for your team.
Schedule a Demo