AI Automation
Agents, workflows and integrations that replace the manual process eating your week. Built to run unattended and to fail loudly when they should.
Read moreAI automation & search growth
I build the automationand the visibility that actually runs
Most automation projects die in a slide deck. Mine ship. I replace the manual process that is eating your week, and I make sure the right people find you in Google and in ChatGPT. You work with me directly. No account manager, no junior doing the real work.
- Reply within 24h
- Work ships in days
- You own the code
1
Person you talk to, brief to launch0
Account managers in the way100 %
Of the code and accounts are yours24 h
Maximum reply time on any enquiryWhat unattended means
Software that does the job while you sleep
An automation that needs someone to babysit it is not an automation. It is a second job with extra steps.
What I build runs on a schedule or a trigger, handles the cases that go wrong, tells you when something needs a human, and keeps a log you can read afterwards. That last part matters more than people expect. When a process runs unattended for six months, the log is the only way to know it did the right thing.
- Retries and backoff, so a flaky API does not silently drop work
- A dead-letter queue for the records that fail, not a swallowed error
- Alerts routed to the person who can act, not to a shared inbox
- Plain-language logs you can search without me
# runs every 5 minutes, no one watchingintake-agent --source=forms --dry-run=falsefetched 14 new enquiriesclassified 14 / 14 (routing rules v3)enriched 12 with firmographics2 missing domain -> queued for reviewcreated 14 CRM records, 0 duplicatesdone in 6.2s next run 09:05What I do
Five things, done properly
I would rather be genuinely good at five things than mediocre at twenty. Each of these is a full practice, not a line item.
AI Search Optimisation
Rank in Google and get cited by ChatGPT, Perplexity and AI Overviews. Technical foundations first, then the content and entity work that answer engines actually read.
Read moreHealthcare Marketing
Patient acquisition for clinics, dental groups and medical spas. Written by someone who knows what you can and cannot say, and why your intake form is the real bottleneck.
Read moreWhite-Label Fulfilment
I do the work, your agency signs it. Senior output under your brand, with deadlines that hold and reporting your account managers can hand straight to a client.
Read moreWeb & Conversion
Fast WordPress and Shopify builds, landing pages that load in under a second, and CRO work driven by what the session recordings show rather than what a checklist says.
Read moreThe numbers are the point
Every case study on this site lists where things started, what I changed, how long it took and what happened next. If a number is not verifiable, it is not on this page.
Receipts
Real projects, real numbers
Not logos on a wall. Each one shows the starting point, the method and the result, so you can judge whether the same approach would work for you.
Built a multi-tenant agency portal in Laravel + Filament in 6 weeks
Read the breakdownMigrated a 1,200-page healthcare network from Wix to WordPress without ranking loss
Read the breakdownCut a derm group’s cost-per-lead 64% in 90 days while doubling consult volume
Read the breakdownHonest comparison
Working with me vs. hiring an agency
An agency is the right answer for some jobs. If you need six specialists across five channels and a dedicated account team, hire one. Here is the honest difference for everything else.
| What matters | Working with me | Typical agency |
|---|---|---|
| Who does the work | Me. The person on the call is the person writing the code. | A junior, supervised by whoever sold you the project. |
| Time to first shipped thing | Days. Usually the first working version inside a week. | Weeks of onboarding, then a phased roadmap. |
| Who owns the code | You. Your repo, your cloud accounts, your API keys. | Often the agency, on their platform, until you leave. |
| Commitment | Project by project. No minimum retainer. | Six or twelve month retainer, usually with notice periods. |
| Reporting | Direct access to the dashboards and the logs. | A monthly deck summarising the dashboards. |
| Breadth | Five practices, deeply. I say no to the rest. | Everything, at varying depth. |
| When something breaks at 11pm | You have my number. | A ticket, triaged tomorrow. |
| Capacity | Limited. I take a handful of projects at a time. | Scales with headcount. |
Before you ask
Questions I get every week
Are you an agency?
No. I am one senior operator who takes a small number of projects at a time. For larger builds I bring in specialists I have worked with for years, but I stay on the project and I remain the person you talk to. Nothing is handed to a junior after the sales call.
How fast can you actually ship?
A focused automation is usually running in production inside a week. A full silo of search work takes longer because the results take longer, but the technical fixes land in the first few days. I will give you a date in the proposal and I will tell you before the date if it is going to move.
Do I own what you build?
Completely. The code goes in your repository. The automations run in your cloud accounts on your API keys. The tracking lives in your analytics property. If we stop working together, you lose nothing and you do not need my permission to keep running any of it.
Do you work on retainer?
Only if it genuinely suits the work. Most engagements are fixed-scope projects with a defined deliverable. Ongoing search and automation programmes do work better as a monthly arrangement, and in those cases I will say so, but I will not put you on a retainer to do a job that has an end.
What does it cost?
It depends on scope, which is why the quote form asks about the problem rather than the package. As a rough guide, a single automation build starts in the low four figures, a technical search engagement is a few thousand, and a full site build with conversion work is more. Tell me what you are trying to fix and you will get a real number, not a range.
Insights
Notes from the work
Build logs, benchmarks and opinions. No recycled listicles.
Why this site exists, and what you’ll find here
Notes on the publishing rules, what gets through editorial, and how to use the search.
ReadCursor vs Claude Code vs Windsurf for backend work — 90 days in
Same backend feature set, three editors, three months. What changed about how I work.
ReadVercel AI SDK vs Mastra vs raw Anthropic SDK — production comparison
Three weeks shipping the same agent on three SDKs. Latency, token cost, ergonomics, failure modes.
ReadNext step
Tell me what is broken
One paragraph is enough. You get a straight answer on approach, rough cost and timeline. If I am not the right person, I will say so and point you somewhere better.
- Reply within 24h
- No retainers required
- Straight answer either way