When headcount growth should not mean finance headcount growth
Bristol builds project management software for distributed engineering teams. When the company grew from 80 to 120 people in under eighteen months, the finance team — still just three people — became the single biggest bottleneck in the business. Every new hire meant a new card request, a new spend policy exception, a new approval queue. Every team lead had a different idea of what was in budget. And every end of month meant someone was untangling six weeks of approvals that had piled up in a Slack thread.
The team wasn’t slow. The tools were. Approvals lived in email. Budget visibility required a finance analyst to manually pull data from three systems and build a spreadsheet. By the time anyone knew a project was over budget, the money was already spent.
Approvals that move at the speed of the business
Bristol’s Head of Finance, Priya Anand, had one clear requirement when evaluating Pivoter: she needed approvals to be instant, not eventual. The previous process required a spend request to travel from team lead to department head to finance before a card could be issued. By the time it arrived, the deadline had often passed — or someone had used their personal card and submitted an expense instead.
With Pivoter, Bristol set up approval chains that mirror their org structure. A team lead can approve anything under €500 in their category. Anything above routes to the department head automatically. Finance only sees what falls outside policy — and gets an alert in real time, not at month end. Cards are issued instantly with pre-set spend limits. When a limit is hit, the card stops — no conversation needed.
The result: more scale, same team
In the quarter after rolling out Pivoter, Bristol’s approval cycle dropped from an average of five days to same-day. Finance admin hours fell by 40%. And for the first time, they closed a quarter with zero over-budget projects — compared to fourteen in the previous quarter.
Bristol has since grown to 200 people. The finance team is still three. Not because they’re stretched thin, but because Pivoter does the work that used to require headcount. Priya’s team now spends their time on forecasting, scenario modeling, and supporting the business — not chasing approvals and reconciling surprises.
