What Is an Outcome? Why We Price by Completed Work, Not Pages or Seats

What is an outcome?

Ask a software vendor what their platform costs and you’ll usually hear about seats, pages, or usage tokens. Ask what you actually get for that money, and the answer gets vague. We think the unit you pay for should be the unit you care about: finished work. That’s the idea behind outcome-based pricing for document automation — and it starts with a simple definition.

An outcome is a piece of work that reaches a useful business result. It’s counted once, whether the process behind it took two steps or twenty. The invoice is the document; the outcome is what got done with it.

That definition matters because documents don’t create value — completed work does. A scanned invoice sitting in a folder is storage. An invoice that has been read, validated, approved, and posted to your accounting system is a result. Outcome-based pricing charges for the second one.

How an outcome is counted

One process, one outcome — no matter how many steps, approvals, or documents it involved. 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”

Supporting measures are counted separately and transparently. When IDP Outcomes™ reads a four-page invoice that flows through approval into QuickBooks, that’s 4 IDP Pages plus 1 Outcome. If the same pages were only extracted for indexing and filing, they’d count as IDP Pages only — no outcome, because no business result was reached. You never pay an outcome charge for work that didn’t finish.

Why not seats, pages, or tokens?

Each traditional model charges for something other than results:

Per-seat pricing charges for every person who touches the work. Add a reviewer, an approver, an outside partner — the bill grows, so organizations ration access and collaboration suffers. MaxxLogix plans include unlimited users: everyone who participates in a process can participate, at no extra license cost.

Per-page pricing charges for volume, not value. A page that goes nowhere costs the same as a page that completes a process, and your bill rises with your paper problem instead of your results.

Token billing ties cost to AI model usage. Usage fluctuates with document complexity and retry behavior, which makes the monthly number variable and genuinely hard to forecast.

Pay per outcome instead, and the math changes: your investment lines up with completed work, capacity is planned annually, and growth in users doesn’t trigger a licensing conversation.

What this means for your budget

Outcome Capacity™ is planned, not metered by the minute. You choose an annual capacity aligned to the volume of business results your organization produces — outcomes, IDP pages, MaxxOwl™ SI Units, repository storage, and import sources — and expand any measure with capacity packs as you grow. Finance gets a predictable number. Operations gets a platform the whole organization can actually use.

If you’d like to see how your current document volumes translate into outcomes, read how our outcome-based pricing works — or tell us your volumes and we’ll map them to a plan.

Business Outcomes. Delivered.