Why CFOs Should Ask “Are We Ready?” Before “What Will It Cost?”

Cost is the wrong first filter

CFOs are paid to control spend. So it is natural that ERP conversations begin with cost: license fees, implementation estimates, internal resource loading, and payback assumptions.

But cost is not a readiness indicator. A firm can approve a well-structured budget and still be organizationally unprepared for what implementation will demand: decision discipline, data remediation, adoption ownership, and sustained capacity from teams that are already stretched.

The better first question is not "What will it cost?" It is: "Are we actually ready to implement?"

Why cost-first decisions create false confidence

When leadership anchors on budget approval, the project gains political momentum. Momentum is useful, but it can also suppress the questions that would slow the initiative down for good reason.

Vendor proposals are designed to answer cost questions. They are not designed to expose unclear ownership, principal exceptions, unreliable project data, or finance teams that cannot absorb disruption. Once the budget is approved, those topics start to sound like obstacles instead of prerequisites.

For CFOs, the risk is signing financial accountability for an outcome the organization has not honestly assessed.

Readiness signals CFOs should see before approving spend

Before major ERP spend is approved, CFOs should be able to answer yes with evidence, not optimism, to questions like:

If the answers are vague, the firm is not ready to treat cost estimates as reliable.

• Who owns decisions at each phase (selection, design, build, adoption, and post-go-live?
• Does finance have capacity to support implementation without breaking close and reporting?
• Are known data problems named openly (WIP, job cost, billing, project structures?
• Will principals and partners operate the process the system requires, or will exceptions continue?
• Who will champion adoption when consultants leave?
• Is partner selection based on fit and complexity, or proposal language alone?

The hidden cost of skipping readiness

When readiness is deferred, the firm does not avoid cost. It buys additional cost, usually in consulting hours, timeline extension, rework, and leadership time spent on conflict instead of execution.

CFOs see it in variance explanations that blame "change management" without naming ownership gaps. In reporting cycles that lose credibility during transition. In steering committees that meet often but decide little.

Readiness work is not a delay tactic. It is how CFOs protect the integrity of the budget they are being asked to approve.

Ask readiness first. Then cost.

The sequence matters. Readiness first gives cost conversations context. It clarifies what remediation is required, who must be involved, and what implementation can realistically fix.

CFOs who ask "Are we ready?" before "What will it cost?" make better decisions, and enter Deltek or ERP implementation with a budget tied to operational reality, not presentation optimism.