Have a team? Start here → Take the free test →

Systems & automation

The work you don't want,
handled by something else.

Every build ships with a stack. Here is what goes into one, what each part removes from your desk, and where AI earns a place.

See the stack → Watch one workflow run

How we choose

Boring software first. AI where judgement is the job.

A scheduling rule does not need a language model. Routine steps run on ordinary automation because it is predictable, cheap, and it does the same thing every Tuesday at nine. That reliability is the point.

AI comes in where the work is reading, weighing and writing: sorting a messy inbox, drafting a reply in your voice, pulling the three relevant lines out of a forty-page document. We use it there without hesitation. How much runs unattended is your call: guardrails are a design decision, and most builds keep a person approving anything that touches money, contracts or a client relationship.

Nobody gets the whole list. Your Professional Profile and your business decide which parts you actually need, and we say no to the rest.

The stack

Nine layers. You will use some of them.

We stay deliberately platform-agnostic. The layer is what matters; the product filling it is chosen per client, and swapped when something better arrives.

Orchestration

The spine everything else plugs into. One place where a trigger fires a chain of steps across every other tool, versioned and monitored.

Takes off: copy-paste between apps

Intake & scheduling

Enquiries arrive structured instead of as a paragraph at midnight. Booking, reminders and reschedules run without a single back-and-forth email.

Takes off: chasing to book a call

CRM & pipeline

Every conversation logged against the right person without anyone remembering to log it. Follow-ups fire on their own schedule.

Takes off: forgotten follow-up

Documents & signature

Proposals and agreements generated from a template with the details already filled in, sent for signature, countersigned and filed.

Takes off: rebuilding the same proposal

Billing & collection

Deposits taken before work starts, invoices raised on milestones, reminders escalating on their own so you never ask twice.

Takes off: chasing late payment

Client communication

Status updates that write and send themselves from the state of the work, so clients stop asking and you stop reporting.

Takes off: the "any update?" email

Knowledge & retrieval

Your documents, notes and past projects made searchable in plain language, so the answer comes back in seconds instead of an afternoon.

Takes off: hunting for the file

AI assistants & agents

Narrow agents with one job each: triage the inbox, draft the reply, summarise the call, prepare the brief. Scoped, logged, and reviewable.

Takes off: reading and drafting

Model fit & monitoring

Which model for which task, benchmarked on your work rather than a leaderboard, then watched for cost, latency and drift.

Takes off: guessing, and bill shock

Layers are described in general terms because the detail is trade-specific. Billing for a plumber taking deposits on emergency callouts looks nothing like billing for a clinic working against insurance codes, and the same is true of intake, documents and compliance. Scope, tooling and what is feasible are confirmed per engagement and set out in your proposal. Terms and conditions apply.

Where the hours go

A new enquiry, from arrival to kickoff.

Getting from first contact to a signed, paid, onboarded client is a chain of handoffs. How many, and how many need you, depends entirely on the business — that is what the design work decides.

Runs itself

Arrival and qualification

Enquiries land structured, get read, and are ranked before anyone opens them. What reaches you is a short brief, not an inbox.

You

The conversation

The part nobody should automate. You arrive already briefed, and the record writes itself afterwards.

Runs itself

Proposal and agreement

Built at your published price so nothing is discounted in the moment, then sent, tracked and countersigned.

You

One approval

A single read and a single click. Anything touching money or a contract stops here by design.

Runs itself

Payment and onboarding

Deposit taken, project opened, intake sent, first milestone already scheduled before you have closed the tab.

The specific triggers, routing logic and templates behind each phase are built per client and stay with the engagement.

On agents

An agent is a narrow worker, not a robot employee.

The useful ones do a single job on a schedule, hand back something you can check, and stop. Here is what that looks like in practice.

  • Inbox triageSorts the morning's mail into reply-now, reply-later and ignore, with a draft attached to the first pile.
  • Research briefReads the prospect's site, filings and recent news, returns a page you can hold in a meeting.
  • Document extractionPulls the dates, figures and obligations out of a contract into a table you can scan.
  • Content repurposingTurns one recorded conversation into a post, a newsletter section and three follow-up notes.
  • Quality checkRe-reads work before it goes out and flags the missing attachment, the wrong figure, the stale date.
  • CounterpointArgues the other side of an irreversible decision before you commit to it.

Each is scoped to one task, given only the access it needs, and logged. Where the approval line sits is set during the build, to the level of oversight you want. How each agent is constructed, prompted and constrained is part of what you are buying.

Free · Under 5 minutes

Which of these you need depends on how you work.

The assessment maps that first. The stack is chosen second.

Take the free test →