Case studiesInbound triage
Restaurant software company
Every demo request sorted before the calendar loads.
Their demo calendar was taking whoever showed up. Now every inbound request is researched, scored and routed in about two seconds, and a second research pass hands big operators back to sales when the form made them look small.
to research, score and route each demo request, while the prospect is still on the form.
- Applied AI
- GTM engineering
- RevOps
- Company
- Restaurant software company
- Systems
- CRM, Revenue Hero, Slack
- Work
- Applied AI, GTM engineering, RevOps
- Engagement
- Inbound triage live since April 2026
In their words.
Paraphrased from working sessions.
- The sales team, in the first sessions
Noise versus signal.
Reps qualified leads by hand, Googling companies and eyeballing location counts, and too many booked demos turned out to be unqualified. The fear was filtering out good leads by accident.
What we found.
- 1
location, typed by a manager at one site of a large group, was enough to send a big operator to self-serve. The form’s self-reported count decided routing.
- 46%
of self-serve leads used webmail, so research by company domain could not identify the real business.
- 3
pings per lead reached reps, as the owner, the booking and the enrichment arrived one by one.
What we built.
Quick wins first, then the bigger pieces, all in their own accounts.
Triage behind the demo form
Free rule checks first, then a check that the business exists, a read of its website and one Claude call that recommends a routing tier. Deterministic rules handle the edges.
- Claude
- Google Places
- Rules first
Six routing lanes and a fit score
Verified leads to the demo calendar, a short qualification call, self-serve, partners, compliant regions and a polite decline. A four-factor fit score is written to the CRM on every lead.
- CRM
- Revenue Hero
- Fit score
A rescue pass and one clean alert
Every lead sent to self-serve is researched again within a minute or two. If it finds five or more locations, the lead goes back to sales, and the rep gets one Slack alert with everything in it.
- Slack
- Research pass
- Spend cap
What changed.
- ~2 s
to route each demo request, while the prospect is still on the form.
- 31%
of inbound filtered before a rep’s calendar in the backtest, about 56 hours a month back.
- 282
locations at the operator the rescue pass pulled back from self-serve on its first live run.
Zero false positives when the rules were run against 450 recent leads. About $0.03 of research per lead, under a daily spend cap.
The stack
The stack, all in their accounts
- CRM
- Revenue Hero
- Claude
- Google Places
- Slack
- Vercel
Bring last week’s demo calendar.
On the first call we’ll look at who booked, who should have, and what a triage step would change.