Private equity and portfolios
Value creation levers for AEC private equity platforms
By SourceX Editorial · Updated
Short answer
Value creation in AEC private equity platforms usually comes from pricing, utilization, cross-sell, systems and talent, plus a sixth lever that is easy to overlook: data. The data lever starts with a portfolio-level assessment of each firm's internal project records, such as RFI logs, review comments and staffing plans, kept separate from client-owned deliverables.
Key takeaways
- Pricing and utilization move margin fastest, but both depend on consistent time and project codes across acquired firms.
- Cross-sell works when acquired firms share client and capability records, not only a common brand.
- Systems consolidation is the moment acquired firms' archives are either preserved or lost.
- The data lever covers internal workflow records; client deliverables such as drawings and models are usually carved out.
- Assess records firm by firm, then decide at platform level which firms to pursue first.
Which levers drive value creation in an AEC platform?#
AEC platforms typically build value with six levers: pricing, utilization, cross-sell, systems, talent and data. The first five are familiar from most professional services roll-ups. Data is the least familiar, and it depends on decisions made in the systems lever.
The table shows each lever with a typical move, the records that show progress and the pitfall that most often stalls it in an engineering or architecture platform.
| Lever | Typical move | Records that show progress | Common pitfall |
|---|---|---|---|
| Pricing | Revisit fee structures and multipliers; capture additional services | Project reports in Deltek Vantagepoint or BQE Core, change order and additional services logs | Raising rates without fixing scope creep on fixed-fee work |
| Utilization | Balance staff across offices; reduce non-billable drift | Timesheets, resource plans, phase codes | Comparing firms whose time codes mean different things |
| Cross-sell | Offer one firm's services to another firm's clients | CRM records, proposal library, win and loss notes | Acquired brands quietly competing for the same client |
| Systems | Move to one ERP, one document control and shared BIM standards | System inventory, migration plan, archive map | Migrating active projects only and retiring old servers |
| Talent | Retain licensed principals and build the PM bench | HR records, licensure and registration records | Losing stamp authority when an owner leaves after an earnout |
| Data | Assess and license internal workflow records to AI developers | RFI logs, submittal registers, QA/QC comments, plus a rights record | Confusing client deliverables with company records |
Pricing and utilization: the margin levers#
Pricing and utilization are the margin levers, and both rely on project data being comparable across acquired firms. A multiplier review means little if one firm books coordination time to a project phase and another books it to overhead.
Standardize phase codes, labor categories and project types early, ideally before a firm moves onto the platform ERP. That one decision makes write-off analysis, fee benchmarking and utilization reports trustworthy. It also produces cleaner project histories, which matters later for the data lever.
Cross-sell and systems: the integration levers#
Cross-sell and systems are the integration levers, and they succeed or fail on shared records. Cross-sell needs a single view of clients, past proposals and capabilities across firms, so a civil firm's PMs can see that a sister MEP firm already works for the same hospital system or school district.
Systems consolidation is where AEC platforms tend to lose history. Moving to one ERP, one document control system in Procore or a shared Bluebeam setup is sensible, but migrations usually carry active projects only. Closed projects left on old servers or in cancelled subscriptions become hard to find when a claim arrives or a client asks for prior work. Build an archive map into every systems plan.
Talent: the lever that protects the others#
Talent is the lever that protects the others, because an engineering or architecture firm's capacity, licensure and client relationships sit with a small group of people. Losing a licensed principal can remove stamp authority in a state or discipline, and losing senior project managers can remove the relationships cross-sell depends on.
Retention terms, succession for responsible charge and a visible path for project managers belong in the plan from the first add-on. Talent also connects to data: the reasoning in RFI responses and review comments stays in the firm's records after the people who wrote it move on, which is one more reason to preserve those archives.
How does the data lever work in an AEC platform?#
The data lever in an AEC platform means licensing internal project-workflow records to AI developers building tools for design review, RFI response, scheduling and proposal writing, while each firm keeps ownership. The records with the most potential show professional reasoning: why an RFI was answered a certain way, what a QA/QC reviewer flagged, how a submittal was resolved.
Client deliverables are a different matter. Drawings, models and specifications are often governed by contract terms on ownership and confidentiality, so they are usually carved out or reviewed contract by contract with counsel. Carry the lever in the plan as upside until a buyer has reviewed a defined package. The table shows how record families typically sort.
| Record family | Typical status | Why |
|---|---|---|
| RFI logs and responses | Candidate after rights review | Internal reasoning; project and client identifiers removed in preparation |
| Submittal reviews | Candidate after rights review | Shows review decisions and resolution history |
| QA/QC comments and markups | Candidate after rights review | Captures expert review on real work |
| Proposals and fee build-ups | Company-owned, sensitive | Pricing details may be excluded by choice |
| Staffing plans and schedules | Company-owned | Internal planning records |
| Drawings, models and specifications | Usually carved out | Ownership and confidentiality often set by client contracts |
| Client correspondence | Depends on terms | Confidentiality clauses differ by client |
Running a portfolio-level record assessment#
A portfolio-level record assessment compares acquired firms on the same questions, using metadata only. It can run alongside systems planning because it asks many of the same questions about where history lives.
- List each firm's systems for time and billing, document control, markups, BIM and email, with years of history each still holds.
- Note past migrations, retired servers and any archives on personal or external drives.
- Tag record families as internal workflow records or client deliverables.
- Collect the contract forms each firm uses by client type, including public-sector terms.
- Rate each firm on history, linkage between records, rights clarity and export effort.
- Choose one or two firms with strong scores and simple approvals to pilot.
Illustrative: a four-firm AEC platform assesses its records#
Illustrative: a fictional AEC platform owns a civil engineering firm on Deltek Vantagepoint, an MEP engineering firm on BQE Core with Bluebeam Studio for reviews, an architecture studio on Ajera with Revit models on file servers, and a land surveying firm. The platform is planning to consolidate onto one ERP.
The MEP firm ranks first: its QA/QC markups in Bluebeam link to RFIs and responses across several years of projects. The civil firm does a large share of public-sector work whose contracts carry records and confidentiality clauses, so it goes to rights review. The architecture studio lost older project history in a past server migration, which the team learns only because the assessment asked. The surveying firm's records are mostly client deliverables, so it is not pursued.
The platform pilots the MEP firm and adds a full archive export to the ERP consolidation plan for all four firms, so no further history is lost.
How SourceX approaches AEC platforms#
SourceX treats each acquired firm, not the platform, as the supplier, because each firm's own contracts and client terms govern its records. The SourceX five-step transaction runs firm by firm: Supply, Rights, Preparation, Approval and Delivery. At the Rights step, drawings, models and other client deliverables are usually set aside, and the firm's principal or authorized signer approves the remaining scope.
Because the fit check uses only descriptions of systems and archives, it can run while ERP consolidation is still being planned. The SourceX Enterprise Data Value Framework compares firms on record depth and linkage, and each package that proceeds carries a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization.
Frequently asked questions
Does licensing income count toward a seller's earnout?
It depends on how the purchase agreement defines the earnout metric, such as the acquired firm's revenue or EBITDA. Licensing income from that firm's records could move the metric, and sellers still on an earnout may have views on the effort and timing. Read the earnout definitions with counsel before scoping a package, and agree in writing how any licensing income and preparation costs are treated.
Does licensing project records conflict with client confidentiality?
It can if done carelessly, which is why rights review comes before preparation. Client-controlled material is carved out, client and project identifiers are removed, and each firm's contracts are read for confidentiality and data-use terms. Counsel reviews which laws and terms apply to each deal.
Who at the platform should own the data lever?
The operating partner usually sponsors it, with the platform COO or CIO running it alongside systems consolidation. Each firm's principal answers metadata questions and approves scope, and general counsel or outside counsel leads the rights review.
Do firms need to be on one ERP before an assessment?
No. The assessment works from metadata and is most useful before consolidation, because it shows which archives to export in full before old systems are retired. Running it afterward often means discovering that an acquired firm's history was left on servers or subscriptions that no longer exist.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.