Melbourne · Since 2003
We build the systems businesses run on.
Twenty-three years in Melbourne. Some of our systems we still run. Some were good enough that somebody else took them over.
Years building software in Melbourne
Years our longest-running platform has been live
Systems built, operated and supported
Handed to acquirers or internal teams, not replaced
The difference
Anyone can launch software. Very few build it to be handed over.
Most business systems fail slowly. They are built by someone who understands the technology but not the operation, they go live, and then the person who designed them moves on. Three years later the business is working around the software instead of with it.
Ours have gone the other way. One has been in production for a decade and is still being extended. Others ended because the client was acquired, or raised enough money to bring development in-house, or grew large enough to build their own team — and in each case the system we built went with them rather than being replaced.
That only happens if the architecture was right at the start and the code was written to be read by someone who has never met us.
What we do
Three things, and we say no to the rest.
Business systems
Cloud platforms that run an operation end to end — jobs, quoting, scheduling, production, dispatch, invoicing, reporting, roles and permissions. Built for a specific business rather than configured from a template.
Websites and applications
The customer-facing side, built to the same standard and connected properly to the systems behind it. Websites, ecommerce, client portals, iOS and Android.
Support and continuity
We host, maintain and keep developing what we build. We also take on systems built by someone else and left without support, which is a more common problem than it should be.
How the work gets delivered
Small by design, with a decade-old delivery partnership behind it.
Dean Tsoupas runs discovery, designs the architecture and stays with the system afterwards — the same person you will be speaking to in year six.
He also builds. He reads and writes the code, works directly in the database, and traces the faults himself. That matters more than it sounds: the person who sat through your discovery sessions is the person who can open the system and find the problem, so nothing is lost being handed to someone who was not in the room.
Development is delivered with Jetbro, a team in Ahmedabad led by Sharva Jethwa. We met in Melbourne fifteen years ago and worked together on projects here before he returned to India and founded the company. We have been building together ever since. It is the same people on every project, and they know these codebases as well as we do.
That arrangement is how a business this size takes on systems this size, and it is why there is no single point of failure sitting behind your platform.
2003 – 2011
Eight years of clients who checked everything.
Our first eight years were brand, campaign and digital work for large companies. Nothing shipped without going through several rounds of review by people whose job was to find the flaw in it. That habit — assuming someone will check, and building so it holds up when they do — is the part we kept.
Tell us what the problem is.
Most of our projects start with a conversation about an operation that has outgrown the way it is being run. No pitch, no obligation — if we are not the right fit we will say so.