Pilot register  ·  internal assessment

Internal working document · P1–P12

Twelve candidate RCM pilots, scored for comparison

Each candidate process is scored on the same axes so they can be compared directly. Only one will become a live engagement, and this register records the reasoning behind that choice.

Illustrative and internal

Register

All twelve, ranked by verdict

Verdict is a curated aggregate that weights measurable cash and sales-cycle fit, and penalises competitive density, capital needs and data-access difficulty. It is not a raw average.

ID Pilot Readiness Competition Effort Cash Verdict
P1Denial & underpayment recoveryRecommendedOpen wedgeMediumHigh
96
P8Work prioritisation by expected recoveryReadyOpen wedgeLowHigh
90
P7Appeal drafting (copilot)ReadyOpen wedgeMediumHigh
88
P9Payment / remittance reconciliation & underpayment detectionReadyPartialMediumHigh
82
P6Denial classification & root-causeReadyPartialLowIndirect
72
P2Claim / invoice document ingestion & extractionReadyCrowdedLowIndirect
62
P3Coding consistency & required-field checksReadyCrowdedMediumMedium
55
P4Eligibility / prior-auth failure triageReadyCrowdedMediumMedium
48
P10Aged AR / slow payment chaseReadyCrowdedMediumMedium
45
P5Payer rule validation (eClaimLink-oriented)ReadyCrowdedHighMedium
40
P11Denial prevention (pre-submit) — later phasePhase 3+CrowdedHighMedium
28
P12Full RCM takeoverLockedCrowdedHighHigh
0
Detail

Each pilot in sequence

Ordered by recommended run sequence. Positioning is shown by default; problem statement, current market solution, process steps and scoring sit behind disclosures.

P1

Denial & underpayment recovery

Recommended Open wedge
Verdict 96/100 Effort Medium Measurable cash High Sequence 1

Recovery SWAT overlay: historical denial audit → score expected AED → draft appeals → human approve → book cash vs written baseline. Offering: onboarding fee + % of incremental collections. Pricing angle: aligned with hard recoveries, not hours or factoring discounts.

The problem

Denied and underpaid claims sit in AR while billing teams chase volume work and FIFO queues.

Who feels it: clinic-group CFO (cash & AR days), billing lead (appeal backlog), site managers (write-off pressure).

Failure mode: denials age past appeal windows; underpayments are posted as “paid” without variance chase; no written baseline means nobody can prove incremental recovery.

Cash / ops impact: at-risk AED compounds across payers; scarce billing minutes are spent on low-yield items; outcome economics cannot be sold without a measurable recovery loop.

How it is solved today

Labour BPOs staff AR / denial follow-up at ~hourly directory rates. Full-cycle AI platforms bury recovery inside opaque SaaS+services. Klaim Recover overlaps economically but sits inside a revenue-treasury / Accelerate liquidity story. Few sell a crisp clinic-group overlay priced as % of incremental recovery with no payment custody.

Process steps (6)
  • Load denial / remittance sample packIngest synthetic Clinic Demo LLC claims, denial letters, and remittance advice into the recovery workspace.
  • Audit & score expected recoveryAI scores each denied/partial claim: gap AED × recoverability − effort. Surface evidence from denial letters.
  • Prioritise work queue by AED × probability − effortRank open recoveries; lock a top-N worklist for appeal packaging.
  • Draft appeal / resubmission packageAssemble evidence pack and simulated appeal narrative from denial + claim fields.
  • Human approve or overrideapproval gateBilling lead reviews AI recommendation, confidence, and evidence; approve, request edits, or reject.
  • Log outcome vs baseline (synthetic)Book synthetic recovered AED against written baseline (0 in demo) and update metrics.
Scores and competitive read
Ease of implementationhigher is easier
Measurable cash impacthigher is better
Sales-cycle fithigher is better
Competitive densitylower is better
Required capitallower is better
Working capitallower is better
Data-access difficultylower is better

Competitive: Klaim Recover overlaps economically; FinPro/Escrow/Focus do AR follow-up as labour. Few sell % of incremental recovery as a crisp clinic-group overlay with no payment custody.

P2

Claim / invoice document ingestion & extraction

Ready Crowded
Verdict 62/100 Effort Low Measurable cash Indirect Sequence 2

Shared document spine for all pilots: ingest → simulated extract → confidence + evidence → human field override. Not differentiated alone; priced as enabling capability inside the recovery overlay, not a separate SaaS seat pitch.

The problem

Claims, remittances, denial letters and invoices arrive as PDFs, scans, and CSVs. Without structured fields + confidence + source evidence, every downstream pilot is blind.

Who feels it: RCM ops (manual re-key), analysts (broken joins), compliance (weak audit trail).

Failure mode: wrong claim IDs, missed variance lines, no snippet linking an extracted denial code to the letter.

Cash / ops impact: indirect but foundational — bad extraction multiplies false appeals and missed underpayments.

How it is solved today

Every AI RCM platform and e-claim gateway does variants of OCR/NLP extraction. Sold as platform plumbing or EMR-embedded capture, rarely as a standalone clinic-group product with explicit confidence/evidence UX.

Process steps (5)
  • Upload or load sample documentsBring in denial letters, claim CSV, remittance, and invoice stubs for Clinic Demo LLC.
  • Ingest & normalise textNormalise encodings and document types; stamp audit stub per file.
  • Simulated extract of key fieldsHeuristic extraction of claim ID, payer, amounts, denial codes — labelled simulated.
  • Show confidence + evidence snippetsEach field shows confidence and the source span used.
  • Human override fieldsapproval gateBilling user corrects low-confidence fields before routing downstream.
Scores and competitive read
Ease of implementationhigher is easier
Measurable cash impacthigher is better
Sales-cycle fithigher is better
Competitive densitylower is better
Required capitallower is better
Working capitallower is better
Data-access difficultylower is better

Competitive: Every AI platform and e-claim gateway does variants. Still required plumbing for all pilots — not differentiated alone.

P7

Appeal drafting (copilot)

Ready Open wedge
Verdict 88/100 Effort Medium Measurable cash High Sequence 2

Copilot drafts from denial + claim evidence; human edits/approves. Throughput lever for the recovery wedge. Pricing stays on incremental cash, not draft seats.

The problem

Writing appeals is slow. Juniors paste templates; seniors rewrite; evidence packs are incomplete.

Who feels it: billing leads (throughput), CFOs (appeal lag → write-offs).

Failure mode: weak narratives, missed attachments, no human gate before resubmit.

Cash / ops impact: high when paired with P1 — minutes/claim drop and recovery rate rises.

How it is solved today

Often buried in BPO labour. AI platforms may draft inside denial modules but public packaging of “appeal copilot + human approve + outcome fee” is thin.

Process steps (5)
  • Select denied claimPick a high-gap denied claim from the recovery queue.
  • Assemble evidence packPull eligibility notes, clinical stubs, fee references (synthetic).
  • Generate simulated appeal draftProduce narrative with requested AED — labelled simulated.
  • Human edit / approveapproval gateBilling lead edits tone/facts; approve or reject before queue.
  • Queue for resubmission logLog approved package ID for resubmit tracking (no live rail).
Scores and competitive read
Ease of implementationhigher is easier
Measurable cash impacthigher is better
Sales-cycle fithigher is better
Competitive densitylower is better
Required capitallower is better
Working capitallower is better
Data-access difficultylower is better

Competitive: Thinner public packaging; often buried in BPO labour. Copilot + human gate is a clear rehearsal for recovery economics.

P8

Work prioritisation by expected recovery

Ready Open wedge
Verdict 90/100 Effort Low Measurable cash High Sequence 2

Rank by expected AED × probability − effort; assign top-N. Core differentiator inside P1. Makes outcome pricing credible (“we work the EV queue, not everything”).

The problem

Teams work FIFO or loudest payer. High-AED recoverable items age out while low-yield noise fills the day.

Who feels it: billing leads (queue design), CFOs (AED per hour).

Failure mode: no expected-value sort; effort ignored; gain-share pilots cannot prove focus.

Cash / ops impact: high — same headcount, more incremental cash when ranking is real.

How it is solved today

Weakly packaged publicly. Some platforms have worklists; BPOs use tribal priority. Differentiator if transparent and tied to gain-share pilots.

Process steps (4)
  • Score open denials (demo model)Apply demo EV model to denied/partial/open claims.
  • Sort by expected net recoveryPresent ranked list with gap, probability, effort minutes.
  • Assign top-N to worklistapproval gateHuman confirms lock of top-N for the shift/pilot slice.
  • Track minutes vs AED outcomeSynthetic feedback loop: minutes spent vs recovered AED.
Scores and competitive read
Ease of implementationhigher is easier
Measurable cash impacthigher is better
Sales-cycle fithigher is better
Competitive densitylower is better
Required capitallower is better
Working capitallower is better
Data-access difficultylower is better

Competitive: Weakly packaged publicly; differentiator if real and tied to gain-share pilots.

P6

Denial classification & root-cause

Ready Partial
Verdict 72/100 Effort Low Measurable cash Indirect Sequence 3

Lightweight taxonomy → frequency dashboard → feed P1 scoring. Sold as part of recovery overlay insight, not a BI seat. Makes gain-share conversations sharper (“we’ll work DOC+COD first”).

The problem

Without a taxonomy, denial work is reactive case-by-case. Patterns (eligibility, coding, docs, fee) never become ops fixes.

Who feels it: RCM managers, quality leads, CFOs asking “why is denial rate sticky?”.

Failure mode: every denial treated equal; prevention backlog empty; recovery queue polluted.

Cash / ops impact: indirect alone; high leverage when linked to P1 prioritisation and P11 later.

How it is solved today

SAMCO denials practice; Humaein/SISGAIN denial modules. Taxonomy exists inside platforms/BPO SOPs but is weakly packaged as a clinic-group product tied to recovery economics.

Process steps (4)
  • Ingest denial batchLoad denied/partial claims and associated denial letters.
  • Classify into taxonomy bucketsBucket by denial family: ELIG, PA, COD, DOC, FEE/UND, other.
  • Aggregate root-cause frequenciesShow counts and AED at risk per bucket for ops review.
  • Export pattern summary for opsapproval gateHand-off summary for process owners; optional human sign-off on priority themes.
Scores and competitive read
Ease of implementationhigher is easier
Measurable cash impacthigher is better
Sales-cycle fithigher is better
Competitive densitylower is better
Required capitallower is better
Working capitallower is better
Data-access difficultylower is better

Competitive: SAMCO denials practice; Humaein/SISGAIN denial modules. Partial — taxonomy + recovery link is still weakly packaged for clinic groups.

P9

Payment / remittance reconciliation & underpayment detection

Ready Partial
Verdict 82/100 Effort Medium Measurable cash High Sequence 3

Match remit → billed, flag short-pay, estimate recoverable gap, route into P1 queue. Same gain-share economics as denials. Distinguish from Klaim Accelerate (liquidity).

The problem

Remittance advice does not always match billed/contracted amounts. Short pays post as closed; variance dies quietly.

Who feels it: finance (understated revenue), billing (no chase queue), auditors.

Failure mode: REM lines with positive variance never become recovery cases.

Cash / ops impact: high — underpayments are often easier than full denials when fee schedules are clear.

How it is solved today

Humaein remittance/bank gaps; Klaim underpayments; FinPro “pending amount recovery”. Idea exists; packaging & outcome pricing still fragmented.

Process steps (4)
  • Match remittance lines to billed claimsJoin REM-DEMO-* lines to CLM-DEMO-* billed amounts.
  • Flag short-pay varianceHighlight variance AED > 0 with remark codes (UND-FEE, UND-BUN).
  • Estimate recoverable gapDemo estimate of chaseable AED given contracted fee hints.
  • Route to P1-style recovery queueapproval gateHuman confirms push of underpays into recovery worklist.
Scores and competitive read
Ease of implementationhigher is easier
Measurable cash impacthigher is better
Sales-cycle fithigher is better
Competitive densitylower is better
Required capitallower is better
Working capitallower is better
Data-access difficultylower is better

Competitive: Humaein remittance/bank gaps; Klaim underpayments; FinPro pending-amount recovery. Idea exists; packaging & pricing still fragmented.

P3

Coding consistency & required-field checks

Ready Crowded
Verdict 55/100 Effort Medium Measurable cash Medium Sequence 4

Use coding checks as a recovery amplifier (flag after denial + before resubmit), not as the first product. Human gate on flags. Pricing remains attached to recovery outcomes, not scrubber seats.

The problem

Inconsistent CPT/ICD pairing and missing required fields become denials after submit — or silent underpayments.

Who feels it: coders, billing leads, clinicians whose notes don’t support codes.

Failure mode: high-ticket cardio/ortho lines sail with mismatched ICD; PA-required fields blank.

Cash / ops impact: preventable denials (e.g. DEN-COD-07) and rework minutes; measurable if tied to avoided write-offs.

How it is solved today

Axora, Humaein, SISGAIN, Pure Validator and similar sell pre-submit scrubbing heavily. Crowded prevention / coding lane with opaque SaaS packaging.

Process steps (5)
  • Load claim sampleOpen synthetic claims with known coding defects (e.g. CLM-DEMO-1004).
  • Run required-field checklistDemo checklist: member ID, DOS, CPT, ICD, PA segment where required.
  • Flag coding inconsistencies (demo rules)Surface CPT/ICD medical-necessity pair failures with evidence.
  • Route flags to human reviewapproval gateCoder/billing lead accepts, waives, or corrects before resubmit path.
  • Log preventable vs non-preventableTag which flags would have avoided denial vs documentation gaps needing clinical input.
Scores and competitive read
Ease of implementationhigher is easier
Measurable cash impacthigher is better
Sales-cycle fithigher is better
Competitive densitylower is better
Required capitallower is better
Working capitallower is better
Data-access difficultylower is better

Competitive: Axora, Humaein, SISGAIN, Pure Validator are heavy here (pre-submit scrubbing). Crowded prevention lane.

P4

Eligibility / prior-auth failure triage

Ready Crowded
Verdict 48/100 Effort Medium Measurable cash Medium Sequence 5

Triage overlay on denial feed: classify ELIG/PA/other → score recoverability → route appeal vs front-office fix. Supports P1 queue hygiene. Outcome fees only where appeal path recovers cash.

The problem

Many denials are eligibility or prior-auth failures. Treating all denials as “appeal everything” wastes minutes and burns payer goodwill.

Who feels it: front office (eligibility on DOS), billing (PA gaps), patients (unexpected balances).

Failure mode: appeals filed when auth was prospectively required; or recoverable coverage-proof cases written off.

Cash / ops impact: mixed — some AED recoverable, much value is process-fix prevention.

How it is solved today

Embedded in full-cycle RCM & EMR gateways (eligibility checks, PA workflows). Rarely sold as a standalone clinic-group triage product with recover-vs-fix disposition.

Process steps (4)
  • Classify denial as eligibility / PA / otherMap denial codes (DEN-ELIG-*, DEN-PA-*) from letters and claim status.
  • Score recoverabilityCoverage-proof cases score higher; missing prospective PA scores low for appeal.
  • Suggest route: appeal vs process fixDisposition recommendation with evidence snippets from eligibility notes.
  • Human confirm dispositionapproval gateOps confirms route; audit trail stores approve / edit / reject.
Scores and competitive read
Ease of implementationhigher is easier
Measurable cash impacthigher is better
Sales-cycle fithigher is better
Competitive densitylower is better
Required capitallower is better
Working capitallower is better
Data-access difficultylower is better

Competitive: Embedded in full-cycle RCM & EMR gateways. Hard to own as a standalone first pilot.

P5

Payer rule validation (eClaimLink-oriented)

Ready Crowded
Verdict 40/100 Effort High Measurable cash Medium Sequence 6

Demo rule pack only (not a live rail). Use to speak eClaimLink fluently in buyer demos and to annotate recovery evidence — not as first commercial wedge. Avoid competing head-on with gateway vendors.

The problem

Dubai claims ride eClaimLink/DHPO. Rejectable patterns (segments, code pairs, auth rules) create hard rejects and rework.

Who feels it: billing submitters, IT/gateway admins, CFOs seeing reject spikes.

Failure mode: teams learn rules only after rejects; demo confusion with live rail claims.

Cash / ops impact: medium — prevention of rejects; crowded and integration-heavy.

How it is solved today

e-claim gateways (ClinicGateway, QC Messenger) + AI scrubbers already sell payer/DHA-style validation heavily as clean-submit infrastructure.

Process steps (4)
  • Load claim against demo rule packBind synthetic claims to a DHA/eClaimLink-oriented demo rule set (offline).
  • Validate required segments / codesCheck member format, DOS window, CPT/ICD allow-list, PA segment for specialty.
  • Surface rule hits with evidenceShow each hit with claim field evidence — clearly labelled demo, not live DHPO.
  • Human accept / waiveapproval gateSubmitter accepts fix or waives with reason for audit.
Scores and competitive read
Ease of implementationhigher is easier
Measurable cash impacthigher is better
Sales-cycle fithigher is better
Competitive densitylower is better
Required capitallower is better
Working capitallower is better
Data-access difficultylower is better

Competitive: e-claim gateways (ClinicGateway, QC Messenger) + AI scrubbers already sell this heavily.

P10

Aged AR / slow payment chase

Ready Crowded
Verdict 45/100 Effort Medium Measurable cash Medium Sequence 7

Age buckets + chase packs + timing metrics as an extension of recovery overlay. Explicitly not factoring. Price chase outcomes only where incremental cash is attributable; else keep as ops hygiene for P1.

The problem

Aged open balances drain cash. Without age buckets and chase packs, ops cannot decide chase vs write-off.

Who feels it: CFO (AR days), collectors, site admins.

Failure mode: 90+ day balances ignored; chase letters generic; confusion with liquidity products.

Cash / ops impact: medium — some recoveries, but overlaps classic BPO AR.

How it is solved today

Classic BPO AR follow-up. Klaim Accelerate is liquidity (receivables purchase), not chase ops — buyers often conflate the two.

Process steps (4)
  • Bucket AR by age (0–30 / 31–60 / 61–90 / 90+)Classify open/denied/partial claims into age buckets.
  • Build chase pack for selected bucketGenerate synthetic chase list for 90+ with claim + payer contacts stub.
  • Simulate chase outcomesDemo outcomes: partial collect, promise-to-pay, write-off candidate.
  • Compare AR days before/after (synthetic)approval gateHuman signs off on synthetic AR-days delta for the rehearsal.
Scores and competitive read
Ease of implementationhigher is easier
Measurable cash impacthigher is better
Sales-cycle fithigher is better
Competitive densitylower is better
Required capitallower is better
Working capitallower is better
Data-access difficultylower is better

Competitive: Classic BPO AR. Klaim Accelerate is liquidity, not chase ops — distinguish carefully in buyer talks.

P11

Denial prevention (pre-submit) — later phase

Phase 3+ Crowded
Verdict 28/100 Effort High Measurable cash Medium Sequence 11

Mark Phase 3+. After P1 proves cash, reuse denial taxonomy to score pre-submit risk. Still overlay; still not a scrubber price war. Outcome story remains recovery-first.

The problem

Intervene before submit using learned denial patterns. Valuable long-term, but crowded and not the first outcome-priced pilot.

Who feels it: coding leads, submitters, CFOs wanting denial rate ↓.

Failure mode: buying prevention SaaS without proving recovery economics first; long sales vs hospital platforms.

Cash / ops impact: medium avoided denials — hard to attribute without baseline; Phase 3+.

How it is solved today

Axora, Humaein, Pure Validator and peers dominate pre-submit prevention / scrubbing with platform retainers.

Process steps (4)
  • Load pre-submit claimOpen a not-yet-submitted synthetic claim with risk factors.
  • Score denial risk (demo)Demo risk score from historical taxonomy (COD/ELIG/PA patterns).
  • Suggest fixesPropose ICD alignment / PA check / doc attach before submit stub.
  • Human accept before “submit” stubapproval gateHuman accepts fixes; no live eClaimLink submit in prototype.
Scores and competitive read
Ease of implementationhigher is easier
Measurable cash impacthigher is better
Sales-cycle fithigher is better
Competitive densitylower is better
Required capitallower is better
Working capitallower is better
Data-access difficultylower is better

Competitive: Axora, Humaein, Pure Validator dominate prevention. Mark as Phase 3+, not first pilot.

P12

Full RCM takeover

Locked Crowded
Verdict 0/100 Effort High Measurable cash High Sequence 99

Explicitly locked. Prove recovery economics on P1 first. Future expand only as overlay modules — not rip-replace EMR/BPO. No full-takeover pricing in phase 1.

The problem

End-to-end claim management — eligibility through cash posting. Attractive as land-and-expand fantasy; disastrous as first pilot.

Who feels it: buyers wanting “one throat to choke”; vendors selling full-cycle retainers.

Failure mode: multi-year replacement, hospital-bias platforms, lost focus on measurable recovery.

Cash / ops impact: theoretically high, but capital, density, and sales cycle make it wrong first move.

How it is solved today

ACCUMED, Escrow, Humaein, SISGAIN and others sell full-cycle RCM (labour and/or AI platforms). Dominant commercial language in UAE clinic outsourcing.

Process steps (1)
  • Not available in this rehearsal UIFull RCM takeover is locked. Use P1–P11 modules to rehearse the wedge.
Scores and competitive read
Ease of implementationhigher is easier
Measurable cash impacthigher is better
Sales-cycle fithigher is better
Competitive densitylower is better
Required capitallower is better
Working capitallower is better
Data-access difficultylower is better

Competitive: ACCUMED, Escrow, Humaein, SISGAIN and others sell full-cycle. We stay overlay until recovery economics are proven.

Legend

How to read this

Open wedge
Thin public packaging by existing vendors — hypothesised white space.
Partial
Some overlap with existing offerings, but no crisp clinic-group product.
Crowded
Many public vendors already in the lane.
Teal dots
Higher is better on this axis.
Rust dots
Higher is worse on this axis — density, capital, working capital, data difficulty.
Approval gate
A step where an authorised human must approve before anything is filed.