Be careful with anyone who promises you a savings number.
You've heard the pitch. "We'll save you 15%." "We'll get your mod down by next year." It sounds great in the meeting.
Then a year goes by, and nobody can show you where the money went.
A promise isn't proof. Frost was built around that rule.
Why do savings promises fall apart?
Because most of them are never checked. A number gets said in a meeting, a year passes, the premium moves for a dozen reasons, and nobody can separate the work from the weather.
That matters more than it sounds. A saving only helps your net operating income if it's real. If you plan around a promised number and it never shows up, you've budgeted profit you don't have.
Owners deserve to know what actually changed.
What should you ask for instead?
Ask for a review and for proof. A saving should only be reported once it's verified.
That comes with a few rules worth holding anyone to:
- Every estimate is a range, and it starts with the safe number.
- Proven savings are kept separate from estimates.
- A saving counts only when a document proves it.
- A vendor's sales pitch never counts as savings.
That last one matters more than you'd think. Plenty of "savings" are really somebody's sales brochure.
It also means nobody should promise a mod number by a date. Your experience mod comes from the NCCI worksheet, and it reflects work done years earlier.
What's the difference between an estimate and a proven saving?
An estimate is what a change should be worth. It's useful for choosing what to work on first. It's not money in the bank.
A proven saving is what a change was actually worth, backed by a document: a revised invoice, an audit credit, a premium change tied to finished work, a claim that closed for less because it was reported fast.
The two should never share a column. When they do, the estimates quietly become the story, and the real number gets lost.
Here's a simple way to picture it:
- Estimate: "Collecting certificates from every sub should cut audit charges."
- Proven: "This year's audit charge for uninsured subs came in lower than last year's, and here's the audit statement."
Only the second one goes into the total. Only the second one counts toward net operating income in a plan you'd show your banker.
Estimates should also be weighed against what the fix costs. When a saving is proven, look at what it took to get there too.
How does the proof loop work?
The method is one loop: find the cost, set the plan, do the work, prove the savings.
- Diagnose. Ask the right questions and collect the right records.
- Baseline. Add up what risk really costs you across six areas. (See the hidden bill.)
- Plan. A 3-year goal, a 1-year plan and a named owner for each role. (See the one-page plan.)
- Commit. Pick 3 to 5 tasks for the next 90 days, each with one owner and a due date.
- Run. Meet on a steady rhythm and solve problems as they come up.
- Prove. Every finished task gets a short report signed by the owner and the advisor.
That signature is the heart of it. Both sides sign off, and the work is real.
Where does the proof live?
In a Frost program, everything lives in one place. The advisor works from the Console, and the owner's team gets its own Portal login showing the plan, what's owed and what has been proven.
You don't have to take anyone's word for anything. You can look.
The rhythm keeps it honest too: a day-60 check-in, a planning session every 90 days and a yearly session well before renewal.
What should you know about how your advisor is paid?
Ask. Whoever runs your program, you should know what they earn from it: commission, fees or both. Ask for it in writing, on each line. Here's how broker compensation and fees work.
What does proof do for you?
Proof changes how you lead.
You can show carriers the before-and-after work at renewal. You can show your lender a company that's getting safer. You can show your crews that the safety work is paying off.
And you can put a real number next to net operating income instead of a hopeful one. Tracked against revenue, it becomes your scoreboard.
From hearing promises to signing proof.
Try this
Look back at the last savings anyone claimed for your company: a lower premium, a new program, a vendor's pitch. Ask three questions:
- Is there a document that shows it?
- Did anyone measure it against a starting number?
- Did anyone sign off on it?
If the answer is no, it was an estimate at best.
Where to start
If you'd rather see proof than hear promises, ask your broker or risk advisor to set a Baseline with you, then hold every claimed saving up against it. Approved Frost agents run this kind of program for contractors, start to finish.
The reference entries behind this page: definitions, the math and the sources.
Risk baseline and verified savingsCost-benefit analysis of safety spendingBrowse the whole Library →Quick answers
Why shouldn't I trust a promised savings percentage?
Because a promise isn't proof. Estimates should be given as ranges starting with the safe number, and a saving should only be reported once a document proves it.
What counts as a verified saving?
A saving tied to a finished task, measured against the Baseline and backed by a document, with a short report signed by the owner and the advisor. A vendor's sales pitch never counts.
How do I see what's been proven?
In a Frost program, the owner's team gets a Portal login showing the plan, open tasks and the savings that have been proven.