You paid for pages. Now you pay for finished work.
fileAI is moving away from per-page pricing. Under outcome-based pricing, you pay only when an Agent Flow reaches a defined, successful outcome. Not for every file you send.
Charged for every page, whether or not anything useful came out the other end.
Outcome-based pricing
Starting from
$0.015 /completed run
Charged only when the Agent Flow reaches its defined outcome.
Why we changed it
Paying for effort was never the point. Here’s what moved us off per-page pricing.
Extraction isn’t the main deliverable anymore
fileForge has grown past pulling data off a page. It now runs complete Agent Flows that apply your business rules, reconcile documents, resolve exceptions, and post a finished result into your system of record.
Most customers want more than just “a file processed”
They want a posted, reconciled ledger entry. A resolved claim. A validated policy update. Billing for pages processed instead of the outcome delivered means billing for effort instead of value.
We’re joining a small group
Bain & Company reviewed pricing across nearly 200 B2B SaaS companies in June 2026 and found only about 10% of AI-native and hybrid vendors have moved to outcome-based pricing.
Most vendors still bill effort or output. We’re pricing for results.
How outcome-based pricing works
Every fileAI Agent has a built-in definition of “done”. That definition—not pages, not tokens—is what you’re billed against.
1
You send a file, record or case
An invoice, a claim packet, a policy update, a bank statement - whatever your Agent Flow is built to handle.
2
The Agent Flow runs your logic
It applies business rules, cross-checks evidence, resolves exceptions, and routes approvals, exactly as your SOPs require.
3
It reaches a defined outcome
A posted entry, a resolved case, a validate update - or an exception your contract explicitly counts as complete.
4
That’s one Billable Run
Price against the published starting price for that Agent. Tokens and model calls never appear on your invoice.
Never billed: technical failures, duplicates fileAI caused, and reruns fileAI triggered. If the job didn’t finish because of us, you don’t pay.
Agents & plans
Every Agent has its own plan and a published starting price per completed Run. Here’s what each on delivers, and what counts as one Run.
fileForge
the platform underneath every Agent
fileScout
Inspects and maps a file into system-ready data
Outcome Delivered
One page inspected, mapped and returned as an AI schema—or as an actionable exception.
An Agent Flow hitting a defined, successful outcome - a purchase packet posted to the ledger, a claim delivered for action. An actionable exception can count too, if your contract defines it as one.
How is an outcome defined?
An outcome is the finished result an Agent Flow delivers. Each self-serve fileLedger agent has one clearly defined outcome. Our fileForge and fileShield agents, listed with a starting price, can be customised to deliver the specific outcome you need.
Do I pay if a run fails?
No. Technical failures, fileAI-caused duplicates, and fileAI-triggered rerun are never billed.
How is this different from per-page pricing?
Per-page pricing charges for volume, regardless of outcome. Outcome-based pricing charges for finished, successful work. Cost tracks value delivered, not effort spent.
How do the volume bands work?
Pick a band based on expected annual Run volume. Price per Run drops as committed volume rises. Business plans can be customised to unlock greater volume discounts and feature customisation.
Get the starting run price for your workflow
Tell us which Agent Flow you’re evaluating and your expected volume, and we’ll walk you through pricing and tiers.
.svg)
.svg)
.svg)
.png)