Ten to fifty, and the handover stops being a conversation.
FigsFlow is practice management software for growing accountancy practices — pricing delegated with guardrails, onboarding that runs the same way across every team, and capacity visible before it becomes a problem. The setup that held together at ten people needs different edges at thirty.
Partner or practice manager, start with what changes below. Team lead, jump straight to the FAQ.
- Teams Three teams · one shared price list
- Pricing Delegated · approval above a threshold
- Onboarding Same steps, every new client
- Capacity Visible before the deadline
- Audit trail Who changed what, and when
growth that does not need a new spreadsheet each time
Ten to fifty people.
If you have outgrown the point where one person can hold it all in their head
You are hiring, the partners are no longer across every client, and the informal way of doing things has started to cost you. The question is how to add process without adding a layer of admin.
What changes when process survives the next ten hires
Three shifts show up in practices between ten and fifty people, and none of them are about buying more software — they are about the same decisions holding when you are not in the room.
Pricing you can delegate
Team leads quote inside agreed bands, and anything outside them is routed for approval rather than quietly discounted.
Onboarding that does not vary
Every new client goes through the same steps, regardless of which team wins the work or who is on leave that week.
Capacity before the crunch
Workload sits against team and deadline, so resourcing decisions happen in November rather than in January.
How a growing practice phases it in
Map the current process
What is actually done today, not what the org chart says.
Set the pricing bands
And who signs off on anything outside them.
Pilot with one team
One team, one quarter — never at year end.
Roll out team by team
With a short review between each team.
Questions growing practices ask first
Four that come up on almost every call.
How do we roll this out without disrupting a busy season?
Most practices pilot with one team outside of January and the summer deadlines, then review before rolling out to the next team. A full rollout rarely needs more than a quarter.
Can we restrict who is allowed to discount?
Yes. Pricing bands are set per role, and anything outside the band routes to a named approver rather than going out at a team lead's discretion.
How does it handle clients moving between teams?
The client record moves with the client. Pricing history, engagement letters and the audit trail travel with the reassignment, so nothing is rebuilt from scratch.
What reporting do partners get?
A capacity view by team and by deadline, plus an audit trail of who changed what. Custom views can be configured on request.
See it running across more than one team
A short walkthrough built around your own team structure and approval thresholds, with no preparation needed.