Knowledge base
Where your institutional knowledge lives.
Every team runs on knowledge that never made it into a manual – how commissions actually tier, which accounts get trued up, what counts as material. The knowledge base is where that knowledge gets written down, approved, and put to work on every run.
Every source, same journey.
- workbooksxlsx
- policy documentspdf
- free texttxt
Procedure document
v2 · approved
- reference tablesrate schedules, mappings, thresholds
- calculationshow each number is computed
- proceduresthe steps, in order
Written procedures as the source of truth.
Workbook extraction writes the procedures, just like how accountants would today with desktop procedures and policies – the source of truth every rule is derived from.
Rules you can read one at a time.
From the approved procedure, every rule is derived, risk-tagged, and machine-readable – reviewable on its own, versioned, and cited by the runs that use it.
Spot a gap? Modify or propose the rule.
Highlight the sentence in the procedure and propose the rule it implies – the draft lands in the review queue, and nothing goes live without approval.
Versioned, reviewed, approved.
Procedures and rules carry versions and approval states – edits go back through review, history keeps every version, and nothing reaches a run without sign-off.
Early pilot
We're onboarding a handful of early teams.
Tell us where your close hurts. That answer doesn't go to a sales queue – it goes to the founders who write the roadmap. Pilot teams get early access, and first say in what we build next.