Mar 18, 2025
Growth
Read time: 3 min read
If a platform already exists for your industry, your branded system is usually running within weeks. A system built from scratch has a working first version in your hands within the first few months. Either way, it keeps improving monthly, because a business system is never finished.
Weeks, if a platform already exists for your industry. I have built compliance platforms for builders, operations systems for trades, and care-minutes dashboards for aged care. If your business is in one of those lanes, your branded, single-tenant system is deployed from that platform and configured around your processes. Discovery, configuration, integrations, go live: usually inside the first month or two.
A few months to a working first version, if the system is new. Discovery takes a week or two, including a day on site if it is practical. Then the first version, with the core records and the integrations that matter most, is in your hands within the first few months. From there it improves monthly.
The question is how much of what you need already exists. The honest way to find out is a call: you describe what the business runs on today, I tell you how much of it I have built before and how much is new.
A business system is not a website. The business changes, so the system has to. New staff, new compliance requirements, a new service line, a new integration. Every month there is something.
That is why I work on a monthly engagement rather than a fixed-price build. The job is not to deliver something and walk away. It is to keep the system useful. Clients get a release most months and talk to the person who built it, not a support desk.
In my experience, two things. Not being able to get a decision from the business quickly, and not having access to the systems that need connecting (Xero, rosters, email). Both are fixable on day one if you know to expect them.
Write down what the business runs on today: the apps, the spreadsheets, the folders. Bring that list to a call and I will tell you which answer applies to you and roughly what it costs.
One email when a new article or case study goes up. No drip sequence.
Plain writing on operations, compliance and the systems businesses actually run on.
Oct 7, 2026
Engineering
Every MCP server loads its tool list into an agent's context before you type. Why that costs accuracy and speed, and why I build CLIs instead.
Oct 7, 2026
Operations
How an aged-care provider moved care-minutes and AN-ACC reporting from a quarterly spreadsheet to a daily dashboard on roster, clinical and Medicare data.
A 30 minute call. You describe the spreadsheets, the apps and the paperwork; I tell you what I would build and roughly what it would cost.