Proof
What this looks like in practice
16-store optometry group
The problem
Around $600,000 a year of digital spend with no reliable attribution, figures nobody trusted, silent system failures, and more than ten logins per store.
What we did
One on-site workshop day produced a validated architecture map, a force-ranked opportunity list and two fixed-price scopes. Discovery surfaced eight months of work built against the wrong service, a three-month silent booking-email outage, and patient data leaving Australia.
Where it landed
A $5,000 workshop led to scoped foundation work. The first data pipeline was proven end to end and deployed. A multi-phase platform roadmap followed.
NDIS provider, 30+ support workers
The problem
Roughly $150,000 a year of manual reporting labour. Twenty to thirty percent of shift notes going missing undetected. Incident reports with no alerting behind them.
What we did
Discovery produced a before-and-after table with about $125,000 a year of addressable savings, and a phased roadmap built on the Microsoft stack they already pay for. No replatforming. No rip-and-replace.
Where it landed
A discovery engagement and a proposed phased roadmap. Gap detection on shift notes, incident alerting, and plain-English answers from their own data sit on that roadmap as later work. Each phase priced separately so they could stop at any point.
Start with one conversation
If one of these problems sounds like yours, tell us. We will say whether we have done this kind of work, and what a first fixed piece would be.