About

I run the infrastructure these sites live on. Not a reseller account with someone else's logo on the invoice — actual servers I administer: the reverse proxy that terminates TLS, the database, the deployment pipeline that ships a change to production, and the monitoring that tells me when something stops answering. When a site I built goes down at 9pm, there is nobody for me to open a ticket with. That is the arrangement, and it is the reason I am careful about how these things are built in the first place.

Most agencies hand you off — a designer who leaves after the mockups, a developer you never speak to, and a hosting company that has never seen your site. Every one of those handoffs is a place where something gets lost and nobody is accountable for it. Here there is one person to ask, and that person has access to every layer of it.

The businesses I do my best work for are small ones where a website has a specific job — getting the phone to ring, filling a booking calendar, making it obvious what you sell and how to buy it. I am not the right call for online stores with large catalogues, marketplaces, or anything needing payment processing and inventory; I would rather say that here than three weeks into a project. Everything else is remote, so where you are does not matter.