Our Process
Four phases.No disappearing for a quarter.
You approve the scope before anything is built, you see working software while the engagement is still open, and you finish owning it outright. Here is exactly what that looks like.
- Week 1
- Audit delivered
- 8 weeks
- Typical full build
- Staged
- Live before we finish
- Yours
- Credentials at handover
Audit
We map how the work actually flows today — not how the org chart says it does — and find where the hours are going. You get the map whether or not you hire us.
You get
- A written map of the workflows that cost you the most time
- A shortlist of what to automate first, ordered by payback
- An honest note on anything we think isn't worth automating
We need
- An hour with whoever actually does the work, not just whoever manages it
- Read access to the tools involved
Design
We spec what gets automated first, in the order that pays back fastest. You approve the scope before anything gets built.
You get
- A scope document covering exactly what will and won't be built
- The integration points, and what happens when each one fails
- A fixed sequence, so you know what lands when
We need
- A decision-maker to approve scope
- Admin access to the systems in scope
Build & deploy
We ship in stages rather than disappearing for a quarter. Each piece goes live and gets used while the next one is being built.
You get
- Working automations in production, not a demo environment
- A short check-in each week showing what went live
- Changes made against real use, while the build is still open
We need
- One person to be our point of contact
- A few staff willing to use each piece as it lands and tell us what's wrong
Hand over
Documentation, runbooks, credentials and training. You finish the engagement owning the system outright.
You get
- Documentation written for whoever runs it, not for us
- Runbooks for the failure modes that actually occur
- Every credential, in your name
- A training session with the people who'll own it
We need
- An hour with whoever is taking ownership
The part that matters
The engagement ends. The system doesn't.
Plenty of agencies build automations that only they can maintain, on accounts only they can access. It's good for recurring revenue and bad for you.
We hand over the credentials in your name, documentation written for whoever runs it rather than for us, and runbooks covering the failure modes that actually occur. Then we train the people who will own it.
If a system needs us permanently in order to keep working, we built it wrong.
Common questions
What people ask about the process.
Get started
Start with the audit.
Thirty minutes with the founder. You leave with a map of where your hours are going, whether or not you hire us.