Why we built this.
The same spreadsheet, in every organisation
Zubl started from a pattern that repeats in almost every organisation with more than one entity or division: the records that run it — who the entities are, who may approve what, what the risks are, who works here and on what terms, what the contracts oblige — live in spreadsheets, maintained by hand, by people senior enough to know exactly how fragile that is.
The software that claims to fix this mostly hasn't. Enterprise suites are bought by the largest organisations and then resented by them: implementations measured in quarters, costs measured in multiples of the licence, and a user experience that pushes people quietly back to the spreadsheets. Everyone else is offered nothing at a price they can defend.
The first observation underneath Zubl is that these are not separate problems. Every one of those records describes the same organisation — the same people, the same structure, the same entities. Build that model once, properly, and every app that runs on it inherits what the spreadsheets can never have: one version, scoped to whoever is looking, with evidence attached.
The second observation arrived with AI. Generating an application stopped being the hard part. What remains hard — deciding access, keeping evidence, honouring where data may live, surviving upgrades, answering questions across it — is exactly what the platform was already built to carry. So the apps became the proof, and the platform became the product: a place where AI-built applications are safe to run.
Four commitments
We will never sell consulting.
Implementation and advisory work belongs to our partners. We won't compete with them for it.
Only you can change your partner.
If you work with an implementation partner, that relationship is yours to end, not ours.
Pricing stays published.
If it changes, it changes on the page, not in a negotiation.
You can always leave.
Full export, open formats, no exit fee.
Honestly: early
Zubl is an Australian company building a new platform. The apps and the builder are in use with design partners now; general availability follows them. There are no customers to name yet, no logo wall and no case studies — when there are, they'll be real ones. Our security position, including what is not yet certified, is published in full.
We are looking for three kinds of people: design partners with a real problem in one of the app families, implementation partners with domain knowledge, and investors who see what we see about where the value in business software is moving. If that stage is disqualifying for you, that's a reasonable position and we'd rather you reached it here than three meetings in. If it isn't, the contact form reaches us directly.