Lead-to-Sale
Turn online enquiries into sales-ready opportunities.
A connected workflow that captures, validates, scores and enriches each enquiry, runs a bounded automated sales conversation and qualifies it on budget, authority, need and timing. Qualified opportunities go to one named owner and are tracked through to an accepted, paid or lost outcome.
A real customer situation
An office submits a website form asking for weekly catering. Before making an offer, the owner needs its location, headcount, budget, who approves the purchase and when it should start — and usually has to chase for them between jobs.
Where the owner wants to be
Every enquiry is recorded once, explained with a score, followed up within limits and either handed to the owner with a clear brief or parked with a reason. The owner only prices opportunities that fit.
What it handles
- Validates the form and merges duplicates into one lead
- Scores fit, need, timing, budget and decision access with the evidence shown
- Runs up to three follow-ups and stops on reply, opt-out or the limit
- Extracts BANT from replies and leaves unknowns unknown
- Hands one owner a brief, then tracks the approved offer to won, lost or pending
What it deliberately does not do
- Never sets a price or scope — the owner approves every offer
- Positive sentiment is not a sale; won needs acceptance and a payment event
- The public demo sends no outreach and writes to no real CRM
Interactive demo
Try it with sample data
No sign-up needed. Pick a scenario, change the inputs, then play the customer and the owner. The right-hand panel only shows what the workflow actually recorded.
Interactive simulation using sample business data. No emails are sent, no CRM is written and no payment is taken.
Choose a scenario
In-zone office, 40 people, starting in 3 weeks.
Use ops@harbourlane.example to trigger the duplicate check.
Newcastle and Wollongong are outside the delivery zone.
Minimum order is 10 people.
Leave blank to test an unknown start date.
Customer side · Email thread with the lead
Press “Run scenario” to start. Every message and record here comes from sample data.
Workflow and harness
How Lead-to-Sale runs
Reference schematic for the proposed workflow. Blue steps do the work, purple paths handle exceptions and returns, and amber checks are the harness controls that a step cannot pass without.
Overview — business stages
Read the full flow as text
- Capture and validate lead (business step)
Required fields, email format, duplicate lookup by email. Output: Lead record (created or updated). Leads to: Initial score and enrichment; Duplicate record. - Initial score and enrichment (business step)
Deterministic 100-point score; fixture enrichment. Output: Initial score with evidence. Leads to: Automated sales conversation; Poor fit (stop). - Automated sales conversation (business step)
Max 3 attempts, 2 days apart; constrained questions. Output: Messages in outbox, replies classified. Leads to: BANT and final score; No reply within limit. - BANT and final score (business step)
Extract budget, authority, need, timing with evidence. Output: BANT fields + final score. Leads to: Human handoff and offer; Not ready yet. - Human handoff and offer (business step)
One owner, acknowledged; offer from catalogue price. Output: Handoff brief + versioned offer. Leads to: Accepted paid or lost outcome; Scope or price questions. - Accepted paid or lost outcome (business step)
Won only with accepted offer and verified payment. Output: Won / lost / pending status. - Duplicate record (exception or return path)
Merge into the existing record. Output: Updated lead, no new record. Leads to: Initial score and enrichment (merge). - Poor fit (exception or return path)
Stop before outreach. Output: Closed lead + referral draft for owner. - No reply within limit (exception or return path)
Retry until 3 attempts, then stop. Output: Nurture with dated trigger. Leads to: Automated sales conversation (timed retry ×3). - Not ready yet (exception or return path)
Park with 30-day trigger. Output: Nurture record. Leads to: Automated sales conversation (nurture trigger). - Scope or price questions (exception or return path)
Route to owner; never auto-change price. Output: Revised, owner-approved offer version. Leads to: Human handoff and offer (human review). - Evidence and score rules (harness check)
Each part cites evidence; unknown ≠ negative. Output: Pass / fail with reason. Leads to: Initial score and enrichment (required check). - Contact and stop rules (harness check)
Enquiry reply only; max 3; stop on opt-out or human takeover. Output: Allow / stop. Leads to: Automated sales conversation (required check). - Owner approved offer (harness check)
Owner approval required; no price with unknown budget. Output: Approved offer version. Leads to: Human handoff and offer (required check). - Verified payment event (harness check)
Event must reference the current offer version. Output: Verified payment reference. Leads to: Accepted paid or lost outcome (required check).
Harness controls
- Preserve lead source and contact permission on every record
- Bound attempts and timing; stop on reply, opt-out or human takeover
- Explain every score component with its evidence
- Require owner approval before any offer is sent
- Acknowledge handoff to exactly one owner
- Deduplicate every write with an operation key
Systems and data
Production uses forms, CRM, a verified enrichment provider, an eligible email/SMS channel, a scheduler and a proposal/payment system. Actual connectors require discovery and access checks. The demo uses fictional enrichment fixtures and an outbox that holds every message.
Demo boundary
External calls, customer messages, payments and business writes use synthetic fixtures and an on-screen outbox. The demo shows only verified demo state. Custom production connections are a paid implementation deliverable.
What gets delivered
The records your business receives
CRM opportunity
One record per contact with source, score history, BANT fields, owner and status from new to won or lost.
Owner handoff brief
Company, need, timing, stated budget or ‘unknown’, conversation summary and the recommended next step.
Versioned offer
Owner-approved offer with version number; revisions supersede earlier versions and payment links point to the current one.
Custom deployment
Configured for your business during a paid implementation. Integrations are confirmed during discovery, never assumed.
Your business rules
- Your service area, minimums and catalogue prices
- Score weights and thresholds calibrated on your past wins and losses
- Follow-up timing, channel permissions and attempt limits
- Who owns which leads and how handoffs are acknowledged
Systems we connect
Measurement
We measure completed business against a baseline, not messages sent. No results are promised before discovery.
Business results
- Qualified opportunities per week
- Attended sales calls
- Completed sales and contribution after acquisition and delivery cost
Operational reliability
- Duplicate leads created (target: zero)
- Messages sent after opt-out (target: zero)
- Handoffs acknowledged within the agreed time
Want this following up your actual enquiries?
Book a call about Lead-to-Sale. We start with discovery: your current process, volumes, systems and who handles exceptions. The proposal then defines the integrations, approvals and acceptance tests before anything goes live.