Operations
What you own, what you buy and sell, who you trade with, and what your people spend — as registers that share one organisation model, so an asset knows its custodian, a supplier knows its contracting entity, and an expense claim knows its approver's delegation.
Written for the people who carry this
The COO and operations leads
The asset list is in a spreadsheet, the software licences in another, the cloud resources in nobody's. Nobody can say what the organisation holds, where, or who is accountable for it.
Procurement and sales operations
Items are defined differently in the purchasing system and the sales system. The same organisation is a customer in one and a supplier in another, entered twice, with two addresses.
Finance operations
Expense claims arrive as photos in email. Travel is booked before it is approved. Reimbursement is reconciled by hand against a policy nobody has read.
6 apps, one model underneath
Asset register◦ early access
The register of everything you own or hold — vehicles, equipment, IT kit, software licences, cloud resources — in one place rather than split by kind. Use it to know what you have, where it is, who is accountable for it, what it cost, and when it needs renewing, servicing or replacing.
Asset categories with defaults · assets (physical and virtual), lifecycle from on-order to disposed
Item master◦ early access
The master list of things you buy, hold and sell — goods, services, subscriptions, digital products — defined once and used everywhere. It describes what each thing IS: its identity, unit of measure, classification and specification. What it costs and who supplies it belong to the trading records that point at it.
Item categories · items · variants · item relationships
Item trade◦ early access
The commercial side of the item master: who supplies each item and on what terms, how much stock to hold and where, and what you sell — catalogues, offerings and prices. The item says what a thing is; this says what it costs, where it comes from and how it is sold.
Supplier items · purchase prices · stock policies · catalogues · price lists · offerings and prices
Trading partners◦ early access
Customer and supplier accounts: the trading relationship between one of your entities and an outside party, with its terms, addresses, contacts and electronic routing. Being a customer or supplier is a role a party plays, not a kind of record, so the same organisation can be both without being entered twice.
Payment terms · customers · suppliers, with onboarding and gated activation
Expenses◦ early access
Employee expense claims from capture to reimbursement: receipts, lines, policy checks and approval. Use it to let people claim what they have spent, give approvers what they need to decide, and hand finance a clean, evidenced record.
Expense types · per-diem and mileage rates · claims · lines with receipts
Travel◦ early access
Business trips: the request and approval, the flights and hotels that make up the journey, and any cash advanced before departure. Use it to get travel authorised before it is booked, to know where your people are, and to tie the eventual expense claim back to the trip.
Travel requests · segments · advances · airports
◦ Early access: in the catalogue now and installed for design partners first; general availability follows as partners put it to work.
How it connects. Connector apps appear only when both sides are installed: assets ↔ finance (depreciation and disposals post to the ledger), assets ↔ insurance (which policy covers which asset), assets ↔ contracts (the lease or subscription behind an asset), assets ↔ items (forty identical laptops share one specification), trading partners ↔ finance and expenses ↔ finance (posting to the right accounts).
Operational registers that already know the organisation.
An asset's responsible unit, custodian and location come from the organisation tree. A customer or supplier is a role an organisation plays, not a second record. An expense claim is approved by someone holding the right delegation, against rates and policies that are data. When finance is installed, approved claims and asset events post to the ledger through connector apps — and until it is, everything works exactly as before.
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.
Legal and contracts
The agreements in force and the obligations inside them — after signature, where the commitments have to be met.
Strategy and delivery
From a strategic plan to the objectives, projects, products, releases and sprints that deliver it — with measures, not slideware.
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.