Private equity A/E firm acquisitions: firm methods vs client-owned design work

Which records an A/E platform can license

In private equity architecture and engineering firm acquisitions, the records a platform can most plausibly license are the ones that show how the firm works: CAD and BIM standards, QA/QC review checklists, design review comment logs, proposal and go/no-go histories, and project accounting. Drawings, models and specifications delivered to clients are a separate question, because the owner-architect or owner-engineer agreement on each project decides who controls them and what stays confidential.

A platform that has bought a dozen firms has inherited a dozen sets of contract habits: industry standard forms, clients' own paper and old agreements nobody has reread since closeout. Sorting records into firm-owned, client-controlled and shared piles before any inventory leaves the company keeps the introduction clean.

The demand side is specific. AI developers building agents for technical and professional work need records of how design decisions are made and checked: a reviewer's comment, the designer's response, the revision, and whether the same issue came back during construction. Mature design firms produce that trail on every project, so a firm's own process records can be worth more to a buyer than any single drawing set.

What records do architecture and engineering firms hold?

The firm-versus-client sort

Every record set goes into one of three piles before an inventory leaves the building.

1. Firm-owned. Material the firm's employees created for the firm's own operations: standards, templates, QA programs, proposals and accounting. The Copyright Office's circular on works made for hire explains that work an employee prepares within the scope of the job belongs to the employer, while work from an outside contractor may stay with the contractor unless rights are transferred in a signed writing. Lead with this pile.
2. Client-controlled. Deliverables and project information whose ownership, license or confidentiality the client agreement governs. The Copyright Act lets an owner transfer rights in whole or in part and hold exclusive rights separately, so one project's contract may leave copyright with the firm and give the client a license, while the next assigns everything to the client. Read the contract, not the firm's habit.
3. Shared or third-party. RFIs, submittals and coordination models that mix the firm's work with contractors', manufacturers' and subconsultants' material. Subconsultant deliverables can remain the subconsultant's property, so this pile stays out unless counsel clears specific sets.

This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

Which A/E companies fit the baseline

Apply the SourceX baseline to a design firm this way: a US company that has reached 50+ full-time employees at peak (contractors excluded), with several years of documented project history, the right to license the records in scope, and a sponsor with authority, whether the owner, CEO, CFO or an authorized representative, who would consider an exclusive AI-training license for an agreed term. Detail on each test sits on the who qualifies page.

Stronger candidates:

• Platforms that merged add-ons into one operating company and kept read-only archives of each firm's old systems.
• Multi-discipline engineering firms (civil, structural, MEP, environmental) with a written QA/QC program and review logs that go back years.
• Firms with a long run of project accounting in one ERP, or a preserved export of the previous one.

Weaker candidates:

• Small add-ons that still operate as separate legal entities and never met the size baseline on their own.
• Firms that wiped file servers after moving to a new document platform.

Whether pre-acquisition records moved with each deal is a separate question; the answer on licensing an acquired company's historical records walks through it.

Rights and confidentiality pitfalls specific to A/E

• Contract forms differ by add-on. Build a simple contract map: which standard forms each acquired firm used, which clients insisted on their own terms, and which confidentiality or ownership clauses survive project closeout.
• Security-sensitive projects. Drawings of utilities, transit, schools, data centers or government facilities can carry restrictions beyond ownership terms. Exclude them by default.
• Client details inside firm records. QA comment logs and lessons-learned registers name projects, sites and owners. The company agrees redaction rules with SourceX before any export begins.
• Disputes and claims. Project files tied to open claims, litigation holds or insurer involvement stay out until counsel clears them.
• Personal data. Professional license numbers, seals, continuing-education records and HR files belong on the exclusion list.
• Earlier arrangements. If any record set was already licensed for AI training, that is a red flag for a new exclusive license.

When to raise it during the hold

Who makes the introduction, and how it runs

Operating partners responsible for A/E platforms, platform CFOs, integration leads and the M&A advisers who sold firms into the platform all see the systems map early. The operating partner referral guide covers screening a whole portfolio.

1. Ask the platform CEO or CFO the three pile questions in general terms; no files change hands.
2. Run the company fit checker for a preliminary, non-binding read.
3. Create your partner account, then either send the CEO your referral link or file the company through the referral form.
4. SourceX's qualification call with the sponsor covers headcount, years of history, the spread of systems and rights.
5. The company builds a data inventory listing each system, its years of history and whether it exports, with the firm-versus-client sort written into the scope.
6. Price and terms are agreed, buyers review, the agreement is signed, data is delivered under the agreed redaction rules and the company is paid.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, and the reward becomes payable only after the buyer pays and SourceX receives its fee. It is funded from SourceX's fee, so the platform's proceeds are never reduced, and rewards are not guaranteed.

A conversation starter for the platform CEO

Next step

Sort one platform's records into the three piles with its CFO this month. If the firm-owned pile is deep, register as a partner and send the CEO your referral link to apply at sourcex.si/apply. For a sector with the same report-versus-process split, read the guide on testing, inspection and certification roll-ups.