Legal and contracts
Contract tools get things signed. This is for what happens next: the register of agreements in force, what each one obliges you and the other side to do, who signed it under which delegation, and making sure nothing renews or lapses by accident.
Written for the people who carry this
The General Counsel
The contract repository holds PDFs. Nobody can list the obligations the organisation has actually accepted, or show that a signature was within the signer's authority.
The contract owner
Renewal dates live in calendar reminders. Notice periods are missed, and an auto-renewal is discovered after it happened.
The Chief Risk Officer
Contractual obligations are a risk category with no register behind it, so a breach is found by the counterparty first.
One app, built to be extended
Contract management
What happens after a contract is signed: the register of agreements in force, and the obligations each one places on you and on the other side. Contract tools get things signed; this is for making sure the commitments inside them are actually met, and that nothing renews or lapses by accident.
Contracts · contract obligations (open, met, breached, waived)
How it connects. A leased or subscribed asset points at the contract that governs it (operations). Supplier and customer accounts (operations) carry their own terms; the contract register holds the agreement.
Signed by a person, under an authority, with an entity.
A contract on Zubl names the contracting legal entity from entity governance, the signatory from the people list, and the delegation they signed under — so "could they sign this?" has an answer. Its obligations are records with owners and due dates, chased as tasks, linkable to the risks and compliance obligations they create.
Extend these apps, or build the one you need.
Every app here is open to extension on the same licence: a field, a lifecycle state, a link to a record in another family, a rule. Additions sit beside our definition and survive every upgrade.
And if the register your organisation needs is not here, describe it to the AI builder. It arrives governed — same access engine, same audit trail, same reports — because those belong to the platform, not to the app.
Every family is included on every plan
Governance, risk and compliance
Entities, delegations, risk, obligations, incidents, sensitive registers, insurance, audit and policy — on one model of the organisation.
Strategy and delivery
From a strategic plan to the objectives, projects, products, releases and sprints that deliver it — with measures, not slideware.
Operations
Assets, items, customers and suppliers, expenses and travel — the operational registers that feed finance and usually live in five systems.
Finance
The chart of accounts, dimensions, periods and journal that operational apps post into — foundations, stated honestly as foundations.
People
The workforce register: who works for you, on what terms, doing which job — employees, contractors, agency and supplied workers, secondees, affiliates — with the evidence employment law expects.
Community services
Volunteers and supporters, for not-for-profits: the people who give time and the people who give money, as relationships on the same people list — not two more lists.
We're working with design partners now.
A small number of organisations shaping the first release, in exchange for early access, direct influence over what ships next, and pricing that reflects the risk of going first.