01A specialist trained on AI and automation
Trained on Claude, automation tools and our documentation habits before they touch your account.
How we work
Delegation that sticks, because it's written down.
Most handovers fail quietly: knowledge stays in someone's head, the hard parts drift back to you, and nobody said how long ramp-up would take. We designed around each of those.
The process
Six steps, every engagement.
01
Discovery call
Thirty minutes to map what you want off your plate, including a short live demo of a real process running with AI. Free.
02
Runbook setup
We interview you and document every task you're handing over into the starting SOPs your specialist will work from. Free, bundled into onboarding.
03
Specialist matched
A trained specialist from our cohort is assigned, briefed on your runbook and introduced in your portal.
04
Ramp window
One to two weeks while your specialist learns your tools, logins, voice and edge cases. Expect more questions early on; full speed by week two.
05
Day-14 calibration
A direct conversation about what's working and what isn't, and a plan to fix the second part.
06
Weekly rhythm
Friday reports, a living runbook, and a portal where you delegate, track progress and flag anything urgent.
Included
The standard you can hold us to.
01
02A runbook you own
Every recurring task written down well enough for someone else to pick up. Built during onboarding, kept current.
03Screen-recorded SOPs
Anything non-trivial is recorded as it's built and turned into a step-by-step procedure.
04A Friday report
Done, next, blocked, and what we need from you. Every week, in your portal.
05A day-14 calibration call
Two weeks in, we ask the direct question: is this working? Then we adjust.
06An honest ramp
The first one to two weeks are for learning your tools and edge cases. We say so up front.
Ownership
Automations you own, not rent.
Built in your accounts
Automations run under your logins and your billing. Nothing sits in an account you can't see.
Source and configs handed over
Custom code, n8n or Make exports and Zapier setups are documented and handed to you.
A control interface
See every run, retry failures and pause a workflow without calling us.
No lock-in
If we part ways, your systems keep running and your runbook explains how.
CRM
Billing
Support desk
Database
Email
Spreadsheets
Automation layerZapier · Make · n8n · custom code
Your control interface
Every run, logged
Retry failures
Pause a workflow
Docs per flow
Comparison
How this differs from the alternatives.
Engagements
Month to month, sized to the work.
Part-Time
40 hours / month
One Operations Specialist for a focused set of recurring work. The smallest engagement worth running well.
Discuss scopeHalf-Time
80 hours / month
Enough capacity to own a whole function, such as outbound, support or back-office, end to end.
Discuss scopeSprint
Ad-hoc block
A defined push: a migration, an automation build or a backlog clear-out, with no long commitment.
Discuss scopeFAQ
Straight answers.
What's the difference between an Operations Specialist and a virtual assistant?
A typical VA executes tasks you hand over. Our specialists are trained on AI tools and automation, so they can run a whole process end to end, improve it, and document it. You delegate outcomes, not keystrokes.
Why does it take one to two weeks to ramp?
Because learning your tools, logins, voice and edge cases takes real time, and we'd rather tell you than pretend otherwise. It's the same investment as onboarding an in-house hire, compressed. Full-speed delivery begins by week two.
What happens if my specialist leaves?
We don't keep a person idle on standby, and we won't pretend to. What we do is document every process from day one, with screen recordings and written procedures, so a handover picks up from your runbook instead of starting from zero.
Which tools do you work with?
Whatever you already use. Common ones include Google Workspace and Microsoft 365, HubSpot, Pipedrive, Notion, Slack, Zapier, Make, n8n, Shopify, Zendesk, QuickBooks and Xero. Where no tool fits, we build a custom integration.
Do we own the automations you build?
Yes. They're built in your accounts, and you receive the source code, configurations, documentation and a control interface to monitor and manage them.
How do you handle our data and credentials?
Credentials are shared through a password manager with scoped vaults, never over email or chat. We work on least-privilege access, sign NDAs and data-processing agreements, and document what AI tools may and may not see.
Which time zones do you cover?
We're a distributed team working across time zones, with overlap on US and UK business hours as standard. Coverage windows are agreed per engagement.
How do we get started?
Book a discovery call. If there's a fit, we send a proposal, run the free runbook setup, and your specialist starts on a month-to-month engagement.
Tell us the process you'd hand off first.
Thirty minutes, no charge. We'll map what to take off your plate and show you a real process running with AI, live.