I build technology that solves real problems — not technology that looks impressive.

Most of what I build starts with the same conversation. An owner describes their week, and somewhere in the middle they say something like “and then I write it in the book” or “I have to text everyone the night before.” That sentence is usually the whole project.

I'm a developer who works on the operations side of small businesses — the part that happens after the website. Booking that respects a real schedule. Orders that arrive somewhere organized. Customer records that survive a staff change. Payroll that isn't reconstructed from memory in April. The unglamorous parts that decide whether a business feels calm or chaotic.

Some of the systems in this portfolio are client work. Some are businesses I own and operate myself — which means I've also been the person answering the phone at 7pm, and I know exactly what a badly designed admin screen costs you on a busy day. Everything here is labeled with which is which.

I care a lot about honesty in software. A dashboard that shows a guess styled like a measurement is worse than no dashboard. A system that quietly drops a lead when an email provider goes down has failed at the one thing it existed for. That principle — build it so it tells the truth, including when something is broken — runs through all of it.