What we do
Tools
Industries
Department
How we workLet's talk →
Home/Litify
Litify

Litify on Salesforce: What Running Your Firm Inside Salesforce Means

Litify isn't a separate system that syncs with Salesforce. It's a legal layer installed inside a Salesforce org, so your matters, intake and referrals are Salesforce records, and your attorneys sign in through Salesforce. That brings reporting, automation and a huge integration ecosystem. It also brings Salesforce's admin load. Here's what that trade looks like for a law firm.

Where Litify stops

It's built on Salesforce, so connecting it to everything outside is real integration work.

Stuck on Litify? Let's solve it →

What being on Salesforce gives a firm, and what it asks back

What you get

Salesforce's depth, applied to legal work

  • Matters, intake and referrals sit in the same database as everything else in the org, so a report can cross them.
  • Flow and Apex can automate almost any step, on Litify's records as on any others.
  • Anything that can talk to Salesforce can talk to Litify, through the same APIs.
What it asks

Someone who owns the org

  • A Salesforce admin, in-house or on retainer, for users, permissions, fields and reports.
  • Care with custom automation, because Litify ships package upgrades into your org.
  • Discipline about API use and integrations, since every connected tool draws on the same org.

Firms that get the most out of Litify treat it as a Salesforce org with legal software in it, and staff it that way. Firms expecting a closed system that runs itself tend to find the right column a surprise.

Settle these before the Litify contract, or the first week after

These are the Salesforce-side questions that decide how smooth the next three years are.

  • "Who is our Salesforce admin, and how many hours a week do they have?"

    Litify's implementation gets you live. Someone still has to add users, adjust page layouts and fix the report that broke when a field changed.

  • "Which of our tools are already on Litify's integration list?"

    Litify lists connectors for QuickBooks, Accounting Seed, DocuSign, NetDocuments, iManage, Case Status, CallRail and RingCentral, among others. Anything on that list should be switched on, not rebuilt.

  • "Do we get a sandbox, and where will custom work be tested?"

    Custom flows and code should be built and tested away from live matters, then deployed. Without a sandbox, changes get made straight in production.

  • "What happens to our custom automation when Litify upgrades?"

    Package upgrades can add or change fields and behavior. Automation that only reads and writes documented fields, and is tested after each upgrade, survives. Clever workarounds often don't.

  • "Which systems will call into the org, and how often?"

    Lead vendors, phone systems, document tools and reporting all draw on the org's API allowance. A few chatty integrations can crowd out the rest.

Where custom work fits around Litify

Billing, documents, e-signature and client status updates already have Litify modules or listed partners. The gaps are usually elsewhere.

01

Intake from sources with no connector

Lead vendors, web forms on your own site, chat tools and referral partners that aren't on Litify's list. n-frames posts each one into Litify intake with the source, the campaign and the answers the lead gave, so nobody retypes them and the source is reportable.

02

Reporting on data that lives outside the org

Litify can report on everything inside Salesforce. Ad spend, call tracking costs and vendor invoices often sit elsewhere. Bringing those in makes cost per signed case, by source and practice area, a standing report.

03

Automation on Litify's own records

Record-triggered Flows and Apex on matters and intakes, written against the package rather than around it, documented, and re-tested when Litify upgrades.

04

Firm systems nobody else connects

An in-house tool, a niche vendor portal or an old database the firm still relies on. If it has an API, the build uses the Salesforce API. If not, it's scheduled exports and imports, with checks on what didn't match.

Litify next to the other legal systems

Litify tends to make sense for firms running high intake volume or a large docket, where Salesforce's reporting pays for the admin effort. Smaller general practices usually get more from standalone systems; the trade-offs are laid out in legal case management software and, for injury practices, personal injury case management software.

If the question is the stretch before a matter exists, the first call to the signed engagement letter, start with law firm CRM. For Litify's integration surface in detail, see Litify API and integrations, and for case referrals between firms, Litify referral network automation.

Let's talk

Getting Litify to see the rest of the firm

n-frames builds the integrations and automation inside a Litify org: intake from the lead sources Litify doesn't connect, reporting that includes spend from outside Salesforce, and flows on matters that keep working through package upgrades. The work runs alongside your Litify implementation partner, not instead of it.

Route every lead source into Litify →

Questions people ask

Is Litify built on Salesforce?

Yes. Litify is installed as a package in a Salesforce org, and its sign-in runs through Salesforce. Underneath its legal screens, it uses Salesforce's data model, permissions, reporting and automation tools.

What does Litify cost?

Litify doesn't publish pricing. It quotes each firm on its size and the modules it wants, such as intake, matter management, documents, and time and billing, with implementation on top. Budget for Salesforce admin time as well, because that's a running cost, not a one-off.

Does n-frames implement or configure Litify?

n-frames builds what sits around Litify in the org: integrations with outside systems, flows and Apex on Litify's records, and reporting that pulls in outside data. Setting up Litify itself, its matter types, layouts and licences, is done by Litify or its implementation partner, and we work alongside them.

What is the Litify referral network?

Litify's tooling for firms that send and receive case referrals, common in personal injury, so a referral is tracked in the same place as the matter it becomes. What happens after a referral lands, routing, notices and fee tracking, is covered on the referral network page.

Does Litify have an API for integrations?

It uses Salesforce's. Because Litify's records live in your org, outside systems read and write them through the standard Salesforce REST, Bulk and event APIs, with the same authentication and the same daily allowance as any other Salesforce integration.

Do we need a Salesforce admin to run Litify?

In practice, yes, or a partner on retainer. Litify handles the legal layer, but users, permissions, reports and any custom automation are Salesforce administration, and someone has to own them.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.