The Library Is the First System to Break
When two or three AEC firms merge, the proposal library breaks first. Each legacy firm brings its own staff resumes, project sheets, past-performance matrices, qualification narratives, certifications, and naming conventions. On day one, the combined firm has multiple versions of everything — and an upcoming SOQ deadline that doesn't care which legacy template wins.
This piece is for the BD director, proposal manager, or principal at a firm that just merged, just announced an acquisition, or is signing an LOI. The purpose is practical: what to triage, what to defer, and how to land a clean qualification library inside the first 90 days without missing a pursuit.
Mergers Are No Longer Edge Cases for AEC Firms
On April 7, 2026, three Salt Lake City–based engineering firms — Spectrum Engineers, Colvin Engineering Associates, and Envision Engineering — combined to form Lynk Engineers. Three firms with three resume templates, three project-sheet formats, three past-performance taxonomies, and three SAM.gov registrations became one firm overnight.
This is not unusual. PSMJ tracks 450+ AEC M&A transactions per year. Capstone Partners' AEC services sector update reports private-equity-backed deals are up 181.6% since 2018 and now represent 38.3% of all AEC M&A activity. In the first quarter of 2026 alone, multiple mid-market firms announced acquisitions — water resources, MEP/healthcare, structural, and land development specialties all changed hands.
For mid-market firms, the question is no longer "if our firm gets involved in M&A" — it's "when, and what shape will we be in when it happens." The proposal library is the system most likely to be in the wrong shape.
What's Actually Inside Three Proposal Libraries on Day 30
In the first 30 days post-close, the combined proposal library is the union of three separate systems that don't agree on anything. The visible inventory looks like this:
| Content type | What three firms bring | Integration problem |
|---|---|---|
| Staff resumes | Three formats; possibly hundreds of staff; overlapping people from prior acquisitions | No agreement on which template is canonical; duplicate entries for overlap staff |
| Project experience sheets | Three layouts; three "highlight" conventions; three sets of project tags | Same project may exist three times with different framing across firms |
| Past-performance matrices | Three different ways of categorizing project type, client type, and project size | Section F of the next SF330 needs one matrix, not three |
| Qualification narratives (Section H, executive summaries) | Three voices; three positioning angles; three sets of capability claims | Boilerplate sounds like three firms wrote it because three firms did |
| Certifications (DBE, MBE, SBE) | Tied to legacy entities; SAM.gov registrations belong to dissolved firms | Reps and certs need to flow to the new entity name |
| Subconsultant agreements (SCAs) | Three sets of teaming relationships, each with their own templates and signed agreements | Active subconsultants may have agreements with two of the three legacy firms |
| Naming conventions | "Smith_resume_Final_v3.docx" multiplied by three | Trying to find one resume requires guessing which firm's folder it lives in |
| CRM and pursuit history | Three systems with three definitions of "active pursuit," "win," and "loss" | Forecasting and capacity planning require unified data |
The visible inventory is not the hardest problem. The hidden problem is: nobody on the new combined team knows what the other two firms had, where it lived, or what version was current.
The 90-Day Triage Playbook
Trying to fix everything at once produces nothing. The right approach is sequential — high-touch, high-pain items first; lower-friction items run in parallel with active pursuits.
| Window | Priority | Why first |
|---|---|---|
| Week 1–2 | Inventory all proposal-relevant content. Count it. Don't merge yet. | You can't sequence a fix you haven't measured. |
| Week 3–4 | Standardize the staff master list — one row per person, one resume of record per person. | Resumes are the highest-touch, highest-frequency asset in any pursuit. |
| Week 5–6 | Merge project experience into one taxonomy. | Project sheets carry past performance — must unify before next major pursuit. |
| Week 7–8 | Past-performance matrix consolidation. | Section F of every SF330 needs this; agencies will not wait for tri-merger logistics. |
| Week 9–10 | Qualification narrative and Section H boilerplate harmonization. | Sounds like polish. It's actually what evaluators read first when they open Section H. |
| Week 11–12 | Certifications, SAM.gov reps, SCAs, branding alignment. | Lower-friction but legally required. Run in parallel with active pursuits. |
The order is not arbitrary. Staff resumes get touched on every pursuit; project sheets nearly every pursuit; past-performance matrices on every federal SF330. Boilerplate gets touched less frequently and tolerates inconsistency longer. Branding alignment can wait — clients evaluating qualifications care more about the content than the logo color.
The Single-Source-of-Truth Test
The fastest way to surface the integration problem is to imagine the next concrete pursuit. Suppose a state DOT SOQ is due three weeks after close. The proposal manager needs Section E (Resumes) for six key personnel. Whose resume template wins?
Three legacy firms had three formats. The new firm needs one. There are three ways to choose:
- Pick the dominant firm's template. Fast, but signals which legacy firm is the dominant party in the merger. Politically loaded — and often inaccurate, since the merger may be a merger of equals.
- Pick the "best-looking" template. Subjective. Creates friction with the legacy teams whose templates didn't win.
- Pick the format that best meets the next pursuit's evaluation criteria. The pursuit dictates the format, not legacy preference.
Option three is the right answer. If the next pursuit is a federal SF330, standardize on an SF330-compliant Section E layout — it's the format that has to exist anyway. If it's a state DOT, use that state's preferred resume layout. The firm template emerges from the pursuit calendar, not from internal politics.
The same test applies to project sheets. If the next pursuit needs project experience formatted to a specific client's RFP, that format becomes the new firm template. The next pursuit drives the template; the template drives the library.
The People Problem Behind the Library Problem
Resumes are not just files. They belong to people who:
- May or may not be staying after the merger
- Have project history that may overlap (worked at firm A, then firm B's prior acquisition)
- Have certifications — PE licenses, LEED, ENV SP, security clearances — tied to specific employer registrations
- Have SAM.gov reps and DBE/MBE/SBE qualifications tied to legacy firm names that need re-verification under the new entity
The library audit is also a people audit. Inventorying resumes means reconciling:
- Who's still working there at day 30, day 60, day 90 — voluntary attrition runs higher in the year following an AEC merger than in steady-state operations
- What projects each person actually worked on, especially when the same engineer may have project credit on two legacy firms' past-performance matrices
- How current each person's certifications are, and whose name the certificate is in
- Which people are qualified to be "key personnel" for the new entity's federal pursuits
The number that matters is not the headcount — it's the staff who are still on payroll, still licensed, and still willing to be named in proposals 90 days after close. That subset is the only basis for an honest qualification library.
Why Firms That Merge Well Already Had Structured Content
The firms that come out of a merger with a working proposal library inside 90 days share one thing in common: their legacy firms already had structured proposal content before the merger. Specifically:
- Staff data lived in a database, not a folder of Word documents on a shared drive
- Project history was tagged by sector, scope, and client type — not described in free-text paragraphs
- Resumes were generated on demand from structured profiles, not stored as static files
- Certifications had expiration dates tracked, not buried inside individual PDFs
For firms going into a merger with a scattered Word-doc state, the merger forces the structure migration. The painful way to do it is during a 90-day post-close sprint with active SOQ pursuits in flight. The less painful way is to do it before the LOI is signed.
The structural insight: M&A integration cost on the BD side is largely a function of how structured each legacy firm's content was on day zero. Firms that had built their qualification library as data — not documents — pay the integration cost in days. Firms that had built it as files pay it in weeks of manual reformatting and judgment calls under pursuit deadlines.
What to Tell Your Principal
For BD directors and proposal managers in the middle of an active or anticipated merger, the case to leadership is straightforward:
- "We need 90 days of focused library work before our pursuit calendar normalizes. Without it, every pursuit takes 2–3× longer because we are reformatting from three sources every time."
- "Show the math: 3 staff lists × 3 templates × N pursuits per quarter = 9N reformatting cycles in the first quarter. Cutting that to N is the highest-return post-close investment on the BD side."
- "Frame it as M&A integration cost, not proposal team overhead. The integration cost shows up somewhere — either in upfront library work or in slipped pursuits and missed shortlists six months later."
A single source of truth for staff and project content is the BD-side change that pays back fastest after a merger. It is also the most measurable: time to assemble a Section E, time to assemble a Section F, percentage of pursuits where the proposal team flagged "we couldn't find the right project sheet."
Frequently Asked Questions
We just signed an LOI. When should we start library integration?
Before close. The LOI period — typically 60–120 days for an AEC transaction — is the right window to inventory both firms' proposal libraries, agree on a target structure, and identify the high-friction items (overlapping staff, conflicting project tags, certifications tied to legacy entities). Library work after close competes with active pursuits; library work before close has cleaner timeboxes and lower urgency.
Should we keep the legacy firm names on certifications and past performance?
Past performance from a legacy firm carries forward to the new entity in most contexts — the project happened, the firm did the work, the experience counts. Certifications are different: DBE/MBE/SBE classifications are tied to the legal entity that earned them, and post-merger re-certification is often required. SAM.gov registration also flows to the new entity name. The standard practice on past performance: cite the project under the new firm name with a short footnote indicating the work was performed under the predecessor firm.
What about CRM history — proposals submitted, win/loss data, pursuit pipeline?
Win/loss data is the highest-value record from each legacy CRM and the hardest to merge cleanly. Pursuits in flight at close need to migrate together with their context (key correspondence, evaluator feedback, pricing). Historical win-rate data is useful as benchmark but should be tagged by legacy firm so post-merger trend analysis stays honest. Most firms run two CRMs in parallel for the first 30–60 days and migrate active pursuits first, archived data second.
Whose project experience "counts" for federal past performance?
The combined firm inherits the past performance of all legacy firms for federal pursuits, with the standard caveat that the work must have been performed under contract by the predecessor entity. SF330 Section F project sheets should cite the prime firm under which the work was performed — even if that prime firm has since merged into the new entity. Federal evaluators are familiar with M&A; what they will not accept is past performance claims that obscure who actually performed the work.
How do we handle staff who came from a firm that was previously acquired by one of the merging entities?
This is one of the most common library-integration tangles. Engineers and architects in the AEC market often have multi-firm résumés that may include prior acquisition events on both sides of the current merger. The clean rule: list project experience under the firm name in effect at the time of the project, not the current parent entity. Resumes should reflect actual project history, not retroactive corporate branding. This is also the standard federal SF330 expectation.
The merger announcement is the easy part. The proposal library work is where the integration ROI actually shows up — in the time-to-Section-E on the next SF330, in whether your firm makes the next state DOT shortlist, and in whether your principals stop hearing "we couldn't find the right project sheet" three months after close.