Services

Automation in the work your team does by hand. Without it landing on you.

You own a business doing $5–50M a year. You already use AI and pay for it. What you don't have is someone to say where it goes, build it, and keep it running — so you never end up being the software developer.

That's the job. Cost down, your time back, revenue up. Three pieces, in the order they happen. Each one is billed for the time I work, and each one ends.

01

Planning

One meeting to get a clear definition of the problem: what the bottlenecks are, and which number in the business each one is tied to. If we can name the problem and why moving it matters, I write the plan.

You walk away with a written plan. Which jobs, in what order, and the number each one moves.
Every job gets one question first. Whose day does this change, and does their life get better or worse? Taking away someone's data entry is a relief. Taking away the job that feeds their family, or the personal touch with a prospect, is not. If it isn't lined up with your people, they won't use it.
Billed for time. Then it's done. You can take the plan to me, to someone else, or do it yourself.

02

Building

Hand me the plan, or any piece of it, and I build it. One job at a time.

Built on your systems. Your AI account, your tools, your data. Nothing runs on anything I control, so there is nothing to migrate off if we stop.
You own the code. It's your project. The only exception is a product I already own and bring with me — that part stays mine, and I'll say so before we start.
Measured against the people doing it today. Every build ends with a number next to the team's number, on the same work.
Billed for time. Then it's done.

What stops it doing something stupid

The question owners ask me most, in one form or another. Anything I build that talks to your customers or touches your records gets the same rails I built for the recruiting agents that text thousands of people a month:

It can only do what it's been given permission to do. The list of allowed actions lives in code you can read, not in the model's head.
It sends one message per turn, never a burst, and it won't message anyone outside the hours you set.
If it keeps failing to get somewhere with one person, it stops on its own and hands them back to you.
It drops anyone who no longer qualifies, so it isn't chasing a customer who already bought.
Every decision it makes is logged, so when you ask "why did it do that?" there is an answer.
Anything with a clock in it — the follow-up in five minutes, the next-day 9am message, the 48-hour close — gets tested on a fake clock in seconds, before it ever runs on a real one.

Why the rails exist: one unguarded loop I found later had run 178,745 requests and about $280 in five days on a cheap model. On a top-tier model the same loop would have cost about $8,000. It's the kind of thing you only see if somebody is looking, which is what support is for.

03

Support

Models change, vendors change, your own process changes. Somebody has to watch for that, and it shouldn't be you. Two ways to have it. You pick.

Priority support — monthly

I hold time open for you, watch the system, and handle drift before it's your problem. You get a response time. This is the only thing I sell month to month, and it's the half that's worth paying for in a month when nothing breaks.

Best-available support — hourly

Nothing gets switched off; it runs on your systems whether I'm involved or not. Work gets booked when my availability allows, and you pay for the time. What you don't get is a response time.

Finding the next job is part of either. You name it, or you teach me how the business works and I bring back the opportunities with the number each one moves.

What it costs to run

Whatever I build uses AI, and AI has a meter on it. It runs on your own account, so the provider bills you directly. You see every penny and you can cap it wherever you like.

It's usually small. In one case, working a list of 523 written-off leads cost about $200 in model usage from end to end. But it isn't zero, and anyone who tells you their AI system is free is billing you for it somewhere else.

What I won't take on

If we can't name the cost line or the revenue line a job moves, it isn't work I want. I'll say so before either of us spends anything, and that rule doesn't loosen once you're a paying client — it's the whole reason the number at the end of a build means something.

Start with the planning meeting

Tell me what the business does and where it's slow. That's enough for me to say whether it's a fit and book the meeting.

Not ready to pay for anything yet? There's a free two-week Proof Run: one job, built and measured, and you keep it either way.

Tell me where the business is slow

Two or three sentences. What the business does, what your team does by hand, and roughly what it costs you.