Service 01 · Workflow automation
The spine that connects your tools.
Trigger-based automation between the systems your team already uses. CRM, comms, billing, ops, and a central data hub talking to each other so the same record stops getting re-keyed across three places. Built, documented, and handed back to your team.
01 — Who this is for
Where the work gets lost.
Between the tools you already have.
Teams of one to fifty where the same record lives in the CRM, the project tool, and a spreadsheet. Ops chases sales for status updates that already exist somewhere. New starters need three days to learn which spreadsheet is current. This is the layer that connects what you already have.
02 — Common symptomsIf one or more sound familiar
01The same record gets typed into the CRM, the project tool, and the invoicing system.
02Lead routing is whoever happens to be free, not a documented flow.
03Ops chase sales for status updates that already exist somewhere.
04New starters need three days to learn which spreadsheet is current.
05The same export-CSV-then-import-CSV runs every Friday afternoon.
06Reports get rebuilt by hand every month because nothing talks to anything.
03 — What we build
Concrete deliverables.
No retainers in disguise.
- 01Trigger-based automation between your toolsCRM, comms, billing, ops, and data hub wired together. When something happens in one place, the right things happen everywhere else, automatically.
- 02Routing logic that matches how your team splits workInbound enquiries, jobs, or tickets routed by territory, capacity, or any rule your team actually uses. Not round-robin for its own sake.
- 03A central data hub as the source of truthUsually Airtable. The record that every system points back to, so reporting and integrations have one consistent layer to read from.
- 04AI nodes inside the pipeline where judgment is neededClassification, extraction, drafting. The light touch here; the depth on guardrails, evals, and human-in-the-loop lives on the dedicated AI automation page.
- 05Custom interfaces where off-the-shelf tools do not fitWhen the workflow needs a screen the team actually opens, built so it slots into the rest of the stack rather than living alongside it.
- 06Documented handoverWorkflows, integrations, and the runbook to maintain them. Your team owns and adjusts what we built without us in the loop.
04 — How an engagement runs
Map, build, hand over.
Your team runs the workflow from there.
Your team runs the workflow from there.
Four phases. The owner is named on day one. Duration is scoped up front. A written handover closes it. A monthly retainer picks up after, only if iteration is useful.
Phase
00
01
02
03
04
05
06
07
08
09
10
11
12
13+
01
Map
02
Build
03
Handover
04
Filed
◆ Your team runs it. We step out.
After handover →
Retainer
optional · continuous
Run
→
Iterate
→
Design
→
Build
01 · Map
You
Tell us where it is breaking. One workshop, the people doing the work in the room.
Us
Trace the actual flows. Write the gaps. Cost the work.
Filed
Mapped flows · costed scope · phased options
Clear before we start.
02 · Build
You
Stay reachable. Loom walkthroughs when there is something to see.
Us
Ship into your stack. Workflows, integrations, the data hub. Some weeks visible, some under the hood.
Filed
Workflows live · integrations wired · in your tenancy
Visible progress. No dark rooms.
03 · Handover
You
Name the owner. Walk it with us.
Us
Document it. Train the owner. Close out.
Filed
Runbook · owner · review cadence
Yours from here.
04 · Filed
◆ MILESTONE
You
Run it. Adjust the workflows in-house.
Us
Grace period covered. Anything after is booked.
Filed
File closed · no ongoing dependency
The point.
↻ Retainer · optional
Iterate on what’s
live, by the month.
live, by the month.
One cycle · run, iterate, design, build
01 · Run
Keep it operating.
02 · Iterate
Act on what usage shows.
03 · Design
Scope the next thing worth building.
04 · Build
Ship it. Measure it. Back to run.
Typical follow-on
Usage optimisation, workflow tweaks, feature additions. Shape varies by what was built and what the team needs once it’s in their hands.
Cancel any month · 30 days' notice
Engagement is always the foundation · retainer never required
06 — Smallest useful first move
A one-week mapping engagement.
Standalone. No follow-on required.
We sit with your team, trace how the work actually moves, and write up the gaps and the cost of closing them. One week, on-site or remote. You get a written plan with phased scope and indicative costs before any commitment to build. If you stop there, you stop there.
07 — Start a conversation
If this is the kind of work you’re after, here’s how to begin.
Thirty minutes. What’s in the way, what you’ve already tried, whether there’s a useful first move. No deck, no proposal.