You already bought the platform. What you needed was an architect.

We scope and price against your requirements rather than publishing a rate card, because the same job varies by an order of magnitude depending on five things: how many practice areas and matter types need distinct logic, how many systems the data is migrating from, how many integrations are in scope, how much of the requirement needs custom development rather than configuration, and how many users need enabling. An advisory and architecture phase is fixed-scope and can be bought on its own; delivery is phased so you approve each phase against a written scope before it starts.

Often for a defined piece of work rather than permanently. A good admin runs and improves a system; architecture, data migration, integration design and custom development are different disciplines, and asking one person to cover all of them is how orgs accumulate technical debt. The common pattern is that we design and build the structural change, your admin runs it afterwards, and we stay available for the work that needs a developer or an architect. Where there is no admin at all, managed support covers that gap.

Yes, and it is a regular part of our legal practice. We start with an assessment of what exists — objects, automation, integrations, data quality and undocumented customization — and separate it into what is sound, what needs rework and what should be removed. You get that assessment before any remediation is scoped, so the decision to continue, rebuild or stop is yours and is based on evidence rather than on our preference.

We work with what you have wherever the foundations hold. A rebuild is genuinely warranted when the core data model cannot support how the firm now operates — for example when matters were modelled as opportunities, or when several practice areas were forced onto one record type that no longer fits. That is a specific, demonstrable condition, and we show the evidence rather than asserting it. Everything short of that is remediation, and remediation is cheaper, faster and less disruptive than starting again.

Twopir Consulting is headquartered in Pune, India with a US office in New Haven, Connecticut, and we serve clients across the US, Canada, the UK, the UAE, Australia and New Zealand. Engagements run remotely with a named delivery lead, an agreed overlap window with your working hours, a demo at the end of each delivery increment and a written scope for each phase. What we need from your side is a business owner who can make decisions and subject-matter time from the practice — that is the input that most reliably separates engagements that land from engagements that drift.

Yes. Every implementation includes hypercare through the first weeks after launch, plus documentation and admin handover so the knowledge stays with your firm. Beyond that, managed support is an ongoing arrangement with agreed response expectations, release testing in a sandbox before anything reaches production, and a rolling enhancement backlog you prioritize. It is optional by design — the handover is written so that a firm with its own admin can decline it.

That is what the advisory and architecture engagement is for, and it is the most common way firms start with us. We assess your matter types, process complexity, reporting requirements, integration surface and current license position, then recommend an architecture with the reasoning written down — including the option of configuring Salesforce alone where a legal application would not earn its licence. We implement Mitratech CaseCloud, Litify and nuLaw and resell none of them, so the recommendation follows the requirements.