Examples

What good automation looks like

Anonymised composites — each shows the problem, our approach, and the outcome. No client logos or guaranteed metrics.

Supervised

Inbox triage (supervised)

Problem

Small team gets the same questions daily. Replying takes hours.

Approach

Indexed FAQ and past replies; agent drafts responses with source links. Billing and complaints route to a human queue.

Outcome

Draft replies from your knowledge base. Human approves before send. Billing escalates.

Script

Weekly client update

Problem

You ship every week but client updates lag — summarising what changed is tedious.

Approach

Script pulls completed tickets from your tracker, groups by theme, fills an email template. No AI needed for the core loop.

Outcome

Script collects completed items, groups by topic, produces a draft. Human reviews, then sends.

Local

Local document assistant

Problem

Contract work under confidentiality. Uploading to a public AI site is not acceptable.

Approach

Local embedding index on a workstation; queries stay on disk. Export only when the user copies an answer out.

Outcome

Local indexing and queries on your machine. Nothing leaves unless you copy it out.

Script

Lead routing from web forms

Problem

Inbound leads land in one inbox. Sales spends time sorting instead of calling.

Approach

Form webhook tags leads by service line and region, creates a CRM entry, notifies the right rep with context.

Outcome

Leads arrive pre-tagged with a one-line summary. Rep gets a Slack ping with the form details attached.

Supervised

Long document summarisation

Problem

Team reviews 40-page vendor proposals. Reading everything takes half a day.

Approach

Upload to a private workspace; agent extracts requirements, risks, and pricing tables into a one-page brief. Human verifies numbers.

Outcome

One-page brief with page references. Reviewer checks flagged sections, not the full document.

Skip

When we said: don't automate

Problem

Owner wanted AI to make strategic decisions that change weekly.

Approach

Mapped the decision tree — inputs changed too often, exceptions were common. Proposed a weekly review checklist instead.

Outcome

We documented why automation would cost more than it saves. Proposed a checklist instead.

See matching playbooks →

Have a workflow in mind?