19 years shipping software · remote, worldwide

The engineer you call when it has to work this week.

I build products end to end and rescue the ones that broke. Founders and small businesses hire me to ship real software fast — deliberate, tested, and made to last — without breaking what already works. Most of them keep me around long after the first thing is done.

Tell me what's broken Read my notes Reply within a day, usually within an hour.

19 yrs

Writing production software

Dev → CTO

Contributor, lead, and technical founder

Side projects launched and maintained solo

< 24h

Typical time to a first answer

How people usually work with me

01 / Rescue

Urgent fixes and firefighting

A broken checkout, a site that fell over after an update, a bug that only happens for one customer at 3am. I diagnose first, patch fast, then tell you honestly what still needs doing properly.

Often same-day · fixed fee once scoped

02 / Build

Ship the thing end to end

Web apps, APIs, admin tools, mobile apps. One person who can take a rough idea through database, backend, interface and release without three handoffs and a project manager in between.

Weekly rhythm · demo every Friday

03 / Partner

The developer you keep on retainer

For teams with a product and no in-house engineer: someone who already knows your stack, watches the boring failure modes, and picks up the phone when something changes.

Ongoing · a set number of days a month

Rush work

Something is down, and nobody knows why.

Send me access and the symptom. I'll tell you within a couple of hours what's actually wrong, what it takes to stop the bleeding, and what should be fixed properly afterwards — in plain language, before any invoice exists.

Start an urgent fix

01 Production outages and post-deploy regressions

02 WordPress and WooCommerce sites gone slow, broken or compromised

03 Payment, auth and integration failures losing real orders

04 Data problems: bad migrations, corrupted records, lost rows

05 Projects abandoned mid-build by the previous developer

Building, not generating

Real software, in an era of software that almost works.

It has never been easier to produce a demo that falls apart the moment a real customer touches it. I use modern tools — AI included — the way a good builder uses power tools: to go faster, never to skip understanding what I'm shipping.

That means code you can hand to the next person, decisions I can explain, data models that hold up under load, and the boring edge cases handled before they become a 3am message. Sixteen years of shipping is the part a prompt can't fake.

Made to be handed off

Readable code, real tests, and a short doc that means the next developer — or you — is never locked in to me.

Built for load, not for the demo

Data models, queries and failure paths that behave the same with ten users and ten thousand. The hard part is the part nobody sees.

Decisions you can question

I can tell you why every meaningful choice was made, in plain language. Nothing in your product is a black box neither of us understands.

Where I've sat

Developer, then lead, then CTO of two early-stage startups — and ten side projects of my own that taught me what founders actually feel when a release slips. I've been on both sides of the estimate, which is why mine tend to hold.

2007 — 2013

Developer, agency and product teams

Client work across a lot of stacks. Learned to be dropped into unfamiliar code and be useful the same week.

2013 — 2017

Lead developer

Owned architecture and releases, mentored juniors, and did the unglamorous work of making deploys boring.

2017 — 2020

CTO, early-stage startups

Two companies from prototype to paying customers. Hiring, technical strategy, and the tradeoffs behind every roadmap.

2020 — now

Developer and technical founder

Working directly with founders and small businesses. Developing my own products and maintaining them.

Notes from the work

All writing →

Startups