What actually gets built in the first month
Not a demo, not a trial account. The same stack we run this business on, stood up under your domain and handed over.
A server that is yours
We provision it, or use one you already have. The assistant runs on it around the clock — not in someone else’s tenant, not behind a per-seat licence. If you ever want us gone, the root password is yours and the machine keeps working.
A delegated key to your Workspace
A service account in your own Google Cloud project, authorised in your own Admin console, scoped to exactly what your automations need and nothing more. That grant is domain-wide delegation, and it is the thing the rest of this site is about.
Email and calendar under management
The assistant reads the mailboxes you point it at, drafts replies for you to approve, files what does not need you, and keeps the calendar honest. Drafts, never sends — until you tell it otherwise.
Two automations you choose
You name the two jobs you most want off your desk. We build them in the first month. The catalogue is 222 patterns we already run, so most answers start from something proven rather than a blank page.
How the month actually goes
Day 1 — one decision
Dedicated service account and Cloud project, or reuse something you have. We recommend dedicated: an always-on internet-facing box is a bigger attack surface than a laptop, and a scoped identity keeps the blast radius small if it is ever compromised.
Days 1–2 — the plumbing
Server, project, service account, API enablement, the Admin console grant, and a probe per API proving each one answers under the real subject. Observed results, not “should work”.
Week 1 — it starts working
The assistant comes online against your mailbox and calendar. You talk to it the way you would text an assistant. It reports back where you already are.
Weeks 2–4 — your two jobs
We build the two automations you named, run them alongside whatever you do manually today, and only cut over once they match. Nothing silently replaces a process that works.
What we learned the hard way, so you do not have to
A shared short-lived auth token took our own command centre down for 10.8 hoursbefore we traced it. Every build now ships a long-lived token in the service environment instead. That fix, and about forty others like it, are already in the setup we hand you — which is the actual difference between this and a weekend of following Google’s documentation.
Why you would trust us with a key to your mail
Reasonable question, and the honest answer is that we gave ourselves the same key first. This business runs on this exact stack: one service account across three Workspace tenants with 39 authorised scopes, driving client mail, document assembly, calendar, reporting and a call-triage pipeline. Every pattern in the catalogue is something running in production here, not an idea. When something breaks, we have usually already broken it — the unauthorized_client walkthrough is on this site because we spent a day on it.
What it costs
Month one — free
Server, delegation, assistant, two automations. No card, no contract. If you do not want to keep it, we hand you the keys or shut it down. You are not trapped and there is nothing to cancel.
Month two onward — monthly
A flat monthly package: the assistant stays running and supported, and the base feature set grows as we ship. Priced when we have seen your setup, because quoting before that would be a guess.
Bigger builds — hourly
Anything beyond the package is $500 an hour, billed in quarter-hours after the first. Most single-tenant delegation work finishes inside the first hour.
Start the free month
Tell us the two jobs you most want off your desk. We reply the same working day, and the first reply is a person, not a sequence.