Work
Twenty-three years of work. The systems below are where most of the last fifteen years has gone.
A cloud platform supporting the delivery of healthcare services, built from the ground up and in continuous production for ten years. We designed the original architecture, built the system, and have developed and supported it ever since as the business has changed around it.
Ten years of continuous extension is the real test of a system’s design. Software that cannot absorb a decade of change gets replaced in year four. This has not been.
Dental Technique is an Australian dental laboratory running two connected businesses — a B2B lab serving dental practices and other laboratories, and a consumer-facing clinic. The operational complexity sits in the overlap: different clients on different pricing, cases moving through production with material traceability requirements, and two quite different sets of customers looking at the same lab.
We are building two linked products. A marketing website with a CMS the team manages themselves, and a business management portal covering quoting, invoicing, per-client pricing, material traceability, audit logging, dispatch, time tracking, machine scheduling, granular permissions and patient management.
The engagement started with structured discovery rather than a specification — sessions covering the full case lifecycle, roles and permissions, scheduling, pricing, compliance and reporting — before any architecture was drawn.
A startup with a product idea and no engineering. Discovery started in 2016, two years before anything shipped — working out what the product actually needed to be before committing to an architecture. It launched in 2018 and we ran its development for seven years in total, through multiple rounds of investment, as the product and the company changed shape around it.
Building through funding rounds is a specific discipline. The product has to be demonstrable at each raise while the architecture underneath keeps absorbing scope nobody could have specified at the start. Most startup builds solve for the demo and leave a codebase that gets thrown away at the next raise.
This one did not. In 2023 the company rebranded as Sureal and moved development in-house, and the system went with them — the foundation the internal team took over, rather than something they had to replace. Seven years of accumulated product decisions survived the handover intact.
Outdoor seasonal cinema concentrates a year of ticket sales into a few months, across multiple cities, with demand spiking hard the moment a season is announced. We built the platform and then ran it for seven years — hosting, operations, seasonal campaigns and the day-to-day management of a system selling tickets to the public.
The business was acquired by Event Cinemas and the platform moved with it.
A public arts institution publishes constantly and unpredictably — exhibitions, programmes, events, and an annual competition with its own submission cycle arriving in a rush once a year. We built and managed the website, the systems behind the annual competition, and the campaign work alongside it, for nine years.
The Centre built an internal digital team and took the work in-house.
A booking and appointment scheduling system for community service delivery, and the public site around it.
The organisation funded the platform through government grants. When that funding ended the service was wound down and the site retired. The system worked; the funding did not continue.
A national campaign site, built and supported by us, and still running after a decade. Deliberately simple — it does one job, it has needed almost nothing from us in ten years, and it has never gone down. Not every system needs to be large to be worth keeping.
2003 – 2011
Our first eight years, for large companies who noticed detail.
No pitch, no obligation — if we are not the right fit we will say so.
