Custom software & AI infrastructure
What actually holds your operations together?
The honest answer is: you do.
I build custom software and AI infrastructure for businesses adopting AI into their operations — wired into your real stack, tools and data, with AI configured alongside it.
One builder. The person who scopes it is the person who ships it.
Mapped source
The numbers that only one person can reconcile.
Read, written and checked by the system instead of by hand, against the sheet you already keep.
You already bought the AI. So how are you using it?
ChatGPT is open in a tab. Someone tried a tool. Someone ran a pilot. And the way work actually moves through the business hasn't changed at all.
That's not a tools problem. Most businesses have a coordination problem wearing a technology costume, and AI dropped onto that mess just makes the mess move faster.
A business is only as steady as the system underneath it.
- 01
The tools aren't the problem.
Nothing is wired together, so nothing can see anything else.
- 02
AI can't work on data it can't reach.
Half the operation lives in spreadsheets and someone's memory.
- 03
The owner is the integration layer.
Every handoff goes through one person. That person is you.
The system underneath, then AI on top of it.
Custom software wired into the tools and data you already run on. AI configured to work alongside it and earn its place.
One view of the whole operation
Entities, functions and workflows that currently can't see each other, pulled into a single live read instead of an end-of-month reconstruction.
The manual middle, gone
Reconciliation, document handling, routing: the work that lives between systems and lands on a person, streamlined and automated.
Intelligent design
AI integrations handling the predictable patterns across your work.
Map the operation. Build the system. Wire in the AI.
I walk through the whole operation and map every part of it, then architect and build the system around efficiency, cost effectiveness, fault tolerance and how you actually want to work, bringing custom software, automation workflows and AI together into one integrated system.
- Step 01
Map the operation
Every part of it, as it actually runs.
- Step 02
Build the system
Efficient, cost effective, fault tolerant.
- Step 03
Wire in the AI
One integrated system, not a pilot.
Software that changed how the work runs.
Some deployed with clients, some built to prove the pattern. What each one replaced, and what it does now.
- 01
Audit Room
deployedA persistent AI analyst built on a firm's own data, answering questions with grounded, cited responses and a full audit trail. Institutional knowledge made queryable, so it doesn't walk out the door when someone leaves.
- 02
Ledger
deployedInstallable software for bookkeepers that catches reconciliation errors, duplicates and mismatches before they reach the books.
- 03
Counterstock
proof of conceptA live operations system for workshops. Jobs, parts and daily flow in one real-time view instead of scattered across whiteboards and spreadsheets.
- 04
Meridian
status tbcCloses the gap between what's sold and what's delivered, so commitments don't slip between teams.
Common questions.
Do we have to start with an audit?
Usually, yes. It's how the work gets scoped honestly before either side commits to anything. It's free and takes 40 to 60 minutes.
Who owns what you build?
For a full custom build, you do. Every line is yours on payment, self-hostable, no lock-in and no per-seat pricing — you could hand it to another developer tomorrow and owe me nothing. A Claude environment setup is different: the runtime is a subscription you hold, and the formats and setup are portable files you keep.
What does it cost?
The audit is free. A Claude environment setup starts at $2,000 AUD one-time. A full custom build starts at $4,000 AUD with 20% to begin, quoted after the audit so the scope is real before the price is.
How much of our time does this take?
The audit is 40 to 60 minutes. A build needs a few hours across the first fortnight — mostly showing me how the work actually happens.
Can you work with our existing tools?
That's the usual shape of the work. Xero, MYOB, Karbon, ServiceM8, simPRO, Cliniko, Tradify and similar. Nothing gets replaced unless replacing it is the point.
What if we already have someone technical?
Then you probably don't need me. If you've got in-house developers, this isn't the right fit and I'll say so on the call.
Start with a map, then a design.
A 40–60 minute operational diagnostic. I map your business end to end, find where you're losing time and money, then we walk through what's worth building.
Stop being the system. Use one instead.
Built around what matters most to you. And if you don't need to build yet, I'll tell you.