Apps and internal tools
Small web applications built for one job. The spreadsheet that quietly became a system. The manual process that eats a morning every week. The SaaS subscription that does too much and still not quite enough.
What counts as a tool
Internal dashboards, quoting calculators, booking and intake flows, data clean-up jobs, and integrations between systems that refuse to talk to each other. If your team runs on a spreadsheet with rules everyone has to remember, that spreadsheet is usually the candidate.
Try one first
Two of my own tools are public: URL Valet, which went from idea to live product in a day, and a colour contrast checker. Both are built the way client tools are built, and the account of building URL Valet is in the writing section.
You own it
A tool you commission is yours: the repository, the accounts, the data. If I vanished tomorrow, your tool would keep working and any developer could pick it up. That is a deliberate design constraint, and I build to it from the first commit.
Price
Scoped and priced per project, after a discovery call. You get a written figure before any commitment, and if the honest answer is that an off-the-shelf product already does what you need, I will name it instead.
Related: custom websites · support