
Why Professional Services Firms Struggle to Standardize Tools Across Practice Groups
A 90-person consulting firm has three practice groups. One tracks projects in Asana, one in Monday, and one in a spreadsheet that a senior manager built in 2019. Each group has its own client portal, its own e-signature subscription, and its own idea of where the final deliverable lives. Nobody chose this on purpose. It happened one reasonable decision at a time, and now the managing partner cannot answer a simple question: which tools does the firm actually pay for?
This pattern is common in professional services, and it has a structural cause. Understanding the cause is the first step to fixing it without starting a fight with the partners who run the revenue.
Why partnerships fragment by design
Most professional services firms are built on partner autonomy. A partner or practice leader owns a client book, a P&L, and a team. They are rewarded for results, not for conformity. When a tool would help them win work or deliver faster, they have the authority and the budget to buy it, and often a corporate card to do it with.
That model works well when the firm has 15 people. At 40, 80, or 150 people, it quietly produces a different outcome:
- Each group optimizes locally. A tax group needs different document workflows than an advisory group, and both are right. But a local optimum for each group rarely adds up to a coherent firm.
- Acquisitions and lateral hires import tools. A partner who joins from another firm brings a preferred stack. A merged practice arrives with its own contracts and logins.
- No one is accountable for the whole picture. The office manager handles purchasing, the MSP handles support tickets, and no one owns the question of whether the tools fit together.
None of these are failures of discipline. They are the predictable result of a governance model that was never designed for the firm's current size.
What fragmentation actually costs
The cost does not show up as one line item. It spreads across four places.
Duplicate spend. Two groups paying for separate subscriptions to the same category of tool is the visible part. For illustration, consider a 120-person firm with four practice groups where each group independently buys a project management tool at $15 per user per month for 25 people. That is $4,500 a month, or $54,000 a year, for a function that one negotiated firm-wide agreement would likely cover for less. The exact figure varies by firm, but the arithmetic is worth running with your own invoices.
Unused licenses. Industry research on software spend consistently finds that organizations do not use a large share of what they buy. Zylo, a SaaS management vendor, reported that companies use only about half of the software licenses they purchase, based on its 2023 data. Treat that as a vendor-sourced benchmark rather than a precise measurement, but the direction matches what most firms find when they audit their own accounts.
Security and compliance exposure. Every tool that holds client data is a place that data can leak. When each group chooses its own platforms, the firm ends up with inconsistent access controls, different retention settings, and no single list of where client information lives. This matters most for firms handling regulated data. An accounting or tax practice, for example, is a covered financial institution under the FTC Safeguards Rule, which requires a written information security program based on a risk assessment. You cannot assess the risk of systems you have not inventoried.
Friction on cross-group work. The most valuable engagements often draw on more than one practice group. When those groups use incompatible tools, someone exports files, re-enters data, or forwards email threads. That overhead is real, and it lands on the people who bill the most.
The shadow tool problem is getting worse
Tool sprawl used to mean a handful of extra subscriptions. Now it includes AI assistants that individual staff adopt on their own. IBM's 2025 Cost of a Data Breach Report found that one in five organizations surveyed had experienced a breach linked to shadow AI, and that organizations with high levels of shadow AI paid roughly $670,000 more per breach than those with little or none. The report also noted that most organizations lacked policies to manage or detect unsanctioned AI use. You can find the report on IBM's Cost of a Data Breach page.
For a professional services firm, the exposure is specific. Staff paste client financials, draft contracts, and engagement notes into public tools because it saves an hour. Without a firm-wide standard for approved tools, there is no clear line between acceptable and unacceptable use.
Why standardization efforts stall
Plenty of firms have tried to standardize and given up. The failures follow a few patterns.
- The mandate arrives without a reason. A memo announcing that everyone will move to one platform by quarter end reads as an IT preference overriding a partner's judgment. Partners ignore it or negotiate exceptions until nothing changes.
- The chosen tool fits one group. Standardizing on whatever the largest group uses leaves smaller groups with a tool that does not match their work.
- No one has the authority or time to run it. A migration needs a sponsor with standing to say no, plus someone who can manage vendors, data moves, and training. An office manager or an overextended IT generalist usually has neither.
- The firm standardizes everything at once. Trying to align project management, document storage, CRM, billing, and communication in one effort overwhelms the groups and guarantees pushback.
A practical framework for standardizing without a revolt
Firms that make this work treat it as a governance decision first and a technology project second. This sequence holds up in practice.
1. Build the inventory before you argue about tools
Pull 12 months of card statements, accounts payable records, and single sign-on logs. List every application, who pays, how many people use it, what data it holds, and when it renews. This usually surfaces tools no one remembered buying. It also turns the conversation from opinion into fact.
2. Sort tools into three tiers
- Firm standard: tools every group uses, such as email, file storage, identity, and security tooling. These are not negotiable.
- Approved by exception: tools a practice group justifies with a specific need the standard cannot meet, reviewed for security and cost.
- Not approved: anything that fails a security review or duplicates a standard without justification.
The middle tier is what makes the policy survivable. Partners keep a path to what they need, and the firm keeps visibility.
3. Decide who decides
Name a single owner for technology decisions across the firm. At firms of this size, that is often a role the firm has not hired for. A managing partner can sponsor the policy, but someone needs to do the work: evaluate requests, negotiate renewals, and say no with a clear rationale. This is the gap that fractional IT leadership fills, giving the firm accountable technology oversight without a full-time executive salary.
4. Start where the pain and the savings overlap
Choose one or two categories where duplicate spend is highest and the cost of fragmentation is most visible, usually identity, document management, or project tracking. Win those first. A successful consolidation in one area gives you credibility for the next.
5. Tie renewals to the policy
Most of your leverage comes at renewal. Set a rule that no software renewal above a set dollar threshold proceeds without review. This stops new sprawl without requiring a confrontation over existing tools, and it gives you a calendar of natural decision points.
6. Measure and report it
Track the number of applications, annual spend per head, and the share of tools that pass your security review. Report these to the partners twice a year. Standardization holds when partners can see the results.
Where the MSP fits
Your managed service provider is not the right owner for this, and that is not a criticism. An MSP keeps systems running: patching, monitoring, help desk, backups. Deciding which project management platform the firm should use, or negotiating a firm-wide contract against a vendor's list price, is a strategy and governance job. Elevaire Systems works alongside the MSP you already have. Your MSP keeps the lights on, and fractional IT leadership makes sure the lights are pointed in the right direction.
Frequently Asked Questions
How do we standardize tools without alienating our partners?
Give them a role in the process. Use the three-tier model so partners can request exceptions with a clear justification, and involve practice leaders in choosing firm standards. People accept constraints they helped shape far more readily than constraints announced to them.
How much can a professional services firm save by consolidating software?
It depends on how fragmented the firm is today. The reliable way to find out is an inventory of 12 months of spending: duplicate subscriptions and unused seats are the first places savings appear. Many firms also gain leverage by negotiating one firm-wide agreement in place of several small ones.
Does standardizing tools mean every practice group has to work the same way?
No. Standardizing the platform layer, such as identity, storage, and security, does not dictate how each group runs its engagements. Groups can still configure workflows inside shared tools, and they can request exceptions where their work truly differs.
How does this work alongside our existing MSP or IT team?
Your MSP continues to handle support, monitoring, and infrastructure. Fractional IT leadership sits above that relationship, owning the tool strategy, vendor decisions, and policy, and holding the MSP accountable to the standards the firm sets.
How long does it take to standardize tools across practice groups?
A first pass at the inventory and policy typically takes a few weeks. Consolidating individual categories happens over months and is best timed to contract renewals. Trying to finish in a single quarter is the most common reason these efforts fail.
How do we get started?
Start with the inventory: pull a year of card and accounts payable data and list every application with its owner, cost, and renewal date. Elevaire Systems can walk through that picture with you in a free consultation and recommend where to focus first.
About Elevaire Systems
Elevaire Systems provides fractional Chief Information Officer (CIO), Chief Technology Officer (CTO), and Chief Information Security Officer (CISO) leadership, along with infrastructure modernization, intelligent automation, and compliance strategy for growing organizations.
Ready to Put This Into Practice?
Schedule a free consultation and let's talk through what this means for your organization specifically.
