Why this one

Ten things that are true here.

Not a feature list — the structural decisions underneath one, each of which changes what the software can promise.

01

Status is derived, never picked

One board, nine stages, and the stage is a consequence of what somebody did — a quote sent, a contractor assigned, a clock started. There is no dropdown to keep tidy and no team ritual holding the data together.

02

The customer watches the invoice being made

The live visit gauge and the final bill run the same arithmetic on the server. What the customer sees mid-visit is what they are charged.

03

A contractor is not your seat

Trades hold their own account, their own credentials and their own books, and work for as many organisations as they like. Vetting is per client; availability is global; nobody sees who else they work for.

04

Whoever uses it pays for it

Metered things — messages, mapping, storage, document reading — are billed to the party that spent them, whether that is an organisation or an independent trade. Nobody quietly subsidises anyone.

05

A portal on their own address, same day

Every organisation gets a generated hostname under a wildcard the platform already holds. No DNS conversation, no certificate wait. A domain of your own is an upgrade, not a prerequisite.

06

Native where it matters. PWA where it wins.

Customer, tenant and contractor portals: App Store on iOS, installable PWA on Android — their logo as the icon, their colours, their address. No release cycle for the Android side.

07

It reads the documents the trade already has

Merchant bills, agency works orders, remittance advices and equipment rating plates are read automatically. The integration story is “send us what you already get”.

08

It arrives configured for what you are

Eleven kinds of business, each switching on a real set of capabilities at signup. Dozens of capabilities exist; nobody is shown all of them.

09

Compliance can block, not just remind

A tenancy will not activate on a property whose statutory certificates are out of date. The control is in the workflow rather than in a report somebody reads later.

10

Their money never touches ours

Payments run on each organisation's own connected Stripe account. We never hold their customers' funds, and we are never in their compliance path for it.

Put your operation on the record.