Skip to content

Case Studies

Saving a $350K ERP Contract Before Kickoff

How fast ownership of resourcing and communication kept a client from cancelling before work began.

Engagement
ERP implementation
Pricing
Hybrid
Stage
Before kickoff
Stakeholders
Executive team and C-suite

The situation

An enterprise client had signed a $350K ERP implementation, but before work even started, its executive team was preparing to cancel.

What was really going wrong

  • Kickoff had slipped because consultants weren't available right away.
  • The client's early escalations had gone largely unanswered.
  • As a result, the executives no longer believed the team could deliver on the agreed timeline.

How we fixed it

Step 1: Step in before the official start.

Rather than wait for the formal handover, we spoke with the client directly to rebuild trust and show clear ownership:

I will work with the team to ensure we are available and ready to engage fully and meet your timelines.

Step 2: Commit the capacity.

We committed to increasing the team's allocation so the original deadline could still be met, and tracked it in a resourcing and budget plan the client could see.

Step 3: Free up the team internally.

We met the internal delivery team and moved other projects around to create the time this client needed, then checked in with the client several times a week through kickoff.

What we refused to allow

The team dropping its committed allocation once the pressure eased. Internally, the message was simple: we're not dropping the ball, and we want this client as a reference.

Tools we used

Resource allocation and budget tracker.

The results

  • $350K

    contract kept instead of cancelled

  • Kickoff

    with the client's confidence restored

  • Escalations stopped

The lesson

Early loss of confidence can end a project before it starts. At that stage, fast ownership of resourcing and communication matters more than technical delivery.

Facing something similar?