Policy feedback is arriving faster than recurring administrator problems can be separated from one-off complaints.
The feedback loop needs broad coverage, while Policy decisions need evidence a Product Manager can inspect and challenge.
Who you’d be doing this for
“I’ve flagged this same exception pattern three times, and every review starts from scratch.”
Kerem Aksoy · Expense Administrator
Runs policy exceptions and approval workflows for a corporate expense program.
What is at stake
Recurring policy-review friction is being buried across separate administrator feedback reads. You must decide what AI clusters, what Product Managers verify, and how the team runs the loop afterward.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- broad feedback coverage vs inspectable evidence
- faster discovery vs PM judgment
- customer context vs scoped access
- shared AI platform vs Policy-specific learning
Why Navan
Navan Expense Policy sits between automated compliance guardrails and the administrators who must explain exceptions at close.
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.