Procurement logic fails on implementation
Implementation partner selection is often run like a procurement exercise: RFP, demos, reference calls, score sheets, price comparison, award. That process works for commodities. ERP implementation in an AEC firm is not a commodity.
The firm is not buying a product off the shelf. It is entering a multi-year working relationship during which the partner will see the firm's operational mess, political dynamics, data problems, and leadership gaps, usually under deadline pressure.
The right question is not only "Who has the best proposal?" It is "Who can work with us honestly at our actual complexity?"
Why fit matters more than polish
A strong proposal can describe a clean path. A strong partnership survives the path when it gets dirty, when job cost design sparks principal conflict, when billing workflows expose office variation, when data remediation takes longer than the timeline assumed.
Partners differ in methodology, team structure, industry depth, and how they handle client-side dysfunction. Firms differ in governance maturity, finance capacity, office variation, and willingness to enforce operating discipline.
Mismatch is expensive on both sides. The firm blames the partner for "poor delivery." The partner blames the firm for "lack of engagement." Often, both are partially right, and readiness was never assessed honestly before the relationship began.
Common procurement traps in AEC ERP selection
CFOs and selection committees should watch for these patterns:
- Price as primary filter. Lowest cost proposals often assume a cleaner operational starting point than the firm actually has.
- Demo dazzle. Polished demos show what software can do, not whether the firm can adopt the process the demo assumes.
- Reference mismatch. References from simpler firms or different service-line mixes do not predict success in your operating complexity.
- Scope optimism. Proposals that treat data cleanup, change management, and principal alignment as "phase two" are pricing fantasy, not plan.
Good partner selection starts with honest self-assessment, not only vendor comparison.
Fit criteria worth weighing before award
Before selecting a Deltek or ERP implementation partner, leadership should evaluate:
- Does the partner's AEC experience match our service lines, billing models, and office variation?
- Does their methodology account for remediation and governance, or only configuration?
- Do we have internal capacity to meet them at the level their approach requires?
- Are they clear about what the firm must own versus what they will deliver?
- Did we assess our readiness honestly, or did we select based on who made us feel most confident?
Partner selection advisory is not about picking a winner from a score sheet. It is about matching firm readiness, complexity, and culture to a partner the organization can work with when the project gets hard.
Choose a partner you can work with, not just hire
Implementation partners are not interchangeable vendors. They become part of the firm's operating change story, for better or worse.
CFOs who treat partner selection as a high-stakes working relationship, not a procurement award, reduce the odds of expensive mismatch and protect the firm from entering implementation with the wrong collaboration model.
Next step
If this pattern sounds familiar, you do not need to wait for the first implementation warning sign.