Find the revenue hiding in your dealer network.
XCOUTER's Market Velocity Engine (MVE) reads the ERP data you already have and shows which dealers are going quiet, which accounts are buying elsewhere, and where your next sale is.
Built for owners, GMs, sales leaders and CFOs of distributors with 10-200 people — food & beverage, building materials, healthcare. Starting in Florida.
Where it runs
In production at a US channel distributor: 250+ partners, 100,000+ transactions.
Four signals live, a fifth (Credit Risk) in development
The model underneath
We build the ontology underneath: the model that puts your partners, their movements, and their business into one picture — the map you have been commanding without.
Leakage
Reorders that stopped: customers who used to reorder every 30 days and went quiet.
Decay
Dealers going quiet: order cadence stretching, baskets shrinking — months before they're gone.
Commercial competition is a war of position. You cannot win a war you cannot see.
Wallet Share
What share of each dealer's buying you actually get.
Whitespace
Products a dealer should be buying from you and isn't.
Who you're actually working with
Twenty years of ethnographic fieldwork and digital solutions developed across forty-plus countries taught me that the number on the dashboard is never the thing that's happening. Distribution is full of people who know their business is drifting and have no instrument that shows it — so I built one.
Gabriel Bedoya · Founder, XCOUTER
Credit RiskIn development
Utilization patterns that move before the revenue does.
What MVE is
A living console of your business: every partner's position, momentum, wallet, and renewals, on your own single-tenant instance, live in days. It reads the data you already have — the ERP export you could send this afternoon — and tells you what's moving before it shows up in the quarter. That is the seeing half. The Market Velocity Engine (MVE) is the acting half: it turns a position into the moves your team makes on Monday, ranked, each one showing why it is on the list.
The Scan tells you which signal is bleeding you — deployment starts there.
How we work
Three stages. You can stop after any of them.
Scan
Architect
Operate
Start with the Scan
Two weeks, one ERP export, a findings briefing that names the signal bleeding you. If your business turns out to be tight, that's the cheapest audit you'll ever run.
A general with no map is not a general. He's a man with an opinion.
You are not short of data. You have every transaction of the last four years — every order, every partner, every renewal, sitting in the ERP. What you don't have is a way to look at it.
And the truth about a business is never in a single number. It's in how the numbers relate. A partner going quiet is worth knowing. A partner going quiet whose wallet is shifting to your competitor, with a renewal falling due in sixty days — that's not three facts. That's one situation, and it's the call you make this morning. No report puts those three things on the same page. A map does.
That's the work: not more data, and not another chart. A picture of your business accurate enough to act on, where you can see position, movement, and threat at the same time — the way anyone commanding anything has always needed to see them.
That picture has a name, and it is not a dashboard. It's an ontology: a model of your business in which partners, movements, baskets and renewals stand in the right relation to one another — so that "who is going quiet, whose wallet is moving, and what falls due in sixty days" is one question with one answer, instead of three reports you reconcile by hand at midnight. Building that model is the work. The picture is what falls out of it.