Procore Paid $845 Million to See the Jobsite

Procore Technologies, Inc. filed a Form 8-K on September 9, 2026 stating that it consummated its merger with DroneDeploy, Inc. that day and acquired the company for a purchase price of approximately $845.0 million in cash, subject to certain adjustments for working capital, transaction expenses, cash and indebtedness. DroneDeploy survives as a wholly owned subsidiary of Procore. The deal had been signed on July 27, 2026, when Procore entered an Agreement and Plan of Merger with DF Merger Sub, Inc., DroneDeploy and Fortis Advisors LLC as stockholder representative, and the July 29 8-K that disclosed it set the conditions: adoption by DroneDeploy’s stockholders, the expiration or termination of the Hart-Scott-Rodino waiting period, and other customary terms, with completion anticipated by the end of 2026. It closed forty-four days after signing. That same filing describes DroneDeploy as a software company that provides cloud-control software for drones and other robots, including automated flight safety checks, workflows, and real-time mapping and data processing. Two terms sit outside the headline price. Procore agreed to create a retention pool of equity awards, or cash where equity cannot be granted, for certain DroneDeploy service providers, in addition to the purchase price and in an amount the filing does not state. And Procore obtained a representations and warranties insurance policy for the transaction.

The financing is spelled out more fully than the price. At signing, Goldman Sachs Bank USA committed up to $700.0 million under a 364-day senior secured bridge loan facility, and the 8-K states the merger was not conditioned on that or any other financing. Procore went to the convertible market instead. It announced a proposed $750.0 million private offering on August 3, priced an upsized $825.0 million the same day, and on August 6 completed an offering of $950 million aggregate principal amount of 0.00 percent Convertible Senior Notes due August 15, 2031, after the initial purchasers exercised their full option for an additional $125 million. The initial conversion price is approximately $82.89 per share, a 50 percent premium over the $55.26 closing price on August 3, and Procore bought capped calls with a cap price of $110.52 to limit dilution. Procore reports net proceeds of approximately $926.6 million, of which it used approximately $59.1 million for the capped calls and approximately $175 million to repurchase approximately 3.17 million shares, with the remainder going to a portion of the DroneDeploy cash consideration and general corporate purposes. That remainder computes to roughly $692.5 million, or about 82 percent of the headline price. The filings do not say how much of it was actually applied to the purchase or whether the bridge facility was ever drawn, so no one should state a debt-funded share of the deal from the record.

What Procore bought is the picture of the build. Its July 29 announcement, filed as Exhibit 99.1, says DroneDeploy is used on over 3 million jobsites across more than 180 countries and captures three-dimensional ground and aerial imagery through drones, ground-deployed robots, and mobile, fixed and wearable cameras, covering active construction sites and operational assets. The release sets the two datasets side by side: Procore’s record of construction decision-making, which it puts at nearly 400 million photos, over 126 million drawings and over 10 million RFIs, submittals and inspections in the last year alone, and DroneDeploy’s visual record, which it puts at approximately 20 trillion square feet of visual data, tens of millions of user-generated annotations and more than 100,000 labeled safety issues. Those figures are the companies’ own claims, not PSV findings. Chief Executive Officer Ajei Gopal said Procore plans to cross-sell DroneDeploy into its customer base immediately after closing and, longer term, to deliver what the company calls digital coworkers that track what is happening on a project, make sense of it, and act to change the outcome. In a post published on closing day, Gopal described the mechanism more concretely: cameras and robots continuously scanning a site, with digital coworkers comparing what they see against the project’s BIM model and schedule.

That comparison is the part a real estate operator should read twice, because it is the same comparison a construction lender pays for every month. A draw request asserts percent complete against a schedule of values, and someone, usually a lender’s construction consultant on a site walk, decides whether the claim is true. A single platform holding the schedule, the drawings, the inspections and dated imagery of the site puts the evidence for that decision in one place, and puts it with the software vendor rather than with the owner, the lender or the consultant. Scale explains why this matters beyond construction trade press. Procore reported second quarter 2026 revenue of $375 million, up 16 percent, a 95 percent gross revenue retention rate, and 2,871 organic customers contributing more than $100,000 of annual recurring revenue. Its full-year 2026 revenue outlook of $1,510 million to $1,514 million excludes any contribution from DroneDeploy, and the approximately $845 million price computes to roughly 56 percent of that range’s midpoint. Procore has not disclosed DroneDeploy’s revenue, so unlike Autodesk’s MaintainX purchase in August, no revenue multiple can be computed from the record. The pattern is the same, though: in one quarter, two major built-world software companies each paid cash for a layer of data about physical buildings that they did not previously own.

The workflow this deal points at is draw verification: reconciling what a pay application claims against what the site record shows, before money moves. The inputs are documents a development team already produces each month. The contractor’s application for payment with its continuation sheet, meaning the schedule of values with scheduled value, work completed to date and percent complete per line; the approved budget and every executed change order; the current construction schedule; the prior month’s construction consultant report; the stored materials invoices and delivery tickets; the conditional lien waivers; and the month’s site capture, whether that is a drone orthomosaic, a set of dated photos by location, or both. The output is one table with a row per schedule of values line: the claimed percent complete, the prior approved percent, the change this period, the specific image or document offered as evidence with its capture date and location, a plain statement of what that evidence shows, and a flag on every line where the claim has no dated evidence at all. That last flag is the deliverable. The value is not confirming the lines that reconcile, it is finding, say, the curtain wall line billed at 60 percent when the most recent capture of that elevation is five weeks old.

The reviewer is the owner’s project manager, working with the lender’s construction consultant, and the approval gate is that the table informs the draw but never funds it: a named inspector or consultant certifies percent complete, and the lender releases money on that certification, not on a reconciliation. Two things an assistant should not decide. It should not certify completion from imagery, because a photograph of installed ductwork does not show whether it passed inspection, and percent complete is an engineering judgment about cost to finish rather than a reading of a picture. And it should not rule on change order entitlement, which is a contract question. One structural step is worth taking whichever vendor you use: keep a copy of the site imagery you commissioned, with capture dates intact, in storage your company controls, because the reason to build this evidence is that it outlasts the software contract. PSV has not tested Procore or DroneDeploy, is describing a workflow it would run on documents a development team already holds, and is not claiming any time or cost result from it.