Eight things that change.

These are outcomes, not features.

One authoritative answer, read by everything

Stock, price, entitlement and customer history resolve to one record. The counter, the field technician, the website and the back office all read it. Disagreement stops being something to manage and becomes something that cannot happen.

Who notices first: the person on the phone who no longer has to apologise for the screen.

The post-sale business becomes visible, and therefore manageable

Service, protection, trade-in, refurbishment and repeat purchase are modelled as first-class events rather than exceptions, so the margin they carry can be measured instead of estimated.

Who notices first: whoever is asked, every quarter, where the aftermarket margin actually went.

Eight or more systems stop needing to be kept alive

Designed to retire the patchwork and the integrations holding it together — with the licences, the upgrade windows and the specialist knowledge each one demanded.

Who notices first: the two people who spend most of their week keeping the seams from tearing.

The month closes on evidence, not on reconstruction

Records are written as work happens, in one place, with one permission model. Closing becomes reading what is already true rather than rebuilding it from exports.

Who notices first: finance, in the first week of the month rather than the third.

Proving what happened takes minutes

Tamper-evident records, one permission model, one retention policy. An audit request becomes a query with an answer rather than a quarter of somebody’s year.

Who notices first: whoever currently owns the spreadsheet that reconciles the other spreadsheets.

Intelligence you can let near a decision

Because the record is coherent and authority is explicit, a model can be given real work. It proposes; a person disposes; anything irreversible waits for confirmation.

Who notices first: the manager who has been told for two years that the data is not ready.

Configuration instead of change requests

Differences between sites, entities and jurisdictions are configuration, not custom code. Opening a site is an operational act, not a project with a vendor attached.

Who notices first: the operations lead who has stopped asking for small changes because of what they cost.

Software your whole workforce can actually use

WCAG 2.2 AA is a build condition. Shift staff, technicians, managers and finance are not power users, and the system does not require them to be — or exclude the ones who use it differently.

Who notices first: the employee who has been quietly working around software that was never tested with them in mind.

What is not true yet

Orbit is in active development. Everything above describes what is being built and the standards it is being built to, not a system you can buy today. Nothing on this site is an offer, a commitment, or a representation that a described capability is currently available.

We would rather publish that sentence than have you discover it in a procurement meeting.

We are building this now.

Orbit is in active development. If you run a multi-site operation and this describes a problem you recognise, we would like to hear about it.

Get in touch