Intake leaks qualified prospects
Enquiries arrive by form, phone, referral and email, then get triaged by hand. Good matters go cold before anyone owns them, and the firm never sees which ones it lost.
Most law firms do not have a demand problem — they have a systems problem. Enquiries sit too long, retainers stall, matters open slowly, billing runs behind and partners have no clean operating data. Twopir Consulting builds the Salesforce architecture that closes those gaps, from first enquiry through collection. Intake, matters, billing and trust on one architecture.
Trusted by 500+ organizations — including law firms and legal technology companies building their operations on Salesforce with Twopir Consulting.








Practice Types We Build For
Firms that scale cleanly control every handoff — enquiry to signed engagement, engagement to matter open, work completed to invoice paid. Every delay in that chain compounds, and every one of them is a systems choice.
Enquiries arrive by form, phone, referral and email, then get triaged by hand. Good matters go cold before anyone owns them, and the firm never sees which ones it lost.
When enquiries and referrer relationships sit in spreadsheets and inboxes, attribution is guesswork and pipeline visibility always lags the reality by a fortnight.
The client says yes, and staff re-key the same details across intake, matter management and billing. The one moment the firm has full attention is spent on data entry.
Invoices, retainer balances, trust ledgers and matter progress live in different systems, so collections slow down and every reconciliation is manual work someone does twice.
Re-entry, status chasing, duplicated work and missed reminders. None of it is anyone's fault, and almost all of it exists because the systems underneath do not talk to each other.
Managing partners need clean answers on intake, stalled matters, WIP and collections. Instead they get spreadsheets assembled after the fact — too late to change the outcome.
For a law firm, Salesforce is the operating platform underneath the business of running a practice: every enquiry and referrer relationship, the conflict screening and engagement that convert them, the matters that follow, the time and disbursements recorded against those matters, and the invoicing, trust handling and collections that close the loop — all on one data model, reportable in one place.
What the platform supplies: the client and contact model, security and sharing, automation and approvals, document storage, portals, reporting and an API surface. What a legal application supplies: the matter machinery Salesforce does not ship — Mitratech CaseCloud (formerly AdvoLogix), Litify or nuLaw install matters, deadline logic, matter templates and legal billing into the same org. Which route a firm should take is set out on Salesforce legal matter management.
What Twopir Consulting delivers is the architecture and the build: the data model, the intake and conflict flow, the matter lifecycle, the billing and trust integration, the reporting partners actually use, and the migration and adoption work that makes any of it real. We are Salesforce-first in execution and platform-agnostic in thinking, and we work with growing, mid-market, and enterprise organizations that need help with complex CRM implementations, integrations, and business system challenges.
Our standard is not a successful go-live. It is a system your attorneys and operations team still rely on eighteen months later — one that holds up under more matters, more offices and more practice areas than it launched with.
This is the lifecycle a firm actually runs — not lead, opportunity and closed won. Each row is a handoff, and every handoff is somewhere revenue or time escapes when the systems on either side of it do not share a record.
Scroll to compare →
| Stage | What breaks without a system | What we build | What leadership sees |
|---|---|---|---|
| Enquiry & referral | Enquiries land in a shared inbox and are triaged by whoever is free; referrer relationships live in someone's memory | Multi-channel capture straight into the record, routing by practice area and value, referral sources modelled as records | Enquiry volume and source, response time measured from actual arrival |
| Consultation & conflicts | Conflict checks run informally, and declined matters leave no trace to learn from | Conflict screening triggered on contact and party creation, approval steps, decline reasons captured | Conversion by practice area, and why matters are being turned away |
| Engagement & retainer | Engagement letters typed from scratch, chased by email, and funded before anyone confirms the terms are recorded | Documents generated from the record, e-signature routing, fee arrangement and retainer terms captured as data | Time from consultation to signed engagement, and what is unsigned right now |
| Matter open & work | The same details re-keyed into a second system; stage means something different to each attorney | Matter created from the accepted engagement with parties and terms attached, lifecycle and deadlines per matter type | Matter aging, stalled matters, capacity by team and office |
| Time & billing | Hours reconstructed at week's end and invoices assembled by hand, so billable work is quietly lost | Time capture at the point of work, rates by role and arrangement, invoices generated from tracked activity | WIP, unbilled time, realization against agreed rates |
| Trust & collections | Trust balances and receivables tracked outside the matter, so nobody sees an unfunded matter until it is a problem | Payment and retainer events posted back to the matter, trust and operating funds kept distinct, finance sync | Collections, aged receivables, and which matters are funded |
| Close, retain & refer | The matter closes and the relationship goes quiet; the referrer who sent it never hears anything again | Closure and retention states, client history that survives the matter, referrer follow-up built into the process | Repeat and referred work as a share of new matters |
The intake half of this lifecycle is delivered as a legal CRM implementation; the matter half is covered on Salesforce legal matter management.
Every engagement starts with how your firm wins clients, opens matters, coordinates work, gets paid and makes decisions. We design the architecture around that reality, never around a template.
Capture every enquiry, route it correctly, and build real accountability around follow-up — without manual triage or a shared inbox in the middle.
From signed retainer to matter-ready without duplicated effort, loose handoffs or attorneys chasing status across three systems.
Time, invoices, retainers, trust balances and matter status connected — so collections move and reconciliation stops being a monthly project.
Engagement letters and matter documents generated from data, signed electronically, and filed against the record without anyone moving a file.
The numbers a managing partner runs the firm on, available on a Monday morning rather than assembled for a quarterly meeting.
Connecting what the firm keeps, and building what no package covers — in the same org, on the same data model.
These are the systems a firm actually runs on, and what moves between each of them and Salesforce. Direction matters as much as connection — an integration that moves data the wrong way creates two versions of the truth instead of one.
Matter, document and billing objects inside the same org, so client and matter data are one record rather than two synced ones. We implement, configure and extend it — how we do it.
Client payments and retainer funding post back to the matter with trust and operating funds kept separate, so whoever is running the work can see whether the matter is funded without opening a payments portal.
Native Salesforce accounting: tracked time and matter costs become invoices and ledger entries without leaving the org, which removes the export-and-reconcile step between practice and finance entirely.
Bi-directional sync for trust accounting, settlement entries, vendor bills and expenses — finance keeps its ledger as the book of record while the firm keeps one operational view of every matter.
Retainers and legal documents generated from matter data go out for e-signature; executed copies and completion status land back on the matter automatically, so chasing a signature is a report, not a memory.
For firms keeping a dedicated document system, matter documents link across so attorneys work from one place without the firm losing the store of record, its retention rules or its existing governance.
Email and calendar log against the client and the matter, so correspondence history and hearing dates belong to the firm rather than to the individual mailbox they were sent from.
OCR-driven extraction pulls data from medical records and settlement documents straight into matter records — custom-built beyond any package, and worth building only where document volume justifies it.
A focused first phase — intake, the matter record and baseline reporting — typically runs 6–10 weeks; billing integration and multi-office rollout extend it. We phase delivery so the firm gets something usable before the programme ends.
We map how enquiries arrive, how matters open, where time goes and what partners cannot see — including the spreadsheets and inboxes nobody lists as systems. You get a written picture of the current state and the gaps worth closing first.
The client and matter data model, the security design, and the decision about what belongs in native configuration, in a legal application, or in custom development — with the licence implications and the reasoning written down before anything is bought.
Build in phases that each ship something the firm can use: intake and the matter record first, then billing, documents and the integrations to finance and e-signature. Migration runs with validation and a parallel period rather than a single cutover leap.
Role-based training for intake staff, attorneys and finance, hypercare through the first weeks, then the reporting layer partners run the firm on — and support as the firm adds practice areas, offices and people.
Two documented Twopir engagements with law firms. Each number is scoped to what it measured in that engagement, and is not presented as a benchmark for what another firm should expect.
Twopir provided Salesforce customisation and integration services to help us build a robust, compliant, and scalable legal operations platform — connecting case management, document processing, and financial systems into one unified workflow. The result was transformative for how we run case-to-cash operations.
Streamlining case-to-cash operations with Salesforce, AWS and QuickBooks.
Twopir's specialized Salesforce customization enabled efficient integration of third-party systems and streamlined administration and billing, leading to seamless financial operations and enhanced productivity. Automated mass billing and matter management minimized errors across our entire legal workflow.
A 50% efficiency gain from Accounting Seed and Salesforce integration.
More legal delivery detail: the AdvoLogix implementation case study, and our write-up on how AdvoLogix streamlines legal operations and case management.
Firms rarely struggle because they lack software. They struggle because the systems underneath intake, matters, billing and reporting were never designed to work together under real operational pressure.
Before we touch Salesforce we map how your firm wins clients, opens matters, tracks time and invoices. The system reflects your actual workflow rather than a default template someone else's firm was built on.
We do not hand over a configuration document. We design, build, integrate, migrate, test and launch — and we stay until the system performs the way the scope said it would.
Intake, matter operations, billing, trust, collections and reporting are not separate projects. Built separately, they produce the reporting layer nobody trusts. We design them as one connected system.
We have built Salesforce and CaseCloud infrastructure for personal injury, family law and corporate practices, connected to accounting, payment, document and AI systems. The workflows and the pitfalls are familiar ground.
More matters, more offices, more practice areas. The architecture you launch should be the foundation for the firm's next stage of growth rather than the thing that has to be replaced to reach it.
Only if it is solving something your current tool cannot. Practice-management software is usually strong at running matters and weak at everything before and around them: multi-channel intake, referral attribution, business development, cross-practice reporting and integration with the rest of the firm's systems. Firms move when growth exposes those gaps — several practice areas, several offices, a real referral network, or reporting that has to span enquiry through collection. If your matter process is straightforward and your enquiry volume is modest, staying where you are is usually the better use of the money, and we will say so.
Salesforce on its own is not a legal billing or trust accounting system, and no configuration turns it into one. What a firm runs is a combination: a legal application such as Mitratech CaseCloud supplies time, matter billing and retainer handling; payments come through a provider like LawPay that keeps trust and operating funds distinct; and accounting lives in Accounting Seed inside Salesforce or in an external ledger such as QuickBooks. We design and integrate that chain so matter, invoice and balance data stay consistent. Compliance with your jurisdiction's trust rules depends on how the whole arrangement is configured and operated, so we build to the requirements your firm and its accountants specify and expect them to sign off on the design.
It is one of the strongest reasons to be on this architecture. Practice areas get their own matter types, stage models, intake routing and document templates while sharing one client record and one reporting model, so a partner can compare offices without anyone exporting anything. Access is controlled per office, team or individual matter where confidentiality requires it. We roll out practice area by practice area rather than firm-wide on one date, which keeps the risk contained and lets each group's requirements be learned from before the next one starts.
Less than firms fear, but not nothing, and the parts that matter cannot be delegated to us. We need a business owner who can make decisions without convening the partnership, a few hours of subject-matter time from each practice area during design, and users who will test against real matters rather than nod at a demo. Most of the heavy work — configuration, migration, integration and documentation — is ours. The single most reliable predictor of an implementation landing is whether the practice was involved before go-live rather than informed at it.
Usually yes. QuickBooks, iManage, SharePoint, DocuSign, LawPay and most e-billing platforms integrate with Salesforce through supported connectors or APIs, and where a system is working and finance trusts it, replacing it is rarely the best first move. What we insist on is deciding which system owns each piece of data and which direction it flows, so the firm never ends up with two versions of a balance or a document. Where a system genuinely caps growth, we will say so and set out the cost of keeping it against the cost of replacing it.
By closing the gaps where billable work and cash quietly escape. Time captured at the point of work rather than reconstructed at week's end means fewer hours lost; invoices generated from tracked activity rather than assembled by hand go out sooner; retainer and trust status visible on the matter means unfunded work is caught before it accumulates; and WIP, unbilled time and aged-receivable dashboards mean partners see a problem while it is still fixable. The size of the improvement depends entirely on where your firm is leaking today, which is what the audit phase measures — we do not quote a percentage before we have looked.
Firm size matters less than complexity. A boutique with high enquiry volume, a real referral network and two practice areas often gets more from this architecture than a larger firm doing repetitive work in one practice area. The honest test is whether your growth is currently limited by process rather than by demand. We work with growing, mid-market, and enterprise organizations, and where a smaller firm's needs are genuinely served by simpler tooling, the discovery call is where we say that rather than after a proposal.
Talk to a Twopir legal systems architect. We will review how work moves from enquiry to collection in your firm, show you where it is stalling, and tell you what the right Salesforce architecture looks like — before any engagement begins.
Speak with a team that understands legal systems, architecture & firm scale