Ask a room of partners who owns the firm’s CRM and you’ll usually get a pause, then three different answers. IT, because it’s a system. Marketing, because they send the campaigns. Business Development, because the pipeline lives there.
That pause is the problem.
Software rarely fails on its own
Most CRM programmes that disappoint don’t fail because of the software. They fail because nobody inside the firm owns them. The project team disbands after go-live, every department uses the system its own way, and there’s no one whose job it is to make it work for the business.
The symptoms are familiar:
- The same information is captured in several places by different teams.
- Spreadsheets and inboxes become competing systems.
- No proof. Without a baseline, nobody can show what the investment achieved.
Go-live is the start, not the finish
In larger firms, where CRM spans many offices, service lines and departments, these problems compound. Each team adds its own fields and habits, hand-offs break down, and partners drift back to their own lists.
Implementation is not the end of a CRM project. It is the beginning. What happens next depends on whether someone is accountable for the platform, its data and how it changes over time.
A quick test
Can you name the one person in your firm responsible for making CRM deliver for the business? Not the person who fixes it when it breaks, but the person who owns the outcome.
If you can’t, our whitepaper, CRM Manager: The Vital Role in Top Accounting Firms, explains why larger firms need a named CRM owner and what the role involves.
