Guides
What we have learned building the software that runs a business.
Most of what breaks in a business is not the software. It is the space between the systems, which no vendor owns and which therefore falls to you. These guides are what we have learned working in that space, written from the problems Australian owners and operators describe in their own words, and each one carries the date we published it.
By subject
- Everything (4)
- The same number, typed twice (1)
- The spreadsheet that became the system (1)
- Automation that tells you when it failed (1)
- The number the owner actually wants (0)
- Priced the same way twice (0)
- What happens to your data (1)
· What happens to your data · 5 min read
Just use AI and it will fix anything
Two identical kitchens, the same recipe, wildly different dinners. The model is the kitchen. The outcome is the corpus, the rules and the plumbing around it.
· The spreadsheet that became the system · 6 min read
Spreadsheets break, formulas get deleted, and which version is this?
The four ways a spreadsheet fails once it becomes the system of record, the split between the ones that compute and the ones that join, and how to count both.
· Automation that tells you when it failed · 5 min read
Stop fighting your software and fix the plumbing
Most connections between business systems exist because they could be built, not because anyone named an outcome. The test, and four ways a connection lies.
· The same number, typed twice · 6 min read
The sunk-cost trap
You did the due diligence, bought the advanced feature, and found a basic one missing. Why the answer is usually connecting around the gap, not replacing it.
The guides describe the work. How an engagement runs →