Has your leadership team ever looked at a slow process, a disconnected workflow, or a frustrated team and thought, “We just need a better tool?” It’s a natural instinct. Something isn’t working, so you look for a solution.
But I’ve seen time and time again, working with firms across the country, the tools usually aren’t the problem. The problem is how those tools relate to each other and to your firm’s strategy, workflows and people. In other words, the problem is your architecture.
Understanding the difference is one of the most important leadership moves you can make.
The stack versus the architecture
Your tech stack is the collection of primary applications your firm relies on to get work done. It includes your practice management system, tax and audit solutions, document management platform, portals and communication tools. Many firms have very good tech stacks.
Architecture is how all those tools connect, communicate and support each other as a system. It’s the logic behind why you chose each tool, where data lives, how it flows (or doesn’t) from one platform to another and how the whole ecosystem serves your firm’s goals.
You can have excellent individual tools and a broken architecture. In fact, that’s exactly what many firms have, especially after growth, acquisitions or years of adding solutions one at a time to solve one problem at a time.
For example, through a merger or acquisition, your firm might inherit a set of tools the other firm used. Those tools weren’t chosen to complement yours. Data doesn’t flow between platforms, so your team members have to re-enter information or run parallel processes. You have an architecture problem that needs to be solved intentionally.
This isn’t just an IT problem
Technology decisions in accounting firms used to live almost entirely in the IT department. The partners decided what the firm needed, and IT figured out how to make it work. If data didn’t flow correctly or systems didn’t talk to one another, that was IT’s problem to solve.
That model is obsolete.
The technology decisions your firm makes should be inseparable from your business strategy, service model, talent pipeline and client experience. When systems don’t work together, it creates bottlenecks for your team, inconsistencies in client deliverables and blind spots in your firm’s data.
IT can absolutely help you clean it up. They’re an essential part of the conversation. But the decision to address your architecture is a leadership decision. It belongs in the room with managing partners, operations leaders, department heads and the technology team.
The cost of a short-term mindset
One pattern I see frequently is firms making technology decisions in silos. A tax partner sees a demo and wants to add a new tool. Marketing uses one CRM platform, client service uses another and nobody’s quite sure where the source of truth is. Each decision makes sense in isolation, but collectively they compound your architecture problem.
The short-term fix is to grab a new tool to solve an immediate pain point. But when you don’t consider how it fits into the broader system, that mentality is expensive in ways that aren’t always visible on a budget spreadsheet. It costs staff time in training, data quality issues and the opportunity cost of not having systems that actually talk to each other.
The firms that get ahead of this ask, “How does this tool fit into our overall ecosystem, and does it move us toward or away from where we want to be?” They don’t just look for a new tool to solve the problem.
Here are a few questions to ask in your next technology conversation:
- Are we making this decision in the context of our full tech ecosystem?
- Does this tool integrate with what we already have, or does it create another data silo?
- Are we solving a symptom, or are we addressing the underlying architectural gap?
- Who owns this decision? Do the right leaders have a seat at the table?
Where to start
If you’re reading this and recognizing your firm, the good news is this is a solvable problem. It’s not always fast, and it’s rarely painless, but firms do this work every day and come out better positioned to serve clients and attract talent.
The starting point is awareness. Before you change anything, get honest about what you have. Map your current systems and ensure you understand where data enters your ecosystem, where it needs to go and where it gets stuck or duplicated. Which integrations work well, which are held together with manual processes and which don’t exist at all?
From there, you can start to make decisions that are strategic rather than reactive.
It’s helpful to connect with peers who are working through the same challenges. Technology decisions are complex enough without having to figure it all out from scratch. That’s a core reason the Boomer Technology Circles exist. They give firm leaders a structured, trusted community where they can share what’s working and learn from firms that are ahead of them on this journey.
The leadership takeaway
Your firm’s competitive advantage is how you deploy and integrate technology in service of a clear strategy, with the right people and through well-designed workflows.
Your tech stack might be just fine. But if your architecture is fragmented, disconnected or the product of years of short-term fixes, no individual tool can solve that. It takes intentional leadership, a systems mindset and the willingness to step back before stepping forward.
That thinking starts with you.
===
Marc Staut is a shareholder and Chief Innovation & Technology Officer at Boomer Consulting, Inc.
Sign in to get access to this free resource, and all of our whitepapers and reports.
Download this content today!
Register Now Already registered? Click here to Log In
![Marc_Staut_(grey_BG)[1]](https://www.cpapracticeadvisor.com/wp-content/uploads/2022/04/Marc_Staut__grey_BG__1_.5edff0550f4dd.png)