Demo requests pile up across email, forms, and chat—and your sales team has no way to know which ones are worth picking up before they go cold.
Your sales team is drowning in demo requests, but not all of them are worth the time. Some come from companies that don't fit your ICP. Others are from tire-kickers doing research. The rest are real opportunities—but they're buried in the noise. This workflow automates the entire intake-to-routing pipeline. When a prospect requests a demo (via form, email, or chat), the system immediately enriches their profile with company data, employee count, industry, and funding stage. It then scores them against your ICP using a simple rule engine: minimum company size, industry match, geography, and intent signals. Qualified leads get routed to the right sales rep with a pre-built context card—company summary, why they match your ICP, what they said in the request, and any prior interactions. Unqualified leads get a polite auto-response and logged for nurture. The result: your sales team spends zero time on qualification and 100% of their time on conversations that have a real chance of closing. Demo request-to-first-call time drops from days to hours. And because every rep gets the same enriched context, you eliminate the "who should take this?" debate. The workflow works best when you have a clear ICP definition (company size, industry, geography, revenue stage) and a CRM that can accept incoming data via API or webhook. It requires one approval gate: a human review of the qualification rules before you flip the switch, and a weekly audit of false positives (qualified leads that turned out to be unqualified).
Trigger: Demo request submitted via web form, email to a dedicated inbox, or chat widget. Webhook fires to your automation platform.
Receive demo request from web form, email, or third-party tool. Log request with timestamp and source. Ensure all required fields are present; flag incomplete submissions for manual follow-up.
Use data enrichment API (e.g., Apollo, ZoomInfo, Hunter) to append company size, industry, revenue, tech stack, and decision-maker titles. Verify email validity. Flag enrichment failures for manual review.
Query CRM to detect existing contacts or opportunities from same company or email domain. If duplicate found, merge data and link to existing record. Prevent duplicate routing.
Evaluate prospect against ICP criteria: company size, industry, revenue range, location, use case fit. Assign qualification score (0–100). Document scoring logic for transparency. Threshold example: score ≥70 = qualified.
Route qualified leads (score ≥70) to routing logic. Route lower-scoring leads to nurture sequence or manual review queue. Sales ops can override scoring for edge cases.
Route to rep based on territory, account ownership, or round-robin assignment. Consider rep capacity and current pipeline. Log assignment reason in CRM.
Create opportunity in CRM with enriched data, qualification score, source, and assigned rep. Set stage to 'Demo Scheduled' or 'Demo Requested.' Link to contact record.
Send rep email or Slack notification with prospect summary, enriched company data, use case, and direct link to opportunity. Include suggested talking points based on use case.
For leads scoring below threshold, create contact record with 'Unqualified' tag and reason. Add to nurture campaign or drip sequence. Set review date for re-qualification.
Log time from request to routing, qualification rate, conversion to demo, and rep response time. Feed metrics to dashboard for continuous optimization.
1. Define your ICP in writing: minimum company size, target industries, geographies, and revenue stage. 2. Connect your form/email/chat tool to your automation platform via webhook or API. 3. Add an enrichment step using a data provider (Apollo, ZoomInfo, Clearbit, or similar) to pull company profile on the prospect's domain. 4. Build a scoring rule: assign points for ICP match (e.g., +10 for right industry, +5 for right company size, +10 for right geography). Set a threshold (e.g., 20+ points = qualified). 5. Create two routing paths: qualified leads go to your CRM with a pre-built context card; unqualified leads get a nurture tag and auto-response. 6. Set up a weekly audit: pull a report of all qualified leads and spot-check 10–20 for false positives. Adjust rules if needed. 7. Brief your sales team on what context they'll receive and how to use it.