witn is outcome-based billing infrastructure for AI agent builders. Instead of charging by tokens, seats, or API calls, witn lets you bill for verified results — a resolved ticket that stays closed or a merged PR that holds.
What is witn?
witn is a resolution engine that ingests events from your product, evaluates them against billable conditions you define in plain English, and confirms or rejects outcomes automatically. It outputs invoice line items with an auditable event trail. Built for teams building AI agents (coding, support, SRE, voice), witn runs on your existing event stream and is model- and framework-agnostic.
Key Features
- Outcome-native billing — Charge for verified results, not activity. Conditions are boolean rules evaluated over time; only confirmed outcomes appear on invoices.
- Define success in plain language — Set outcome terms from a dashboard. Use decision graphs, weighted scoring, or simple criteria like "rating > 3, within 48h".
- Real-time outcome resolution — Signals are evaluated as they arrive. Each event updates the outcome state until it is confirmed, failed, or settled.
- Settlement window — witn waits after the latest event (default 72h, up to 180 days) before finalizing. Reversals reset the timer, preventing billing for reversed outcomes.
- Per-customer contracts — Set custom products, prices, and outcome definitions per customer without branching billing logic.
- Simulation & replay — Preview changes by replaying historical events to see how outcomes and revenue would shift before shipping.
- Auditable event trail — Every signal and decision is recorded in order, so teams can answer disputes without digging through logs.
- Integration with existing stack — Works with Segment, Rudderstack, PostHog, and Stripe. No new systems required; forward events from where work happens.
Who is it for?
- AI agent founders and product leads — Monetize agent work by pricing outcomes (e.g., per resolved ticket) instead of tokens or subscriptions.
- RevOps teams — Define, simulate, and manage per-customer pricing strategies without code forks.
- Finance teams — Recognize revenue under ASC 606 with clear success criteria, a defined reversal window, and an ordered event trail for each outcome.
Use cases
- Customer support agents — Bill per resolved ticket that stays closed for a defined period; replays and reversals are handled automatically.
- Coding agents — Charge per merged pull request that holds without reversion; activity signals (commits, reviews) feed the condition.
- SRE and voice agents — Any agent that sends events can be monetized with outcome-based billing.
How does it work?
- Define outcome terms in simple language from the dashboard.
- Forward your existing events from your product (no new systems).
- witn resolves outcomes from signal to settlement — each signal updates state until confirmed, failed, or settled.
- Every charge is explained with an ordered event trail on the invoice.
FAQ
What is the settlement period?
The time witn waits after the latest event before making the current result final. Every event resets the timer. Defaults to 72 hours, can be up to 180 days, and is set per task contract.
What happens if a result is reversed (e.g., a support ticket reopens)?
Nothing is billed until settlement. A reopening event resets the timer and flips the condition, so the outcome does not confirm.
How is witn different from usage-based billing platforms like Metronome or Orb?
Usage platforms meter activity (tokens, minutes, API calls). witn bills verified outcomes. Activity signals feed the billable condition instead of landing on the invoice.
Do I need to rebuild my billing stack?
No. Keep your stack and send events from where work happens. witn tracks outcomes and produces invoice line items with an auditable event trail.
