The partner you choose to implement Litify or Salesforce has as much influence on your project’s success as the platform itself. The right partner understands your work, plans realistically, and stays with you after launch. The wrong one can leave you with a system your team works around instead of with.
In full transparency, BRIO is a Litify and Salesforce partner, so we’re not neutral. But these are the questions we’d ask if we were in your seat, and we think any good partner should welcome them.
Experience and expertise
1. Do you understand legal work, not just the software?
Configuring Litify well requires knowing how intake, case work, and billing actually happen in a firm. Ask who on the team has worked in or alongside legal practices.
2. What projects like ours have you delivered?
Ask for examples that match your practice areas, firm size, and source system. Case studies are useful; conversations with past clients are better.
3. Who will actually work on our project?
Ask to meet the people who’ll do the work, not just the people who sell it, and ask how they keep the same team from start to finish.
Process and planning
4. How do you run discovery?
A strong partner spends real time understanding your workflows before configuring anything, and documents what it learns in a design you approve.
5. How do you estimate, and what happens if the scope changes?
Look for a clear process: changes are described, estimated, and approved before work begins, rather than absorbed or surprised on an invoice.
6. How will you keep us informed?
Ask how often you’ll meet, what status reporting looks like, and who your day-to-day contact will be.
Data and technical depth
7. Who handles our data and document migration?
Migration is often the riskiest part of a project. Ask whether the partner does it in-house, how they validate results, and how many test loads they typically run.
8. How do you handle integrations?
Ask how the partner connects Litify or Salesforce to the other systems you rely on, and whether they can build custom integrations when standard connectors fall short.
9. How do you manage environments and releases?
Ask how they use sandboxes, how changes are tested, and how deployments to your live system are handled.
After go-live
10. What does support look like after launch?
The first weeks after go-live matter most. Ask what support is included, how issues are tracked, and how quickly they respond.
11. Can you support us long term?
Your needs will keep changing. Ask whether the partner offers ongoing support, admin services, or additional phases with a team that already knows your org.
12. How do you use AI, and how do you govern it?
AI is changing how implementations are delivered. Ask how the partner uses it, how they protect your data, and how they verify its output.
Red flags to watch for
- A fixed timeline promised before discovery.
- No clear answer about who will do the work.
- Data migration treated as an afterthought or handed to an unnamed third party.
- No plan for support after launch.
- Reluctance to share references.
Making the decision
Compare partners on how well they understand your firm, not just price. The lowest estimate can become the most expensive project if it leaves out discovery, migration, or support. The best partnerships often last well beyond the first project. Some of ours have lasted a decade and counting.
Want to see how we’d answer these questions? Read what to expect when you work with BRIO, learn about our Litify implementations, or start a conversation.
Frequently asked questions
What should I look for in a Litify implementation partner?
Look for legal industry experience, relevant past projects, a clear discovery and change process, in-house data migration expertise, and support after go-live.
Why does the implementation partner matter so much?
The partner shapes how the platform is configured, how your data is migrated, and how your team is supported. A poor fit can leave you with a system your team works around instead of with.
What are red flags when choosing an implementation partner?
Watch for fixed timelines promised before discovery, unclear staffing, migration treated as an afterthought, no post-launch support plan, and reluctance to share references.
