Service · ongoing
Monthly Revenue Leak Monitoring
We scan your portal every month and tell you what changed, what got caught, and what’s still open. One page you can hand to a finance director without translating it first.
What a finding looks like
Four example findings from one portal, shown the way we would show yours.
All four came from the same sample report.
Finding 02 · departed owners
$64,000 a year in deals owned by people who’ve left
Method. 38 open deals assigned to four deactivated users, the earliest inactive for 14 months. Valued at deal amounts on record, multiplied by your own win rate at each stage. Nobody is working these, and nothing in the portal will tell you that.
Finding 04 · stale pipeline
$118,000 a year in deals past their close date
Method. 61 open deals with a close date more than 30 days past and no logged activity since. Valued at the deal amounts on record, multiplied by your own historical win rate at each stage, computed from 412 closed deals over 18 months.
Finding 06 · missing close dates
$9,400 of uncertain and invisible opportunities
Method. 143 open deals with no close date set at all, worth $412,000 in total. We’ve costed only the small slice statistically likely to be lost through inattention, which is why the figure looks modest. The real cost isn’t leakage, it’s that none of these 143 deals appear in any forecast. Your pipeline reporting is currently blind to $412,000 of activity.
Finding 09 · lifecycle stages · not costed
We’re not putting a number on this one
What we found. Your lifecycle stages have stopped meaning anything consistent. Roughly 3,100 contacts sit in stages that contradict their deal status, and three teams are using the same stage names to mean different things.
Why we won’t cost it. This is almost certainly the most expensive thing in your portal. But costing it would require assuming what the stages are supposed to mean, and that’s a decision your business hasn’t made yet, not a measurement we can take. Any number we produced would be our assumption wearing your data as a costume.
What to do instead. Get the three teams in a room and agree what each stage means. That’s a two-hour conversation, not a project. Once it’s decided, we can measure the gap properly.
In a typical Revenue Leak Report, we include nine findings, each shown this way, then allocated to who should act on them. On most reports the longest column is the one that says do it yourself.
What lands each month
Three numbers and a changelog
Number one
New leakage
What appeared this month that wasn’t there last month. On a stable portal this is often near zero, and we’ll say so rather than dressing something up.
Number two
Total open
Everything currently detected and unfixed, so you can see whether the pile is growing or shrinking over time.
Number three
Value protected
Cumulative, since we started. An estimate of what was caught before it cost you anything, shown with its range, like every other number we give you.
The page
The changelog
What changed in the portal, what we caught, what got fixed, what’s still open, what we’re watching. Ninety seconds to read.
The honest bit
This only pays for itself if your portal moves
Monitoring detects drift. A portal that isn’t changing doesn’t drift, which means there’s nothing to find and no honest way to make the monthly report interesting.
- Worth it if you’re hiring reps, launching campaigns, adding integrations, or someone is actively building in the portal each month.
- Not worth it if your portal is stable, your team is small, and nothing has structurally changed in a year.
- Not a substitute for having someone who can do the work. We watch and report. We don’t fix things unless you ask us to separately.
We’d rather tell you at the Revenue Leak Check that you don’t need this than sell you twelve months of quiet reports.
Before you start
Fix something first
Monitoring works on a portal that’s been acted on. Watching a portal you already know is broken produces the same findings every month, which helps nobody.
- Run a Revenue Leak ReportSo there’s a baseline. Every monthly report references it, what we found then, what’s been fixed, what has come back.
- Act on itThrough AI Enablement, through us actioning a build or through your own team. Any of the three is fine. Doing nothing isn’t.
- Then start monitoringTwelve-month term, billed monthly. Recurrence is the strongest argument for this service, and you’ll see it in the data by about month four.
“This is the second time I have worked with CogniOps. Throughout our many engagements they have always gone over and above, immersing themselves in the company goals and acting as an extension of the team.”Jessica TurnbullMarketing Director · Logistics
Start with the baseline
A Frede Revenue Leak Check shows you one number today. The report gives you the full picture. Monitoring keeps it that way — but only once there’s something worth keeping.