Before you brief anyone

Notes for the person deciding whether to build something, and what to build first. Budgets, timelines, the trade-offs nobody mentions until the invoice arrives. Nothing here is written for other developers: if a piece cannot help you decide something or ask a better question, it does not get published.

7 articles so far, in four groups: what an internal tool costs and how it is scoped, what changes when the product lives on a phone, how automated tests earn their keep, and what it takes to release and keep something alive. New ones arrive every few days — the schedule is set, so the queue does not depend on anybody remembering.

Marketplace development: what it costs and how long it takes

Marketplace development

The parts of a marketplace that only break after launch

The demo always works. What fails in month two is the paid order whose seller was banned, the deposit that half-arrived, and the dispute about a file nobody kept. A list worth reading before you sign anything.

5 min read
What we build

Reading rather than deciding? The case studies are the same arguments applied to two real products, with the prices, the timelines and a demo you can open on sample data.