Question 1

What does Floe need access to?

Accepted Answer

Five read-only inputs: the contract or order form, the vendor’s event logs or usage reports, the invoices, an export from your own system of record (helpdesk, CRM, claims, contact center), and your outcome rules. Nothing is written back to any system.

Question 2

Does my vendor have to cooperate?

Accepted Answer

No. The audit runs on what the vendor already gives you: usage reports, event exports, invoice detail. If they share more, the classification gets finer. It does not depend on them.

Question 3

What counts as a valid outcome?

Accepted Answer

An outcome passes three tests: it matches the contract definition, your records confirm it happened, and it meets your acceptance rule (not reopened, not escalated, not a duplicate). You set the rules. Floe applies them the same way every time.

Question 4

Is a model deciding what’s valid?

Accepted Answer

No. The classification is deterministic: same inputs, same answer, every line traceable to its source. There is no language model in the arithmetic.

Question 5

What do I get at the end?

Accepted Answer

Four numbers: dollars recoverable, cost per contract-valid outcome, cost per buyer-validated outcome, and the share of paid outcomes that failed your standard. Plus a dispute file with every outcome ID behind each number, and a renewal position with recommended contract language.

Question 6

How long does it take?

Accepted Answer

30 days for one vendor. Days 1–10 connect, 11–20 classify, 21–30 deliver. Pick the contract with the nearest renewal, ideally within 180 days.

Question 7

How is it priced?

Accepted Answer

Contingency, as a share of recovered credits, or a fixed per-vendor audit. Nothing found, nothing owed, and your exports are deleted.

Question 8

Will this damage the vendor relationship?

Accepted Answer

The adjudication method is published and findings are documented to a standard both sides can check. Vendors can read and propose; only your owner accepts. Vendors with accurate bills get faster renewals and fewer disputes out of it.

Question 9

Which contracts fit?

Accepted Answer

Customer-service, sales and voice AI billed per resolution, conversation, lead, appointment or similar outcome unit. Seat-only contracts have little to audit.

Question 10

Isn’t this what our FinOps or observability tool does?

Accepted Answer

Those tell you what you spent, at list price, by API key or trace. Floe reconciles what you were billed against what you contracted and what your systems confirm, down to the invoice. It reads those tools; it doesn’t replace them.

Question 11

What happens to our data?

Accepted Answer

Read-only exports, held for the audit, deleted if you walk away. Ask for the security overview before the pilot starts.

Question 12

What comes after the audit?

Accepted Answer

Renewal control on every AI vendor, then the cost and margin ledger the audit runs on. Each switches on without a new integration. None of it is required to get the first audit.

Vendor claimed	Contract-valid	Buyer-valid	Billed	Floe action
yes	yes	yes	yes	Accept
yes	no	no	yes	Credit
yes	yes	no	yes	Renewal lever
yes	yes	yes	no	Unbilled revenue
dup / reversed	no	no	yes	Dispute

Your AI vendor counts the resolutions. Then it sends the invoice.

The price per resolution is the easy part. The definition is what you're paying for.

Who picks the definition? The party sending the invoice.

Four numbers. One dispute file.

Contract → vendor logs → invoice → your records → your rules → one row per outcome

If a vendor bills you per outcome, Floe can audit it

Before you send us anything

No new budget line. Paid from what the audit finds.

Start with found money. The rest switches on.

Who's behind Floe

Before you send us anything

Before you send us anything