Your company’s brain shouldn’t walk out the door.
om asks the people who know, and keeps only what they approve. Every answer shows its source and owner.
The risk
When a key person leaves, the why leaves with them.
Why seat cuts are never refunded. Why coupons come off before tax. Only they knew why.
Vikram S. · Finance · last day Friday
- Why aren’t seat cuts refunded mid-period?No one to ask
- Why do coupons come off before VAT?No one to ask
- Why do downgrades wait for the period to end?No one to ask
Map once
om maps what your systems already know.
One onboarding pass reads your code, docs, tickets and threads. After that, every merged change updates the map.
Then on every merged PR: only what changed is re-read.
- Code and PRsGitHub · GitLab · Bitbucket
- DocsConfluence · Notion · Google Docs
- TicketsJira · Linear
- ThreadsSlack · Teams
- SupportZendesk
- IncidentsPostmortems · INC notes
- Calls and PDFsRecordings · contracts
Make it authentic
Nothing counts until the person who knows approves it.
om finds each rule’s owner, asks only what sources can’t answer, and settles conflicts before anything is trusted.
- Codebuild_pay_in_advance_fixed_charge_service.rb:31if delta_units <= 0 → build_zero_amount_feeEvidence
- Commentsame file · line 30“We don’t refund pay-in-advance”Duplicate, merged
- PRPR #4836 · QA return“Invoice should be generated but with a 0 fee”Evidence
- Older codePR #4763 · 8 Jan 2026return result unless zero_amount_fees_enabled?Conflicts with code
- Commentcharges/update_children_service.rb:28# skip touching to avoid deadlocksNot a rule, dropped
PR #4763 skipped the $0 fee when an org turned $0 fees off.
QA return #4836 settled it: always issue the $0 fee.
Owner check
Cutting units on a pay-in-advance fixed charge is never refunded.
A $0.00 fee still records the change, even when an org turns $0 fees off.
- Source
- build_pay_in_advance_fixed_charge_service.rb:31 · PR #4836
- Owner
- Billing team · fixed charges
- Approved
- Merged after QA, 15 Jan 2026
- Freshness
- Still true on main, 19 Oct 2026
Keep it
A brain that stays when people go.
Every rule keeps its source, owner and approval. When someone leaves, their rules stay and pass to a new owner.
When an owner leaves, every rule they approved stays lit, with its proof, and passes to the next owner.
Ask om
Everyone asks om. Every answer comes with its proof.
In chat, on a call, in Slack or Teams, or through MCP inside Claude, Cursor and Codex.
- Chat
- Phone call
- Slack
- Teams
- Claude
- Cursor
- Codex
- Support
- Finance
- Executive
MD
Meera D. · Product
A customer cut seats from 10 to 3 mid-month. Do we refund the 7?
No. Cutting units on a pay-in-advance fixed charge is never refunded. Lago issues an invoice with a $0.00 fee to record the change, even if the org has $0 fees turned off.
- Sources
- build_pay_in_advance_fixed_charge_service.rb:31PR #4836 · QA returnpay_in_advance_units_change_spec.rb
- Owner
- BTBilling team · Fixed charges
- Status
- Merged after QA, 15 Jan 2026Checked against main, today
Not in the code: why cuts aren’t credited instead. Asked the billing owner.
Trust
Built for the security review.
Your data stays where you put it. People see only what they’re allowed to. Every answer leaves a trail.
Runs where you choose
Your infrastructure, hybrid, or AppThentic cloud. Readers are read-only.
Never trains on your data
Enterprise AI models under zero data retention, or a model inside your network.
Access checked before retrieval
om checks who is asking before it reads anything. What isn’t allowed is never retrieved.
Every answer leaves a trail
Who asked, what om used, who approved it and when. Owners can correct it any time.
Unapproved means unapproved
AI readings are labelled until an owner approves them. When om doesn’t know, it says so.
Dev A. · Engineer sees what an admin allowedPayment provider terms · restricted, never retrieved
Stop rebuilding what your people already know.
Thirty minutes with the founders. We connect one of your systems and you ask om live.