Reckon
Sign inGet started

Early access

The commercial record
your coding agent works from.

Every number traces to something the client said. Scope, pricing, and proposals built on immutable statements, deterministic math, and enforced provenance — so the agent reasons on solid ground.

HVAC system — Standard complexity, medium data sensitivity, 2 integrations, $185/hr

230 hrsconventional effort
−45.7%AI work-class reduction
125 hrspost-AI build effort
×1.28overhead — PM 10% · Comms 5% · Revisions 8% · Deploy 5%
160 hrs+ non-build delivery time
×1.10risk contingency (medium data sensitivity)
176 hrstotal delivery
×$185/hrrate
$32,534standard value
−12.6%discount
$28,435your price

Every number is deterministic. No AI inference in the calculation.

The commercial record

·
Immutable statementswith speaker, date, and evidence level
·
Requirements traced to statementsvalidated before they become scope
·
Scope items that cannot render without provenanceenforced in code, not convention
·
Versioned estimates and pricingevery revision preserved, reproducible
·
Full audit trail per mutationactor, action, before, after, reason
·
Deterministic reconciliationquotedValue ÷ rate = deliveredHours × 0.874
·
Deal state with enforced exit criteriacode decides transitions, not the model
·
Subscription entitlementsbrowser free, MCP requires Solo or Team

Working together inside Claude

Developer

Is the QuickBooks integration in scope for the Acme HVAC deal?

Reckon

Yes. QuickBooks Integration is scope item scope_007, Phase 1.

Traced to statement stmt_042: “I need it to sync with QuickBooks” — Jim (Owner), discovery call.

Requirement req_018: bidirectional sync with QBO for invoices and payments. Status: VALIDATED. Assumption: OAuth/API availability — VERIFIED.

The developer asks. Claude reasons. Reckon supplies the record — statement ID, requirement status, assumption verified. The provenance chain is traceable.