Every legal organization runs the same lifecycle. Almost none of them run it on one platform.

Three layers. The Salesforce platform provides the client and contact data model, security, automation, document storage, reporting and the API surface. A Salesforce-native legal application — Mitratech CaseCloud, Litify or nuLaw — adds the objects Salesforce does not ship, such as matters, conflicts, statute clocks, matter templates and legal billing. Configuration and custom development make both behave the way your organization actually works. Twopir Consulting delivers the second and third layers and the integrations around them.

It depends on how much matter-specific machinery you need. Salesforce alone, configured well, can carry client records, intake, request routing, tasks, documents, approvals and reporting — which is enough for some in-house teams and for firms whose matter process is simple. Once you need statute and court-date logic, matter templates, trust accounting or legal invoicing, building that from scratch usually costs more than licensing a legal application that already has it. We answer this question in discovery, against your matter types, and we will say so when a package is not warranted.

All three are legal platforms that run natively inside a Salesforce org rather than beside one, so the integration question is similar for each. They differ in the practice types their packaged workflows assume, how much of your process arrives pre-built versus needing configuration, and how licensing is structured. We evaluate them against your matter types, reporting requirements, integration surface and current Salesforce license position rather than defaulting to one — and the vendors' own current documentation stays the authority on feature detail.

The platform provides the mechanisms: role hierarchies, sharing rules, record-level and field-level permissions, restricted access to individual matters, and audit trails on record changes. Whether your obligations are met depends on how those mechanisms are configured against your specific confidentiality, ethical-wall and retention requirements — that configuration is part of what we design, and we document it so it can be reviewed. Your own compliance and risk function should sign off on the design; we build to it rather than deciding it for you.

Yes, and often more directly. In-house teams already sit inside a business that runs on Salesforce, so a legal request portal, a matter model and outside-counsel spend tracking can be built on the org the company already owns — with single sign-on, existing security controls and reporting the CFO already reads. The lifecycle is request → triage → matter → outside counsel or self-serve → spend → close, and the metrics are spend against budget, cycle time and how much work stays in-house.

Scope determines timeline. A focused first phase — core matter management, billing setup and baseline reporting — typically runs 6–10 weeks. Multi-practice rollouts, migrations from several legacy systems, external billing integrations and custom document automation take longer, and we phase them so something usable ships before the whole programme completes. Twopir scopes delivery against your actual requirements before any work begins rather than quoting a timeline from a template.

Vendors build and support their product. We design the operating model around it, decide what belongs in the package versus in configuration versus in custom development, migrate the data, integrate the systems the product does not own, and stay through adoption. We are independent of any one legal platform, so the recommendation can be that you need a different product — or none.