top of page
Won by being first to build legal case management natively on Salesforce, letting it out-invest at product while rivals split resources between infrastructure and legal features.
1
MODEL
BUSINESS MODEL
Vertical Integration, API Platform
model bm
HOW THEY BUILT IT
- Founded 2016 in Brooklyn; raised $2.5M (2017), $5M (2018) and a $50M Series A (2019) led by Tiger Global, later changing ownership through a Bessemer-affiliated acquisition.
- Built entirely on the Salesforce Lightning platform rather than its own infrastructure, inheriting enterprise-grade security, reliability and integrations for free.
- Acquired LegalStratus in 2021 to add e-billing and financial-analytics capability rather than building it organically.
- Counts Salesforce's own 70,000-person internal legal support function as a flagship customer, using Agentforce AI on top of Litify's data foundation.
HOW TO ARCHITECT IT
1. Choose an underlying platform (Salesforce) with enterprise infrastructure already built, because reinventing security and scalability wastes capital better spent on vertical features.
2. Target an industry (legal) the platform owner hasn't natively served, because "legal on Salesforce" was unclaimed territory in 2016.
3. Sell to both law firms and corporate legal departments as a dual ICP, because legal-ops spend exists on both sides of any client relationship.
4. Acquire adjacent point solutions (billing via LegalStratus) instead of building them slowly, because legal-ops buyers want one vendor relationship, not five.
5. Use the platform owner's own internal team as a flagship reference customer wherever possible, since "the platform owner uses the vertical app" is an unusually strong trust signal for enterprise buyers.
DISTRIBUTION MODEL
Channel Sales, Direct Sales
dm
HOW THEY OPERATIONALIZED
- Listed on the Salesforce AppExchange, which drives discovery and lends third-party credibility to enterprise buyers already trusting Salesforce.
- Direct enterprise sales team for large plaintiff firms, insurance-defense practices and corporate legal departments.
- A network of certified Litify implementation consultants (specialized Salesforce + legal expertise) supports rollout, effectively a channel-partner layer for delivery.
HOW TO REPLICATE WHAT WORKED
What worked: listing on an established platform marketplace (Salesforce AppExchange) to borrow the platform's trust and procurement approval with enterprise buyers, then building a certified-partner delivery layer so implementation complexity doesn't bottleneck a small direct sales team.
The trap: don't assume marketplace listing alone drives volume - Litify still needed a dedicated enterprise sales team for large accounts, since AppExchange discovery converts curiosity into pipeline, not closed deals, on its own.
| PATTERNS OF THIS MODEL
PATTERNS IN VERTICAL APPLICATIONS BUILT ON AN ENTERPRISE PLATFORM:
1. BUILD ON AN EXISTING ENTERPRISE PLATFORM TO INHERIT SECURITY, RELIABILITY AND INTEGRATIONS, spending your capital on vertical depth instead of infrastructure.
2. TARGET AN INDUSTRY THE PLATFORM HAS NOT NATIVELY SERVED. Unclaimed vertical territory on a major platform is a genuine market position.
3. SERVE BOTH SIDES OF A PROFESSIONAL RELATIONSHIP where budget exists on each — firms and their corporate clients.
4. PLATFORM DEPENDENCE MEANS INHERITING ITS PRICING AND ROADMAP. Your gross margin is partly set by a vendor you do not control, which must be modelled from the start.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — INHERIT ENTERPRISE INFRASTRUCTURE INSTEAD OF BUILDING IT.
Standard: building on Salesforce Lightning delivered security, reliability and integrations free, letting capital go into vertical legal features rather than reinventing a platform.
GOLDMINE 2 — TAKE THE VERTICAL THE PLATFORM HASN'T CLAIMED.
Standard: legal on Salesforce was unoccupied in 2016. Platform ecosystems have identifiable empty verticals, and the first credible entrant gets the ecosystem's promotion.
GOLDMINE 3 — SERVE BOTH SIDES OF THE LEGAL RELATIONSHIP.
Standard: law firms and corporate legal departments both hold legal-ops budget, and Salesforce's own 70,000-person legal support function as a flagship customer is a trust signal nothing else provides.
THE PIT — PLATFORM DEPENDENCE MEANS SALESFORCE'S PRICING AND ROADMAP ARE YOUR COST BASE.
Customers pay Salesforce licences plus Litify, making you structurally more expensive than Clio or Filevine — and Salesforce can enter legal directly at any time.
THE SECOND PIT — A $50M TIGER GLOBAL SERIES A IN 2019 PRECEDED AN OWNERSHIP CHANGE VIA A BESSEMER-AFFILIATED ACQUISITION.
MOVE WITH CAUTION — ACQUIRING E-BILLING (LEGALSTRATUS, 2021) PUT LITIFY AGAINST BRIGHTFLAG AND TYMETRIX SIMULTANEOUSLY.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
MARKET TYPE
Fragmented Market
WHY THEY WON
The US has more than 40,000 law firms with no dominant legal-tech incumbent serving the scale gap between small-firm tools (Clio, PracticePanther) and enterprise legal departments. Litify won by targeting exactly that scale gap - large plaintiff firms and corporate GCs needing enterprise configurability - riding on Salesforce's existing enterprise trust rather than building that trust from zero itself.
ENTRY STRATEGY
Greenfield Entry
EXECUTION
Litify entered the market by building on top of Salesforce's Lightning platform rather than owning its own infrastructure - effectively a licensing-style entry mechanism where it pays for and depends on Salesforce's cloud, in exchange for inheriting its security, scale and integration ecosystem instantly.
FOOTHOLD STRATEGY
fs
Lighthouse Customer Strategy
Litify's foothold came from large-scale plaintiff/personal-injury firms as early flagship customers, and later Salesforce's own internal legal department as the ultimate lighthouse account - a reference so credible ("even Salesforce uses Litify") that it de-risks the purchase decision for every subsequent enterprise prospect evaluating Litify against competitors.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
AppExchange visibility and reviews used as a discovery/trust channel; detailed case studies (e.g., Salesforce's own legal team reporting being "twice as efficient"); the LegalStratus acquisition used as a feature-expansion announcement to re-engage the market.
KEY LEARNING
If you're building vertical software on someone else's platform, use "the platform owner is also our customer" as your single strongest case study whenever it's true. If your vertical's buyers are naturally risk-averse about new vendors (as legal always is), acquiring an adjacent, already-trusted point solution (billing) is often faster than building trust in a new category organically.
gc
Market Context
| MARKET INTELLIGENCE
THE STANDARD: Targeting the scale gap between small-firm tools and enterprise legal departments, on top of an existing enterprise platform, borrows trust you would otherwise have to build.
RULE 1 — BUILDING ON AN ESTABLISHED PLATFORM IMPORTS CREDIBILITY AND SECURITY POSTURE. Enterprise buyers accept the underlying platform before evaluating you.
RULE 2 — THE SCALE GAP IS REAL AND STRUCTURALLY UNSERVED. Large plaintiff firms have enterprise complexity and no enterprise legal-tech option built for them.
RULE 3 — PLATFORM DEPENDENCY MEANS INHERITED PRICING AND ROADMAP RISK. The underlying licence cost is part of your customer's total spend and outside your control.
RULE 4 — CONFIGURABILITY ATTRACTS THE LARGE FIRM AND CREATES IMPLEMENTATION DRAG. Services revenue rises with deal size and depresses the multiple.
MARKET TYPE: Fragmented Market (legal practice management), platform-native.
| MARKET ENTRY PLAYBOOK
THE STANDARD: BUILDING ON A MAJOR PLATFORM TRADES PERPETUAL COST AND DEPENDENCY FOR INSTANT ENTERPRISE-GRADE INFRASTRUCTURE.
RULE 1 — INHERIT SECURITY, SCALE AND ECOSYSTEM RATHER THAN BUILDING THEM.
For a vertical application, the platform supplies years of infrastructure work and an existing integration marketplace.
RULE 2 — THE PLATFORM'S LICENCE COST SITS INSIDE YOUR PRICE FOREVER.
You can never undercut a natively built competitor; position on capability, not price.
RULE 3 — PLATFORM ROADMAP AND PRICING CHANGES ARE YOUR BUSINESS RISK.
Write down the downside scenario before committing the architecture.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: The most powerful reference is your own platform partner using the product internally.
RULE 1 — WIN THE LARGE FIRMS WHOSE SCALE MAKES PROCESS ESSENTIAL. High-volume plaintiff practices manage thousands of matters and need systematised intake and case management.
RULE 2 — A PLATFORM PARTNER'S INTERNAL ADOPTION IS AN UNMATCHABLE CREDENTIAL. When the company whose infrastructure you build on uses you themselves, the risk question is answered.
RULE 3 — BUILDING ON AN ESTABLISHED ENTERPRISE PLATFORM BORROWS ITS SECURITY AND COMPLIANCE POSTURE. That shortcut is why the architecture choice is commercial, not technical.
RULE 4 — PLATFORM DEPENDENCE MEANS INHERITING ITS PRICING AND ROADMAP. Your cost base and capability ceiling are set by someone else.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
REVENUE MODEL
Subscription
PRICING MODEL
Value-Based Pricing
WHY THEY WON
Custom-quoted, per-user subscription priced around firm size, structure and selected modules (document management, eBilling, timekeeping, analytics), configured by the Litify team to match each firm's or legal department's specific workflows rather than sold off a fixed price list.
Pricing is quote-based and tied to the configuration a firm needs (core matter management vs. full billing/analytics/AI stack), reflecting the actual efficiency value delivered (e.g., handling 2x the matter volume with the same staff) rather than a simple per-seat list price.
TARGET AUDIENCE
CUSTOMER BUYING BEHAVIOUR
tg cb
Mid-to-large law firms (plaintiff, insurance defense, immigration, family law), corporate in-house legal departments, and government legal agencies.
Committee- and procurement-driven, often RFP-based for large firms and corporate legal departments; purchase decisions are justified through efficiency metrics like legal-budget-to-revenue ratio and matters handled per staff member.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Building on a platform means inheriting its buyer and its price floor, and legal case management on Salesforce is priced accordingly.
RULE 1 — NATIVE-ON-PLATFORM POSITIONING PRE-QUALIFIES YOUR MARKET TO FIRMS ALREADY SPENDING.
You reach only buyers committed to substantial platform costs, which raises your floor and shrinks your market.
RULE 2 — THE PLATFORM LICENCE SITS BENEATH YOUR PRICE AND BUYERS ADD THEM TOGETHER.
Your effective cost includes their underlying seats.
RULE 3 — PLAINTIFF FIRMS PAY FROM CONTINGENCY REVENUE, WHICH IS LUMPY AND LARGE.
Case outcome value, not hourly billing, sets willingness to pay in this segment.
RULE 4 — MATTER DATA AND WORKFLOW CONFIGURATION ARE THE SWITCHING COST.
Once cases are in the system, migration is unthinkable mid-matter.
A firm is buying case throughput without adding paralegals. Where revenue depends on case volume, software prices against capacity — the same logic as every professional services vertical.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
Custom-quoted per-user pricing configured per firm means every deal is bespoke, which caps sales velocity and raises cost of sale.
Building on a major CRM platform accelerates development and makes that platform's pricing and roadmap your constraint.
Legal software revenue tracks firm headcount and case volume, both cyclical.
Configuration-heavy implementations are services revenue that dilutes margin and slows time-to-value.
Enterprise legal departments and large firms are few, so each loss is material. No revenue published.
Where the model can break
4
MOTION
LinkedIn: https://www.linkedin.com/company/litify | listed on Salesforce AppExchange: https://appexchange.salesforce.com/
GROWTH EXPANSION MODEL
COMPETITIVE STRATEGY
motion ge cs
Vertical Integration, Platform Expansion
HOW THEY EXPAND
Litify expanded across 15+ specific legal practice areas (personal injury, immigration, insurance defense, family law, corporate/litigation) rather than staying generic, and rides Salesforce's own platform expansion (e.g., Agentforce AI) to add new capability to its legal-specific data foundation without having to build the underlying AI infrastructure itself.
Differentiation
HOW THEY COMPETE
Litify differentiates on its Salesforce-native architecture - an enterprise-grade, continuously-updated infrastructure layer that standalone legal software vendors would need years and significant capital to replicate on their own, making it a durable technical edge rather than a marketing claim.
GROWTH ENGINE
GTM
ge n gtm
Partnership Growth, Platform Integrations
Litify's growth loop runs through its relationship with the Salesforce ecosystem: every Salesforce customer already trusts the underlying platform, so Litify's AppExchange presence and platform integrations (DocuSign, Outlook, Workday, SAP, QuickBooks) convert existing Salesforce trust into faster legal-vertical sales cycles than a standalone vendor could achieve.
AppExchange-led discovery for inbound credibility, paired with direct enterprise sales built around vertical case studies (especially Salesforce's own legal department) and RFP responses tailored to specific practice-area workflows.
SUSTAINING MOATS
Switching Costs, High Customer Lock-In, Brand Power, Technology Advantage (complex enterprise scenarios)
moat
Litify's core moat is inheriting Salesforce's platform ecosystem - infrastructure, security certifications, and a constantly-improving AI layer (Agentforce) that Litify didn't have to build itself and that a standalone legal-software competitor can't match without years of investment. On top of that sits genuine switching costs: once a firm's matters, billing rules and reporting dashboards are deeply configured inside Litify, ripping it out means rebuilding years of firm-specific workflow logic from scratch.
| MOAT INTELLIGENCE
THE STANDARD: Building a vertical application on a major platform trades independence for enterprise credibility and inherits the platform's economics.
RULE 1 — THE PLATFORM SUPPLIES SECURITY, INTEGRATION AND TRUST YOU WOULD OTHERWISE BUILD, which shortens enterprise sales cycles substantially — and it means your customer pays two licences.
RULE 2 — LEGAL MATTER AND CASE DATA CARRIES PRIVILEGE AND RETENTION OBLIGATIONS, making migration a governance exercise rather than a data project.
RULE 3 — PLAINTIFF FIRMS OPERATE ON CONTINGENCY, so software that improves case selection and settlement outcomes is measured against recovered fees rather than against cost.
THE SIGNAL: platform-native vertical applications are defensible while the platform stays committed to the vertical. The strategic risk is not competition — it is the platform deciding to serve the industry directly.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — BUILD LEGAL SOFTWARE ON A PLATFORM YOU DO NOT MAINTAIN
Building on Salesforce gives enterprise security, identity and integration on day one, and permanently ties your pricing and roadmap to theirs.
Target plaintiff and personal injury firms, where case volume and settlement economics justify real software spend.
$1–5M ARR — PRACTICE-AREA DEPTH BEATS GENERAL CASE MANAGEMENT
Intake, medical records, liens and settlement workflows specific to one practice area are what firms actually buy.
WATCH: matters managed per firm.
$5–10M ARR — INTAKE IS WHERE THE MONEY IS
For contingency-fee firms, converting more leads into signed cases is directly revenue. Sell that, not document management.
$10–50M ARR — PLATFORM DEPENDENCY IS THE STRUCTURAL RISK
Your cost base includes another vendor's licence, which caps your margin and your pricing freedom.
NOTE: no ARR disclosed; reported funding varies by source.
$50–100M ARR — LEGAL TECHNOLOGY CONSOLIDATES AROUND PAYMENTS AND PLATFORMS
Larger legal platforms acquire practice-area specialists. Clean data and portable integrations determine your price.
$100M+ ARR — NOT IN EVIDENCE
Rule: building on an enterprise platform buys credibility and sells your margin. It is the right trade when the buyer's security requirements would otherwise take you years.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: Listing on an established platform marketplace borrows the platform's trust and procurement approval — but discovery is not pipeline.
SEQUENCE:
1. Build on the platform enterprise IT already trusts and approves.
2. List in the marketplace for discovery and credibility.
3. Build a certified-partner delivery layer so implementation doesn't bottleneck a small sales team.
WORKED: Platform-marketplace listing borrowing enterprise procurement approval, plus a certified partner layer handling implementation complexity.
CAUTION:
1. MARKETPLACE LISTING CONVERTS CURIOSITY INTO PIPELINE, NOT INTO CLOSED DEALS. A dedicated enterprise sales team was still required for large accounts — do not plan headcount on the assumption the marketplace sells for you.
2. PLATFORM-NATIVE ARCHITECTURE CAPS YOUR TAM to that platform's installed base.
bottom of page