The Accounting Firm Growth Strategy Everyone Gets Backward
Share this article
Most accounting firms do not struggle to find growth strategies. They struggle to absorb the growth those strategies create.
Every year, firm leaders return to the same list: acquire another practice, invest in technology, add advisory services, or grow through referrals and specialization. Those are all valid choices. I have seen each one work.
I have also seen firms pull the right growth lever and create a bigger operational problem.
The strategy was not the constraint. The firm's operating system was.
By operating system, I mean the practical structure that moves work through the business: who owns each decision, where information lives, how one team hands work to another, and which systems enforce the process. When that structure was designed for a smaller firm, growth exposes every weak point at once.
That pattern is not unique to accounting. We see it across service businesses from $2 million to $50 million in revenue. Leadership chooses the growth strategy first. The operational design comes later, usually after the backlog, rework, and client frustration have already started.
The firm that grew fastest last year can easily become the firm carrying the most operational debt this year.
The Strategy Conversation Usually Stops Too Soon
Most accounting firm growth discussions center on four paths.
A firm can acquire a smaller practice to add revenue, staff, and clients quickly. It can buy technology to increase capacity per employee. It can add advisory services such as fractional CFO work or tax-planning retainers. Or it can grow organically through referrals and a sharper niche.
None of those choices is wrong. The mistake is treating the strategic choice as the completed plan.
Consider an acquisition. A firm buys a smaller practice that brings $1.5 million in revenue and 300 clients. The financial case looks clear. The operational reality is less tidy.
The combined firm may now have two practice-management systems, two onboarding processes, and two partner groups with different definitions of when a tax return is complete. Those differences do not resolve themselves. The firm can spend the next 18 months running two operating models while leadership tries to force them together.
The purchase price accounted for revenue and client count. It probably did not account for the cost of that friction.
Technology creates a similar problem. A firm replaces spreadsheets and email with a workflow platform. Six months later, the staff still exports data to spreadsheets because the new platform does not connect cleanly with the CRM, billing system, or practice-management software.
The software may be working exactly as designed. The missing piece is the design between the tools.
This is why I keep coming back to the same point: most businesses do not have a technology problem. They have a systems-design problem. Buying another tool does not decide how data should move, who owns the handoff, or what happens when an exception appears.
The same issue appears when firms try to automate before they define the process. A partner asks for an automated client reminder sequence, but the team has three different rules for when a reminder should go out. One manager sends it five days before a deadline. Another waits until two days before. A third calls the client instead because the relationship is sensitive.
Software cannot resolve that disagreement. It can only repeat whichever rule someone configures.
The design work comes first. Leadership has to decide which conditions trigger the reminder, who can override it, how the exception gets recorded, and what the next step is when a client does not respond. Once those decisions are clear, automation can reduce manual work without removing judgment from the people who need it.
Without that clarity, the firm automates inconsistency. The result looks efficient on a workflow chart and creates more cleanup for the staff handling real clients.
What Breaks First
When an accounting firm grows without redesigning its operations, three problems tend to surface early.
Client onboarding depends on one person
In many firms under $10 million, a partner or office manager carries the onboarding process in their head. That person knows which engagement letter applies, who runs the conflict check, what information the client must provide, and how the details enter the practice-management system.
That can work with 40 clients. It becomes a ceiling at 150.
If a growth initiative adds clients faster than the firm can redesign intake, the result is not clean growth. It is a backlog, inconsistent client communication, and one exhausted person trying to hold the process together.
Advisory work gets forced into a compliance workflow
Advisory services run on a different rhythm than tax compliance.
Compliance work is seasonal and deadline driven. Advisory work is ongoing and relationship driven. It requires recurring conversations, requests that do not arrive on a predictable schedule, and billing that often happens monthly.
When a firm adds fractional CFO work, forecasting, or cash-flow strategy without changing how it schedules staff, tracks time, communicates with clients, and defines completion, it creates two businesses inside one firm. The systems support only one of them.
The advisory practice then appears unprofitable or difficult to manage. The market may not be the problem. The workflow may be.
Referrals outrun delivery capacity
A focused referral engine is one of the least expensive ways to grow. It is also one of the fastest ways to expose a capacity problem.
If new-client volume rises 20 percent while staffing and workflow capacity stay flat, service quality drops. New clients feel the delay, and existing clients feel the attention shift.
The referral strategy worked. The delivery system could not carry what it produced.
A Practical Example
Picture a $12 million regional accounting firm with 40 employees, three partners, and a strong compliance practice. Leadership decides to build an advisory line offering fractional CFO support, cash-flow forecasting, and quarterly strategy sessions.
The demand is there. Two partners know how to deliver the work. The move appears straightforward.
Six months later, the firm has 11 advisory clients and loses money on every engagement.
Pricing is not the main issue. The firm schedules advisory work in the same system it uses for tax deadlines. That system assumes work arrives in seasonal waves and gets billed at year-end. Advisory requests arrive throughout the month. Meetings recur. Analysis changes as the client's business changes. Billing should happen monthly, but no one tracks advisory time separately from compliance time.
The same partners delivering advisory work also approve tax returns during the weeks their advisory clients need them most.
The strategy was sound. The firm needed three operational decisions before launch:
- A separate time category that made advisory profitability visible.
- Scheduling rules that protected advisory commitments during tax season.
- A monthly billing process built into the practice-management system.
Those changes are not expensive. They are not technically complex. They require leadership to treat operational design as part of the growth decision instead of work to clean up later.
That is the pattern I see when a growth initiative underperforms. Leadership gives the strategy serious attention. The operating system expected to carry it gets designed under pressure after launch.
Reverse the Order of Operations
The answer is not another strategy session. It is a better sequence.
Before committing to a growth lever, put the operational questions in the same room as the strategic ones. Three questions reveal most of the risk.
1. What will this strategy require that we do not have today?
An acquisition needs a plan to combine two client-facing processes within a defined period. Advisory expansion needs a way to track engagements with different cadences and definitions of completion. Referral growth needs a staffing and workflow model that can flex before the new volume arrives.
Name those requirements before approving the growth plan.
If the firm cannot describe what must change operationally, it has not finished designing the strategy.
2. Where does critical information live in someone's head?
This is one of the most common constraints we find in service businesses.
If one person remembers the onboarding sequence, pricing rules, client history, or handoff logic, that person has become part of the infrastructure. The business cannot add volume without adding pressure to the same individual.
Documenting that knowledge is only the first step. The firm also needs to assign ownership, define decision boundaries, and place the information in a system the right people can use.
That work is not glamorous. It has more impact than buying software that automates a process nobody has clearly defined.
I would also look for unofficial workarounds. A private spreadsheet, a folder on one employee's desktop, or a recurring message thread often contains the version of the process people trust. Those workarounds are evidence. They show where the formal system fails to support the job.
Do not remove them before understanding why they exist. Use them to identify the missing rule, field, or handoff, then rebuild that function in the shared process.
3. What is the smallest system we can test safely?
Firms often respond to growth by overbuilding. They buy an elaborate technology stack before they know whether the new service, acquisition model, or referral process works in practice.
Start smaller.
A firm piloting advisory services with three clients can use a manual but clearly defined workflow for 90 days. That test will reveal how meetings should be scheduled, what information must be captured, where requests stall, and how profitability should be measured.
Once the firm understands the work, it can automate the stable parts. Automating too early only makes an unclear process move faster.
How to Read the 2026 Growth Playbooks
M&A, technology investment, advisory expansion, specialization, and referral growth remain credible strategies for accounting firms in the $2 million to $50 million range.
The order matters.
If leadership asks, "Which growth strategy should we pursue?" before asking what operational design that strategy requires, the firm is optimizing the visible decision and ignoring the structure underneath it.
A better sequence starts with the load the business expects to add. Then leadership identifies where the current process would fail, decides what must change, and tests the smallest workable version. Only then does the firm scale the strategy.
That approach may feel slower during planning. It is faster once real client work begins because the team is not rebuilding the process while trying to deliver through it.
The growth strategy creates the opportunity. The operating system determines whether the firm can keep the gains.
Where I Would Start
If your firm is considering an acquisition, launching advisory services, or trying to convert more referrals, map where your current operation would break under 30 percent more volume.
Do not begin with a software list. Follow one client engagement from first contact through delivery and billing. Mark every point where a person re-enters data, waits for an answer, relies on memory, or carries work between systems by hand.
That map will tell you more about your growth ceiling than another list of strategic priorities.
At Foundari, we help service businesses design the operating systems that allow growth strategies to hold. If you want a second set of eyes on where your growth plan and daily operations are out of alignment, reach out. I would be glad to walk through it with you.


