.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Which Pricing Metric Fits Durable Medical Equipment Suppliers SaaS Best: Per Seat, Per Transaction, or Per Outcome?
A durable medical equipment supplier does not buy software merely to give staff another screen. It buys software to move a wheelchair, CPAP device, hospital bed, oxygen concentrator, or diabetic-supplies order through an exacting chain of documentation, insurance verification, fulfillment, billing, and collections. A missed signature can delay a claim. An incorrect modifier can trigger a denial. A slow authorization process can hold up patient care and tie up working capital.
That operating reality makes pricing unusually consequential. A supplier with 10 billing users may process 1,000 monthly orders; another with the same 10 users may process 15,000. A per-seat price treats them as near equals even though the software creates radically different value and may incur very different support, data-processing, and integration costs. Outcome pricing appears more aligned with reimbursement, but reimbursement depends on payers, physicians, patients, and changing coverage rules that the software provider does not fully control.
Monetizely’s position is clear: DME supplier SaaS should use transactions as its primary pricing metric, supported by a base platform fee and limited seat-based access. Outcome pricing should be reserved for narrow, auditable services where the vendor controls enough of the workflow to stand behind the result. The winning architecture is not a vague blend. It is a transaction-led model built around completed DME workflow events that customers can verify and finance teams can forecast.
DME economics reward pricing that rises with processed work
DME is a regulated, documentation-heavy business where volume creates both revenue opportunity and operational strain. Medicare’s Durable Medical Equipment, Prosthetics, Orthotics, and Supplies program requires suppliers to meet enrollment, quality, and claims requirements, while coverage and payment rules differ by product category and payer. A supplier does not simply ship equipment and send an invoice. Staff often must collect medical records, obtain physician orders, confirm eligibility, secure authorization, manage delivery proof, submit claims, resolve denials, and pursue payment.
Each step creates a practical question for the SaaS provider: what activity should trigger revenue?
A seat is easy to count, but it measures headcount rather than work completed. An outcome sounds attractive, but it can turn ordinary implementation and support disputes into contract disputes. A transaction, defined carefully, sits between those extremes. It reflects meaningful work completed in the supplier’s system while remaining observable and billable.
The distinction matters more as software automates tasks that once required users. A supplier that deploys automated eligibility checks, document collection, claim edits, and patient communications should not be penalized for reducing the number of people logging in. If a pricing model taxes efficiency, customers will either resist automation or share fewer workflows with the vendor.
The following ranking reflects that commercial reality.
Pricing metricRank for DME supplier SaaSVerdictWhat to do in practicePer transaction1Use as the primary meterCharge by completed order, claim submitted, or another customer-visible workflow event, with volume bands and a contracted annual minimumPer seat2Use for access, not core valueInclude a defined number of named or concurrent users in the platform fee; charge for specialist roles or unusually high user countsPer outcome3Use only for tightly controlled add-onsApply to measurable results such as recovered underpayments only when baseline, attribution, and exclusions are contractually clear
The table points to a simple conclusion: transaction pricing captures the scale of a supplier’s business without tying revenue to the manual work that software is meant to remove.
Monetizely’s 5-Step Pricing Framework provides a disciplined sequence for decisions that too often get collapsed into a rate card. The five steps are goals and segmentation, packaging, pricing metric, price points, and operationalization. Goals and segmentation determine which suppliers the company intends to win, such as a regional respiratory provider with 20 staff or a national distributor serving tens of thousands of patients. Packaging then defines what each offer includes, from intake and inventory through claims, patient payments, and analytics. Only then should the company choose the metric, set price points, and build the systems that meter usage, enforce entitlements, generate invoices, and support renewals. As Monetizing Agentic AI argues, pricing breaks down when a company picks a meter before it knows the job the product is performing.
For DME SaaS, the framework leads toward transaction pricing because the relevant customer segments differ most by order and claim throughput, not by login count. A 2024 CMS claim-processing rule can affect every order a supplier touches. A change in payer documentation requirements can create thousands of extra work items for a high-volume supplier but almost none for a small provider. Software value scales with that throughput.
The five steps also prevent a common mistake: treating all transactions as identical. A refill order with stored documentation may require little system work. A complex power-mobility claim may require authorization, documentation checks, delivery proof, and appeal support. The primary metric can remain transactions while package design distinguishes standard and complex workflows.
Seat pricing protects familiar budgets but punishes the customer’s efficiency
Per-seat pricing became dominant because it is easy to explain. Salesforce still prices many products by user type, including Sales Cloud editions sold per user per month as of its July 2025 pricing page. HubSpot similarly prices Sales Hub around seats, with a Professional seat listed at $100 per month on its pricing page as accessed in July 2025. Those products support work performed by identifiable human sellers and managers. More sellers often means more potential value.
DME suppliers do have identifiable users: intake coordinators, billers, warehouse staff, respiratory therapists, customer-service agents, and compliance managers. A seat charge therefore belongs in the commercial model. It just should not carry the economic weight of the deal.
Consider two suppliers:
Supplier profileUsersMonthly completed ordersValue created by workflow automationWhat pure seat pricing missesRegional respiratory supplier181,500Faster eligibility checks and recurring-supply processingModerate usage from a stable teamMulti-state DME platform1812,000Large reduction in rework, claim edits, and manual follow-upEight times the order volume with the same user countGrowth-stage mobility provider352,500Complex documentation and authorization supportMore specialists, but not necessarily more throughput
The table shows why seats are an incomplete signal. The first and second businesses could pay the same amount under a pure seat model while drawing substantially different value from the platform.
A pure seat model also creates a strategic contradiction. Suppose a supplier uses automation to reduce a 20-person billing team to 12 people while maintaining monthly claim volume. The customer has achieved the result the software vendor promised: more output with less labor. Yet the vendor’s recurring revenue falls by 40% if all pricing rests on seats. That is not a sustainable alignment of interests.
Industry evidence from adjacent software markets reinforces the pattern. Zendesk announced in February 2024 that it would price its AI agents at $1.50 per automated resolution, rather than price the product solely through agent licenses. The shift reflected a basic commercial fact: when automation resolves customer issues, human-agent seats cease to be a reliable proxy for delivered work. DME software faces the same pressure as intake, claim edits, eligibility, and communications become more automated.
Per-seat pricing has also created visible friction where user count is a poor measure of use. Basecamp’s public pricing has long offered organization-wide plans rather than charging every employee separately, a direct response to buyers’ dislike of escalating headcount charges for broadly used collaboration software. The lesson is not that every DME vendor should copy Basecamp. The lesson is that buyers resist a meter that rises when they expand participation but not necessarily when they receive more business value.
Transaction pricing links revenue to the supplier’s operating engine
Transaction pricing succeeds when the event is meaningful to the customer, measurable by the vendor, and close to both value and service cost. DME SaaS can meet all three conditions.
The most useful transaction is rarely a button click or API call. Those events are too technical and too easy to dispute. Better choices include:
A supplier recognizes these events. Operations can forecast them. Finance can reconcile them. Product teams can meter them without exposing internal system complexity to the customer.
Several B2B software companies demonstrate why meaningful transaction meters work. Twilio’s Communications Platform pricing is based on usage, including messages, minutes, and phone numbers, as shown on its July 2025 pricing pages. Stripe charges a percentage plus a fixed fee per successful card transaction in the United States, according to its July 2025 pricing page. Shopify’s merchant economics also scale with transaction activity through payment-processing fees, as disclosed in its 2024 Form 10-K filed February 2025. Each company charges on an observable event that customers understand as part of their own business volume.
The DME parallel is strong but not identical. A DME SaaS provider should not price like a payments processor simply because both touch transactions. The supplier’s transaction unit must reflect completed workflow work, not the dollar value of medical equipment sold. A $5,000 power wheelchair order should not automatically cost five times more to process than a $1,000 CPAP order unless the workflow and support burden truly differ.
A well-designed DME transaction model therefore needs clear boundaries.
Design choiceRecommended ruleWhy it mattersPrimary eventCount completed orders or claims submitted, not logins or clicksThe event maps to supplier throughputComplex workflowsCreate a separate rate for defined complex order classesComplex mobility and authorization work can require more system and support resourcesIncluded volumeBundle annual transaction capacity in each editionBuyers can budget; vendors secure committed ARROverageApply published or contracted per-transaction rates above the included amountRevenue grows when the supplier growsCredit rulesDo not count voided, duplicate, or test transactionsPrevents invoice disputesAudit trailShow transaction counts by location, payer, and workflow stageGives finance a way to reconcile the bill
The table identifies the practical discipline behind transaction pricing. The meter must be legible enough that an accounts-payable manager can trace an invoice back to operating activity.
Usage pricing can fail when buyers fear an unbounded bill. DME suppliers already manage uncertain reimbursement, prior-authorizations, denials, and seasonal demand. A vendor that introduces surprise overages will make procurement more difficult, not easier.
The answer is not to retreat to pure seats. It is to create a transaction-led annual commitment. The customer purchases a platform subscription with a stated volume allowance, receives a transparent rate for additional activity, and can select higher-volume bands at renewal or through a midyear true-up.
A $36,000 annual platform fee might include 6,000 completed orders, with a $4.00 rate for incremental standard orders and a separate $12.00 rate for defined complex authorization cases. Under that design, a small supplier knows its baseline spend. A growing supplier can expand without re-opening a seat negotiation. The vendor can support gross margin because heavy users generate more revenue rather than consuming unlimited capacity under a fixed license.
The following scenario shows the commercial consequences.
Annual customer profilePure seat model: 20 seats at $180/monthTransaction-led model: $36,000 platform fee plus volumeBetter alignment6,000 standard orders$43,200$36,000Customer receives predictable entry price12,000 standard orders$43,200$60,000Vendor participates in scale created by the platform6,000 standard plus 1,500 complex orders$43,200$54,000Price reflects costly, high-value workflow workAutomation reduces staff from 20 to 12 while volume stays at 12,000$25,920$60,000Vendor revenue remains tied to output, not avoided labor
The point is not that these precise rates fit every supplier. The point is that only the transaction-led model preserves the vendor’s economics when the product succeeds at removing manual work.
Snowflake offers a useful adjacent example. Its platform charges primarily based on consumption of compute and storage, and its 2024 Form 10-K describes revenue as driven by customers’ use of cloud services. The company’s meter is not an employee count because data workloads, not user headcount, drive both customer value and vendor infrastructure cost. DME workflow software has lower infrastructure variability than cloud data warehousing, but supplier throughput remains closer to its economic center than number of users.
Outcome pricing has intuitive appeal in DME. A vendor might offer to charge only for claims paid, denied claims overturned, days in accounts receivable reduced, or recovered underpayments. The promise is compelling because suppliers care about cash.
The trouble begins with attribution. A claim may be denied because the prescriber’s documentation was incomplete, the patient lost eligibility, delivery proof arrived late, a payer policy changed, or the supplier selected the wrong product. A SaaS vendor can improve workflows and still be unable to control payment. If the contract makes the vendor bear every external variable, the vendor will either charge a heavy risk premium or avoid the very accounts that need help most.
Intercom’s Fin AI agent illustrates the conditions under which outcome-like pricing can work. Intercom priced Fin per resolution at $0.99 when it launched the model in 2023, and its pricing page continued to describe a resolution-based charge in July 2025. The event is attributable: the agent resolves a customer conversation without human intervention according to defined rules. DME reimbursement does not offer a comparably clean event unless the vendor owns a much larger part of the claim-recovery process.
Outcome pricing can be appropriate for specialized services, including:
Each case requires a baseline period, a shared definition of success, exclusions for supplier-caused errors, payer-change protections, and data access. Those requirements make outcome pricing a premium add-on, not a simple SaaS meter.
The history of AI pricing offers a warning. Vendors increasingly move from per-seat pricing to usage or resolution models when automation replaces manual work, but they still need tightly defined events. Salesforce introduced Agentforce pricing at $2 per conversation in 2024, then added Flex Credits and other consumption options in 2025 as customers sought more flexible ways to buy agent capacity. The change did not prove that outcome pricing is wrong. It showed that a metric breaks when it lacks a stable, understandable unit of work.
For DME SaaS, a paid claim is often too far downstream. A completed claim submission, authorization request, or validated order is more controllable and more suitable as the core transaction. Vendors should earn a share of recovered reimbursement only where they can document their contribution and manage the workflow end to end.
Product telemetry determines whether the pricing model can survive renewal
A transaction meter is a product decision as much as a pricing decision. If a vendor cannot reconstruct why an order was counted, it cannot defend the invoice. If it cannot separate a canceled order from a fulfilled order, the customer will distrust the meter. If implementation teams manually reconcile usage in spreadsheets, margin disappears before the renewal conversation begins.
The operating requirements are straightforward but non-negotiable:
HIPAA does not dictate a specific SaaS pricing metric, but it raises the stakes for data governance. The HHS Office for Civil Rights states that covered entities and business associates must protect the privacy and security of protected health information under HIPAA rules. A pricing system should therefore meter workflow events and account identifiers rather than retain unnecessary clinical content for billing analysis.
The implementation sequence matters. A company that launches transaction pricing without customer-visible measurement will face sales exceptions, finance credits, and renewal friction. A company that builds clean events first can make the pricing model feel routine.
A transaction-led architecture gives each stakeholder a reason to support the change
Commercial models survive when stakeholders see their interests in the design. A COO wants cost to scale with operations rather than with a fluctuating staff roster. A CFO wants an annual commitment and a credible forecast. A chief compliance officer wants a defensible audit trail. A vendor’s chief revenue officer wants expansion revenue that does not require a full enterprise renegotiation each time a customer opens a new branch.
Per-transaction pricing satisfies those needs better than its alternatives when it is framed as business capacity rather than as a surcharge. The supplier is purchasing a system that can process a defined volume of work reliably. Extra activity costs more because the supplier is using more of the platform’s operational capacity and receiving more economic benefit.
Sales teams should not lead with “usage-based pricing.” That phrase can imply volatility. They should lead with the customer’s annual order and claims plan, explain the included capacity, and show how the supplier’s cost changes at 80%, 100%, and 120% of forecast volume. The buyer should see what it will actually pay over three years under realistic growth scenarios.
Monetizely’s position is therefore not to eliminate seats or reject outcomes. Seats belong in entitlement design. Outcomes belong in tightly bounded recovery or approval services. Yet neither should displace the transaction as the primary meter for core DME supplier SaaS.