It runs on someone else's dictionary
Your vendor decided what a job is, what done means, and who counts as the customer. Their definitions don't match yours. They never do. So the chart isn't blank — it's wrong, in a very nice font.
Business Intelligence Platform
The answers are already inside your business.
We go in and get them.
Every operation leaves evidence — in the quoting system, the schedule, the production log, the billing queue. Most companies pay a subscription to have that evidence ignored, beautifully. We build the layer that actually reads it, then hand you the keys.
Built for people in a hurry — press / to jump anywhere, ? for the rest.
01
Your dashboard is lying to you
Politely. Confidently. In your brand colours.
You've been renting it for five years
And you own precisely nothing. No schema, no pipeline, no history you can walk out with. Cancel on a Friday and the intelligence leaves with the invoice, waving.
Nobody has checked it since it was built
Somewhere upstream a join is quietly dropping four percent of your rows, and has been for years. The system says so isn't a source. It's a rumour with a login.
02
Four things — and you keep all four
When we leave, they don't come with us.
The Spine
One substrate under everything. Every record from every system you run — the ERP, the scheduler, the field app, the spreadsheet nobody admits to — pulled in, resolved to real entities and queryable in one place. This is the bit that makes every question after the first one nearly free.
The Taxonomy
Your vocabulary, written down and enforced. What a job is. What complete means. Whether the customer is the buyer, the payer or the one who signs. Most failed analytics projects were failed vocabulary projects wearing a technical disguise.
The Ninja
An AI that lives inside your data instead of next to it. Ask it anything in your own words. Better — it doesn't wait to be asked. It taps you on the shoulder when the margin drifts, when a site quietly stops following the process, when the thing that always goes wrong starts going wrong again.
The Deed
The schema, the pipelines, the code and the data are yours. On the balance sheet, not the P&L. That's the whole difference between five years of subscription and five years of something you can actually sell.
03
The mission
Nobody gets a twelve-month roadmap and a hope. Phases. Each one with a way out.
The Briefing
We map the terrain before anyone moves. Every system you run, every record it holds, and — the interesting part — every decision you currently make blind because the answer would take three days to assemble.
You walk away with a terrain map and a mission plan with a number on it. Fund it or don't.
Quick Strikes
Thirty to sixty days against the noisiest, most repetitive surfaces you've got — intake, verification, scheduling, follow-up, collections. This is where the automation goes, because this is where the leak is obvious.
You walk away with wins visible enough to pay for the rest of the mission.
Hold Your Ground
Gains evaporate without structure. So: the SOPs out of one person's head and onto paper, an org chart that matches who actually decides things, and a sixty-minute weekly cadence that keeps everyone honest.
You walk away with improvements that survive turnover, a bad quarter, and your own holiday.
Own Your Domain
The platform becomes yours outright — spine, taxonomy, ninja and code. You stop paying rent on the intelligence layer of your own company and start carrying it as what it is: an asset with a valuation attached to it.
You walk away with the deed. Rent becomes equity.
04
Rules of the dojo
Eight of them. Every single one was paid for by something going badly wrong first.
Verify first. Trust nobody's self-report.
Every claim gets a row count, a log line or a query behind it before anyone acts on it. Agents included — especially agents. A system reporting its own success is just a system with an opinion.
Taxonomy before technology.
You cannot measure what you haven't named. Agreeing what the words mean is the hard part and the valuable part. The tooling is downstream and frankly the easy bit.
The substrate is the asset. The dashboard is just a view.
Build the layer underneath and reports become disposable — make one, bin it, make a better one. Build reports first and you'll be rebuilding them forever, every time somebody asks a new question.
Graduate, don't gamble.
New work gets done by hand and verified. Then proven as a repeatable pattern. Only then does it run on its own. Nothing goes hands-off on its first outing, however good the demo looked.
Phases, with stop conditions.
Anything you can't take back — production config, client systems, migrations — moves through gates. Each gate has a verification and an explicit way to halt. Never one shot. Never a big bang on a Friday.
Audit adversarially.
Before anything ships, someone who sees only the artifact — not the reasoning, not the author — tries to break it. Work that survives a hostile reader is work you can put in front of a client.
Hard boundaries stay hard.
Regulated or sensitive data stays inside its boundary. No convenience carve-outs, no exceptions because the deadline is tight. Cross it once and nothing else you built matters.
Honest imprecision beats false precision.
If the data won't support a number, you get a range and the reason why. A decimal place invented to look rigorous is the most expensive thing on any dashboard.
05
Every industry, one skeleton
They all think they're special. They're all the same five moves in different costumes. Learn the skeleton and you can drop into any of them.
The universal spine
Demand→Commitment→Production→Delivery→Settlement
Plus the things that move through it — who, what, where — and the exceptions, which is where every business on earth quietly loses its money. A truss plant and a dental group run the identical skeleton in different dialects. The translation is the deployable part.
06
Map your terrain
Three questions. We'll draw where your records actually live, where they stop talking to each other, and what you can't currently answer because of it. No email, no signup.
- 1What do you run?
- 2Where do the records live?
- 3What are you guessing at?
07
Meet the ninjas
Two of us. One has run the floor at three in the morning. The other builds the machine so nobody has to again.
The Architect
Matt Rimmer
Data infrastructure · Entity resolution · Agent orchestration
- Origin story
- Spent long enough inside other people's analytics stacks to spot the con: gorgeous charts, billed monthly, balanced on a schema nobody in the building could explain. So he went and built the thing underneath instead — ingestion, entity resolution, the substrate that turns a three-day question into a three-second one.
- The tell
- He doesn't ask what the report says. He asks where the number came from. The system says so is where his conversation starts, not where it ends — and more often than anyone would like, the system has been wrong since before you got there.
- Signature move
- “Show me the row count.”
- Weapon of choice
- The taxonomy. Name things properly once and every question for the next decade gets cheaper.
The Operator
Jeff Oldroyd, MHA
Operations · P&L · Staffing · Contracts & M&A
- Origin story
- Started in financial services, then spent two decades actually running things — executive director, chief executive, co-owner. He has negotiated contracts across the table from people who negotiate for a living, made payroll in weeks where it was genuinely close, and bought and sold companies. He has never once been impressed by a dashboard.
- The tell
- He can walk an operation and find the constraint before lunch. Not the loudest problem — everybody finds the loudest problem. The one that, when you release it, drags everything downstream along with it.
- Signature move
- “Where's the leverage?” — Time. Money. People. Customers.
- Weapon of choice
- The mission plan. Phases with stop conditions, rather than a project plan with a wish stapled to the end.
Most business intelligence is built by people who have never had to make payroll. Most operators have never had an instrument they could trust. That gap is the entire reason this company exists.
08
The things you're already thinking
Asked in most first meetings, so here they are before the meeting.
We already have Power BI. Or Tableau. Or Looker.
Keep them. Those are views, and they're good ones. The problem is almost never the chart tool — it's that the numbers feeding it carry one system's definitions and nobody can reconcile them with another's. We build the layer underneath. Your existing tool gets better the day it points at it, and you don't retrain anybody.
Our data is a mess.
Everyone's is. That's the job. If it were clean and already joined you wouldn't need us — you'd need a contractor and a fortnight. Phase 0 is a terrain map precisely because nobody knows the true state of it until somebody actually looks, including you.
How long before we see anything?
The briefing is weeks, not quarters, and it ends with a priced plan rather than an invoice for discovery. Phase I aims at visible wins inside 30 to 60 days, because the automation goes where the leak is already obvious. That's deliberate: the early work should pay for the work that follows it.
Who owns what at the end?
You do. Schema, pipelines, code, data. That's the entire point of Phase III — the intelligence layer belongs on your balance sheet rather than ours. If a vendor won't tell you plainly what you own when you leave, that's the answer.
We're in a regulated industry.
Then the boundary is the product. Regulated data stays inside its boundary, with no convenience carve-outs and no exceptions because a deadline is tight. If that constraint makes a piece of work impossible, you'll hear it before you fund it rather than after.
How big do we need to be?
Big enough that two systems disagree and somebody spends a day a week reconciling them by hand. It has far more to do with how many systems you run than with headcount — a thirty-person operation on six systems has this problem worse than a two-hundred-person one on two.
What does it cost?
The briefing ends with a number for the mission, scoped to what was actually found. We won't quote a platform before seeing the terrain — that's how you end up with a six-figure surprise in month four and a build nobody can stop.
09
Request the briefing
We map the terrain — your systems, your records, and the decisions you're making blind right now — and hand you a plan with a number on it. No deck, and no discovery call that's secretly a sales call.