Method
How we arrive at our findings
Most revenue leak claims are an industry percentage applied to your revenue. Ours are calculated from your own deal and portal history and published with the range we’d defend. This page explains exactly how, including the parts where we stop.
The four steps
Detect, cost, band, route
Every finding in every report goes through all four stages.
Detect
We run a combination of human based interpretation and a range of detection patterns against your portal, read-only. Each action is a precise query, guided by our expertise and best practice knowledge. Every result gets checked and deciphered in detail by our team before it goes any further.
Cost
Each finding is valued using multipliers calculated from your own data, such as your win rate by stage from your closed deals, your average won value and your contact-to-deal conversion rate. Where a multiplier has to be assumed rather than measured, we say which one and where it came from. Industry averages appear nowhere in the calculation.
Band
Every calculated finding is presented as a range, with the two or three things that would move it stated plainly. The width of the band is critical, as a narrow one means we measured, a wide one means we’re estimating and you should treat it accordingly.
Route
Each finding is allocated to whoever should act on it: your team this fortnight, your admin with training, us doing the work, or a proper rebuild. On most reports the longest column is the one that says do it yourself. That’s not modesty, a report that routes everything back to the people who wrote it isn’t practical.
Where we stop
Two things we won’t do
Rule one
We won’t cost a finding that needs an assumption you haven’t made
If valuing something requires deciding what your lifecycle stages are supposed to mean, that’s a decision your business owns. We’ll describe the finding and leave it uncosted rather than dress our assumption up as your data.
Rule two
We won’t manufacture a finding to fill a report
Some portals are in good shape. Four real findings beat nine padded ones.
Try it
A rough estimate, built the honest way
Four inputs you already know. What comes back is a range, the formula that produced it, and a blunt note about which part of it is our guess rather than your data. That last part is the whole point of this tool.
Everything currently open, across all pipelines.
In AUD, excluding GST.
Percentage of deals you close. A rough figure is fine.
This is the input we turn into an assumption. See below.
Estimated value sitting in stale pipeline
— Low estimate · high estimateThe formula, in full
open deals × stale fraction × average deal value × win rate
The band comes from two places: a range on the stale fraction rather than a single figure, and ±15% either side of your stated win rate, because self-reported win rates are usually optimistic and occasionally understated when closed-won records aren’t kept clean.
The part that’s our guess, not your data
Our results are inferred from how often your pipeline gets reviewed, using a range we’ve drawn from portals we’ve worked in. It’s also the input the answer is most sensitive to. In a real Revenue Leak Report we don’t do this: we would count the actual deals past their close date with no activity, so the fraction is measured rather than assumed and the band gets much narrower. That difference is the entire reason a report costs $3,500 and this page is free.
“Not once have they baulked at a challenge, preferring instead to respond with excellent questions, suggestions and framing that helps us get to the heart of the issues.”Craig DavisCo-Founder · Logistics
Find out what your portal is costing you
The Revenue Leak Check is twenty minutes, free and read-only. One finding, calculatedfrom your own data, with the method and the range shown the way this page describes.