After the Deal: Vendor Due Diligence for Law Firms
Opus 2's Bundledocs acquisition prompts a practical law-firm review of vendor continuity, data portability, support, integrations, and roadmap claims.
Quick answer
When a legal technology provider is acquired, a law firm should verify what changes for its own service, contract, data, support, and integrations before making a decision. The October 1, 2026 announcement that Opus 2 acquired Bundledocs does not itself establish a migration, price change, or product disruption. It does give firms using document bundling and dispute workflows a concrete reason to confirm continuity and understand what the combined company plans to deliver.
Start with the agreement and the firm's actual workflows. Ask the provider for written answers about account ownership, renewal terms, support contacts, data export, integration dependencies, and any announced roadmap changes. Record the answer and a tested exit path in the matter-technology file. This is operational guidance, not legal advice.
This article is informational and not legal advice. Contract, confidentiality, records-retention, privacy, and professional-responsibility requirements vary by jurisdiction, client, and matter. Review the applicable agreement and consult qualified counsel before changing a firm's practices.
What the October 1 announcement says
Opus 2 announced that it had acquired Bundledocs, a provider of cloud-based document bundling and collaboration software. The announcement describes Bundledocs as supporting document preparation, integrated review, real-time collaboration, and flexible outputs. Opus 2 said the acquisition would expand its commercial-disputes offering and support its roadmap, particularly for enterprise firms working across multiple jurisdictions. Those are the companies' stated aims, not a promise that a particular feature or integration will arrive on a particular date.
The announcements describe the strategic rationale, but they do not answer every customer-specific question about contracts, service levels, data handling, pricing, or future product packaging. A firm should seek those answers from its account contact rather than infer them from the acquisition headline.
The useful distinction is between a transaction and a customer impact. A change of ownership can create an opportunity to improve a product, combine capabilities, or invest in support. It can also prompt questions about product boundaries, account teams, or integration priorities. None of those outcomes should be treated as certain until the provider confirms them.
Map the workflow before evaluating the vendor news
List the tasks the product supports today. In a disputes practice, a document-bundling workflow may touch evidence collection, document preparation, review, collaboration, exhibit updates, and final delivery. Identify which team owns each step and which other systems provide the source files, matter details, annotations, or approvals.
This map keeps the discussion grounded. A product may be important to a single specialist group, or it may sit across many matters and offices. The response should match the dependency. For a limited use, a written support confirmation may be enough. For a firmwide workflow, the firm may need a tested export, a named transition owner, and an alternative process before a renewal or major change.
Four customer checks to make in writing
1. Service and contract continuity
Ask whether the legal entity providing the service, the current agreement, renewal date, service levels, and support route are changing. Request notice of any proposed changes to fees, packaging, service availability, or product terms. Compare the response with the signed agreement and note any notice periods or customer options that may apply.
Do not assume the acquisition changes a contract, and do not assume it leaves every contractual detail untouched. The agreement and the provider's written notice control the customer-specific answer.
2. Data access and a usable exit
Confirm what the firm can export and in what format. The test should cover source files, bundle structure, page references, annotations, version history, metadata, and audit records that the firm needs to continue its work. Confirm who can request the export, how long it takes, whether fees apply, and how the provider handles data after termination under the applicable agreement.
Where the workflow is important, request a representative export and open it in a separate environment. A clause that permits data export is less useful if the output cannot preserve the structure the team relies on. Keep a dated sample and record what was missing or needed manual repair.
3. Support ownership and escalation
Get the current support route and escalation contact in one place. Ask whether the team handling the firm's account or technical issues is changing, what support hours apply, and how urgent matter deadlines are escalated. A broader company may create more support capacity, but the firm's plan should be based on the actual service commitment, not a general statement about growth.
4. Integration and roadmap evidence
List the integrations and custom steps the firm depends on. Ask which are supported today, which are being maintained, and whether any deprecation or migration notice exists. Separate a confirmed release from a roadmap discussion. For any proposed combined workflow, request a demonstration with the firm's own process requirements and identify how permissions, audit records, and human review will work across the full flow.
Do not buy on the assumption that two companies' products will become one seamless platform. Treat future integration as a hypothesis until the provider supplies scope, timing, availability, and the applicable service terms.
A short review plan for the next renewal cycle
Assign one operational owner to collect the agreement, renewal date, system map, and provider notices. Ask the vendor the four questions above and store its written responses with the firm's technology records. Have the practice team identify an active matter that can be used for a safe export test without exposing unnecessary client data.
Then decide whether the firm needs no change, a documented contingency, or a broader vendor review. A contingency might be as small as confirming another team member can retrieve an export and reconstruct an index. For a critical workflow, it may include a controlled fallback process, a recovery time target, and a scheduled test. The point is proportionality: the more matters and deadlines depend on the system, the more evidence the firm should keep.
The same process is useful for any provider change, whether the product is document bundling, practice management, research, billing, or AI-assisted work. The announcement can start the review, but the firm's own dependency map and written contract answer what action is needed.
Frequently asked questions
Does an acquisition mean a law firm should immediately switch vendors?
No. The acquisition announcement alone does not establish that the service, contract, or product is changing. First confirm the provider's customer-specific plans, then compare the operational risk and available alternatives.
What should a firm ask about its data?
Ask what information can be exported, the available formats, the time and cost, who may request it, and what happens after termination. Test a representative export when the workflow is important enough to justify it.
Should a firm rely on a vendor roadmap after a deal?
Treat roadmap discussions as plans rather than delivered capabilities. Ask for scope, timing, dependencies, availability, and written notice of any change to the current service. Do not base a critical workflow on an uncommitted feature.
Who should own an acquisition review inside a law firm?
Name an operational owner and involve the practice team that uses the product, the person responsible for technology or security, and counsel or procurement where contract terms require review. Keep one record of decisions, open questions, and the next review date.
Sources and scope
This article uses the Opus 2 acquisition announcement and Bundledocs' announcement. Statements about the transaction and product descriptions are attributed to those company announcements. The due-diligence steps are general operational recommendations and do not predict how the acquisition will affect any customer's service or contract.
Sources
Make every matter easier to manage
See how Hammer Lex connects matters, documents, time, billing, and client communication in one operational view.
Book a demo