What it costs, before you ask.
Every price below is the fixed price for the scope described, not a starting point that moves once we talk. Each row links to a page that says exactly where that job ends and what it does not cover — and, for most of them, shows the thing it produces.
Quick jobs · one to three days
Fix a broken automationYour scheduled job stopped. I find out why, fix it, and add a check so you hear about the next one from me rather than from a customer.1–2 days$300Watch it run →Server RescueYour app moves off expensive hosting onto a server you own for about $10 a month — set up properly, secured, and backed up every night.2 days$600Start a rescue →Spreadsheet KillerThe spreadsheet somebody rebuilds every month becomes one button, with a short video showing anyone in the office how to run it.3 days$750See the output →Launch websiteA one-page website in your name, live seven days after you send me the text and images. One payment, no subscription.Live in 7 days$650Five pages instead of one: $1,200Get my site built →Full builds · one to two weeks
Report RobotThe report someone assembles by hand arrives in the right inboxes on schedule — and tells me if it ever fails to.1 week$1,200See the output →Doc & Inbox AgentInvoices, forms and emails become rows in your system. Anything the software is not sure about goes to a person instead of being guessed.1–2 weeks$2,200Entirely on your own hardware: $3,200Watch it run →Lead EngineLeads from several places, scored against your best customers, duplicates removed, written into your CRM, with a summary each morning.2 weeks$1,800See the output →Content PipelineOne subject becomes a finished, published video in your voice, on the days you choose, without ever repeating itself.2 weeks$3,200Each further channel, white-label: $1,200Watch it run →Site AssistantVisitors ask a question and get an answer from your own pages, with a link to the one it came from. If your site does not cover it, it says so.2 weeks$3,500Entirely on your own hardware: $4,500Watch it run →AI Search VisibilityFind out whether ChatGPT, Perplexity, Claude and Google's AI name you or a competitor when someone asks what to buy.One report$350See the output →Keeping it running · optional
WatchI keep watching it after handover: alerts when something breaks, a named response window, up to two hours of fixes a month, and a note on what it processed.Per month$250/moUp to 2 hours of fixes · next business daySee the output →October: three founding-client spots. 20% off any fixed-price build started in October, in exchange for a short written case study I can publish with your name on it. Three spots, first three signed.
Included in every build: Deployed to infrastructure you own · logging and alerting that reaches a human · a one-page runbook · the source in a repo you control · thirty days of fixes at no charge.
If I cannot deliver it, you get the deposit back. Half up front, half on handover. If I get into it and cannot build what we agreed, I tell you as soon as I know and refund the deposit in full — I would rather return the money than hand over something that does not work. If you stop the project yourself, the deposit covers the work already done and you keep everything finished to that point, including the code.
Rather pay by the hour? $65 an hour, billed weekly, with an estimate before I start and a check-in before it runs past it. Good for small fixes, changes to something you already have, or work that is hard to scope. Anything I can scope properly, I will also quote as a fixed price so you can compare.
The list is the common jobs, not the limit. If someone on your team does something by hand, over and over, I can probably build it. Describe it in a couple of lines or take fifteen minutes on a call, and I will tell you straight whether it is worth automating and what it would cost, usually the same day.
What is that job costing you now?
Four numbers you already know. No email, nothing sent anywhere — the arithmetic happens in your browser and stops there.
That pays for itself inside six months. This is the shape of job worth automating.
Tell me about this jobRough figures, usually enough to tell a job worth automating from one that is not. The table on the home page uses the same arithmetic: 48 working weeks a year, 80% of the task automated because someone still checks what the software flags, and a loaded cost of $28 an hour. "3-year savings, after the price" is three years of savings minus what the build cost, before your server and any model costs, usually $10–50 a month. They are estimates from the scope each build covers, not measured client results — there are none of those to show yet, and made-up ones are the one thing this site will not do.
You know the price before I start.
Tell me what's eating your time
A few lines by email, or a 15-minute call. I reply the same day.
You get one fixed price
What I'll build, when it's done, and what it costs. If it takes me longer, you don't pay more.
It's up and running
Set up in your name, with an alert if anything breaks and plain instructions. Fixes are free for 30 days.
You own what I build.
- Your server
- It runs on infrastructure in your name, rented from a provider you pay directly. Never from me.
- Your repository
- The source goes into a repo you control, with the commit history intact.
- Your copyright
- You own the work outright. There is no licence to renew and nothing to keep paying for.
- Your data
- It stays on your machine. Several of these can run with no external API calls at all.
If you stop working with me, nothing switches off. That is deliberate: the alternative is a business built on making you unable to leave.
Who this is for, and who it is not.
A good fit if
- You already know which job is eating the hours — you could name it right now.
- It runs on a schedule, or it repeats: every week, every month, every invoice.
- You want to own what gets built, on your own server, with the code in your hands.
- You want a number you can plan around — a fixed price, or an hourly rate with a cap.
Probably not if
- You want someone to sit in your standups and take tickets — that is a hire, not this.
- The job changes shape every time it runs, so there is no pattern to automate yet.
- You need a big-team build with a project manager and a six-month roadmap.
- You are choosing on price alone. Every price here is published and fixed, but it will not be the lowest quote you get.
The things people ask before they commit.
What if it breaks after you hand it over?
Thirty days of fixes are included at no charge. After that you can either fix it yourself — the runbook and the source are yours — or put it on Watch at $250 a month and I keep it alive. Plenty of people take neither, and their systems keep running.
Why not just use Zapier, Make or n8n?
For something small and stable, use them — genuinely. They fall down when the volume grows, when the cost per run adds up, when you need a step they do not have, or when a vendor changes a screen and the whole flow quietly stops. What I build is real code you own, with logging and alerts, so a failure reaches a person.
What does it cost to run once it is built?
Usually a small server, around $6 to $15 a month, paid by you directly to the provider. If the build calls a paid model or API, that cost is yours too and I will estimate it before we start. None of that money comes to me.
How does payment work?
For a build: a fixed price, half up front and half when it is live. If it takes longer than I estimated, that is my problem, not your invoice. For smaller or open-ended work you can pay by the hour instead — $65 an hour, billed weekly, with an estimate up front and a check-in before it runs past it. Monthly cover is optional; most people do not need it.
How quickly do you reply?
The same day, usually within a few hours. If a job is not a good fit for me I will say so in that first reply rather than waste your week.