Index

はじめる

See fileAI in action.

Book a 15-minute demo and see how fileAI turns your documents into decision-ready data.

Book a Demo

Quick answer

fileAI is retiring per-page pricing. Under outcome-based pricing, you pay only when an Agent Flow delivers the outcome it was built for—not for every file you throw at it. If a run fails for a technical reason, you owe nothing.

fileAI is retiring per-page pricing. Under outcome-based pricing, you pay only when an Agent Flow delivers the outcome it was built for—not for every file you throw at it. If a run fails for a technical reason, you owe nothing.

Why is fileAI moving away from per-page pricing?

For years, we priced by the page. Feed the platform 100,000 pages, pay for 100,000 pages—whether or not anything useful came out the other end.

That made sense when the deliverable was extracted data. It doesn’t anymore.

fileForge, our foundational platform, has long since outgrown just data extraction. It now runs complete Agent Flows: AI agents that ingest files, apply your business rules, reconcile data across documents and references, resolve exceptions, and post a finished result straight into your system of record. An insurer running a Claims Agent Flow doesn’t want a batch of files processed. It wants the claim done: zero-touch when it’s simple, with an adjuster-ready report when it isn’t.

Billing for pages processed instead of the outcome delivered means billing for effort instead of value. So we’re changing it.

This isn’t a fileAI-only shift. Bain & Company reviewed pricing across nearly 200 B2B SaaS companies (June 2026) and found that only about 10% of AI-native and hybrid vendors have moved to outcome-based pricing—most still bill for effort or output. We’re joining that 10% because it’s a better deal for you: you stop paying for effort and start paying for results.

Per-page pricing charges for every page, while outcome-based pricing charges one Billable Run per delivered outcome

What does outcome-based pricing mean at fileAI?

You’re charged only when an Agent Flow reaches a defined, successful outcome. No charge for a technical failure. No charge for a duplicate fileAI caused. No charge for a rerun fileAI triggered.

Outcome-based pricing means different things depending on who’s selling it. Elsewhere, it often ties payment to downstream business results—revenue lift, cost savings realized—outcomes that are hard to attribute and slow to verify. fileAI ties payment to something narrower and immediately checkable: a completed unit of work with a clear, contractually defined finish line.

Every fileAI Agent has that definition builtin. A “Billable Agent Run” is one file, record, case, or business packet delivered to its destination—or an exception resolved in a way your contract explicitly counts as complete. Technical failures never count, full stop.

How does fileAI’s outcome-based pricing work?

Every fileAI Agent—fileScout inspecting a file, a Purchase-to-Ledger Agent posting a payable, a Claims Agent assessing a case—has a published starting price per completed Run. You choose your plan based on expected volume, and the price per Run drops as your committed volume grows. Tokens, pages, and model calls stay internal cost inputs. You never see them on an invoice.

That’s a different model from commodity OCR tools like AWS Textract or Google Document AI, which charge well under ten cents a page because they’re selling a technical component, not a finished outcome. The price for fileAI’s Purchase-to-Ledger Agent is based on a completed packet, because it covers everything you no longer do by hand: coding, exception routing, posting to the ledger. You’re not paying for extraction. You’re paying for a finished, auditable outcome.

Why is outcome-based pricing better for customers?

  • Cost tracks value. You pay when we deliver a finished packet, a matched record, a resolved case—not when a file is merely touched. Fail for a technical reason, and you owe nothing.

  • Budgets stop being a guess. Committed Run tiers give your finance team a number to plan against. The outcome requirement means that number never includes work that didn’t happen. Our published starting prices and Standard Run definitions remove the ambiguity before you sign anything.

  • You pay for what you use, not what you guessed. Under per-page pricing, a straightforward file and one that triggers hours of exception handling cost the same. Outcome-based pricing prices the thing you actually value: a finished purchase packet, a resolved claim, a validated policy update.

What does outcome-based pricing mean for you?

We’ve always stood for governed, auditable, deterministic execution. Now our pricing matches our platform. You pay for finished outcomes, not files that pass through a pipeline.

Talk to fileAI about how outcome-based pricing applies to your Agent Flow—and get the starting Run price for your industry’s most critcial workflows.

Make. Work. Flow. Now we really mean it.

Related posts

今すぐはじめる

実行するほど、組織の記憶が育つ

実行するほど、組織の記憶が育つ

今すぐはじめる

実行するほど、組織の記憶が育つ

Related posts

Building the foundation for agentic AI

Building the foundation for agentic AI

Building the foundation for agentic AI