The method is the product. Here is all of it.
Four steps, and a commitment attached to each one that you can hold me to. Behind them sits a longer internal system, nine phases across four arcs, but you do not buy a process diagram. You buy the fact that one exists and that it has a way of failing.
A demo is not proof. A Tuesday in production is.
Most of what a company asks us to automate should not be automated. It should be deleted, or it should be a setting in software they already pay for. Automating a bad process means the waste happens faster.
So the first job is counting, not building. Some of what comes back is work your own team can fix on Monday for nothing, and you get that list separately, because an assessment that concludes hire me for all of it is a sales document with a price on it.
What never runs on its own
- Moving money, or anything that touches a payment
- Signing anything, or agreeing to terms on your behalf
- Granting, changing, or revoking anyone's access
- Publishing a response to a negative review
- Pricing shown to a customer, without a person checking it
- The monthly report you make decisions from
- Any statement of fact your own records do not contain
Judgment stays yours by design. How we handle your systems and data.
Find
Count what is leaking before touching anything.
Most of what a business is asked to automate should not be automated, it should be deleted. So the first job is not building, it is counting: how work actually moves, where it stops, and what each stop costs in dollars you have already paid to earn. The number comes from your systems, not from an industry average.
- Two maps and a mirror
- One map follows the work from first contact to paid. One follows the decisions: what has to reach you, and why it still does. Then I read it back in your words so you can tell me where I have it wrong.
- The free list
- Part of what I find is fixable by your own team on Monday for nothing. You get that list separately, because an assessment that concludes hire me for all of it is a sales document with a price on it.
- The refusal check
- Before anything gets quoted I ask whether there is a cheaper honest answer than a build. If a setting in the software you already pay for solves most of it, that is the recommendation.
- The baseline
- Whatever we are going to change gets measured first and frozen. Once a leak is fixed the before is gone forever, and a result you cannot compare to anything is not a result.
Build
Inside the software you already own.
The work gets built into the systems your team already opens every morning, because a tool nobody opens is not a tool. No new logins for the office, nothing new to buy, nothing to migrate. Fixed scope, fixed price, quoted before anything begins and never billed by the hour.
- Twenty-one days
- That is the target from kickoff to a system you have accepted, and your own time inside it is a few hours total. If a build cannot hold that shape it is too big and should be cut down.
- You approve what goes out
- Every message that will carry your company's name is read and signed off by you before a single customer sees it.
- Tested on your real work
- Not on sample data. On your actual jobs, your actual customers, your actual edge cases, before it is allowed near anyone.
- Built from patterns, not from scratch
- Twenty-one documented patterns out of previous engagements. Two are graded as measured and the rest as observed, which is stated plainly so nothing gets sold as more settled than it is.
Prove
The number moves, or it did not work.
Shipping is not the finish line and a demo is not evidence. What counts is the same measurement taken again, against the baseline we froze, in production, on an ordinary week.
- The acceptance test, in public
- Five real drafts go in front of you, one question each: would you send this as written, yes or no. Three yes is a pass and I invoice. Fewer and I tune for another week or tell you honestly it should be scoped down.
- Only what I control
- I will put a number on how fast leads get answered, what share of them get answered at all, and whether every open opportunity got worked. I will not promise your close rate or your revenue, because those depend on your pricing, your crews, and your market.
- Confounders travel with the claim
- If something other than the system could explain the change, that goes in the report next to the number, not in a footnote.
- Nothing runs unattended until it earns it
- Every automation starts with a person reviewing each message. It moves to spot-checks, and then to running on its own, based on measured accuracy. It moves back down the same way if it gets one wrong.
Run
Somebody owns it in production.
A workflow built in July is broken by October if nobody is watching it. Vendors change their integrations, tokens expire, formats shift. This is the part that gets skipped, and skipping it is the single most common reason automation quietly stops working.
- Repair is the job
- When a vendor changes something upstream, fixing it is included rather than quoted. You should not find out from a customer that something stopped.
- A kill switch you can reach
- You can stop anything from your phone without calling me first. That is a design requirement, not a courtesy.
- Handover from day one
- Written documentation, your accounts, your data, and an offboarding package that exists before you need it. Knowledge transfer is part of the build, never an upsell.
- Then the next one
- When the first system has run clean for a month, we go find the next thing worth removing. Not before.
Four steps, and you can stop after any one of them.
The Leak Check
Free, 30 minutes
You walk me through how work actually moves, and I tell you where the money is leaking out of it.
You keep the list either way, whether we ever work together or not.
The Systems Audit
Fixed fee, credited toward any build
Your numbers, the arithmetic shown line by line, and a written plan you could hand to somebody else.
The fee credits in full against a build booked within 30 days, so the audit becomes a deposit rather than a purchase. If the honest answer is that nothing here is worth building yet, that is what the audit says.
The Build
Fixed price, quoted before I start
One problem, built inside the software you already own, and yours when it is done.
You own the code, the accounts, and the data. If we part ways it keeps working and it stays yours.
Operating Partner
Monthly, month to month
I run it in production, repair it when a vendor changes something, and take the next problem when you are ready.
Month to month. No term, no notice period, no penalty for stopping.
The expensive resource in this is your attention, not my hours.
- 30 min
- The first conversation, free, and you keep the findings either way.
- 21 days
- Target from kickoff to a system you have accepted, not to a system that merely shipped.
- 2.5 hrs
- A week of your team's time, at the most. More than that means a workflow is missing.
Everything that can be pulled from a system you already run gets pulled instead of asked. Live conversation is reserved for the things a form genuinely cannot capture: what it actually feels like to run this company, and what you would never let software touch.
Tell us what is not working.
Two minutes to write it down, a reply within one business day, and the option to book a call straight away. You keep whatever I find either way.