The trust layer for business data

The dashboard says 24.
The spreadsheet says 12.

Kangaru finds where your numbers collide, gets each conflict decided once, and enforces the ruling every night. Numbers you can defend to your board.

kangaru · nightly collision scan
SYSTEM BI dashboard · CRM
metricvalue
Leads24
Booked revenue$412,500
Demos run36
Close rate33%
SELECT COUNT(*) FROM leads
WHERE created_at IN week -- counts every row
SPREADSHEET VP Sales · weekly_FINAL_v3.xlsx
metricvalue
Leads12
Booked revenue$389,300
Demos run36
Close rate42%
=COUNTIFS(status,"Qualified", duplicate,"No")
-- the real definition, written nowhere else
02:14:07reading both artifacts: 1,214 raw records, 2 formulas parsed
02:14:09tracing 24 → 6 canvass · 4 duplicates · 2 test entries → 12 remain
02:14:11COLLISION leads · dashboard 24 ≠ workbook 12 · hidden rule found in COUNTIFS
02:14:12→ one question sent to the owner. one answer becomes a permanent rule.
SYSTEM CRM · sales pipeline
metricvalue
Bookings (Q3)$1.24M
Closed-won deals58
Avg deal size$21.4K
Win rate31%
stage = "Closed-Won"
-- counts on signature date
SYSTEM ERP · finance
metricvalue
Booked revenue (Q3)$1.18M
Invoiced orders54
Avg invoice$21.9K
Open AR$204K
status = "Invoiced"
-- counts on invoice date
02:19:33no spreadsheet here. comparing 31 shared metrics across crm.production and erp.finance
02:19:35tracing: 58 signed in CRM → 54 invoiced in ERP · 4 orders never made it across
02:19:37COLLISION bookings · crm $1.24M ≠ erp $1.18M · “booked” means two different things
02:19:38→ signed-vs-invoiced is a decision, not a bug. one ruling ends the argument.
SPREADSHEET VP Sales · sales_weekly.xlsx
metricvalue
Commissionable rev$412,500
Jobs sold14
New leads12
Demos run36
=SUM(D2:D15)
-- every signed job counts
SPREADSHEET Finance · flash_report.xlsx
metricvalue
Commissionable rev$377,900
Jobs sold11
New leads12
Demos run36
=SUMIFS(D:D, credit,"Approved")
-- pending credit excluded
02:24:51same company, same week: two master workbooks, two owners, two truths
02:24:53gap traced: 3 jobs pending credit approval · $34,600
02:24:55COLLISION commissionable revenue · sales $412,500 ≠ finance $377,900
02:24:56→ sales and finance answer once, together. both sides run on one rule from now on.
The problem

Both numbers are “right.” That's the problem.

The dashboard counts every lead. The VP only counts qualified, deduplicated ones, a rule that exists nowhere except inside his COUNTIFS formula. Multiply that by every metric in the company, and this is what you get. Enterprises fix it with a full data team. Most companies can't justify one, so nobody fixes it at all.

Every Monday

Meetings start with a fight about whose number is real.

The same disagreements get rediscovered week after week, because the conflict gets argued but the rule never gets written down.

Every company

The real definitions live in one person's head.

When they're out, or gone for good, nobody can reproduce the numbers. Sometimes the formula is literally lost, and a remembered value gets typed in, quarter after quarter.

Every AI initiative

Agents built on contested numbers produce answers nobody believes.

Everyone wants AI in the workflow. What's standing between them and it is data the organization doesn't actually trust.

How it works

Collide. Decide. Enforce.
No rip-and-replace.

Your CRM, ERP, and spreadsheets stay exactly as they are. Kangaru runs alongside them.

01 / CONNECT

Read-only access. That's all we need.

Credentials to the systems you already run, plus the master workbook(s) your team actually trusts. Nothing installed, nothing migrated, nothing disrupted.

connected sources
crm.production● connected
erp.finance● connected
weekly_FINAL_v3.xlsx● parsed · 4 formulas
access levelread-only
02 / COLLIDE

Every disagreement, traced to the record level.

Agents compare each number across systems and spreadsheets, including the formulas, and surface the hidden rule behind every conflict. Not “the numbers differ,” but exactly which records and which rule.

collision report
COLLISION #7 · Leads, week of Aug 10
dashboard24
workbook12
gap traced to6 canvass · 4 dupes · 2 test rows
hidden ruleCOUNTIFS: qualified + deduped only
03 / DECIDE

One question. One human. One ruling, forever.

The system never decides what your numbers mean. Your people do, once. Each answer becomes a written ruling with a name and a date. Early on your team confirms each one; over time enforcement is automatic and the questions get rare. Within weeks, the business rules that lived in people's heads are documented, owned, and enforced.

ruling ledger · entry #14
Ruling · active
A lead = a qualified, deduplicated inquiry. Canvass contacts are counted separately.
decided by VP Sales · aug 26 · supersedes: none · enforced nightly
04 / ENFORCE

Verified every night. Drift caught, named, explained.

Every ruling is re-checked against fresh data nightly. When a number in a closed week moves, you don't get an alert that says “something changed.” You get the exact record that moved it, and why.

nightly tie-out
02:31:04 verify week 2026-08-03 · 4 metrics ..... OK
02:31:05 verify week 2026-07-27 · 4 metrics ..... OK
02:31:06 verify week 2026-07-20 · booked_revenue DRIFT
└─ change order #7312 (+$2,500) entered after close
02:31:06 diagnosis: timing drift · rule holds · owner notified
02:31:07 76 checks complete · rulebook intact
Why now

Nobody talks about the foundation of a house.

Every AI agent you want to deploy, from reporting to forecasting to automation, sits on top of your data. If people don't trust the numbers, they won't trust anything built on them. Kangaru turns your unwritten rules into a governed rulebook: the foundation your agents have been missing.

Sponsor-backed? This is how portfolio-company numbers become defensible to the board and comparable across the portfolio, without replacing a single system.

your systems kangaru rulebook reports everyone trusts AI that actually works

Your data stays yours.

Read-only

We never write to your systems. Your CRM, ERP, and spreadsheets keep working exactly as they do today.

Your rulebook

Every ruling is yours: human readable, exportable, and portable. It's your company's institutional knowledge, written down at last.

Your control

Your data is never shared, pooled, or used to train anything without your explicit permission.

Getting started

Two weeks. Read-only. Zero disruption.

WEEK 0

Connect

Read-only credentials and the workbook(s) your team runs on.

WEEKS 1–2

Trial run

We run alongside your reporting and deliver a report of every place your numbers disagree, and the hidden rules behind each conflict.

FROM WEEK 3

Rulings & enforcement

Your team decides each conflict once. We enforce and verify nightly, and your rulebook grows.

Try it on your data