The Unlikely Catalyst
It started with a $14 coffee. Our lead designer submitted an expense for a working lunch with a client, and it sat in the approval queue for three weeks before being rejected because the receipt was "unclear." That was the moment our design team decided the finance process was broken.
The irony was not lost on us: a team of people whose entire job is to make complex things simple and intuitive was drowning in a process so opaque that no one could explain why a coffee receipt needed three manager signatures.
Building a New Expense Culture
We brought the design team's toolkit to the problem. We ran journey-mapping sessions with both finance staff and employees who submit expenses, treating the approval process as a product to be redesigned. The insights were humbling.
What emerged was a set of principles: every expense touchpoint should take under 30 seconds, employees should never need to re-enter data they have already captured, and the default answer should be approval rather than suspicion.
What Changed for the Team
After switching to Zentry and applying our redesigned policy framework, the finance team reported a 60% drop in inbound queries from employees asking about expense status. The questions stopped because the answers were already visible.
More importantly, a cultural shift happened. Expenses stopped being something employees dreaded and became a fast, forgettable part of the job — which is exactly what they should be.
Lessons Worth Stealing
Apply design thinking to internal processes, not just customer-facing products. Your finance workflow is a product your employees use every day. If it is painful, you are losing productivity and trust.
Start by measuring the cost of friction. Count the hours spent on expense-related back-and-forth each month and multiply by average salary. That number will make the case for change better than any feature comparison.