Before you dive in, here are the core questions to ask:
• Buy vs. Build: Do you purchase an off-the-shelf solution or develop a custom tool in-house? Does your firm have experience building custom solutions? Buying is often faster, but customization can offer better long-term alignment.
• Data Flow: Are there existing APIs from your providers? Can you tap into native integrations, or will you need to build custom data feeds? Does your firm already have a platform to aggregate and manage API traffic?
• Team Resources: Do you have internal capacity for this project, or will you need a 3rd-party vendor or consultant? Even if you manage to build a solution, what kind of maintenance will be needed over time?
• Budget and Timeline: Be realistic – how much will this cost after any changes in scope or priorities? A light automation project may only take a few weeks. A full platform integration could take 6–12 months.
Watch out for common red flags:
• Vague project ownership or change management procedures;
• Lack of clarity on current process;
• Underestimating data quality issues;
• Insufficient dedicated time, budget, or technical expertise; and
• Being unwilling to address criticism or questions when you solicit and integrate attorney feedback throughout the process.
Firms that complete successful automation processes emphasize the importance of aligning expectations early. Great partners and tech, clarity on scope, flexibility for iteration, and strong internal sponsorship are essential. Another key lesson? Be ready to take an iterative approach – a minimum viable product (MVP) can go a long way in proving value and building internal momentum.
Final Thoughts: Map, Measure, and Make it Happen
We may live in Tracker World today, but we don’t have to stay there.
If you're in BD, KM, or IT at a law firm and tired of manually stitching together workflows with Excel and Outlook, it’s time to map your processes, define your goals, and start asking the right questions. Whether you’re replacing a single step or revamping an entire pipeline, the key is thoughtful planning and cross-functional collaboration.
And here’s the good news: these efforts build momentum. As your team learns what works—and what doesn’t—you build skills, strategy, and a foundation for future projects. You learn to see analogous processes and systems that you can lift and drop today’s solutions on tomorrow’s problems. Your tech stack gets smarter, your people get savvier, and what once felt like futuristic talk about automation becomes your new normal.
Say goodbye to Tracker World and hello to the 21st century.