Work with me
I build with Claude Code, Codex, and whichever model fits the job. They are tools that carry my speed and my creativity; the architecture, the review, and the accountability are mine. Every line is reviewed, tested, and handed to you with the repo, the docs, and the accounts.
Get a written scope in 48 hours
How I work with AI
I build with Claude Code, Codex, and whichever model fits the day. They draft fast. I decide the architecture, review every line, write the tests that matter, and take the call when something breaks.
Nobody hires a photographer for the autofocus. You hire the eye behind it.
How I build
| What the AI does | What I do |
|---|---|
| Drafts code from a written spec | Write the spec and decide the architecture |
| Refactors and writes the first tests | Review every diff and add the tests that matter |
| Explains unfamiliar code fast | Run evals and security checks, and decide what ships |
| Switches between Claude Code, Codex, and other models as the task changes | Pick the tool, direct it, and own the result |
| Works at 2 a.m. | Answer the email at 9 a.m. |
No AI in your auth or payments without a test suite around it.
8 builds on this site, each labelled solo or team, synthetic or live93 Lighthouse mobile on this page’s home, 100 desktop, measured 2026-09-05
Six paths, not a grid
Review credits into Build. Build hands off into Keep-It-Running. No prices on this page: you get a written number before you commit to anything.
A working thing you can click by Friday.
You get
Clock
5 business days. Staging URL by day 3.
Starts with a written scope, not a discovery call.
Replace the spreadsheet that runs your team.
You get
Clock
2 to 3 weeks.
Starts with a half-day look at the spreadsheet and the people who use it.
Cites your documents. Says “I don’t know” when it should.
You get
Clock
2 to 4 weeks.
Starts with your documents and twenty questions your team actually asks.
A site that looks like nobody else’s and loads before they notice.
You get
Clock
2 to 4 weeks.
Starts with your current site, your customers, and what you want them to feel.
Make the systems you already run talk to each other, and tell you what is happening.
You get
Clock
3 to 6 weeks.
Starts with a map of your current systems and the three questions you cannot answer today.
You built it fast. I will tell you what breaks first.
You get
Clock
5 business days.
Starts with read access to the repo and the hosting account.
Monthly fixes, upgrades, and a human who answers.
You get
Clock
Monthly.
Follows a build. It is not sold on its own.
Proof
Live · solo buildRudyAnswers from a verified corpus or refuses.
Production · solo · synthetic walkthroughOFSM Inspection TrackerInspection PDFs become tracked records and the exports the team already uses.
Production · solo · synthetic walkthroughFall Protection RegistryA scattered archive becomes one searchable registry.
Sandbox · solo · synthetic dataShockwatchBlocks approval when the evidence does not add up.
Live · solo buildMeera ServicesA ground-up company website, now in production.What you own
You should be able to keep building without me. The handoff is written for the next engineer, not for me.
Fit
Things break when nobody tests the flows that matter and nobody watches production. Every build ships with tests on the critical paths, a staging URL before launch, and 30 days of fixes. Keep-It-Running covers what comes after.
Your team can, because you own the repo, the docs, and the accounts. If you would rather not, Keep-It-Running is a monthly arrangement you can pause or cancel.
No. Your documents and records stay in your accounts. Demos on this site use synthetic data, and any assistant I build for you runs against your own store with the provider settings that keep your data out of training.
That is the plan from day one. Hosting, database, and AI-provider accounts are opened in your name, the repository is yours, and the handoff document is written for the next engineer, not for me.
A fixed scope means you know what you are getting and what it costs before you commit. Hourly billing rewards slowness. When the scope is still taking shape, we start with a Proof-of-Work Week and decide from something you can click.
They are yours, in your accounts, and I tell you the expected numbers in the scope. Assistants get a cost ceiling so a busy month cannot surprise you.
Not without a test suite around it. Auth, payments, and permission rules get written specs, deterministic code, and tests that fail closed. The model can explain a decision. It does not get to make the rules.
Yes. That is the Production Readiness Review. It covers apps built with any of the AI coding tools, or none. You get a plain-English summary and a ranked list of fixes. It is a review, not a penetration test or a certification.
Scope
Five fields. You pick the budget band; I never quote before I understand the problem. This opens your email app with the message drafted, nothing is stored here.