Helixmed scaled 3× without scaling ops

In 2022, Helixmed ran two labs. By the end of 2024, they were running six. The operations team stayed at five people.

This is not a story about doing more with less in the way that phrase usually means — grinding, stretching, absorbing the difference personally. It is a story about a deliberate decision made early enough to matter, and the specific things that decision required them to stop doing.

The moment they knew the old system wouldn't scale

Helixmed's operations lead, Daniel Voss, describes the inflection point as a Thursday morning in March 2023. They had just confirmed a third lab site. The team opened the master tracking spreadsheet — the one that had been running since the first lab opened — and realised that adding a third location to it would require restructuring the entire document.

"We had two years of workarounds in that file," he says. "Every column had a reason. None of the reasons were written down anywhere."

They had been here before, in a smaller way, when they went from one lab to two. That time they had patched it. Added a tab, duplicated some logic, asked the most spreadsheet-literate person on the team to maintain consistency across both. It worked, barely, for fourteen months.

A third site with the same approach would have meant a fourth person dedicated to making the spreadsheet coherent. They didn't have a fourth person. And even if they had, that's not what they wanted a person doing.

What they decided before they chose a tool

The most useful thing Helixmed did in the spring of 2023 was not evaluate software. It was write down, in plain language, what the operations team was actually responsible for — and what it was not.

The list of responsibilities was expected: equipment scheduling, maintenance tracking, consumables, compliance documentation, cross-site coordination. What surprised the team was the second list. The things they were doing that weren't their job, but had become their job by default because no system existed to handle them.

Chasing technicians for job completion confirmation. Manually reconciling equipment records after audits. Rebuilding weekly status reports from scratch because the data lived in four places. Re-answering questions that had already been answered, for people who didn't know where to find the answer.

"We were spending about thirty percent of our week," Daniel says, "on things that should have happened automatically."

That number — thirty percent — became the benchmark. Any system they adopted had to give that time back. Not partially. Substantially.

The three sites Mediora had to handle before they committed

Helixmed did not sign a contract after a demo. They ran a structured evaluation over six weeks across three real scenarios.

Scenario one: a new technician joins a site they've never visited.

Could they find everything they needed — equipment list, service history, site-specific protocols, current job queue — without asking a colleague? In the old system, the answer was no. The answer required a thirty-minute handover call, a forwarded email chain, and usually a follow-up. In Mediora, from day one of the evaluation, the answer was yes.

Scenario two: an unplanned equipment failure at site two during a site-one audit.

Could the operations team manage both simultaneously, from one interface, without losing visibility on either? The old system required someone physically present at each location or a relay of phone calls. The evaluation surfaced that Mediora handled this without the operations team having to context-switch at all.

Scenario three: a compliance report due in forty-eight hours covering all active sites.

How long did it take? In the old system: two days, two people, considerable stress. In the evaluation: two hours, one person, with time left over to check the output twice.

They signed at the end of week six.

What scaling without scaling ops actually looked like

Sites three, four, and five were onboarded to Mediora in sequence over fourteen months. Each one followed the same pattern: equipment records imported in the first week, technician access configured by day three, compliance templates replicated from the existing sites with minor adjustments.

The operations team did not grow. What grew was the system's footprint, not the team's workload.

Daniel is careful about how he describes this. "It's not that the work disappeared. The coordination work — the reconciling, the chasing, the rebuilding — that disappeared. The actual operations work grew. We just did it instead of spending the day looking for information about it."

By site six, onboarding a new lab to the system took four days. Site one had taken, by rough estimate, about six months to get fully organised — across paper, spreadsheets, and shared drives that nobody fully understood.

What they wouldn't do again

Three things, specifically.

They would not run parallel systems during the transition. For the first two months after adopting Mediora, Helixmed maintained the spreadsheet alongside the new system — "just in case." It created confusion about which record was authoritative, extra work to keep both current, and delayed the point at which the team actually trusted the new system. In retrospect, Daniel says, they should have set a hard cutover date and stuck to it.

They would not wait until growth was already straining operations. The decision to act in March 2023, before the third site opened rather than after, gave them time to evaluate carefully and onboard without pressure. Teams that come to this decision under pressure make worse configuration choices and have lower adoption rates. "We got lucky," Daniel says, "that we felt the pain early enough to fix it before it became a crisis."

And they would not underestimate how long it takes to get technicians to stop using the old system. Software adoption by managers is fast. Adoption by field technicians — people whose work habits are shaped by what's reliable in a basement with no signal — is slower, and requires more than a training session. It requires the new system to prove itself in the conditions that matter. For Helixmed's technicians, that took about six weeks.

Six weeks, they have decided, is a reasonable price.