Custom software

What it usually is

A process that lives in spreadsheets, mails and someone's head. An internal tool that grew for ten years and now slows everyone down. A customer portal that a standard product almost covers, but not quite. I design and build the thing that fits.

How it goes

1. Two days on site. I sit with the people who do the work and watch. Most of what a brief says is wrong in useful ways.
2. A prototype in the first two weeks. Clickable, with real data where I can get it. We argue about the prototype, not about a document.
3. Build in short rounds. Every round ships something the team can use on Monday. Design and code come from the same hands, so nothing gets lost between them.
4. Hand over properly. Documentation, a clean repository, and a session with whoever maintains it afterwards.

What you get

Software that people open without being told to, because it is faster than the workaround. A codebase your own developers or the next agency can read. And a clear line of what to build next.

Good fit

Companies from ten to a few hundred people with a workflow that costs real time every week. Less good: greenfield consumer apps that need a large team from day one.