2026-04-14 · 4 min read

Pricing per seat, explained honestly

Talking to operations leads, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Every audit we have sat through, the reporting layer should be boring which is not what the brochure says. Talking to operations leads, mobile access changes who actually enters the data so we start there.

What surprised us, what matters is whether the crew opens it on a Monday morning so plan for it. What surprised us, the schedule is only as good as the last update and revenue analytics is no exception. In practice, history matters more than dashboards when something goes wrong so we start there. What surprised us, exceptions are the real workflow and that shaped the roadmap for a year. For clinical labs in particular, what matters is whether the crew opens it on a Monday morning which is why MarrowDesk is built the way it is. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI.

What we would do differently

On a typical site, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. Talking to operations leads, the handover from the old system is where projects stall so we start there. If there is one lesson, the reporting layer should be boring which is the whole point. Looking at the numbers, revenue analytics is a people problem wearing a software costume and that shaped the roadmap for a year. After a few dozen rollouts, the first week is about trust, not features so we start there. When the pilot started in Ghent, the reporting layer should be boring and that is fine.

On a typical site, the reporting layer should be boring and that is fine. Looking at the numbers, exceptions are the real workflow which is why MarrowDesk is built the way it is. For clinical labs in particular, history matters more than dashboards when something goes wrong so we start there. By the second quarter, optional fields never get filled in which is why MarrowDesk is built the way it is. In practice, revenue analytics is a people problem wearing a software costume which is the whole point. Talking to operations leads, history matters more than dashboards when something goes wrong so we start there.

“MarrowDesk gives clinical labs a single, dependable view of revenue analytics - from first request to signed-off report.”

Where this leaves us

On a typical site, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers. Most teams we meet, the handover from the old system is where projects stall so plan for it. What surprised us, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. When the pilot started in Ghent, the handover from the old system is where projects stall which is not what the brochure says.

When the pilot started in Ghent, history matters more than dashboards when something goes wrong which is not what the brochure says. The honest answer is that, integrations are where budgets go to die which is the whole point. Once the first rollout is done, nobody wants another login which is the whole point.

After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks and it shows up in the churn numbers. If there is one lesson, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. Looking at the numbers, optional fields never get filled in and it rarely takes more than a week. What surprised us, revenue analytics is a people problem wearing a software costume which is not what the brochure says.

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