Skip to content
01 — How we work

How we work

One week to learn the workflow, two to three to build, then it's yours.

02 — The engagement

wk 01 · week one

Learn the workflow

We sit with you for a week and watch the day happen. No code, no proposals: just the actual sequence of things you and your team do, written down.

  • We shadow a normal week
    Calls, messages, the spreadsheet nobody talks about. We watch rather than interview.
  • Every step written down
    One list, in your words, of what happens between a customer arriving and the money landing.
  • We agree what the agent owns
    Scope on paper before anything is built, including the parts we are deliberately leaving alone.

The step list, week one

Mon 8:00

Hot water leak · 14 Harbour St

Dana Rivers
Added by agent
wk 02–03 · weeks two to three

Build the agent

Built on your accounts and your tools, tested against your own messages before a single customer meets it.

  • On your accounts, not ours
    Your number, your calendar, your CRM. Nothing to migrate and nothing that phones home.
  • Tested on your real messages
    We replay the last month of calls and emails through it before it answers anyone live.
  • Live behind a switch
    It starts on the narrow case, after hours or on overflow, and widens once you trust it.

Dana Rivers

Incoming call · answered by the agent

00:42

Agent · Northside Plumbing, how can I help?

Dana · My hot water’s gone. Can someone come Monday?

handover

Hand off and run

The point of the engagement is the day we are not needed. You get the runbook, the keys and a log you can read without us.

  • We train whoever runs it
    One session with the person who will actually watch the inbox, not a slide deck.
  • One switch stops it
    You can pause a workflow, or the whole agent, without calling anyone.
  • Care plan optional
    Monthly tuning if you want it. No retainer, no penalty for saying no.

Every action, readable

08:02booked
08:02handed to you

The log is yours from day one. It is how you check the agent without asking us.

03 — What we leave behind

What we leave behind

A handover is only real if you could hire someone else tomorrow and they would understand it.

A runbook

What the agent does, what it will not do, and what to check on a Monday morning.

Prompts and integrations, documented

Every rule it follows and every account it touches, written down in plain English.

Your accounts and your keys

It runs where it was built: on your logins, your number, your calendar. Nothing routes through us.

An optional care plan

Monthly tuning if you want us watching it. No lock-in and no penalty if you do not.

04 — Our own practice

We ship this fast because our own engineering practice is agentic

The tooling that writes, reviews and ships our code is the same kind of thing we build for you. Three weeks is not a discount on the work; it is what the work costs when the studio runs this way.

The toolchain we run ourselves

Claude logoOpenAI logoGitHub logoLinear logo

Claude · OpenAI · GitHub · Linear

Questions about the process

4 questions

How much of my time does the discovery week take?
A few hours across the week, mostly us watching you do what you already do. We do not need meetings; we need to see a normal Tuesday.
What if the workflow turns out to be the wrong one to automate?
Then we say so at the end of the discovery week and you decide whether to build. It is a cheaper conversation than a wrong agent.
Do you need access to everything?
No. We ask for the accounts the agent will actually use, scoped as narrowly as the tools allow, and we hand the keys back at handover.
What happens after the handover?
It is yours. You can run it as it is, change it yourself, or put us on a monthly care plan. Nothing stops working if you walk away.

We build the agent. You keep running the business.

Tell us what eats your week. We’ll tell you what an agent can take off it.

usually replies same day