Business resources
What to read before you hire anyone — including us.
Everything here is written for the person paying for the software, not the person building it. No gated downloads, no email wall.
Before you commit to anyone
The questions worth asking any developer or agency, and what a good answer sounds like.
How an engagement actually runs
The method, week by week
The questions you're actually thinking
Work out which problem you have
Most operators arrive in one of six situations. Each page describes the symptoms and what the first week does about it.
Recovering from a bad build
Outgrowing your tools
Modernizing a legacy system
Drowning in spreadsheets
See it done
Written up in full — what arrived, what the verdict was, what got built, and what it does now.
Success stories
Notes from inside real builds
Read enough? The next step is a week.
One written verdict, an architecture, and a plan you could hand to any engineer — including one who isn't me.