There’s a very specific moment most mobility professionals know well.
You’ve run the cost estimate using your AIRINC tools.
You’ve outlined the policy.
You’ve sent the numbers.
And then the business replies:
“Oh. That costs more than we expected. What are the other options?”
It had already been a long week.
We had gone back and forth with the business multiple times.
First it was one policy.
Then a lighter version.
Then questions about allowances.
Then another conversation about overall cost.
By Thursday morning, they had finally landed on a direction. So I ran the cost estimate in our AIRINC tools. Carefully double-checked the inputs. Reviewed the policy assumptions one more time. Then I sent it over.
By Friday afternoon, I hadn’t heard anything back. I remember thinking: “Ok. Maybe we’re done. Maybe this one is settled.”
I was smooth sailing into the weekend. Then, I glanced at my email before leaving for the day.
“Thanks for pulling this together. It’s still higher than we expected. What would this look like under a different policy? Can you outline the cost difference?”
So back to the AIRINC tools I went.
New policy structure.
Different benefits.
Adjusted assumptions.
New estimate.
Then I opened both versions and that’s when the real work started, because now I had to calculate the difference manually.
Total cost under Policy A.
Total cost under Policy B.
Subtract.
Double-check.
Make sure the tax impact shifted the way I expected.
And yes, I pulled out a calculator.
Not because the estimates weren’t accurate, but because the comparison wasn’t built in.
So the comparison becomes my responsibility. On a Friday. At 4:47pm.
That Friday wasn’t unusual. It was just the most recent version, because the questions are always some variation of:
What if we reduce housing?
What if we change the policy?
What if we remove one allowance?
They aren’t unreasonable. They’re responsible. The business wants to see trade-offs. They want to understand cost differences before they make a decision.
But every “what-if” means rerunning the estimate, exporting the results, and then manually calculating the difference.
And doing it quickly. And that’s the part that adds up.
The business will always ask for alternatives. That’s not going to change, but the way we respond to those questions can. Navi was built for exactly this moment – the “what if” moment.
Instead of running isolated estimates and manually calculating the differences, Navi allows you to build multiple scenarios within the same employee record.
Change the policy.
Adjust the benefits.
Modify the assumptions.
Each scenario recalculates automatically. Then you compare them side by side, with the cost differences clearly outlined.
No exporting multiple files.
No manual addition or subtraction.
No calculator on your desk at the end of a long week.
You can outline the cost differences before they even ask. That’s decision support.
Because mobility isn’t about producing numbers. It’s about helping the business choose between options. If scenario planning requires separate runs, separate files, and manual math?
That’s not scenario planning. That’s recalculation.
Navi turns recalculation into comparison.
And comparison is where strategy begins.