Solutions
Workflows that do the legwork and stop for a person.
Three illustrative workflows built on fixed sample data. Step through each one to see what a bounded agent does, what it flags, and where a person takes over.

Anatomy of a workflow
Every example follows the same four-part shape.
Keeping the shape consistent makes each workflow easier to test, explain, and hand over.
- 1
Input
Something arrives: a list, a ticket, a batch of records. We define its shape and what “incomplete” looks like.
- 2
Processing
The agent or automation does bounded work — research, classify, group, draft — using only approved tools.
- 3
Checks
Low-confidence or conflicting results are flagged rather than guessed, with the reason shown.
- 4
Human review
A person approves, edits, or rejects. Anything that leaves your organisation waits for this step.
Workflow explorer
Step through each workflow.
Choose a workflow, then press Start demo or move one step at a time. Reset restores the original sample data.
Illustrative demo — sample data
Fictional records. No AI requests, nothing sent.
Lead research
Research a target list before outreach
A sample list of companies is checked against a research checklist, summarised into a structured brief, and handed to a person. Nothing is sent automatically.
Research and drafting only. No automated or unsolicited sending.
- 1Sample input
Sample input: target companies (fictional)
- Fernhill Dental Studiofernhill.exampleResearched
- Kettle & Crane Logisticskettlecrane.exampleResearched
- Blue Juniper Analyticsbluejuniper.exampleNeeds a person
- 2Research
Work through the research checklist
Each company is checked against the same criteria your team would use.
Waiting for the previous step.
- Team size signalFound for 3 of 3
- Services offeredFound for 3 of 3
- Recent hiring for operationsFound for 2 of 3
- Blue Juniper: conflicting location dataFlagged: Flagged
- 3Draft brief
Produce a structured draft brief
Findings become a consistent brief, with sources and gaps stated.
Waiting for the previous step.
Draft brief — Kettle & Crane Logistics - Fit: regional freight broker; job posts mention manual load scheduling.
- Possible angle: dispatch updates assembled from several tools.
- Gaps: no decision-maker confirmed. Verify before any contact.
Draft — not sent
- 4Human review
A person reviews before anything happens
The workflow stops here. Outreach, if any, is a person’s decision.
Waiting for the previous step.
3 briefs ready · 1 flagged for checking
A person decides what happens next.
Support triage
Classify, suggest, and route inbound tickets
Fictional tickets are classified, matched to help content, and routed for approval. Low-confidence cases skip the draft and go straight to a person.
Uncertain cases are flagged, not guessed. Replies need approval.
- 1Sample input
Sample input: inbound tickets (fictional)
- #1042Can’t reset my passwordAwaiting approval
- #1043Invoice shows the wrong planAwaiting approval
- #1044Unhappy with last visit, want to talkRouted to a person
- 2Classify
Classify each ticket
Category and confidence are shown so a reviewer can see why.
Waiting for the previous step.
- #1042 → Account accessHigh confidence
- #1043 → BillingHigh confidence
- #1044 → Complaint / sentimentFlagged: Uncertain — flagged
- 3Suggest
Suggest an answer from help content
Suggestions are drafts grounded in existing articles, never auto-sent.
Waiting for the previous step.
Suggested reply — #1042 (draft for review) - Hi Sam, you can reset your password from the sign-in page using “Forgot password”.
- If the email doesn’t arrive within a few minutes, reply here and we’ll help directly.
- Source: Help article “Resetting your password” (sample).
Draft — not sent
- 4Route for approval
Route for approval
Drafts wait in a queue. The uncertain ticket goes to a person with no draft.
Waiting for the previous step.
2 drafts awaiting approval · 1 routed to a team lead
A person decides what happens next.
Operations summary
Turn scattered activity into a weekly summary
Fictional activity records from several tools are grouped, summarised into a draft, and reviewed by the operations lead before sharing.
A draft for the operations lead — not an automatic report.
- 1Sample input
Sample input: this week’s activity (fictional)
- Orders47 orders, 3 delayedGrouped
- Scheduling2 shifts uncovered on ThursdayGrouped
- InventoryPacking tape below reorder levelGrouped
- Support18 tickets closed, 2 open > 3 daysGrouped
- 2Group
Group records by what needs attention
Records are grouped by urgency rather than by the tool they came from.
Waiting for the previous step.
- Needs action this weekFlagged: 3 items
- On track2 items
- For information1 item
- 3Draft summary
Draft the summary
A short draft in plain language, linking back to each record.
Waiting for the previous step.
Draft — weekly operations summary - Needs action: cover two Thursday shifts; reorder packing tape; follow up on 3 delayed orders.
- On track: 47 orders processed; 18 support tickets closed.
- Watch: 2 support tickets open longer than 3 days.
Draft — not sent
- 4Human review
The operations lead reviews
The lead edits or approves before the summary is shared.
Waiting for the previous step.
Draft summary ready for the operations lead
A person decides what happens next.
What these examples are — and aren’t.
They are
- Patterns we can design and build for your team.
- A way to discuss boundaries and review points early.
- Built with fixed, fictional sample data.
They aren’t
- Case studies or records of past client work.
- Live AI output — nothing is generated in your browser.
- A product you can sign up for.
Where to start
Typical opportunities by team.
Examples of work that often suits a first project. Your own list will depend on your tools, your data, and where your team loses the most time.
Sales
- Research a list of accounts against your criteria
- Prepare a structured brief before each call
- Draft follow-ups for a person to review and send
Support
- Classify and route inbound requests
- Suggest answers grounded in your help content
- Flag uncertain or sensitive cases for a person
Operations
- Group activity from several tools into one view
- Draft weekly summaries and exception reports
- Move data between systems without copy-paste
Which workflow would you take off your team first?
Describe the steps, the tools involved, and where a person must stay in the loop. We’ll tell you whether it’s a good candidate.