Outcome-Based Pricing for Document Automation
Most software charges for seats, pages, or tokens — whether or not any work got done. MaxxLogix® Outcome Cloud™ is different: you pay per outcome, for completed work your processes actually deliver. This page explains how outcomes work, how they're counted, and why that makes your costs predictable.
What is an outcome?
An outcome is a piece of work that reaches a useful business result — counted once, whether the process took two steps or twenty. The invoice is the document; the outcome is what got done with it.
Each of these is exactly one outcome:
- A form submitted and stored
- A form completed through a two-step approval with a digital signature
- An invoice imported, read, approved through seven steps, and posted to QuickBooks — “Invoice approved and entered”
- A patient intake packet captured, verified, and filed — “Patient registered”
- A contract drafted, redlined, signed, and archived — “Contract executed”
How Outcome Capacity™ works
Every Outcome Plan includes annual capacity across five measures, each counted on its own:
- Outcomes — per completed business result
- IDP Pages — per page read by IDP Outcomes™
- MaxxOwl™ SI Units — per Strategic Intelligence task, by complexity
- Repository — secure storage for your documents and records
- Import Sources — per connected source feeding the platform
One counting rule keeps it honest: when extracted data flows through a workflow to a business result, it counts as one outcome plus the IDP pages read. Extraction for indexing alone counts IDP pages only — no outcome. You never pay twice for the same work.
Plans built on outcomes
Outcome Plans — from Foundation to Enterprise Plus — bundle outcomes, IDP pages, MaxxOwl™ SI Units, repository storage, and import sources. Capacity packs expand any measure as your volumes grow. And every plan includes unlimited users: employees, managers, administrators, and approved partners can all participate without per-seat licensing costs. That's Capacity-Based Licensing — your investment tracks business activity, not headcount.
Why not per-seat, per-page, or per-token?
- Per-seat pricing charges you for everyone who touches the work — so collaboration costs extra.
- Per-page pricing charges for volume, not value — a page that goes nowhere costs the same as one that completes a process.
- Token billing ties your bill to model usage, which makes monthly costs variable and hard to forecast.
Outcome-based pricing charges for one thing: work that reached a result.
Tell us your volumes — documents, processes, users — and we'll map them to the Outcome Plan that fits.
Business Outcomes. Delivered.
