The CFO needs a close-process case, while Procurement is comparing a cheaper bundle.
Finance protects credible savings claims, while Procurement protects a comparable commercial decision.
Who you’d be doing this for
“I spent Friday chasing receipts again, and the controller wants to know why it keeps happening.”
Tadesse Nshimiyimana · Expense Administrator
Runs expense-policy exceptions and prepares corporate-card spending for finance review at the prospect.
What is at stake
The CFO has paused the evaluation because Procurement sees a lower per-user price in a card-backed bundle. You must weigh a sharper economic case against assumptions the prospect will actually validate.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- per-user price vs. close-process value
- CFO proof vs. limited customer data
- forecast urgency vs. defensible assumptions
- Procurement comparability vs. differentiated outcomes
Why Navan
Navan Expense connects corporate cards, policy auditing, and ERP-facing reconciliation, so its value case must hold beyond a per-user price comparison.
Written with these in mind
Not your kind of problem? 54 more at Navan, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.