Services
It starts with the business, not the tool. Every engagement is fixed scope and fixed price, and closes with documentation so your team runs the system without me.
What changed
Five years ago companies still bent their processes to fit whatever software the market offered, because building something custom was expensive.
Today we build solutions that adapt to the processes the company already runs — from the architecture up, and flexible enough to fit the budget.
The seven lines
01
Where the work actually goes: who decides what, which system is the source of truth, where the edge cases live. Then what to simplify, what to automate, and what to leave alone.
02
The design decision before the build: what the system has to do, where judgment is genuinely required, and what a rule or a schema resolves better and cheaper.
03
When nothing off the shelf fits the way your business actually works, the solution gets built: an internal app, a client-facing tool, or the piece that closes the gap between two systems that were never meant to talk.
04
The solution reads and writes in the systems you already pay for, not in a copy of them. Often the right integration is the cheap one the client will keep paying to run.
05
A proposal, a report, a client brief: the judgment written down once, so the output stops depending on who happened to build it that day.
06
The circuit running on its own, with a model only in the steps that need judgment. This is the line with the longest track record.
07
For teams producing volume with generative tools, where the real risk is budget: a human gate before anything expensive runs, and a dry run on every stage that spends.
How to engage
Every engagement starts with a free thirty-minute call to confirm the fit. Prices are the floor for that scope, not a starting bid.
01
USD 850 · fixed
One week
The entry point. A deliverable of its own, not a sales proposal in disguise. If the honest answer is that a process should not be automated yet, that is what the report says.
What you get
02
USD 4,500 – 9,000 · fixed
Two to four weeks
The core offer. Design, build against an isolated environment, and layer-by-layer validation before anything touches production.
What you get
03
USD 6,000 – 12,000 · fixed
Scoped per series
Parallel to the Build Sprint, not above it — a different buyer. For small production companies, content channels and agencies that want volume without generation cost running away from them.
What you get
04
USD 2,500 – 4,000 / month
Three-month minimum
The retainer, after a diagnostic or a build. Architecture, continuous implementation, and support on the systems already delivered.
What you get
Scope and currency for projects outside the United States are quoted per project.
After the diagnosis, we build the solution that fits.
Not the most impressive one, and not whatever is in fashion that month: the one your stack supports, your budget sustains and your team can keep running once I am gone. The diagnosis is mine; for the build I bring in solution architects, so the project never depends on one person’s calendar.
What decides it
Not on the model. On the process underneath it. Nobody mapped who decides what, which system is the source of truth, or what happens when the edge case shows up. So you end up with a chatbot nobody opens twice.
No. I build on no-code and low-code tools that do not require developers, and I handle setup and training. Every engagement closes with technical documentation and an operating guide, so your team runs the system without me. That is the point of the engagement, not a consolation prize.
Automating a broken process just makes broken things happen faster. That is why I start with a process audit: organize and simplify first, then automate. Strategy without execution is useless. Execution without strategy is expensive.
Everything is built against an isolated environment first — sandbox accounts, copies of the live data. Nothing touches production until it has been validated layer by layer: assembly logic, then creation, then delivery, then the full circuit end to end.
Professional services firms, agencies and remote teams of 2 to 50 people, with a document-heavy process that eats skilled hours. Not a fit: model training, infrastructure, or one-off prompt writing.
They get reviewed and organized first. The audit defines where to simplify before automating. If the honest answer is that a process should not be automated yet, that is what the report says.
Claude Code, MCP, Claude Skills, n8n, Make, Airtable, the QuickBooks API, Google Workspace, Trello, Gmail and Zapier. If a tool is not on that list, I say so, name the equivalent I do know, and offer to evaluate it during the diagnostic.
Let's talk
I will tell you whether it is worth automating before you spend anything. Thirty minutes, no commitment, no pitch deck.