The Integration Verisk Killed Is Why It Must Now Buy AccuLynx

Six days after announcing it would buy AccuLynx for $2.35 billion, Verisk emailed a roofing-software rival and called off the deeper Xactimate integration the two companies had spent months exploring.¹ On August 7, 2026, the Delaware Court of Chancery ruled that the email is the reason Verisk must now go through with the acquisition it had spent eight months trying to escape.¹

The post-trial opinion in Verisk Analytics, Inc. v. ExactLogix, Inc. runs 63 pages of merger-agreement construction, and most of the coverage has read it as a deal story.³ There is a second document inside it. For anyone who prices property losses for a living, the trial record is a sworn account of how Verisk decides who gets access to Xactimate pricing data — and what that decision cost when a regulator went looking for it.

What the court held

Verisk and AccuLynx signed on July 30, 2025.¹ The merger required clearance under the Hart-Scott-Rodino Act, and the agreement let either side walk away if closing had not happened by an outside termination date.¹ That exit came with a condition. A party could not terminate if its own material breach — or its "other willful conduct" — had been the "primary cause" of the failure to satisfy a closing condition.¹

Vice Chancellor Bonnie David found Verisk's conduct was that primary cause.¹ The purported termination was invalid, and AccuLynx won specific performance: Verisk must use commercially reasonable efforts to obtain HSR clearance and close the merger if the FTC approves it.¹ The court also awarded AccuLynx $3.85 million in direct costs plus prejudgment interest — an award Verisk forfeited any objection to by failing to answer it in the post-trial briefing.¹

The integration that was not

Verisk's Xactware suite includes Xactimate, the estimating platform adjusters and contractors use to price damage after fires and storms, and XactAnalysis, its claims-analytics and benchmarking counterpart.¹ Historically, Verisk offered outside software the same standard integration on the same terms.¹

In late 2024, ServiceTitan — an AccuLynx competitor in roofing business-management software — asked for more than that: "a deeper, more bespoke integration" that would give ServiceTitan contractors access to Verisk's real-time pricing data while they priced insurance estimates.¹ Verisk named it the Enhanced Integration and staffed it with its Vice President of Product for Property Estimating Solutions and that unit's Chief Product Officer.¹

Then came the testimony that explains the rest of the case.

From the trial record, Verisk's VP of Product for Property Estimating Solutions: "There was a lot of risk with this integration. We speculated that it could cannibalize our Xactimate license revenues. So we wanted to proceed cautiously with a proof of concept."¹

Six days after the AccuLynx deal was announced, Verisk told ServiceTitan the enhanced work was finished and offered the standard integration instead.¹ On September 25, 2025, the two companies announced that standard integration publicly: contractors could push ServiceTitan estimate data into Xactimate for review and validation, then pull the completed estimate back into ServiceTitan.² Access to real-time pricing data was not part of the announced scope.²

How a product decision became an antitrust theory

Soon after the FTC opened its preliminary investigation, ServiceTitan told the agency that Verisk had abandoned the Enhanced Integration.¹ The FTC built a novel "market reset" theory around that fact: after the merger, Verisk might develop a more sophisticated pricing integration for AccuLynx and decline to offer it to AccuLynx's competitors, foreclosing them from competing in roofer business-management software.¹

The agency then asked Verisk, repeatedly and in different forms, whether it had ever terminated integration discussions with an AccuLynx competitor or rejected a request for an enhanced integration.¹ Verisk did not realize the FTC was asking about ServiceTitan, and answered no each time — while the FTC already knew from ServiceTitan that the answer was yes.¹ Verisk's outside counsel eventually learned of the discussions and disclosed them.¹

The FTC then issued a second request focused on Verisk's integrations. Verisk ran an extensive document search under a quick-look agreement to try to head the request off, and the agency decided it would require full compliance anyway.¹ Days after that decision, Verisk purported to terminate on the extended termination date.¹ The HSR waiting period had not expired, and in late December 2025 the company announced it was walking.³

The court's finding was that the second request traced back to Verisk's own conduct, which is what closed the exit door behind it.¹ Having caused the delay, Verisk could not invoke the delay as grounds to leave.

Why the order is built to hold

Verisk's last line of defence was practical rather than textual: an order of specific performance would be "unworkable, given the complexity and difficulty of judicial oversight."¹ The court answered with its own back catalogue. Delaware has ordered specific performance of efforts clauses in Hexion, Channel Medsystems, Snow Phipps, and Desktop Metal, each time requiring a reluctant buyer to keep working toward a closing it no longer wanted.¹ Quoting Fortis Advisors v. Krafton, the opinion adds that where the parties contracted for specific performance, Delaware courts enforce that bargain unless the breaching party offers a persuasive and case-specific reason not to.¹ Verisk identified no such reason.¹

The opinion also records what Verisk did not do. It never moved for a status quo order, and it pointed to no evidence that AccuLynx had altered the status quo or breached an interim operating covenant, even though AccuLynx had been seeking specific performance since filing its counterclaims and pressing for expedition.¹

An efforts-clause order commands the attempt rather than the outcome, and the court has now said it is willing to supervise the attempt. For a claims-technology market that has spent a decade consolidating around a small number of pricing and workflow vendors, the practical signal is that a buyer's conduct during regulatory review is itself reviewable — by a court, on a trial record, with the buyer's internal product debates entered as exhibits.

What this means for the estimate on your desk

The ruling changes nothing about how Xactimate prices a square of architectural shingle tomorrow morning. What it changes is the evidentiary footing under an assumption adjusters have carried for years — that access to Verisk's pricing data is rationed, and that the rationing follows revenue rather than engineering. That assumption now has a sworn record behind it, given by the executive who ran the project.¹

Two things follow for a claim file.

First, when a contractor's estimate and a carrier's Xactimate output diverge, the difference is not always scope. The two sides may be pricing from different data, on different refresh cycles, through integrations negotiated on different terms. That belongs in the same category of check as the scope gaps that carrier Xactimate files routinely carry — a difference to document and price, rather than argue about in the abstract. When the dispute is genuinely about scope, Verisk's own published scope-writing guidance is still the most useful thing to hold a carrier estimate against.

Second, the integration layer is now a fair subject for a direct question. Contractors and adjusting firms running platforms that connect to Xactware can reasonably ask which integration tier they are on, whether pricing data flows in real time or on a lag, and whether that answer is contractual or discretionary. The trial record establishes that these tiers exist, that they differ materially, and that Verisk weighs license revenue when deciding who gets which one.¹ It does not establish that any particular firm has been disadvantaged — that remains a question to ask, not a conclusion to assert.

The FTC's theory is worth understanding on its own terms, because its logic is not specific to roofing software. The agency's concern was that a company controlling the pricing layer could decide which downstream tools get first-class access to it, and that the decision alone could determine who competes.¹ Public adjusters sit downstream of precisely that choice. An estimate arrives already shaped by which platform produced it, which pricing data that platform could reach, and how current the data was on the day the scope was written. None of that appears on the settlement statement, and none of it is visible from the line items alone.

For public adjusters specifically, the practical exposure sits where it always has: in whether the estimate you are handed reflects current pricing for your market. Overhead and profit disputes and pricing-database disputes look similar on a settlement statement and require different proof. The claimOS workflow for public adjusters treats them as separate line-item challenges for that reason.

What is still unsettled

The deal has not closed. The court ordered Verisk to seek clearance and to close if the FTC approves — an approval that had not arrived when the opinion issued, and the market-reset theory that prompted the second request is still live.¹ Verisk said it "strongly disagrees" with the decision and is evaluating its options, including a possible appeal.⁴ The parties were directed to submit a proposed form of final order.¹

Anyone reading a headline that says Verisk owns AccuLynx is reading ahead of the record. What Verisk owns right now is an obligation to try, a damages award against it, and a federal antitrust file that its own integration decisions helped write. For the next few months, the document worth watching is the FTC's, not the Chancery court's.