The platform for outcome-based work.

Built for a world where companies and agents increasingly buy, sell, and act on results instead of through seats or usage.

Get started free Explore the platform

Seats were provisioned.Usage was metered.Outcomes have to be operated.

Outcome-based work creates a new operational layer between the agreement, the evidence, and whatever happens next. Spoolis runs that layer.

Outcomes aren't events. They're maintained state.

An event happens once. An Outcome keeps changing as evidence, reviews, disputes, and corrections arrive. Spoolis keeps it current, keeps every version, and every system reads the same one.

out_7Q2K · click a moment

ReportedMatchedDisputedCorrected

Reportedout_7Q2K

Claimed10,000

Accepted—

Open10,000

v1 · current10,000 claimed, nothing accepted yet

What each system can do now

Billingcan’t invoice yetblocked

Financenothing to bookblocked

Workflowwaiting on evidenceblocked

Agentcan’t continueblocked

Acceptedout_7Q2K

Accepted9,412

Rejected338

Uncertain250

v1 · current9,412 accepted against your records

What each system can do now

Billinginvoice 9,412unlocked

Financeaccrue 9,412unlocked

Workflowretry 338unlocked

Agentcontinue on 9,412unlocked

In reviewout_7Q2K

Final9,326

In review86

Rejected338

v1 · current86 disputed, 9,326 final

What each system can do now

Billinginvoice 9,326, hold 86partly held

Financebook 9,326unlocked

Workflowroute 86 to reviewunlocked

Agentpause on 86partly held

Correctedout_7Q2K

Accepted9,398

Rejected352

Change−14

v2 · current9,398 accepted after correction

v1 · history9,412 accepted, superseded, kept

What each system can do now

Billinginvoice 9,398, credit 14updated to v2

Financeadjust −14updated to v2

Workflowretry 14updated to v2

Agentcontinue on v2updated to v2

Products

From defining the outcome to deciding what gets paid.

Outcome PricingFor sellersPrice and sell results, not seats.

Define the billable Outcome, model it on your own history, and send accepted results into billing.

See Outcome Pricing →Outcome GuaranteesFor sellersStand behind the outcomes you sell.

Model what you can afford to promise, then operate the guarantee through performance and remedy.

See Outcome Guarantees →Outcome AcceptanceFor both sidesAgree on what counted.

Set the rules, verify the evidence, and give both sides one signed result they can act on.

See Outcome Acceptance →Outcome SpendFor buyersPay for what actually counted.

Check outcome-priced invoices against your own rules and records before approving payment.

See Outcome Spend →

Built for sellers, buyers, agents, and developers.

For sellers

Sell outcomes without rebuilding the machinery behind them.

Define what counts, prove accepted work, handle corrections, and give customers a result they can trust enough to pay. Add fee-at-risk, credits, or re-performance to the same Outcome without building a second system.

SpoolsBring Your Own JudgeOutcome ReceiptsOutcome Guarantees

For sellers →See how outcome pricing runs →See Outcome Guarantees →

For buyers

Pay for what actually counted.

Reconcile vendor-reported outcomes against your own rules and records. See what matched, what changed, what needs review, and what should actually be payable, across every vendor.

Reconciliation StatementsAcceptance ReviewsDispute Resolution

For buyers →Check an invoice →

For agents and developers

Turn “done” into a result software can act on.

Define what counts, bring your own judge, and get back one durable Outcome with evidence, uncertainty, corrections, and history attached. Billing, workflows, and other agents can act on the same result.

REST APIMCPSandboxCLIOffline verification

For developers and agents →Read the docs →

Works with your stack

Keep your stack. Give every system the same Outcome to act on.

Spoolis connects the systems that know what happened with the systems that act next. The same Outcome carries any kind of work your agreement defines.

Support resolutiona ticket closed without a handoff

Support handoffan escalation a person picks up

Lead qualificationa lead that meets the agreed bar

Code changea changeset merged into your codebase

Fraud decisionan order approved or declined by fraud protection

Vulnerability findinga validated security finding

Chargeback recoverya chargeback actually won

Outcome-linked termsa contract term tied to a result

Or your ownwhatever your agreement defines as done

Agent to agent runs on the same object: an agent can read the Outcome, see what counted, and act without a person in between.

How vendors define an outcome →

Support resolutionsData enrichmentAgent tasks

Evidence in

Spoolis

Systems that act

Ticket systemclosed, reopened
Customer surveysatisfied or not
QA reviewersamples 5%

Outcome · resolved ticket

9,412

9,412 accepted338 rejected250 uncertain

Counts when closed without handoff and not reopened in 7 days.

Moneyinvoice 9,412 resolutions
Workreopen 338 tickets
Recordsbook the accrual
Agentshand 250 to a person

Vendor file48,210 + 1,904 rows
Schema validatorfield rules
Dedupe checkagainst your CRM
Email verifierdeliverable or not

Outcome · enriched record

48,210

48,210 accepted1,904 rejected

Counts when the schema is valid, the record is unique, and the email verifies.

Moneypay for 48,210 records
Workre-request 1,904
Recordsload 48,210 into CRM
Agentsstart outreach on accepted only

Pull requestdiff and author
CI rungreen or red
Test suite312 checks
Code reviewerapprove or change

Outcome · completed task

298

298 accepted14 sent back

Counts when CI is green, tests pass, and a reviewer approves.

Moneycharge for 298 tasks
Workdeploy 298, retry 14
Recordswrite the change log
Agentsstart the next task

The platform

One lifecycle. Every piece it takes to run it.

Everything between the agreement and the systems that act next. Use it through a product, or compose the pieces yourself.

Explore the platform →

01
SpoolsFreeze what counts, what evidence matters, and who judges, before the work starts.Docs →
02
Bring Your Own JudgeYour check, your model, your reviewer, or your evaluator decides. Spoolis records the verdict and its provenance.Docs →
03
Outcome ReceiptsA signed, portable record of what counted, per unit, verifiable offline by anyone.Docs →
04
Acceptance Reviews and Dispute ResolutionUncertain units go to a named person with one link and one deadline. Disputes run under the agreement to a superseding receipt.Docs →
05
Reconciliation StatementsClaimed, accepted, rejected, needs review, the difference and why, as a statement, a booking row, a CSV, or a meter event.Docs →
06
Performance PromisesPut your own promise behind the work: your threshold, your judge, your remedy, run against the same accepted result.See how promises work →
07
Agent interfacesSandbox, MCP server, Outcome Receipts API, CLI, and the Verify action. Try it, wire it, let an agent use it.Docs →

Fastest start

paste this into your coding agent, then ask it to integrate Spoolis

Start with a product. Build anything on the platform.
Read https://spoolis.com/machine.md, then use https://spoolis.com/openapi.json for the HTTP contract.

Try Spoolis on real work.

Every Outcome also builds a history of what was promised, accepted, corrected, and what held up.

Get started free Read the docs

Free toolCheck an invoiceMatch a vendor invoice to your records.Free toolSee how outcome pricing runsTurn outcome terms into acceptance rules, each quoted from your text.DevelopersCall the API or MCPCreate and read Outcomes from your own code.Talk to usContact usTell us about your use case and we will tell you if it fits.