Start in about a minute

Who takes a seat, and who does not

A package's seats are Controller seats. A Controller is somebody who approves money, baselines or contracts, administers people, or runs the business — 10 of the 20 roles the platform grants. The other 10 are participants: site, quality, design, supervision and supply. A participant takes no seat, whether they work for you or for one of your subcontractors, so putting the people who do the work onto the record costs nothing.

That matters most across organisations, because a construction project is not one company. A project invitation never adds anybody to your paid seats. A Controller invited from another firm is admitted on the Controller licence their own organisation — or any company in their group — already pays for; one person holds one seat however many projects they are invited onto, and nobody is charged twice for them.

Where an invited Controller holds no licence anywhere, the platform says so and admits them as a participant until you decide. A Project Controller Pass then opens Controller authority for that one person on that one project, for a period you set up to 12 months, at £40.00 a month. It is bought deliberately and appears as its own line on the invoice. Nothing buys it automatically.

AI a guest runs is charged to the sponsor who agreed to it: their own organisation, under a monthly limit that organisation consented to, or you, once, on an authorisation you gave. Never both, and never without a ledger entry naming which.

Two roles consume no seat on any package: the platform operator, who is barred from your delivery data by the permission model, and a regulator — Building Safety Regulator access is an obligation the asset owner carries, not a licence we sell.

How AI is paid for

Every paid plan credits an AI allowance the moment each month's subscription is paid, and you can top it up whenever you want more. Nothing is credited before the payment settles — a paid account opens when its first month is paid, and the free trial is the one package that carries a grant. The arithmetic behind it matters far less than the guarantee around it: nothing is ever spent without being shown to you first.

When the ACUs run out, AI stops. Not a warning, not an overdraft, not a surprise line on next month's invoice — the work is refused and the platform says why. Every AI action is priced before you press the button, from what that action has actually cost on your account rather than from a list price.

You can set a monthly cap per account, per project or per person. A cap is a reporting ceiling, and we would rather say so plainly than let you find out: when an AI task passes one it finishes, and the spend is named on the entry and on the invoice line. That is deliberate — a piece of reasoning stopped half way has already cost the money and produced nothing you can use, which is the worst of both. Everyone who needs to know is told the moment a cap is reached. The hard stop is the balance, and that one is absolute.

Top up whenever you want more. Unused allowance is exactly what it looks like: credit on the account, recorded as its own entry so an invoice can tell an allowance from a purchase.

The arithmetic, since the Terms refer to it

One ACU is one penny of credit. An AI action costs what the provider charged for it multiplied by between 4 and 10, and where in that range depends on one thing only: how much AI the account has used this calendar month. The smallest consumers pay the top of it, because a run whose provider cost is a fraction of a penny still takes the same routing, reservation, ledger append and settlement as a large one; the rate steps down as monthly usage grows, and the bottom of the range is a floor that nothing goes below. The rate is the same on every package and every bundle — a larger bundle is fewer transactions and one purchase order, not a lower rate, and nothing in the product should imply otherwise. The multiplier each charge was raised at is recorded on its own ledger entry, so what you actually paid is a read rather than an inference. Each paid package credits 20% of its monthly price as allowance when that month's payment settles.

What a trial does and does not include

A trial governs, records and computes — the whole product minus the thing you would take to a client. Every engine runs, the chain verifies, the permission model applies. What a trial cannot do is export or print, and the platform says so in commercial terms rather than returning a permission error that would send you to your administrator.

Two roles are exempt from that limit and the second is the one that matters. A regulator's export is an access the asset owner is obliged to provide, so refusing it on the contractor's subscription would be this platform enforcing a commercial term against a statutory right. It does not get to make that trade.

One company, or a group of them

Any package can be started as a group. Choose a group of companies on the form and the organisation you name becomes the first company of a group you administer; from the Group screen you add the others — up to 5 — each its own tenancy with its own people, records and wallet, and each with the administrators you name. One console over all of them, and nothing operational shared between them.

What happens when you press the button

1. You give an address, a name, an organisation and a jurisdiction.
2. We send a link. Nothing exists yet — no tenancy, no seat, no billing record.
3. You follow the link. That is the point the tenancy is created and you become its administrator.
4. You sign in normally, with MFA. Confirming an address produces an account, never a session.

Registering an address that already has an account looks identical from the outside — we will not tell a stranger which addresses are customers. The owner of the address is told by email either way.