I build

Job orders routed on paper. Appointments in one sheet and the records they produced in another. Approvals that live in an email thread nobody can find. These are the systems a business runs on and nobody sells, and they are the work I do most. I start by watching how the job is done today rather than guessing at a schema, then build the tool that absorbs it: roles, approvals, records, and an audit trail that tells you who changed what.

Start here if your team runs a real process on spreadsheets, paper or an email thread, and nobody can say who changed what.

Full builds where the interface is only half the work. I design the data model, write the API, build the front end against it, and take the whole thing to production. Auth, roles, background jobs, file handling, and the unglamorous parts that decide whether an app survives its first hundred users are part of the scope, not a later phase.

Start here if you need the whole product built rather than the screens: schema, API, interface and the deployment behind them.

A site that is slow, unmaintainable, or stuck on a stack nobody supports any more. I audit what is there, keep the URLs and the rankings, and rebuild the rest on something you can still edit in two years. Migrations run behind a redirect map so traffic lands where it did before, and the performance work is measured before and after, so what you get is a set of numbers rather than a claim.

Start here if you have a site that still works but fights you, and you cannot afford to lose its URLs or its rankings.

Three years of WordPress work, mostly the parts other developers avoid: custom blocks in PHP, an editor a non-technical client can actually use without breaking the layout, and theme code that survives the first plugin someone installs. When the front end deserves better than a theme, I keep WordPress as the editor and serve the site from Next.js.

Start here if you want a site a non-technical colleague can edit without it breaking the first time a plugin is installed.