Examples  ›  Healthcare Positioning  ›  Commure
Healthcare Positioning Dossier

Commure

A clinical AI and revenue cycle platform (born from the merger of a health data company and an FDA-cleared device maker) that connects the clinical encounter directly to the claim, so health systems can document, code, and get paid in one workflow.

Category · Clinical AI + Revenue Cycle Pain Vector · Billing + Provider Satisfaction Move · Name the Enemy Stage · Early Pragmatist

Everything below is sourced from Commure's own website, Tracxn, CB Insights, Becker's Healthcare, Healthcare IT Today, KLAS Research, Fortune, and published investor announcements. Nothing here is insider knowledge. The diagnosis is public. The rewrite is a demonstration, not a prescription.

Part 1

What the public footprint reveals

Segment

A health system CIO, CMO, or VP of Revenue Cycle running 5-8 vendors across the clinical-to-financial workflow (one for ambient documentation, one for coding, one for claims, one for patient engagement) and losing revenue at every handoff between systems. Commure's customer base skews large: HCA Healthcare, CommonSpirit, Sutter Health, Northwell Health, Dignity Health, UCSF, Intermountain, Baylor Scott & White, and Jefferson Health all appear in the logo bar. The realistic buyer is the health system operations leader watching denial rates climb because clinical documentation doesn't flow cleanly into the revenue cycle. The homepage speaks to this buyer generically ("Turn labor into software") without naming her specific pain or her specific role.

Category shelf

Clinical AI. Revenue cycle management. Health system operating platform. Commure sits across multiple existing shelves, which is itself the positioning problem. In ambient documentation, they compete with Nuance/DAX and Abridge. In RCM, they compete with Waystar and R1 RCM. In patient engagement, they compete with Luma Health and Relatient. The page title says "The AI-Native Enterprise RCM & Ambient Platform," which is two categories jammed into one phrase. The buyer shopping for ambient AI lands on a page that also sells RCM, and vice versa. Neither buyer sees a hero written for them.

Where this category sits in 2026

Ambient clinical documentation is crossing the chasm into the early pragmatist majority. Health systems like HCA, CommonSpirit, and UPMC have deployed ambient AI at scale. The remaining buyers are pragmatists who need named references at their exact bed count and EHR. Revenue cycle management is deep pragmatist territory. Both categories require proof, not potential.

Copy implication: Pragmatist buyers don't care that you're "AI-native." They care that Dignity Health cut charting time 41% and that you integrate with their specific EHR. The hero leads with architecture ("AI-native") when it should lead with outcomes.

The substance chain · what Commure can actually claim
Unique attribute Value enabled Who cares most
One data model from encounter to claim — ambient documentation feeds directly into autonomous coding and claims Eliminates the handoff errors between clinical documentation and the revenue cycle that cause coding mistakes and claim denials Revenue cycle leaders losing 3-5% of net revenue to denials rooted in documentation gaps
60+ EHR integrations — works with Epic, Cerner, MEDITECH, athena, and dozens more No EHR rip-and-replace. Deploys on top of whatever the system already runs. CIOs with multi-EHR environments who refuse another migration
40M+ ambient appointments processed — at HCA, Dignity Health, NEMS, and 150+ health systems Scale proof that ambient AI works at volume across specialties, not just in pilots CIOs evaluating ambient vendors who need evidence of production-scale deployment
Athelas merger origin — born from combining a health data infrastructure company with an FDA-cleared medical device maker Only vendor that owns both the software and the hardware layer (remote patient monitoring devices) Health systems building hospital-at-home or RPM programs who don't want another vendor integration

The chain is intact. Commure has real, differentiated substance across the full clinical-to-financial workflow. The problem is that the hero buries all of it behind a five-item product laundry list and an abstract metaphor.

The one sentence Commure's best customers would repeat to a peer

"Document the visit. Get paid for the visit. One system."

This is what a CIO would say to a peer at HIMSS. It captures the structural advantage (encounter flows straight into the claim) and the consolidation benefit (replace 3-5 vendors with one). It does not appear in Commure's hero, subhead, or CTA.

Competitive alternatives the buyer actually considers
Alternative What's different Why buyers shortlist it
Nuance / Microsoft DAX Trillion-dollar parent company. Ambient-only. Deepest native integration with Epic. The "nobody got fired for buying Microsoft" default for ambient documentation.
Abridge UPMC partnership. Ambient-only. Strong clinical fidelity claims. Epic integration. Appeals to health systems that want best-of-breed ambient without the Microsoft dependency.
Waystar Public company. RCM-focused. Strong payer connectivity. No ambient documentation. The default for revenue cycle. But if you buy Waystar for RCM, you still need a separate ambient vendor.
Keep the current vendor patchwork The real competitor. One vendor for ambient, one for coding, one for claims, one for engagement. Each "works fine enough." Zero switching cost. Replacing 3-5 vendors simultaneously is a massive change-management bet. This is what Commure is actually losing deals to.
Internal staffing "We'll just hire more coders and billers." Common in mid-size systems. Avoids vendor risk entirely. Increasingly expensive but feels safer than a platform bet.
Year formed & growth signals

Athelas founded 2016 by Tanay Tandon (CEO) and Deepika Bodapati (COO). Both were Stanford undergrads who built FDA-cleared blood diagnostics devices out of Y Combinator. Commure (the original health data infrastructure company) was founded in 2017. October 2023: Athelas and Commure merged, with Tandon as CEO and Bodapati as COO. The combined entity married hardware (FDA-cleared remote monitoring devices) with software (clinical AI and revenue cycle automation).

  • Total funding: Over $1B raised across multiple rounds. Investors include General Catalyst, Sequoia, Founders Fund, 8VC, Greenoaks Capital, Y Combinator, Human Capital, and Elad Gil.
  • Valuation: ~$6B at time of merger. Series D-2 in June 2025 at $5.83B (per Forge Global).
  • December 2024: Acquired Memora Health (patient communication and care coordination platform).
  • 2025: Named to Fortune Future 50 list. KLAS report: high marks for reducing provider burnout.
  • 2026 metrics: 40M+ Ambient Appointments, $25B+ Annual Claims processed, 150+ Health Systems, 2,000 Sites of Care, 60+ EHR integrations.
  • Published outcomes: NEMS 30% improvement in documentation efficiency, Dignity Health 41% reduction in charting time (350+ hours saved/year), Yale New Haven 54% reduction in no-shows, Mount Sinai 20% increase in patients discharged directly to home, NYC Health System 53% decrease in timely filing denials.
  • Named customers: HCA Healthcare, CommonSpirit, Sutter Health, Northwell Health, Dignity Health, UCSF, Intermountain Health, Baylor Scott & White, Jefferson Health, CVS Health, Adventist Health, Cincinnati Children's, WellSpan Health, NEMS, Tenet Health, US Oncology, Yale New Haven Health, Mount Sinai, Compassus, American College of Cardiology.

Reality-match check: The customer list is genuinely elite (HCA, CommonSpirit, Sutter, UCSF, Northwell). The published outcomes are specific, named, and measurable. 40M+ ambient appointments is serious production volume. This is a company whose product is far ahead of its positioning. The substance is real. The hero is just failing to deploy it.

Roadblocks the public footprint reveals
  1. The multi-product positioning trap. Commure sells five named product lines (Agents, RCM, Ambient AI, Insights, Commure Pro) across three workflow stages (front end, mid cycle, back end). The homepage hero tries to represent all five in one subhead. The result is a laundry list that positions none of them. A visitor arriving from a Nuance/DAX comparison expects ambient AI. A visitor from a Waystar comparison expects RCM. Both land on the same generic hero.
  2. Nuance/Microsoft is the trillion-dollar incumbent. Microsoft's acquisition of Nuance means the ambient documentation category now has a default that feels "safe." Commure has to out-position DAX on the dimension DAX can't match: the connected workflow from encounter to claim. But the hero doesn't make that argument.
  3. The Athelas origin story is invisible. The merger of a health data infrastructure company with an FDA-cleared medical device company is structurally unusual in health IT. Hardware plus software plus regulatory clearance is a trust signal most competitors can't replicate. None of it appears on the homepage.
  4. The "one system" claim requires overwhelming proof. Claiming to handle everything from documentation to payment is a bold claim. Bold claims require proof stacked right next to them. The customer metrics exist (NEMS 30%, Dignity Health 41%, NYC system 53% denial reduction) but they're in a testimonials carousel below the fold, disconnected from the claim they should be proving.
  5. No above-the-fold CTA. The hero has a headline, a subhead, and a stats bar. The only actionable element is a contact form at the very bottom of the page ("Ready to bring AI to your health system?"). A CIO scanning the hero for four seconds sees no next step. No calculator, no demo, no case study link. Just a stats bar and product logos.
  6. The nonconsumer is the biggest opportunity the copy ignores. Health systems still running manual coding workflows and dictation-based documentation are nonconsumers of clinical AI. They aren't shopping for ambient because they don't believe it works at their scale yet. Commure's 40M+ ambient appointments is the proof that converts nonconsumers, but it sits in a metrics bar, not in the hero's value proposition. The nonconsumer doesn't think "I need an AI-native platform." She thinks "Our coders are drowning and our denial rate is climbing." The copy is written for the already-converted, not the unconverted.
What's confusing from a cold reader's perspective

Commure is trying to be five products at once. The hero lists five workflow stages (intake, documentation, coding, claims, payment) in a single line but doesn't explain why handling all five from one system matters. The structural insight (one data model means the encounter feeds the claim without re-keying) is buried in section 2 as "One Data Model. End-to-End RCM Automation." Eighty percent of visitors never reach section 2.

"Turn labor into software" is abstract builder language. A CMO doesn't think in those terms. She thinks: "Our denial rate is 12% and our coders can't keep up." The hero's metaphor is clever in a pitch deck and invisible on a homepage where the reader gives you four seconds.

The Athelas origin story (FDA-cleared devices, Y Combinator, Stanford founders who built diagnostic hardware before building clinical software) is completely absent from the homepage. The buyer doesn't know this company started by putting devices in patients' hands. That's unusual and trust-building in a category dominated by pure-software vendors. It's hidden.

Diagnosis

Where the positioning is leaking

01

Fails the swap test. "Turn labor into software" could be signed by Oracle Health, Epic, Olive AI, or any health IT vendor that has ever automated a workflow. Nothing in the headline identifies Commure specifically.

02

Doesn't own a word. The word Commure should own is "encounter-to-claim" or "one system." The hero doesn't stake a claim on any word the buyer would associate only with Commure.

03

Doesn't name the enemy. The enemy is the vendor patchwork: one system for documentation, another for coding, another for claims. Every handoff between vendors creates labor, errors, and revenue loss. The hero names five product categories instead of naming what's broken about the current approach.

04

Written for the wrong awareness stage. "Turn labor into software" and "AI-native" are builder/visionary phrases. Health system CIOs in 2026 are pragmatists buying proof. They want to know which peer health systems deployed, on which EHR, and what happened to their denial rates and charting time.

05

Buries the structural advantage. The insight that Commure's ambient documentation feeds directly into coding and claims (one data model, no re-keying) appears in section 2 as "One Data Model. End-to-End RCM Automation." This is the single most defensible claim against point-solution competitors, and 80% of visitors never see it.

06

Product catalog, not a promise. "AI-powered intake, documentation, coding, claims, and payment solutions" is a product list. The reader cannot finish "I need this because ______" with anything from the hero. She can only say "... because they have a lot of products." That's not a reason to take a meeting.

Part 2

Positioning as messaging

The goal isn't to tell Commure what to say. It's to demonstrate what the same publicly-known information could sound like if the hero did its job.

The Old Way · Current Hero
The AI-Native Enterprise RCM & Ambient Platform

Turn labor into software with AI-powered intake, documentation, coding, claims, and payment solutions.

40M+ Ambient Appointments $25B+ Annual Claims 150+ Health Systems 2,000 Sites of Care

[No above-the-fold CTA. Contact form appears at page bottom.]

What breaks, line by line
Line What's breaking
AI-Native Architecture jargon. No buyer has ever said "I need an AI-native platform." She says "I need my denial rate to drop."
Enterprise RCM & Ambient Platform Two categories jammed into one phrase. The ambient buyer and the RCM buyer are often different people with different budgets. Neither sees a hero written for them.
Turn labor into software Abstract builder metaphor. Clever in a pitch deck, invisible on a homepage. A CMO doesn't think "I need to turn labor into software." She thinks "My coders can't keep up and my clinicians are burned out."
AI-powered Wallpaper. Assumed infrastructure in 2026. Every vendor in this category uses AI.
intake, documentation, coding, claims, and payment solutions Five-item laundry list. The classic tell of a company that couldn't pick one. Reads as a product catalog, not a value proposition.
solutions The quintessential wallpaper word. Strip it and the sentence doesn't change meaning.
No CTA in the hero A CIO scanning for four seconds sees no next step. The only action lives at the bottom of the page in a generic contact form. Zero conversion path above the fold.
Buried wedge "One Data Model. End-to-End RCM Automation." appears in section 2. This is the structural advantage that point-solution competitors cannot match, and most visitors never see it.
Homepage Rewrite · Lead with Shared Value

The homepage hero. Leads with the shared differentiated value all target segments recognize: one connected system from the encounter to the claim.

Document once. Get paid automatically.

Commure connects clinical documentation directly to coding and claims. No re-keying between systems. No revenue leaking at the handoffs. One data model across 60+ EHRs. 150+ health systems. $25B+ in annual claims. Dignity Health cut charting time 41%. A NYC system cut timely filing denials 53%.

See which workflows your system can consolidate Read the Dignity Health results
Why this reads harder
  • Five words. The headline is the entire pitch. "Document once" is the clinical promise. "Get paid automatically" is the financial promise. The reader understands the full value proposition before she finishes the sentence. No ambient vendor (Nuance, Abridge) can claim "get paid automatically." No RCM vendor (Waystar, R1) can claim "document once." Only Commure does both.
  • Swap test is structural. Neither Nuance nor Waystar can sign this headline because neither owns the full workflow from encounter to claim. The positioning is built on a business model difference, not a style choice.
  • The subhead names the mechanism. "No re-keying between systems. No revenue leaking at the handoffs." This is the specific thing that breaks in the current vendor patchwork, and the specific thing Commure fixes. The reader who manages 3-5 vendors feels this in her gut.
  • Proof sits inside the subhead, not in a logo bar. "150+ health systems. $25B+ in annual claims. Dignity Health cut charting time 41%." The proof earns its position by standing right next to the claim it's proving.
  • "60+ EHRs" clears the integration objection inline. The CIO's first question is always "does it work with our EHR?" The subhead answers it before she asks.
  • The CTAs promise rewards, not meetings. "See which workflows your system can consolidate" gives the CIO a diagnostic before a sales call. "Read the Dignity Health results" offers proof from a peer, not a pitch.
Campaign Variant · In-Market Shoppers

For a dedicated landing page targeting buyers already evaluating ambient or RCM vendors. Names the enemy: point solutions that stop at one step of the workflow.

Your ambient vendor stops at the note.

Commure doesn't. Documentation flows into coding, coding flows into claims, claims flow into payment. One connected system from encounter to reimbursement. No integrations to build between vendors. No data degradation at the handoffs. 40M+ ambient appointments. $25B+ in annual claims. 150+ health systems already consolidated.

See how it compares to your current stack Watch the encounter-to-claim walkthrough
Why this reads harder
  • Names the enemy in seven words. The enemy isn't Nuance or Abridge by name. It's the category limitation: every ambient vendor stops at the note. Commure keeps going. The reader understands the entire thesis before finishing the first sentence.
  • The punch lands last. "At the note" is where the reader feels the limitation of her current vendor. It sits at the end of the sentence where English readers weight it most.
  • The subhead is a chain. "Documentation flows into coding, coding flows into claims, claims flow into payment." The reader sees the connected workflow as a sequence, not a feature list. She can visualize it.
  • "No integrations to build" clears the CIO's objection. The #1 cost of multi-vendor environments is the integration work. Naming it and eliminating it in the subhead removes the biggest hesitation.
  • 40M+ ambient appointments does the credibility work. A buyer evaluating ambient vendors cares about volume. This number signals production-scale proof, not a pilot.
  • The CTAs are diagnostic. "See how it compares to your current stack" turns the CTA into a tool. "Watch the encounter-to-claim walkthrough" offers proof of the connected workflow before a sales call.
Campaign Variant · Out-of-Market Buyers

For buyers not yet shopping. Reframes the decision: your denial problem isn't a billing problem. It's a documentation problem.

Your denial rate starts in the exam room.

When clinical documentation doesn't flow directly into coding, coders guess. When coders guess, claims get denied. Commure captures the encounter and moves it straight through to the claim. No manual re-keying. No handoff errors. Dignity Health cut charting time 41%. A NYC health system cut timely filing denials 53%. NEMS improved documentation efficiency 30%.

See the documentation-to-denial connection for your system
Why this reads harder
  • Reframes the entire problem. Most health systems think denials are a billing problem. This headline teaches them it's a documentation problem. The buyer who hasn't framed the connection between clinical documentation and claim denials sits up and says "wait, really?"
  • Eight words. The reframe is the headline. "Your denial rate starts in the exam room" is a hypothesis about the buyer's world that she hadn't articulated yet. That's what makes it shareable in an internal meeting.
  • The subhead builds a causal chain. Documentation fails, so coders guess, so claims get denied. The reader sees the mechanism of her own problem for the first time. That's rational drowning: the buyer realizes her current approach is worse than she thought.
  • Three proof points, three different angles. Charting time (clinical), timely filing denials (financial), documentation efficiency (operational). The reader sees proof from the dimension she cares about most.
  • Single CTA is a diagnostic, not a meeting. "See the documentation-to-denial connection for your system" lets the buyer experience the reframe before talking to a human. This is how pragmatists want to buy.
What none of these rewrites do
  • Lists five products in the headline. All three rewrites lead with the shared value (encounter flows into claim) and let product pages carry the individual product stories.
  • Says "AI-native," "AI-powered," or "turn labor into software." AI is assumed infrastructure in 2026. Leading with it wastes the reader's four seconds.
  • Uses any wallpaper word. No "scalable," "seamless," "end-to-end," "solutions," "platform," "enterprise," or "transform."
  • Claims anything Commure hasn't already published. Every number, customer name, and outcome in all three rewrites is already on their public site or in published case studies.
  • Writes prescriptive strategy. The rewrites demonstrate what the existing substance could sound like. They don't tell Commure what to build or who to be.
Audit

The 10-point positioning audit

01 · Market category & strategic framing

"Is the category cue the one the buyer already shops?"

The page title says "The AI-Native Enterprise RCM & Ambient Platform." This jams two established categories (ambient clinical documentation and revenue cycle management) into one compound phrase, then adds architecture jargon ("AI-Native") and a wallpaper word ("Enterprise"). The buyer shopping for ambient AI doesn't search for "AI-native enterprise ambient." She searches for "ambient clinical documentation." The buyer shopping for RCM doesn't search for "AI-native RCM." She searches for "revenue cycle management software." The compound category cue serves neither buyer. The market category should be the context where your differentiated value is obvious. Commure's differentiated value is that they connect ambient to RCM in one data model. The category cue should make that connection clear, not hide it behind architecture language.

02 · Competitive alternatives & status quo

"Does the copy confront what the buyer does today?"

No. The primary competitive alternative is "keep the current vendor patchwork." Most health systems run Nuance or Abridge for ambient, Waystar or a legacy vendor for RCM, and a grab-bag of point solutions for patient engagement. Each integration between vendors creates labor, errors, and revenue leakage. But the hero doesn't name this problem. It doesn't say "you're running five vendors where you need one." It doesn't name the cost of the handoffs. The buyer who is satisfied with her current patchwork ("it works fine enough") sees nothing in this hero that would make her question that assumption. You can't sell the gap between current state and future state if the buyer doesn't feel the pain of her current state.

03 · Unique attributes & clinical differentiation

"Are the non-copyable differentiators on the page?"

Commure has four genuine differentiators: (1) one data model from encounter to claim (no re-keying between ambient and RCM), (2) 60+ EHR integrations (works with whatever you run), (3) 40M+ ambient appointments at production scale, and (4) the Athelas merger origin (FDA-cleared devices plus software, a combination no pure-software competitor can replicate). These are the features Commure has that the alternatives do not. But the hero mentions none of them. Instead it leads with "AI-powered" and a five-item product list. "AI-powered" is not a differentiator when every vendor in the category uses AI. The unique attributes live in section 2 and below. The 80% of readers who see only the hero get zero differentiators.

04 · Value realization & measurable outcomes

"Does the copy lead with blunt, published numbers?"

Commure has strong published outcomes: Dignity Health 41% reduction in charting time, NEMS 30% improvement in documentation efficiency, Yale New Haven 54% reduction in no-shows, Mount Sinai 20% increase in direct-to-home discharges, NYC Health System 53% decrease in timely filing denials, and 350+ hours saved per year per physician at Dignity Health. The hero uses vanity metrics (40M+ appointments, $25B+ claims) that signal scale but don't signal value to the reader. "40M+ ambient appointments" tells me Commure is big. It doesn't tell me what happens to my charting time or my denial rate. The outcome numbers that would actually convert a skeptical CIO are in a testimonials carousel below the fold.

05 · Target segment & beachhead focus

"Does the homepage lead with the shared value the best-fit segments recognize?"

The homepage tries to speak to every health system buyer at once: CIOs (technology), CMOs (clinical), CFOs (revenue), and patient experience leaders (engagement). The hero picks none of them. The shared value that all of these buyers recognize is: "the clinical encounter and the financial claim should be one connected workflow." That's the thesis. A CIO reads it as "fewer integrations." A CMO reads it as "less charting." A CFO reads it as "fewer denials." The hero should speak to that shared value in language that transcends any single buyer's jargon. "Turn labor into software" doesn't do this. "Document once. Get paid automatically." does.

06 · Message-market fit · clarity & relevance

"Can a cold reader get it in four seconds?"

After four seconds with "The AI-Native Enterprise RCM & Ambient Platform / Turn labor into software with AI-powered intake, documentation, coding, claims, and payment solutions," a cold reader knows: (1) this is healthcare IT, (2) it involves AI, (3) it does a lot of things. She cannot answer: What specific problem does it solve? How is it different from Nuance or Waystar? Why should I keep reading? The five-second test: can your entire team repeat your company's message in a way that is compelling? No one on Commure's sales team would pitch a prospect with "We turn labor into software with AI-powered solutions." They'd say: "Your ambient note feeds directly into coding and claims. No re-keying. Your denial rate drops." The hero doesn't match the pitch.

07 · Whole product & adoption infrastructure

"Is the full adoption package visible?"

Commure has strong whole-product signals: 60+ EHR integrations (no migration), production-scale deployment at 150+ health systems, five product modules covering front end through back end, the Memora Health acquisition (patient communication), and an FDA-cleared hardware layer. Pragmatist buyers don't buy technology. They buy the whole adoption package. Commure's package is genuinely comprehensive. But the hero doesn't signal whole-product completeness. It lists product capabilities without signaling the adoption experience. The buyer needs to hear "works with your existing EHR, deploys in weeks not months, and we've done this at HCA and CommonSpirit." The page structure (front end, mid cycle, back end) actually tells this story well in section 2. It just doesn't reach the hero.

08 · Credibility · trust · EEAT signals

"Is the trust evidence overwhelming and visible?"

Commure has among the strongest trust signals in health tech: HCA Healthcare, CommonSpirit, Sutter Health, UCSF, Northwell, Baylor Scott & White, CVS Health, and Intermountain in the logo bar. Fortune Future 50 (2025). KLAS high marks. Over $1B raised from General Catalyst, Sequoia, Founders Fund, 8VC. The logo bar appears below the hero, which is standard. But the customer-specific outcomes (Dignity Health 41%, NEMS 30%, NYC system 53% denial reduction) are buried in a testimonials carousel where the reader has to click through them. These numbers should be stacked visibly, not hidden behind carousel arrows. Credibility must be established before teaching. Commure teaches ("Turn labor into software") without first earning the right with proof from peers the buyer recognizes.

09 · Value drivers vs. objection handlers

"Does the copy distinguish between what makes someone buy and what prevents a deal from dying?"

Value drivers create demand. Objection handlers prevent a deal from stalling. Commure's value drivers are: one data model from encounter to claim (creates demand because it eliminates the handoff problem), ambient AI at 40M+ appointment scale (creates demand because it proves production readiness), and the Athelas hardware origin (creates demand for RPM/hospital-at-home buyers). Commure's objection handlers are: 60+ EHR integrations (clears the "will it work with our systems" objection), HIPAA/SOC2 compliance, data security posture, and the Fortune Future 50 / KLAS recognition (clears the "are they a real company" objection). The current hero doesn't lead with either category cleanly. "Turn labor into software" is neither a value driver nor an objection handler. The rewrites lead with the strongest value driver (encounter-to-claim connection) and stack the objection handlers (60+ EHRs, 150+ systems) immediately after. Objection handlers should be easy to find on the page (first scroll, not footer) so the procurement team can check the boxes. But they should never be confused with the reason the CIO took the meeting.

10 · Voice of customer & Jobs to Be Done

"Does the copy sound like the buyer's own words and address her real Job to Be Done?"

The hero sounds like a marketing team writing for an investor deck. "Turn labor into software" is how a CEO describes the company's mission to a board. It is not how a CMO describes her problem to a peer. The buyer's words sound like this: "Our denial rate keeps climbing and we can't figure out why." Or: "My clinicians are spending two hours a night finishing notes." Or: "We're running five vendors for one workflow and the integrations are a nightmare." The buyer's real problem has functional, emotional, and social dimensions. Functionally: "connect what happens at the bedside to what gets billed." Emotionally: "stop the feeling that revenue is leaking and I can't find the leak." Socially: "don't be the CIO who bought five overlapping vendors." The hero addresses none of these dimensions. It addresses the aspirational dimension of the builder: "turn labor into software" is a founder's vision statement, not a buyer's pain statement.

Composite scorecard
# Audit dimension
01Market category & strategic framing
02Competitive alternatives & status quo
03Unique attributes & clinical differentiation
04Value realization & measurable outcomes
05Target segment & beachhead focus
06Message-market fit · clarity & relevance
07Whole product & adoption infrastructure
08Credibility · trust · EEAT signals
09Value drivers vs. objection handlers
10Voice of customer & Jobs to Be Done

Composite read: Commure has perhaps the strongest substance-to-positioning gap of any company in this dossier series. The underlying product is genuinely differentiated: one data model connecting ambient documentation to autonomous coding to claims processing, deployed across 150+ health systems including HCA, CommonSpirit, and Sutter, with 40M+ ambient appointments proving production scale. The Athelas merger gives them hardware (FDA-cleared devices) that no pure-software competitor can replicate. The competitive alternatives are clear (Nuance/DAX for ambient, Waystar for RCM, the vendor patchwork as the status quo). Every link in the positioning chain holds.

The positioning flow is broken at the messaging layer, not at the strategy layer. Commure has chosen a market category (or rather, two categories jammed together). They have identified unique attributes (one data model, 60+ EHR integrations, Athelas hardware). They have proof (named customers with specific outcomes). The problem is that none of this specificity reaches the hero. The hero is a builder's vision statement ("turn labor into software") sitting where a buyer's pain statement should be.

The multi-product trap is the root cause. When you sell five products, the hero doesn't know which product to position. The answer is: don't position a product. Position the shared value. The shared value across all five products is that the clinical encounter connects directly to the financial claim. A CIO reads that as "fewer vendors." A CMO reads it as "less charting." A CFO reads it as "fewer denials." The hero should speak to that shared thesis, and the product pages should carry the individual product stories.

The fix is not strategic. Commure doesn't need a new category, a new segment, or a new product. The fix is structural: move the substance to the hero, name the enemy (the vendor patchwork and its handoff costs), distinguish value drivers from objection handlers, stack the proof from HCA and Dignity Health and NEMS right next to the claim, add an above-the-fold CTA that promises a reward, and let the product's real advantages do the talking.

The principle this example teaches

When you sell five products, don't position five products. Position the one thing they share. The hero that tries to list everything ends up saying nothing.

Commure's current hero lets the reader finish the sentence "I need this because ______" with "... because they have AI-powered intake, documentation, coding, claims, and payment solutions." No CIO has ever said that out loud.

The rewrite lets her finish it with "... because my denial rate is climbing and it turns out the problem starts in the exam room, not in billing." That's the sentence she actually says to her VP of Revenue Cycle on a Monday morning.

The copy that matches the sentence in her head wins. Every time.

Sources

Everything in this dossier traces to a public URL

No insider knowledge. No private conversations. Every claim, number, customer name, and outcome below was pulled from one of these sources.

Company · primary
Funding · growth
Trade press · outcomes
  • Becker's Healthcare — HCA Healthcare and Commure ambient AI deployment coverage, "AI leads the way: 9 megadeals defining digital health in '25"
  • Healthcare IT Today — "Commure Secures $200M to Accelerate AI-Powered Healthcare Transformation" (July 2025)
  • HIT Consultant — "KLAS Report: Commure Ambient AI Earns High Marks for Reducing Provider Burnout" (August 2025)
  • Inc. — Deepika Bodapati named to 2026 Female Founders 500 list
Customer references
  • HCA Healthcare — Dr. Michael Schlosser (SVP of Care Transformation and Innovation) quote on commure.com
  • Tenet Health — Philipp Ludwig (CEO, Tenet Physician Resources) quote on commure.com
  • Logo bar on commure.com: HCA Healthcare, CommonSpirit, Sutter Health, Northwell Health, Dignity Health, UCSF, Intermountain Health, Baylor Scott & White, Jefferson Health, CVS Health, Adventist Health, Cincinnati Children's, WellSpan Health, NEMS, US Oncology, Compassus, American College of Cardiology
  • Published case studies: Dignity Health, NEMS, Yale New Haven, Mount Sinai, NYC Health System, Huron Perth Healthcare Alliance, A&A Women's Health, OB Hospitalist Group, Val Verde Regional Medical Center
Competitive set
  • Nuance / Microsoft DAX — ambient clinical documentation market leader, acquired by Microsoft
  • Abridge — ambient clinical documentation, UPMC partnership, Epic integration
  • Waystar — public company, revenue cycle management
  • R1 RCM / TruBridge — end-to-end RCM outsourcing
  • AVIA Marketplace — Commure competitive alternatives listing (Xealth, Redox, 1upHealth, Health Gorilla as interoperability peers)
Founder backgrounds
  • Sequoia Capital — Commure founder profiles — Tanay Tandon (CEO, Athelas co-founder, Stanford, Y Combinator, science fair to FDA-cleared devices), Deepika Bodapati (COO, Athelas co-founder, Stanford)
  • Commure press releases — October 2023 Athelas merger announcement, Tandon as CEO, Bodapati as COO
  • General Catalyst — $70M backing for Athelas pre-merger

Dossier compiled April 2026. If any source link goes stale, the underlying claim was live and public on the date of compilation.