Refolk
FrameworkSales and go-to-market

The Inbound Hand-Raiser Verdict: Route, Nurture, or Disqualify

You can enrich a raw demo-request form fill from public signals, score fit and intent separately, and return a logged route, nurture, or disqualify verdict inside five minutes.

4 min readLast reviewed October 9, 2026Read as Markdown

Key takeaways

  • Responding to a demo request within 5 minutes makes you 21x more likely to qualify the lead than waiting 30, yet the median B2B response time is 42 hours and only 7% of companies hit 5 minutes.
  • About 30-40% of demo requests in B2B SaaS come from outside the ICP, so a form fill is not an auto-SQL - score fit and intent before you expose a calendar.
  • Score fit and intent as separate numbers and gate on both: a typical route-to-sales rule requires 30+ fit AND 25+ intent, which stops a high-intent competitor from flooding reps.
  • On free email, flag and enrich from the typed company name rather than hard-block, because a dropped gmail buyer never shows up in any report.
  • Refolk's index holds 47,206 US SDR/BDRs against only 1,449 RevOps builders, a 32.6x gap, which is why the scarce resource is the operator and the one unforgivable failure is un-auditable routing.
  • Ban 'bad lead' and 'no response' as reason codes so disqualification becomes a dataset marketing can act on instead of an argument.

A demo request just landed. You have a name, an email, and a company domain, and almost nothing else. This guide is for founders handling their own inbound, account executives, SDR leads, and partnerships teams who have to decide what to do with that form fill before the intent cools. It gives you a repeatable verdict - route to a rep, hold in nurture, or disqualify - that you can defend and log, built around enriching the lead from public signals fast enough to grade it.

Most published guidance stops at "use BANT" and hands you a generic scoring table. That advice assumes a sourced prospect with a full record. It does not fit the inbound hand-raiser, who arrives unbidden with three fields and a clock running. The move here is to treat the bare form fill as a search problem: enrich the person and the company from public signals inside the speed-to-lead window, then score and route.

Why the clock is a research budget, not a reflex

The five-minute window is not a nicety. It is a research budget. Responding to a lead within five minutes makes you 21x more likely to qualify it than waiting 30 minutes, per the MIT/InsideSales Lead Response Management Study, and an HBR audit of 15,000 leads and 100,000 call attempts found qualifying odds drop 400% between 5 and 10 minutes.

So the obvious reading is "respond faster." The subtler reading is the one this guide is built on: the window is long enough to enrich and gate a lead, and short enough that you cannot do it by hand. You spend those minutes on machine work - validate, enrich, score, route - and keep the human for the conversation that follows.

21x
How much more likely a 5-minute response qualifies a lead versus 30 minutes
From the MIT/InsideSales Lead Response Management Study; the same study shows qualifying odds fall 21x and contact odds 100x between 5 and 30 minutes.

The gap between what works and what happens is enormous. The median B2B lead response time is 42 hours, and only 7% of B2B companies consistently respond within five minutes. The practice is rare because it requires the routing to be automated end to end. Momentive cut its speed-to-lead from 20 minutes to 60 seconds by fixing the data foundation under its routing rules, not by telling reps to hurry.

The second reason you cannot skip qualification inside that window: about 30-40% of demo requests in most B2B SaaS funnels come from outside the ICP. That band is a single practitioner source, so treat it as directional rather than an established benchmark, but the direction is the point. A meaningful share of hand-raisers are students, job-seekers, competitors, and researchers. Book every one of them and you have handed your reps a calendar full of noise.

The two things you can enrich and the four you must ask

You can resolve most of a fit score from the email domain alone. What you cannot resolve is intent-of-purchase and the BANT facts - those you ask. Knowing which is which is what lets you run a three-field form and still score the lead properly.

There are two core enrichment layers, both keyed off the business email domain: company fields and contact fields. The must-ask set is budget, authority, timeline, and specific need - the BANT discovery that no public signal reliably reveals.

FieldSourceLatency target
Industry, employee count, revenue, HQ, tech stackEnrich from domainreal-time / 2-5 min
Job title, seniority, verified work emailEnrich from domainreal-time / 2-5 min
Budget, authority, timeline, specific needAsk (form/discovery)at submit / on call

This split is also the argument for short forms. Form conversion more than triples as you cut fields: 23.1% on a three-field form, 11.4% at seven fields, and 6.9% once you pass ten. Every field you can enrich instead of ask is a field you remove from the form, and every field you remove lifts conversion. The short form is not a UX preference. It is the enrichment thesis made concrete.

Latency is the constraint that makes this honest. Use real-time enrichment for inbound, because a 14-day enrichment lag means routing decisions get made on stale data. Target 2 to 5 minutes. If the provider returns nothing - which happens often for new startups that lack public records - flag the record for manual review rather than disqualifying it.

The short form is not a UX preference. It is the enrichment thesis made concrete.

Questions practitioners ask

How fast do I actually have to respond to a demo request?

Inside five minutes if you want the lead to matter. The MIT/InsideSales Lead Response Management Study found that responding within five minutes makes you 21x more likely to qualify a lead than waiting 30 minutes, and an HBR audit of 15,000 leads found qualifying odds drop 400% between 5 and 10 minutes. That window is your whole budget for enrichment and scoring, so automate the capture, validation, and routing rather than relying on a human to notice.

Should I book the meeting as soon as someone requests a demo?

No. About 30-40% of demo requests in B2B SaaS funnels come from people outside the ICP, including students, job-seekers, and competitors. Score fit before you expose a calendar. Enrich from the domain, run hard knockouts, and gate on fit and intent, then offer instant booking only to leads that clear the bar. Treating every form fill as an auto-SQL puts unqualified meetings on your reps' calendars.

Can I just block free email domains like gmail?

Block disposable and invalid addresses, but flag personal domains rather than blocking them. A real buyer who types a gmail address gets silently dropped by a hard block, and that loss never appears in any report. The better default is to accept the signup, tag email_type as personal, and try to find the work address from the person's name and the company they typed in, then enrich and score from there.

What fields can I enrich versus what must I ask?

Firmographics (industry, employee count, revenue band, HQ, tech stack) and contact fields (title, seniority, verified work email) resolve from the business email domain in real time. Budget, authority, timeline, and specific need are BANT fields that generally must be asked on the form or in discovery. This split is why short forms win: form conversion more than triples from 6.9% at 10-plus fields to 23.1% at three fields, so collect name and email and enrich the rest.

What's the route-to-sales threshold?

No single industry standard exists, but practitioner models converge on a Fit plus Intent gate. A common rule routes leads scoring 80-100 to a rep immediately, holds 60-79 in nurture, and requires both sub-scores above threshold - typically 30+ fit AND 25+ intent - before any immediate sales routing. Gating on both numbers, not the combined total, is what stops a high-intent competitor or researcher from clearing the bar on activity alone.

What should I log on a disqualified lead?

At minimum, the rule that assigned it, the timestamp, and a reason code drawn from a short defined list such as company size, geography, or email type. Ban 'bad lead' and 'no response' as codes - they make rejection unauditable and turn it into an argument between sales and marketing. Clean codes turn your 30-40% ICP miss into a monthly dataset that improves your form rules and ICP definition.

Try it on the search you came here for

Stop building boolean strings. Just describe the person.

Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.

  1. 01Describe them

    One plain sentence. Role, city, stack, stage, whatever matters to you.

  2. 02I read the web live

    GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.

  3. 03You read the shortlist

    Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.

  • No boolean, no filters, no seat to buy. One box.
  • Read at search time, so a profile updated yesterday counts today.
  • Every step visible as it runs, every name with its reason.

500 free credits on sign-up. No card, no demo call. See real searches.

Read next