Guides for people deciding whether to build something
Commissioning software is mostly an exercise in uncertainty. These remove some of it — including the parts where the honest answer is “don’t build this”.
AI for business
Where AI genuinely helps, where it does not, and what it costs.
-
How much does AI automation cost?
What drives the cost of an AI feature: the build, the per-use bill that arrives monthly, and the design decisions that make the difference between pennies and a runaway invoice.
Read the guide → -
Should I use AI in my business?
A plain-English way to decide whether AI belongs in your business at all — what it's good at, what it isn't, what it costs, and when ordinary software is the better answer.
Read the guide → -
When should you NOT use AI in your business?
The cases where AI is the wrong tool: exact answers, unverifiable output, low volume, broken processes, and anything a rule would handle better.
Read the guide → -
Where should an established business actually use AI?
A practical test for where AI earns its place in an established business, where it does not, and why the boring applications pay best.
Read the guide →
Internal systems & CRM
Whether to build your own, and what it should actually contain.
Spreadsheets to software
When a spreadsheet has outgrown itself — and when to leave it alone.
Starting a software project
How to commission software when you are not technical.
-
What does custom software actually cost?
What drives the price of custom software, why a first version costs less than people expect, and the running costs nobody mentions until later.
Read the guide → -
What should version one of a new product contain?
How to scope a first version that proves something, why most version ones are too big, and the single question that decides what goes in.
Read the guide →
We’re writing 42 more across these topics, and publishing them as they’re genuinely useful rather than all at once. If there’s a question you want answered, ask us directly — it’ll probably become a guide.