Business process automation, built once and handed over.
The repetitive part of the week — quoting, scheduling, intake, invoicing, the follow-up nobody has time for — built end to end, documented, and running in your own accounts. You own it outright. There is no platform underneath it that you rent from me.
Two sizes, and the difference is honest
One Block — from $4,500, two to three weeks
The single worst block of the week, automated end to end. Usually it is the thing somebody re-types by hand: an order that arrives one way and has to be entered another, a schedule that lives in a phone and a whiteboard at the same time, a quote that gets built from scratch every time even though eighty per cent of it never changes.
One block, done properly, beats five half-connected ones. It ships with documentation and with the access, and when it is finished you are not waiting on me for anything.
The Week — from $12,000, six to eight weeks
The loop rather than one piece of it: several connected systems, plus you trained on all of them. This is the right shape when the blocks depend on each other — when automating intake only moves the pile to scheduling, and automating scheduling only moves it to invoicing.
Accounts, code and documentation are yours from the first day, not the last. The work is built in your accounts, under your logins, with third-party costs at cost and never marked up. The option to never call me again is part of what you are buying.
What gets automated, concretely
- Intake and quoting — a request arriving by form, phone or email becoming a record, a quote and a reply without anyone retyping it.
- Scheduling and dispatch — one place where the day's jobs live, that the field and the office both see.
- Invoicing and chasing — the invoice raised from the job that was actually done, and the polite second reminder that nobody enjoys sending.
- Systems that don't talk — the integration between the two tools you already pay for and currently bridge by hand.
- Reporting — the number you want on a Monday, without an afternoon of assembling it.
- Assisted steps — where a language model genuinely helps: drafting, classifying, extracting from documents. Used where it is the right tool, and not as a headline.
How a build runs
- Map. A working session and a walkthrough of how the job actually gets done. If we came through the Week Audit, this is already on paper and the $750 comes off the build.
- Cut. We pick what gets built first, in writing, with the scope fixed and the price fixed.
- Build. Short cycles with something running you can look at. No six-week silences.
- Hand over. Documentation, access, and a walkthrough with whoever will use it every day.
What it costs, and what it doesn't
Fixed scope, quoted in writing, the same numbers for everyone — the full ladder is published on the home page. There is no hourly rate running in the background. Half is due at signature and the rest on delivery.
Afterwards, Keep it running is $650 a month for monitoring, fixes and small changes, with no minimum term — cancel any month. It is optional, and a build that only works while someone is paying a retainer is a build that was done wrong.
Through 31 October 2026 the first three engagements take 20% off the build — $3,600 for One Block, $9,600 for The Week. What I want in return is permission to say what I built and who I built it for.
If you would rather look than read: four builds are live, with the numbers each one was measured against.
Start with the worst block.
One conversation, no deck. If there is nothing worth automating I will tell you that instead.
Sent. I have your message and will get back to you by phone or email.
That did not go through. Add your name and a phone number or email, or call the number above.
Before you write, look at four systems you can open right now — Lighthouse 89–91 on desktop, 444 pre-rendered frames, two shop sites whose smoke suites pass 68/68 and 48/48, every route of a booking product answering 200. None of the four is client work, and the page that carries them says so.