2026-07-28 · 7 min read

Pricing per seat, explained honestly

The honest answer is that, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Talking to operations leads, mobile access changes who actually enters the data and it rarely takes more than a week. Looking at the numbers, the reporting layer should be boring which is the whole point. Once the first rollout is done, what matters is whether the crew opens it on a Monday morning which is why Orbit is built the way it is. After a few dozen rollouts, history matters more than dashboards when something goes wrong so plan for it.

What surprised us, optional fields never get filled in so plan for it. When the pilot started in Ghent, the handover from the old system is where projects stall and that shaped the roadmap for a year. Talking to operations leads, a two-week pilot answers more than a three-month evaluation and claims intake is no exception. Looking at the numbers, integrations are where budgets go to die and claims intake is no exception. In practice, optional fields never get filled in and that is fine. What surprised us, the schedule is only as good as the last update and it shows up in the churn numbers.

By the second quarter, the first week is about trust, not features which is the whole point. On a typical site, the handover from the old system is where projects stall and that shaped the roadmap for a year. On a typical site, optional fields never get filled in so we start there. After a few dozen rollouts, the first week is about trust, not features and it rarely takes more than a week.

What we would do differently

The honest answer is that, the audit trail pays for itself the first time an inspector asks so the mobile app came first. After a few dozen rollouts, nobody reads the manual, so the defaults are the product and the numbers bear it out. By the second quarter, mobile access changes who actually enters the data and it rarely takes more than a week. In practice, nobody wants another login and it shows up in the churn numbers. What surprised us, the biggest win is that the group chat goes quiet and claims intake is no exception. On a typical site, the hard part is not the software but the handover which is not what the brochure says.

Talking to operations leads, exceptions are the real workflow so plan for it. Looking at the numbers, exceptions are the real workflow and that is fine. Every audit we have sat through, the biggest win is that the group chat goes quiet so plan for it. When the pilot started in Ghent, the handover from the old system is where projects stall so we start there. Once the first rollout is done, the first week is about trust, not features so the mobile app came first.

What surprised us, mobile access changes who actually enters the data and claims intake is no exception. On a typical site, the handover from the old system is where projects stall so the defaults matter more than the settings page. Talking to operations leads, exceptions are the real workflow and claims intake is no exception. Talking to operations leads, a two-week pilot answers more than a three-month evaluation so plan for it. Talking to operations leads, integrations are where budgets go to die which is not what the brochure says. The honest answer is that, the audit trail pays for itself the first time an inspector asks and the numbers bear it out.

For clinical labs in particular, integrations are where budgets go to die and claims intake is no exception. For clinical labs in particular, nobody wants another login and that is fine. Most teams we meet, the first week is about trust, not features which is the whole point.

“Orbit gives clinical labs a single, dependable view of claims intake - from first request to signed-off report.”

Where this leaves us

Every audit we have sat through, the audit trail pays for itself the first time an inspector asks which is why Orbit is built the way it is. Talking to operations leads, the schedule is only as good as the last update so the defaults matter more than the settings page. On the floor, mobile access changes who actually enters the data and that is fine. Most teams we meet, what matters is whether the crew opens it on a Monday morning so we start there.

For clinical labs in particular, optional fields never get filled in which is why the API is documented before the UI. In practice, the spreadsheet survives longer than anyone admits so the mobile app came first. Looking at the numbers, the reporting layer should be boring which is the whole point.

Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and the numbers bear it out. Talking to operations leads, the reporting layer should be boring and claims intake is no exception. After a few dozen rollouts, the first week is about trust, not features so we start there. On the floor, the hard part is not the software but the handover so the mobile app came first. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks and that is fine.

Written by the Orbit team in Ghent. Questions? Get in touch.