How we work
Four steps. Something written at the end of each one.
You should never wonder what's happening, what it costs, or what you'll have if we stop. This page is the whole process, including the parts that need your time.
- 2 weeks
Audit
We map how work actually moves through your business, interview the people doing it, and rank every repetitive task by payoff, effort, and risk. You get a written plan.
From you: About two hours a week from one point person.
- Fixed-price proposal
Plan
Every recommended build comes with a fixed price, a written scope, and a timeline. The plan is yours: use it with us, with another vendor, or with your own team.
- 2–6 weeks, weekly demos
Build
We build in accounts you own, show you working software every week, and keep a person in the loop wherever the cost of a mistake is real.
From you: A short weekly demo and a review during the final parallel-run week.
- Optional, month-to-month
Operate
After handover you can run it yourself, or keep us on a monthly retainer for monitoring, fixes, and improvements. Cancel any month.
Step by step, in more detail
1. Audit — two weeks
We start by looking, not building. In week one we interview the people doing the work, watch the workflow happen, and list every tool it touches. In week two we score each repetitive task on payoff, effort, and risk, sketch what an automation would look like, and price the ones worth doing. You get a written report and a one-hour readout. Some findings will say “leave this alone.” That is the audit doing its job.
From you: one point person for about two hours a week, view-only access to the tools involved, and short interviews with the people who do the work.
2. Plan — a fixed-price proposal you can take anywhere
Every recommended build gets a proposal with one price, a written scope, a timeline, what we need from you, the ongoing third-party costs, and what would trigger a change order. The plan is written so another vendor or your own developer could act on it. There is no obligation to build with us.
3. Build — two to six weeks, weekly demos
Work starts on a signed scope and a deposit. Week one is access and data mapping: we confirm the rules with the person who does the work today. From week two you see working software every week and correct us early. The final week is a parallel run next to the current process, then training, handover, and a written fix window.
From you: a 20-minute demo each week, least-privilege access to the tools we connect, and someone to review results during the parallel run.
4. Operate — optional, month-to-month
After handover you can run the automation yourself with the runbook, or keep us on the operator retainer: monitoring, fixes when a tool or model changes, a monthly block of improvement time, and a written check-in. Cancel any month with the notice in the agreement. Everything stays in your accounts.
What you keep at every step
- After the audit: the report, the ranked list, and the proposals.
- After the build: the code, the prompts, the accounts, the keys, the runbook, and the data.
- After the retainer: all of the above, still running, in your name.
Tools we work with
We connect to what you already use rather than replacing it. Commonly: Google Workspace, Microsoft 365, QuickBooks, HubSpot, Stripe, Square, Calendly, Clio, AppFolio, Buildium, NetSuite, Fishbowl, and anything else with an API or a reliable export. If a tool can’t be connected, the audit says so before you spend on a build. For what we build, we use plain code in cloud accounts you own, so there is no per-task subscription to a middleware tool.
How we handle your data
Least-privilege access, your accounts, no training on your data, deletion at the end. The security page spells it out in plain English.
Start with a 20-minute fit call
What happens after you book:
- You pick a 20-minute slot and answer six short questions, so the call is about your business, not ours.
- On the call we look at one workflow together and tell you honestly whether it's worth automating — and roughly what it would cost.
- Afterwards you get a short written summary and, if it makes sense, a fixed-price proposal. No follow-up sequence, no pressure.
No pitch. We'll look at one workflow together and tell you honestly whether it's worth automating.