Your pipelineleaks whereyour reportssay fine.
Routing Forensics reads your CRM routing, checks it against production every night, and shows you exactly where leads go missing.
Free, in your browser, nothing uploaded. The nightly Monitor works with Salesforce and HubSpot.
Illustration. The tags are real defect types the scan detects.
of B2B leaders say routing must be fixed before AI can scale.
actually have the systems to do it.
The gap between those two numbers is where your leads go missing. An AI agent pointed at it just loses them faster.
LeanData, B2B State of Martech & Revenue Operations 2026. 201 senior leaders at companies of 2,500 or more people, seven countries, April 2026.
What slow and missed leads cost you.
Put in your own numbers. Nothing is sent anywhere: it is worked out on this page.
Pipeline at risk every month
£0
About £0 of revenue a year at your win rate.
- Leads nobody contacted£0
- Leads contacted after the first hour£0
You against 1,000 B2B software companies tested
An estimate from your inputs, not a promise. Leads nobody contacted are valued at your own opportunity rate; late leads at the lift you set. Benchmarks: RevenueHero, 2024, demo requests sent to 1,000 B2B software companies, almost all of 51 to 500 people, automated replies included. Why speed matters: Harvard Business Review, 2011. The nightly Monitor measures yours.
Every defect graded, in seconds.
Drop your routing export on the page. Each problem comes back with its proof and its fix.
- Nothing is uploaded
- Configuration only, never a lead record
- What it cannot prove, it says so
Then it watches every night.
The Monitor counts what routing did to real leads in Salesforce and HubSpot, puts a value on every leak, and tells the owner the first night something breaks.
Where leads went missing last night, worst first, with a value on each leak.
Demo org, synthetic data.
Go as deep as the problem.
Start free on the configuration. Add production checks every night. Bring in the founder for what software cannot prove.
Scan
Grades every rule, flow, queue and picklist your routing depends on.
FreeSelf-serve, in your browser
Run it nowMonitor
Counts what routing did to real leads every night, puts a value on it, and alerts the first night something breaks.
Set with early access teamsPer connected CRM
Ask for early accessForensic Audit
Every rule decoded and proven by hand, with the owner in the room. Ends in a decision, not a document.
£8,000–12,0003–4 weeks, fixed fee
Ask about an auditSix questions. Can you answer them?
Each one has a factual answer that is either in your system or is not. No form, no email.
How many leads from the last 30 days are still sitting at Status = New?
Does every round robin step pull an untouched lead back?
Can you name the owner of every routing rule running today?
What share of leads reach a rep with no campaign attached?
When a rule silently stops matching, does anything alert anybody?
Do all your product lines share one country-to-territory map?
Answer all six and your read appears here.
Built by someone who has carried the number and owned the stack.
When two systems disagree, somebody has to decide which one is telling the truth. That question has landed on my desk for years.
I started on the phones. Nineteen years later I run global marketing operations for an enterprise software business. Routing Forensics is that judgement written down as checks, and run every night.
- Director, Marketing Operations
- years in sales and operations
- Teams in the UK, Spain, Bulgaria and the US
- Salesloft Certified Administrator
- English, Italian, Spanish
Get the nightly Monitor before launch.
A small group of teams run the Monitor on their own CRM while it is being built. In return, they help decide what it checks first.
You get
- The Monitor on your CRM before anyone else
- A direct line to the person building it
- Founding pricing, held while you stay
It asks for
- A read-only user. Never write access, never admin rights
- Thirty minutes a fortnight
- A named owner who will act on what it finds
Before you ask.
Is it live?
The scan is: run it in your browser on your own export, or on a sample org. The Monitor runs today for early access teams, operated by the founder, and becomes self-serve after that.
Which CRMs does it work with?
The nightly Monitor works with Salesforce and HubSpot, and with both at once if marketing runs in one and sales in the other. On Salesforce it also checks native assignment rules, Flow, LeanData and Traction Complete. The free scan reads a Salesforce configuration export. On another CRM? Tell us: requests decide what we build next.
What access does it need?
For the scan, nothing from us. Salesforce only lets a user export configuration if they could also deploy changes, so your own admin runs the export. For the Monitor on Salesforce, one read-only user built from a permission set we supply, so your admin can read exactly what it grants. No create, edit, delete or metadata permissions. On HubSpot, you approve read-only access on HubSpot's own screen. HubSpot tells us every permission the connection holds, and if any could change a record we refuse it and keep nothing.
What does it keep?
Findings, counts, the queries that produced them, and the names of the users and queues holding the most of each count, so a finding says where. Not copies of your lead or contact records.
Our routing tool already has reporting. Why this?
A routing tool reports on what it did. It does not report on the leads it never saw, the rule that stopped matching last Tuesday, or the field that fed it the wrong value. An independent check does not grade its own homework. It works alongside native rules, Flow, LeanData and Traction Complete.
Who is it not for?
Teams on a CRM it does not support yet, for now. Pre-stack startups with nothing to check. And anyone without a named owner to act on the findings, because they will be accurate and nothing will get fixed.
Talk to us.
Early access, an audit, a CRM we do not cover yet, or a question about your routing. The founder reads every message.
About Routing Forensics. We check lead routing independently of the tools that run it. Read-only access, evidence behind every finding, and nothing asserted that the data cannot prove.
Or email hello@routingforensics.com