Why readiness comes before implementation
Most AEC firms enter Deltek conversations with budget estimates, vendor demos, and implementation timelines. Those inputs matter, but they do not answer the question that determines whether the project will succeed: Is the firm ready to implement?
ERP failure is rarely a surprise at go-live. It is usually the reveal of conditions that were already present: unclear ownership, undocumented process exceptions, unreliable project data, overloaded teams, weak internal champions, and leadership expectations that no implementation partner can realistically meet. Rollout is not the same as real change.
When implementation goes sideways, the cost shows up as delayed reporting, frustrated project managers, weak adoption, operational confusion, leadership friction, and lost confidence, not just in the system, but in the change itself.
This scorecard gives firm leaders a structured way to surface those conditions before implementation contracts are signed. It translates readiness into seven categories leadership can discuss together (operations, project management, proposals, marketing, finance, and principals included) and use to challenge optimism before spend becomes irreversible.
Alignarity built this scorecard from twenty years inside the AEC, Deltek, and ERP ecosystem, focused on what breaks in real firms when deployment is confused with adoption, not what looks fine in a steering committee deck.
Scoring method
How to use this scorecard
Use this scorecard in a leadership working session, ideally before vendor selection accelerates or implementation contracts are signed. The value comes from honest answers across operations, project management, proposals, finance, and leadership, not from any single function completing it alone.
Scoring notes
- Score what is true today, not what leadership hopes will be true after go-live.
- If principals, project managers, or operations leaders would answer differently than finance, score lower.
- If the answer is "we will figure that out during implementation," score 1 or 2.
- A single category scored mostly 1s and 2s is enough to warrant a readiness conversation before major spend.
Seven readiness categories
28 diagnostic questions for AEC CFOs.
Leadership Alignment
Implementation succeeds when leadership agrees on why the firm is changing systems, what the new platform will and will not fix, and who owns the outcome. In AEC firms, misalignment between principals, partners, project leadership, operations, and finance is one of the most expensive hidden risks, because major system change forces decisions leadership has deferred for years.
-
Strategic intent
Can leadership articulate a single, consistent reason for the ERP move, and what operational outcomes must improve within 12–24 months?
-
Scope realism
Is there shared agreement on what implementation will fix versus what requires governance, staffing, or process changes the system cannot deliver?
-
Executive sponsorship
Is there a named executive sponsor with authority to resolve cross-functional conflict when operations, project management, proposals, marketing, and finance disagree?
-
Principal/partner habits
Do principals and partners follow defined operational rules today, or do undocumented exceptions and partner-level overrides routinely undermine standard process?
What a low score means
Leadership is entering implementation with different expectations. The project will spend early months negotiating what the system is for, instead of configuring it. Political capital will burn before value appears.
What a high score means
Leadership has aligned on purpose, scope boundaries, and sponsorship. Implementation conversations can focus on design and execution, not re-litigating why the firm is changing.
Process Reality
Firms often know how work gets done, but rarely how it is documented. Implementation designs against process reality, not process mythology. Proposal-to-project transitions, billing workflows, job costing and utilization reporting, project planning and management, and project closeout routines in AEC firms vary by office, service line, and leadership style. Implementation will force those variations into the open.
-
Billing and revenue workflows
Are billing, WIP, and revenue recognition workflows documented end-to-end, including exceptions for fixed-fee, T&M, milestone, and multi-entity arrangements?
-
Project accounting handoffs
Are handoffs between project managers, project accountants, and operations defined, including who owns job cost adjustments, transfers, and write-offs?
-
Utilization and time
Is timesheet and utilization reporting trusted today, or routinely corrected, reconstructed, or overridden before leadership reviews it?
-
Undocumented exceptions
Are known process workarounds documented, or do teams rely on tribal knowledge that implementation partners will not discover until configuration begins?
What a low score means
The firm is not ready to design around how work actually runs. Implementation will become process archaeology: expensive, slow, and politically exposed.
What a high score means
Core workflows are understood, owned, and documentable. Design workshops can focus on improvement, not reconstructing how the firm operates from memory.
Data Discipline
ERP implementations amplify data quality; they do not create it. AEC firms carry complex project structures, job cost allocations, chart of accounts design, billing setups, and reporting hierarchies that must make sense before migration and configuration begin. When WIP, job cost, or project data is already disputed internally, implementation makes that dispute public under deadline pressure.
-
Project work breakdown structure
Is there a clear, agreed standard for project numbering, phases, cost codes, and work breakdown, or do offices and service lines run incompatible structures?
-
Chart of accounts and hierarchy
Is the organization structure designed to support the growth of the company along with both project and accounting needs, and do leaders trust the current reporting outputs used for decisions?
-
Data ownership
Is it clear who owns project data quality, master data updates, and correction authority (operations, project teams, finance, marketing, IT, or a shared model?
-
Known data problems
Are data issues including, but not limited to, WIP accuracy, duplicate records, allocation inconsistencies, and billing leakage discussed openly in leadership meetings, or discussed only informally?
What a low score means
The firm will migrate conflict, not clarity. Data remediation will consume budget and schedule, and teams will inherit reporting they cannot fully trust.
What a high score means
Data structures and ownership are understood. Known problems are visible and prioritized. Migration and design can proceed with realistic remediation scope.
Governance & Decision Rights
ERP projects stall when no one can decide, or when too many people can veto without owning the outcome. AEC firms need clear decision rights across system design, process changes, master data, billing rules, reporting definitions, and adoption enforcement. Without escalation paths, every disagreement becomes a meeting and every exception becomes permanent.
-
Decision ownership
Is there a decision framework for implementation: who decides design, who approves exceptions, and who resolves cross-functional deadlock?
-
Change control
Is there a defined process for approving process and system changes during implementation, including who can request, review, and finalize changes?
-
Executive escalation
Is there a clear escalation path when project managers, operations, proposals, and finance disagree on billing, job cost, or reporting design?
-
Policy enforcement
Can leadership enforce operating policy changes required by the new system, or do principals and partners routinely override standards without consequence?
What a low score means
Implementation will slow at every design decision. Exceptions will accumulate. The firm will configure around politics, not operating discipline.
What a high score means
Decision rights and escalation are understood. Implementation governance can operate without renegotiating authority at every milestone.
Internal Capacity & Adoption Ownership
Implementation demands sustained attention from operations, project leadership, proposals, marketing support teams, finance, and subject matter experts, while the firm still runs projects, closes books, bills clients, and supports leadership. AEC firms often run lean relative to operational complexity. If the people who must own adoption are already overloaded, implementation competes with the business, and the business usually wins.
-
Cross-functional bandwidth
Do the teams who must support implementation (finance, operations, project accounting, and project management) have capacity for workshops, testing, and design decisions without breaking current delivery cadence?
-
SME availability
Are billing, project accounting, proposals, and operations subject matter experts identified, and do their managers expect them to participate consistently through implementation?
-
Adoption ownership
Is someone explicitly accountable for adoption, training follow-through, and post-go-live reinforcement, not just go-live event planning?
-
Internal champion strength
Are there credible internal champions across operations, project management, and finance who will carry the change after consultants leave, not only vendor-led super users?
What a low score means
The firm intends to implement a major system using people who do not have time to implement it. Timeline optimism will collide with operational reality.
What a high score means
Capacity, champions, and adoption ownership are identified. Implementation resourcing is realistic, not borrowed from already strained teams.
Implementation Partner Fit
Partner selection is often treated like procurement. In practice, it is a high-stakes working relationship. Implementation partners bring methodology, tooling, and configuration expertise, but they cannot compensate for unclear readiness, undocumented process reality, or a firm that expects the partner to resolve internal alignment. Fit matters: firm complexity, office variation, service line mix, billing models, and leadership culture.
-
Complexity honesty
Has leadership assessed firm complexity honestly (multi-office variation, billing model diversity, acquisition integration, service line differences) before evaluating partner proposals?
-
Partner assumptions
Are partner proposals being evaluated against the firm's actual readiness gaps, or primarily on price, timeline, and demo quality?
-
Role clarity
Is it clear what the implementation partner will own versus what the firm must own (process decisions, data cleanup, adoption, policy enforcement, and executive alignment?
-
Reference relevance
Are reference checks focused on firms with similar AEC operating complexity, not just similar software modules?
What a low score means
The firm is at risk of selecting a partner for the wrong reasons, then discovering misalignment when readiness gaps surface mid-project.
What a high score means
Partner evaluation is grounded in firm complexity and readiness. Role boundaries between firm and partner are understood before contracts commit.
Implementation Risk Visibility
For CFOs and firm leaders, ERP is not an IT project. It is the system people will rely on for project visibility, billing integrity, forecast confidence, and board credibility. This category measures whether leadership has sufficient visibility into people, process, adoption, and political risk, and whether the firm treats ERP as business risk, not a technical sub-project buried in IT updates. Deployment is not the same as adoption.
-
Risk framing
Is ERP being managed as a business and adoption risk with executive visibility, or primarily as an IT initiative with periodic leadership updates?
-
Reporting trust
Does leadership trust current project and financial reporting enough to baseline success, or will teams be defending new system outputs from day one without a trusted starting point?
-
Cost exposure
Has leadership modeled cost risk beyond license and consulting fees, including internal time, remediation, timeline slip, operational disruption, and adoption failure?
-
Early warning conditions
Are there defined early warning signals (decision drag, adoption resistance, data disputes, scope churn) that trigger executive intervention before the project becomes politically untouchable?
What a low score means
Leadership is accountable for an outcome the organization has not framed as executive business risk, which means problems will surface late, expensively, and with limited room to correct course.
What a high score means
Leadership has visibility, baselines, and escalation conditions. ERP risk is being governed as a firm-wide priority, not a back-office technical upgrade.
Your results
Readiness score summary
Score interpretation
How to interpret your total score
Add the scores from all 28 questions. Use the bands below as a readiness signal, not a pass/fail grade.
28–55
High readiness risk
The firm is likely carrying significant organizational risk into ERP implementation. Gaps are not minor documentation issues; they reflect unclear leadership alignment, weak process discipline, data problems, governance ambiguity, capacity constraints, partner fit uncertainty, or limited visibility into adoption risk.
Likely risk profile
- Decision drag and exception accumulation during design
- Data remediation and process discovery consuming early consulting budget
- End-user non-adoption undermining billing, job cost, and project integrity
- Timeline optimism meeting operational overload
- Reporting credibility at risk before teams trust the new system
Recommended next step
Pause major implementation commitments. Conduct structured readiness work, internally or with independent advisory support, before contracts, partner selection, or large consulting spend lock the firm into a timeline. Use category-level low scores to prioritize leadership conversations across operations, project management, and finance.
56–83
Moderate readiness risk
The firm has meaningful readiness foundation in some areas, but uneven conditions across leadership, process, data, governance, capacity, or partner fit. This is the most common profile for AEC firms that look prepared on paper while carrying hidden friction.
Likely risk profile
- Implementation can proceed, but specific categories will become expensive if unaddressed
- Targeted remediation needed in 2–3 categories before configuration accelerates
- Risk of mid-project surprises where leadership believed readiness was stronger than it was
- Adoption may stall in offices or service lines where alignment was assumed but not verified
Recommended next step
Identify the lowest-scoring categories and assign executive owners to close gaps before or in parallel with early implementation phases. Consider an independent readiness review focused on the weakest categories, especially if partner selection or contract signature is imminent.
84–112
Stronger readiness foundation
The firm has a comparatively strong readiness foundation: leadership alignment, process clarity, data ownership, governance, capacity, partner fit, and adoption visibility are largely in place. This does not guarantee implementation success, but it improves the conditions under which real change can happen.
Likely risk profile
- Lower risk of early organizational stall, but adoption and office-level variation still require discipline
- Partner selection and design can proceed with clearer criteria
- Remaining gaps are more likely to be specific and addressable, not structural
- Leadership can focus on adoption reinforcement and value realization, not basic operating readiness
Recommended next step
Proceed with implementation planning, but maintain category-level honesty. Even strong firms often have one weak category (commonly process exceptions or principal compliance). Address that category explicitly in steering committee governance before go-live pressure makes compromise the default.
CFO conversation prompts
Eight questions for your next leadership meeting
Use these prompts before vendor selection accelerates or implementation contracts are signed. The goal is not to win an argument. It is to surface whether the firm is ready to commit.
- What problem are we solving, and what are we assuming ERP will fix that ERP cannot fix?
- Who owns this decision at each stage (selection, design, build, adoption, and post-go-live), and who resolves deadlock?
- Which workflows differ by office or service line, and who believes the current documentation is accurate?
- What data issues do we already know about, and who has been reluctant to say them in a leadership forum?
- Do the teams who must support this implementation have capacity without breaking current delivery, and who is protecting that capacity?
- Who will champion adoption inside the firm when the consultants leave, and do those champions have credibility with project and operations leadership?
- Are we selecting an implementation partner based on fit with our complexity, or primarily on proposal language and price?
- What early warning signals should trigger executive intervention, and who is accountable for acting on them?
Boundaries
What this scorecard is not
Clarity protects the firm. This scorecard is a readiness diagnostic, not a substitute for disciplined implementation work.
- Software selection: It does not evaluate Deltek modules, licenses, or vendor product roadmaps.
- Implementation methodology: It does not replace the implementation partner's project plan, technical design, or configuration approach.
- A guarantee of success: A strong score improves conditions; it does not eliminate complexity or ensure adoption.
- A substitute for operational discovery: It surfaces risk patterns; it does not replace interviews, workflow review, and data assessment.
- A generic ERP checklist: The categories and questions are oriented to AEC operating reality and Deltek implementation conditions, not platform-neutral transformation templates.
What it is: A diagnostic frame that helps AEC firm leaders see readiness and adoption risk clearly, before expensive implementation begins.