EXAMPLE SCENARIO LIBRARY

How a workflow becomes automation, step by step Problem → Automation → What gets measured

Every card on this page is an example scenario: a worked design for a business type, not a client case study. No client name, revenue figure or ROI number appears here unless it has been measured on a real system and approved in writing for publication.

Request Strategy Audit Discuss Your Proof Pack

No public revenue, ROI or named-client result is shown unless it is verified and approved.

Baseline firstthe current numbers are recorded before anything is built

Same sourcebefore and after are read from the same system, not from a slide

Your sign-offnothing is published without your written approval

No borrowed averagesindustry benchmarks are never presented as your result

These are the rules we apply before any number is published. No industry benchmark is shown here as though it were a result on your business.

FIND AN EXAMPLE SCENARIO

EXAMPLE SCENARIOS

What the automation does, and what gets measured

Each card below is an example scenario, not a client case. It shows the design: the problem, the automation, and the fields that would be measured after go-live.

EXAMPLE SCENARIO · TRADES & HOME SERVICES

Example scenario — not a real client

Example scenario: a plumber stops losing jobs to missed calls

A small plumbing and heating business with two engineers. The phone rings while they are under a sink or on a roof, and enquiries end up in a voicemail nobody listens to.

Problem

Calls arrive during working hours when nobody can pick up. Callers who cannot get an answer try the next business on the list, and the details that matter (address, access, boiler type, whether it is urgent) are never captured in one place.

Automation

A voice assistant answers every call, captures the job into a fixed set of fields, flags genuine emergencies, books routine work into the calendar, and sends the summary to the owner by SMS and email.

What gets measured

Measured, not assumed: calls received against calls answered, how long a caller waits for a reply, quotes sent the same day, and every emergency escalated to a person.

What gets measured

Calls answered vs. receivedTime from call to quoteJobs booked in the calendarEmergencies escalated to a human

Evidence we would attach

Call-flow map
Field list captured per call
Escalation rules
Booking and notification wiring

EXAMPLE SCENARIO · RETAIL & E-COMMERCE

Example scenario — not a real client

Example scenario: a retailer answers product questions out of hours

A retailer selling online and from one showroom, handling stock, delivery and returns questions across chat, email and WhatsApp.

Problem

The same delivery, stock and returns questions arrive outside working hours. Buyers who get no answer leave, and the team spends the next morning repeating the same replies.

Automation

A chat assistant connected to the product catalogue answers delivery, stock and returns questions, qualifies the enquiry, and hands anything that needs a person to the team with the context attached.

What gets measured

Measured, not assumed: questions answered without a person, questions handed over, time to first reply outside working hours, and the topics that still need a human.

What gets measured

Questions answered automaticallyHandovers to the teamTime to first replyTopics that need a person

Evidence we would attach

Catalogue connection
Answer boundaries and refusal rules
Handover rules
Transcript review routine

EXAMPLE SCENARIO · PROFESSIONAL SERVICES

Example scenario — not a real client

Example scenario: a studio stops rewriting the same intake brief

A design or consultancy studio where a small senior team handles most inbound briefs and proposals itself.

Problem

Senior time goes into repeating intake questions, collecting briefs out of email threads, and assembling first drafts by hand before any billable work starts.

Automation

An intake assistant asks the standard scoping questions, writes the answers into one structured brief, and produces a first draft for a person to review before it goes anywhere.

What gets measured

Measured, not assumed: how long intake takes, how many briefs arrive complete, and how much senior time goes on first drafts instead of client work.

What gets measured

Time from enquiry to complete briefBriefs arriving completeSenior hours on first draftsDraft review time

Evidence we would attach

Intake question set
Brief template
Workflow diagram
Review and approval step

EXAMPLE SCENARIO · LEGAL & PROFESSIONAL INTAKE

Example scenario — not a real client

Example scenario: a law firm structures its first-call screening

A small commercial and private client firm that needs structured fact-finding before a matter is opened, under UK GDPR obligations.

Problem

Routine preliminary screening calls and document collection consume fee-earning time, and the answers arrive in inconsistent notes that somebody has to file later.

Automation

An intake assistant runs the standard screening questions, records the answers against a checklist, and passes the file to a person for review. Matters that need a qualified decision are never decided automatically.

What gets measured

Measured, not assumed: time spent on preliminary screening, completeness of the facts captured, and how often a person has to correct or re-ask something.

What gets measured

Time on preliminary screeningFacts captured per enquiryCorrections and re-asksMatters routed to a person

Evidence we would attach

Screening question set
Conflict-check handoff rules
Retention and deletion rules
Partner review step

EVIDENCE MATRIX

Compare what should be proven before results are published

The matrix keeps the page useful without fabricating revenue or ROI claims.

Proof area	Legal intake	Reservations	Proposal workflow
Primary problem	Manual lead qualification	Booking and reminder coordination	Slow proposal assembly
Automation layer	Intake assistant + routing summary	Booking assistant + follow-up sequence	Draft assistant + review handoff
Result claim policy	Private until client-approved	Private until client-approved	Private until client-approved
Evidence to request	Checklist, transcript, routing map	Flow, reminders, exception handling	Brief, draft, review checklist
Best next step	Request proof pack	Request proof pack	Request proof pack

VERIFIED STORY INTAKE

Have a real success story? Submit it for review first.

The form keeps the existing frontend contract, but the copy now makes the credibility rule clear: stories should be reviewed and approved before they become public case studies.

Publication requires consent, review of the final version, and verified metrics or clearly labeled qualitative outcomes.

NEXT STEP

Build a proof pack for your own automation workflow.

Start with an audit, identify the first workflow, and define the metrics before anyone claims results.