Demo · automation flow
Watch a lead get enriched, scored, routed, and notified.
Pick a synthetic lead, press run, and watch it move through a real inbound-lead pipeline stage by stage. Enrichment, scoring, routing, and the notification cards all run right here in your browser.
- Pick a lead and press Run pipeline to start a synthetic run.
// the lead payload appears here and changes at each stage How it works
Five stages, in plain language.
This is the same shape as a real inbound-lead automation: a webhook receives a form submission, enrichment attaches context, a scoring rule decides priority, a branch routes the lead, and a notification fires. Here every step runs in the browser on synthetic data.
Received
A lead arrives from a contact form: name, company, email, channel, and message.
Enriched
A deterministic lookup attaches firmographics: industry, company size band, location, and a fit signal. No vendor is called.
Scored
Visible rules turn the lead into a 0 to 100 score. Company size, intent keywords, and channel each add or subtract points.
Routed
The score maps to a queue and an owner. Hot goes to a senior rep, warm to a nurture queue, spam to archive.
Notified
A Slack-style message and an email draft render in-page, showing what would be sent. Nothing leaves the page.
The scoring rubric
How the score is computed.
The score is a synthetic, computed value. Every input below is visible and deterministic, so the same lead always produces the same score.
| Signal | Rule | Points |
|---|---|---|
| Company size | Larger size bands add more potential | +5 to +30 |
| Intent keywords | Words like automate, integrate, ongoing, retainer, ordering | +8 each |
| Low-fit keywords | Words like website, logo, one-off, brochure | -10 each |
| Channel | Contact form is trusted, bot form is not | +10 / -40 |
| Valid contact | A real-shaped, named sender | +10 |
| Spam markers | All-caps blasts, link bait, noreply sender | -50 |
| Route | Threshold | Outcome |
|---|---|---|
| Route A | score ≥ 65 | Hot. Assigned to a senior rep, Slack ping. |
| Route B | 30 to 64 | Warm. Nurture queue, follow-up email draft. |
| Route C | score < 30 | Cold or spam. Archived, no owner assigned. |
Architecture
The flow shape.
The same topology a production version would run: a webhook trigger, a normalize step, enrichment, scoring, a routing branch, and a notification fan-out. This demo runs it client-side with synthetic data.