IMEUS Ecosystem OS Levels — Pricing Framework

§ 01 · THE FRAMING

Pricing as a journey, not a menu.

Most vendors offer parallel commercial structures and ask the customer to choose one. IMEUS does something different. Each level builds on the level below — adding product, adding alignment, adding mutual stake.

For example, a hospital does not commission a hospital information system once and never again. The relationship matures. What begins as software becomes operations. What begins as operations becomes ecosystem. What begins as ecosystem becomes sovereign infrastructure.

IMEUS prices this maturation explicitly. Level 1 is software. Level 2 adds the BPO-I operational intelligence layer on top of Level 1. Level 3 adds the EcoOS ecosystem orchestration layer on top of Levels 1 and 2. Level 4 adds equity on top of everything. Each level inherits. Each level compounds.

This document defines what each level contains, what it costs, and where it fits. It is the commercial complement to the IMEUS Sovereign Health OS architecture — and it is structured so that procurement, finance, and clinical leadership all see the same picture.

§ 02 · THE STACK

The IMEUS Ecosystem OS Levels

Each level contains the levels below.

A hospital at L3 Ecosystem-Native is paying for L1 SaaS, L2 BPO-I, and L3 EcoOS — three product layers, calibrated together. A hospital at L4 @CountryEquity is paying for all three layers and contributing equity in exchange for cash reductions and sovereign positioning.

The dotted lines mark inheritance. The gold rule at the top of each level marks where new capability — and new commercial logic — is added. Every higher level is structurally additive to the levels below it.

This is why hospitals do not have to "switch" pricing models. They climb the stack as their relationship with IMEUS deepens.

§ 03 · THE FOUR LEVELS

What each level adds.

Each level introduces a distinct product layer, a distinct commercial mechanism, and a distinct strategic positioning. Read them as a ladder.

SaaS · Foundation

SaaS

Software as a Service

The CyberMed Hospital Information System, delivered as a managed cloud service. The foundation every higher level builds on.

What this level adds

The CyberMed HIS itself — FHIR-native, multi-tenant, event-sourced. Core clinical, ancillary, financial, and administrative modules. Implementation, training, hosting, support.

Standard SLA, business-hours support, 99.5% uptime. Annual price escalation capped at 5% or CPI, whichever is lower.

Commercial mechanism

Signon (one-time)US$ 250K – 9.5M
Annual subscriptionUS$ 2,800 – 7,200 / bed
Sizing variableBed count × complexity
Term3 years
Vendor lock-in protectionFHIR R4 export

When this level fits

"We need a modern HIS. We want predictable cost. We are not yet ready to talk about ecosystem orchestration or sovereign positioning. Just give us excellent software."

Performance · BPO-I

SaaS + BPO-I

Revenue Performance

L1 SaaS plus the BPO-I healthcare BPO intelligence layer. Hospital pays a reduced base; CyberMed earns variable fees on measurable operational improvements.

What this level adds

BPO-I — the IMEUS healthcare BPO intelligence platform. Embedded operational analytics, claims intelligence, DRG documentation assistance, length-of-stay optimization, drug wastage reduction, and DSO improvement workflows.

BPO-I sits on top of the L1 HIS data substrate. It is where IMEUS earns the right to participate in operational outcomes.

Commercial mechanism

Signon discount vs L1−60%
Base subscription discount−40%
Performance fee basisΔ above baseline
Performance share range12 – 20%
Annual master cap1.6× L1 SaaS recurring
Term5 years

When this level fits

"We have operational pain points — claims rejection, length of stay, drug wastage, DSO. We want a partner whose income depends on fixing them. We have measurable baselines and the discipline to track improvement."

When this level does not fit

"We don't have clean baseline data. Or we don't have the operational maturity to differentiate vendor-driven improvement from organic improvement. L2 needs both — without them, the contract becomes a dispute factory."

Ecosystem · EcoOS

SaaS + BPO-I + EcoOS

Ecosystem-native

Everything in L1 + L2, plus the EcoOS ecosystem operating system. The hospital becomes the orchestrator of a regional health network.

What this level adds

EcoOS — the IMEUS ecosystem operating system. Hub-and-node architecture connecting clinics, pharmacies, labs, imaging centers, payers, suppliers, and partner hospitals to the hospital's own HIS through standardized FHIR and ISO 20022 rails.

The hospital becomes a regional referral magnet, a payer-of-record orchestration point, and a platform for net-new consortium services that did not exist pre-ecosystem.

Commercial mechanism

Hub fee (annual)US$ 600K – 6.5M
Node fees (annual)9 node types · published rate card
Volume discount−15% / −25% at 20+ / 50+ nodes
Transaction feesPer-event routing fees
Net-new revenue share8 – 12% of consortium-only revenue
Term7 years

When this level fits

"We have or aspire to have a network of feeder clinics, pharmacies, and ancillary partners. We want to be the orchestrator, not just a node. We see referral revenue, ecosystem revenue, and platform revenue as part of our future."

@Country · Equity

SaaS + BPO-I + EcoOS + Equity

@CountryEquity

Everything in L1 + L2 + L3, with mutual equity stakes replacing portions of the cash component. The deepest possible alignment between hospital and IMEUS.

What this level adds

Mutual equity. CyberMed takes 8 – 20% in the hospital's digital subsidiary. The hospital takes 3 – 10% in the IMEUS @Country deployment SPV for that nation. Joint governance, joint board, joint exit alignment.

The hospital is positioned not as a customer but as national health infrastructure — the anchor institution in IMEUS's sovereign deployment for that country.

Commercial mechanism

L3 hub fee−50% reduction
L3 node fees−40% reduction
L3 transaction fees−30% reduction
Joint governance50/50 cost split
Equity in hospital digital sub8 – 20%
Equity in @Country SPV3 – 10%
Term · Lockup10+ yrs · 5 yr min lockup

When this level fits

"We are being positioned by the state — or are positioning ourselves — as critical national health infrastructure. We are willing to share equity for genuine alignment. We see a 10+ year horizon and want IMEUS to be a co-owner of the journey."

§ 04 · STRUCTURAL GUARDS

How the stack stays defensible to a CFO.

A stacked pricing model is only as good as the guard-rails that prevent it from becoming a triple charge. Four structural rules govern every IMEUS engagement.

GUARD 01

Anti-double-count

Each level's economics applies only to value newly attributable to that level. L2 BPO-I performance fees apply only to operational improvements above baseline — not to the hospital's organic revenue. L3 EcoOS revenue share applies only to net-new consortium services that did not exist pre-ecosystem — not to the hospital's own institutional revenue. A given Ringgit of value is shared once, never twice.

GUARD 02

Master annual cap

At every level, the hospital's total annual commercial commitment to IMEUS — across all stacked layers — cannot exceed 1.6× the equivalent L1 SaaS recurring for that hospital. This ceiling protects the hospital from runaway success bills regardless of how much value the stack delivers. Overages are refunded within 30 days of year-end reconciliation.

GUARD 03

Hospital-favorable interpretation

Where reasonable people could disagree on attribution, baseline, or measurement under the contract, the hospital's interpretation prevails. This deliberate asymmetry keeps IMEUS disciplined in its claims and aligned with the hospital's good-faith reading of the agreement. Disputes escalate to the AIAC in Kuala Lumpur as binding arbitration of last resort.

GUARD 04

Anti-lock-in by design

Every level — L1 through L4 — guarantees the hospital's data export rights in open standards. FHIR R4 for clinical, ISO 20022 for financial flows, UBL 2.1 for invoicing. The hospital owns its data unconditionally. Pricing reflects partnership, not captivity. The stack earns its position by being good, not by being inescapable.

§ 05 · SCOPE & TERM

At a glance.

A single-line summary of every level — the table the CFO reads first, before drilling into the detail.

Level	Scope	New layer	Stack	Commercial logic	Term
L1	Point · Institution	SaaS HIS	SaaS	Signon + per-bed annual	3 yrs
L2	Institution	BPO-I	SaaS + BPO-I	Reduced base + Δ-above-baseline performance fees	5 yrs
L3	Institution · Ecosystem	EcoOS	SaaS + BPO-I + EcoOS	Hub + nodes + transactions + net-new share	7 yrs
L4	Ecosystem · Sovereign	Equity	SaaS + BPO-I + EcoOS + Equity	Reduced cash + mutual equity + joint governance	10+ yrs

§ 06 · DECISION LADDER

Where on the ladder are you?

A few honest questions for hospital leadership. Where the answer is yes, the level on the right is where the conversation should start.

Do we just need modern HIS software with predictable annual cost?

Start at L1

Do we have measurable operational pain points and the data discipline to track improvement?

Climb to L2

Are we orchestrating — or do we want to orchestrate — a regional network of feeders, pharmacies, labs, and partners?

Climb to L3

Are we being positioned as critical national health infrastructure, with a 10-year horizon and willingness to share equity?

Climb to L4

Are we evaluating but uncertain about long-term direction?

Begin at L1 · Graduate as confidence grows

§ 07 · CLOSING NOTE

A pricing model is a contract with the future.

The IMEUS Ecosystem OS Levels framework is not a sales tactic. It is a structural commitment about how the relationship between a hospital and its sovereign health technology partner should evolve.

Hospitals that are not ready for L4 should not be sold L4. Hospitals that are ready for L4 should not be confined to L1 because the vendor lacks the structures to receive their commitment. The framework lets the relationship find its level — and lets the level rise as the relationship matures.

Software earns operations. Operations earn ecosystem. Ecosystem earns sovereignty. This is the IMEUS commercial doctrine.

For commercial discussion of any level: [email protected] · For procurement-ready calculations: companion Excel and HTML estimator (separate deliverables).