Stay Agile — Shrink the Team, Grow the Revenue

Here's a conversation I have at least once a month. A founder says: "We just crossed $20M. We need to hire a staff accountant, a senior accountant, an FP&A analyst, and probably a controller." That's four new hires on top of whoever they already have.

My response is always the same: No, you don't. You need the right 3 people with the right systems. Maybe fewer.

The best finance teams don't grow linearly with revenue. They grow logarithmically. Double the revenue doesn't mean double the headcount. It means better tools, sharper processes, and people who can flex across multiple roles.

That's what Agile means in the RAID framework. Not just automation. Organizational agility.

The Headcount Myth

There's an unspoken assumption in the mid-market that more revenue requires more finance bodies. It's wrong.

Most companies between $15M and $30M should operate with 2 to 4 finance people if their systems are configured correctly. At $50M and above, maybe 4 to 6. Not 8 to 10.

The companies running bloated finance teams aren't doing it because the work requires it. They're doing it because their processes are manual, their systems are underutilized, and nobody has ever questioned the org chart. They've added people to compensate for bad workflows instead of fixing the workflows.

That's not scaling. That's patching.

What Agile Finance Actually Looks Like

Agile doesn't mean moving fast and breaking things. In finance, it means building a team and a set of processes that can absorb growth without proportional headcount increases. Three things make this work:

Flexible roles. Your accountant should be able to pull a report AND explain what it means. Your AP person should understand cash flow implications, not just enter invoices. When everyone on the team can operate one level above their job title, you don't need a specialist for every function. You need generalists who go deep when it matters.

Sprint-based projects. Stop treating system implementations and process improvements like six-month initiatives with steering committees and phase gates. Treat them like two-week sprints. Pick one broken process. Fix it in 10 business days. Move to the next one. We've seen companies accomplish more in 8 weeks of sprints than they did in 12 months of "transformation projects."

Scalable processes. Every process you build should work at 2x your current volume without adding people. If your revenue recognition process requires manual journal entries for every contract, it breaks at scale. If it's rules-based and automated, it handles 500 contracts the same way it handles 50.

The Cost of Over-Hiring

This isn't abstract. It's math.

Each additional finance FTE costs $70K to $90K fully loaded — salary, benefits, software licenses, management overhead. If you have 3 people doing work that 2 people plus automation could handle, you're burning $80K per year on inefficiency. That's not headcount. That's waste.

And it's not just the direct cost. Every additional person adds communication overhead, more handoffs, more meetings, more places for things to fall through cracks. A 3-person team that communicates well will outperform a 6-person team that doesn't, every single time.

Speed as a Competitive Advantage

Agile finance means speed in decision support. Your CFO — whether full-time or fractional — should be able to produce a pricing analysis in hours, not weeks. If someone asks "what happens to margin if we discount 15% on orders over $50K?" and the answer takes five days, your systems are too slow.

The bottleneck is almost never the analysis itself. It's finding the data, cleaning the data, and getting it into a format where the analysis is possible. Fix the data infrastructure and the analysis becomes fast by default.

Companies with agile finance functions make better decisions not because they're smarter, but because they can test ideas faster. They can model three scenarios before lunch instead of one scenario by Friday.

A Real Example

A $25M subscription brand came to us with a 5-person finance team and a finance cost running at 4.2% of revenue. They were growing fast — $12M to $25M in two years — and the CEO assumed they needed to hire two more people.

We didn't add anyone. Instead, we implemented automation across AP, bank reconciliations, and revenue recognition. We brought in a fractional CFO for strategic oversight two days a week. We cross-trained the existing team so three people could cover any function.

The result: they scaled from $12M to $25M with the same 3-person core team plus fractional support. Finance cost as a percentage of revenue dropped from 4.2% to 2.8%. They didn't just avoid hiring — they actually reduced the team by two through natural attrition and didn't backfill. The remaining team was less stressed, not more, because the manual work was gone.

The goal isn't the smallest team. It's the most leveraged one.

The Bottom Line

Agile finance isn't about cutting corners or running a skeleton crew. It's about refusing to solve process problems with headcount. Every time you're about to post a finance job req, ask: could we solve this with a better system, a better process, or better training for the people we already have?

Most of the time, the answer is yes. And the companies that figure this out don't just save money on payroll. They build finance teams that are faster, more adaptable, and better prepared for whatever comes next.