Go-to-market · the business case

How a client buys it, deploys it, and trusts it.

Pricing, roadmap, rollout, compliance - and the hard questions, answered.

Business model

Three ways we get paid - all aligned to your outcome

Platform base, usage that tracks value, and a warranty behind the decision.

PlatformModel

Annual subscription, per institution

Charged on the governed core, connectors and the agents you license.

Predictable base; scales with the agents and verticals you turn on.

Per decisionModel

Usage-based, per decision rendered

Charged on every cited, warranted decision the fleet produces.

Price tracks value delivered - you pay for outcomes, not seats.

Decision warrantyModel

Priced on measured defect risk, insurer-backed

Charged on the liability we take on for auto-rendered decisions.

You buy a de-risked decision, not just software. Lower defects → cheaper warranty.

Land on one slice, expand agent-by-agent and vertical-by-vertical - the platform base is the same, so each expansion is mostly incremental.

Roadmap

Now · Next · Later

Land the beachhead, prove the warranty, then expand on the same spine.

Now

Residential income verification (the beachhead)
Verifier + Reviewer core agents live
Encompass overlay + write-back
Decision-warranty pilot with a launch lender

Commercial credit spreading & covenants
More residential conditions (assets, credit)
nCino / Moody's CreditLens connectors
Fair-lending & model-risk evidence pack

Later

Insurance underwriting + claims agents
Guidewire / Duck Creek connectors
Federated cross-lender judgment network
Higher autonomy (L3) on proven slices

Deployment

From shadow to autonomy, with a gate at every step

Tap a phase. Nothing auto-renders until it's earned - no rip-and-replace.

The agent runs silently alongside your team on real files, producing decisions nobody acts on yet.

Human reviews every case100%

Autonomy is earned - the human share only shrinks once the gate clears

Gate to advance: Decision agreement vs. your experts ≥ target; zero fair-lending flags.

Trust

Governance & compliance map

Tap a regime - the exact Arbiter control that answers it lights up.

Regulatory regime

The Arbiter control

Immutable Ledger

Append-only, hash-chained reason codes + evidence trail on every decision.

The Reviewer

Continuous four-fifths disparate-impact testing and nightly re-judging.

Proofset + drift

Golden sets, regression gates and drift monitors with model lineage.

RBAC + isolation

Role access, approval matrix, tenant isolation - your data never trains others.

ECOA requires

Adverse-action reason codes; no disparate impact

Arbiter answers with

Ledger reason codes mapped to ECOA + the Reviewer's continuous disparate-impact (four-fifths) testing.

Tap a regime to see which controls answer it.See the controls in the architecture

Concept · Illustrative · Independent study

How we control it

The four questions your risk team asks first

Each answer is a control you can click through to - not a paragraph.

When the AI is wrong, who is liable?

We are.

Warranty economics

How do you prove fair lending?

Every decision emits ECOA reason codes; the Reviewer runs continuous four-fifths testing.

The Reviewer agent

Model drift over time?

The Reviewer re-judges live decisions nightly and turns confirmed drift into signed-off policy amendments.

Proofset + drift monitors

What about hallucinations?

Grounded-or-abstain: every claim cites evidence or isn't made; arithmetic runs as code, not a guess.

The shared core

Objections, answered

Six more, answered straight

What a CRO, CCO or board asks next - lead clause first, one line to back it.

Those assist; Arbiter decides. Vendor-neutral, with no LOS to protect - it renders and cites the decision on top of whatever LOS you run.