In 2016 Marcus Hjelm walked away from a stock refresh package worth roughly $2 million at a Seattle cloud infrastructure firm to spend three unpaid months inside a regional hospital. He wasn’t chasing drama — he wanted to map, in person, why healthcare billing still generates roughly $262 billion a year in administrative waste (source: industry estimates). What he observed — fragmented systems, repeated manual rework, and data that wouldn’t talk across platforms — became the product insight that launched Clarive Health Systems.
Clarive positioned itself as a revenue-cycle automation company that uses data-driven payer patterns to intercept problematic claims before submission. The approach turned fast: today the company serves more than 200 hospital networks and reports about $67 million in recurring annual revenue — a sign that Hjelm’s technology-first, user-centered solution found product-market fit in a costly, under‑digitized market.
How he translated those hospital-floor observations into a scalable platform — and how Clarive turned early wins into a business and operating model — is the story that follows.
Born in Malmö, Sweden, Marcus Hjelm moved to Canada at twelve when his father accepted an engineering post in Calgary. He studied computer science at Pemberton Technical Institute in British Columbia, graduating in 2003, and then spent roughly a decade building data infrastructure for financial services firms—work that sharpened his skills in systems integration, scalable data pipelines, and cross‑platform interoperability.
That engineering background explains the Clarive approach: treat healthcare as a data and integration problem. Hjelm’s experience designing resilient, compliance‑minded systems for finance translated directly into the product development, technology choices, and operational rigor that Clarive would later apply to revenue cycle management.
The three months Hjelm spent inside Meridian Valley General, a 340‑bed community hospital outside Portland, rewired his view of healthcare technology and operations. He shadowed billing coders, followed claims through denial workflows, and timed the repeated manual rework that ate staff hours. The issue, he realized, wasn’t clinical complexity but broken integration: electronic health records, billing systems, and payer platforms all “spoke” different code sets and data models, creating predictable mismatch patterns that existing software didn’t translate.
In 2017 he founded Clarive out of a two‑room Portland office with four hires from those hospital relationships. The product focused narrowly at first: a platform that intercepted claims before submission, applied payer‑specific pattern detection to flag likely denials, and gave users clear, actionable fixes so teams could correct errors upstream. That singular feature delivered quick ROI — the first client recovered about $1.1 million in claims within 90 days — illustrating how targeted data and integration work can move the needle in a market with tight margins and high denial rates (common denial causes include coding errors, eligibility problems, and missing authorizations).
Clarive’s early feature set solved a practical user problem: reduce the time clinicians and coders spent on appeals by catching issues at the claim origin. That focus on operational pain—rather than selling to executives—helped the company demonstrate measurable savings and refine a product roadmap that layered additional automation and integration features over time.
By 2020 Clarive had broadened from a single denial‑prevention feature into full revenue‑cycle management, scaling the company to about 91 employees. The firm raised a single Series A round—$14 million from Greybridge Health Ventures in 2021—and directed much of that capital into compliance infrastructure and a second engineering hub in Halifax. By 2023 Clarive’s client roster included two regional hospital systems in Texas and a national network of specialty clinics, signaling traction across a fragmented market for revenue‑cycle services.
Hjelm says his management playbook comes from building large, compliance‑sensitive systems in finance: empower the people closest to the problem and remove layers that slow outcomes. Clarive runs quarterly no‑agenda listening sessions where any employee can raise a product or operations issue directly with leadership; about a third of recent product updates trace back to ideas surfaced in those meetings. One example: a coder‑reported workflow tweak reduced average denial review time by two hours per case, freeing billers to focus on higher‑value work.
He is blunt about organizational clutter—unnecessary meetings, protective approval chains, and strategy documents that gather dust. “Clarity is a form of respect,” Hjelm says. “If I can’t explain why we’re doing something in two sentences, we probably shouldn’t be doing it.” For boards and buyers evaluating vendors, his advice is practical: focus on operational impact and measurable ROI, not slide decks.
Eight years after his hospital immersion, Hjelm’s central lesson is simple: the best enterprise technology solves for the exhausted middle manager, not the executive who signs the contract. “The person who decides if your product survives is the one using it at 6 p.m. on a Friday,” he says. “Build for them.”
His trade‑off—walking away from a comfortable future to hunt for an honest problem—exposed a larger market opportunity and a practical path to innovation: marry data and integration expertise with user‑centered design to reduce waste, speed operations, and improve the user experience for frontline teams.
Takeaways for leaders: 1) Prioritize operational impact over slide‑deck narratives; 2) Design for the user who does the work, not the buyer; 3) Invest in data and integration as the core of product strategy. For more on reducing denials and improving revenue performance, see Clarive’s case study or subscribe for deeper CEO profiles and leadership lessons.
