Why We Finish SAP CX Projects When Others Don't

A surprising number of SAP CX projects never go live. Industry estimates suggest 20-30% of enterprise CRM implementations either get cancelled, “paused indefinitely,” or limp into production so late and so over-budget that nobody calls it a success.

We’ve delivered SAP Sales Cloud V2, Service Cloud V2, and Commerce Cloud projects for manufacturers, retailers, and distributors across Europe. Every single one went live. Not eventually. On the date we committed to.

That’s not a sales pitch. It’s a track record we protect fiercely — because the moment we fail to deliver, our reputation is gone. We’re not a 5,000-person firm that can absorb a failed project. We’re a focused team where every project matters.

Here’s what we do differently.

Senior Consultants From Day One

When a large consulting firm wins an SAP CX deal, the team that sold it is rarely the team that delivers it. The sales team had 20 years of experience. The delivery team has 20 months.

We don’t have a sales team and a delivery team. The people who scope your project are the people who build it. Every consultant on a Spadoom engagement has delivered multiple SAP V2 implementations. They know where the platform’s configuration ends and where custom development begins. They know which integrations are straightforward and which will eat three weeks of your timeline.

When we delivered SAP Sales Cloud V2 for Franke in 90 days, the same architect who ran the scoping workshop was configuring the system on day one. No handoff. No knowledge loss. No ramp-up period.

We Say No

This might be the most important thing we do. We say no to projects we can’t deliver.

If a prospect wants to implement SAP Sales Cloud V2, Service Cloud V2, Commerce Cloud, Emarsys, and CDP in a single 6-month project with a team of four, we tell them it’s not realistic. If a company wants to replicate their 15-year-old on-prem CRM feature-for-feature in a cloud system, we explain why that’s the wrong approach.

Some partners say yes to everything because the contract value is too attractive to pass up. Then reality hits at month 3.

We’d rather lose a deal than damage our go-live record. Every time we say no, we’re protecting the next 10 clients who need us to be available and focused.

Fixed Scope, Not Fixed Hopes

Every Spadoom project has a fixed scope document. Not a high-level overview — a detailed list of deliverables with acceptance criteria.

“Configure opportunity management with 4 custom stages, weighted pipeline, and automated notifications” is a deliverable. “Set up CRM” is not.

This protects both sides. The client knows exactly what they’re paying for. We know exactly what we need to deliver. When someone asks for something outside the scope, we don’t say no — we say “yes, here’s what it costs and how it affects the timeline.” Transparent change management instead of scope fog.

Nussbaum’s SAP Sales Cloud V2 implementation took 5 months. Not because we rushed — because the scope was clear from week one. No surprises. No last-minute discoveries. No “we assumed this was included.”

Iterative Delivery With SAP Activate

We follow SAP Activate methodology. Not because SAP says to, but because it works.

Here’s what that looks like in practice:

• Week 1-2: Discover phase — validate requirements, confirm integrations, set up the development environment.
• Week 3-4: First sprint — users see a working system with core functionality.
• Every 2 weeks after that: Demo session with key users. They test. They give feedback. We adjust.
• Final 2-3 weeks: Integration testing, data migration validation, user acceptance testing, go-live preparation.

The critical difference: problems surface in week 4, not month 6. A configuration that doesn’t match the business process gets fixed in the next sprint, not in a crisis meeting three days before go-live.

Direct Access to Decision-Makers

In many consulting firms, there’s an account manager between you and the people doing the work. Want to change a priority? Talk to the account manager. Have a technical question? The account manager will “find out and get back to you.” Need an architectural decision? Wait for the next steering committee.

At Spadoom, you talk directly to the architects and consultants building your system. Need to escalate something? Our CEO picks up the phone. There’s no bureaucratic layer between a question and an answer.

This speed matters. A decision that takes 2 days in a large firm takes 2 hours with us. Over a 5-month project, that difference compounds into weeks of saved time.

Honest Scoping

Before we write a proposal, we run a scoping workshop. Typically 2-3 days, depending on complexity. We map business processes, identify integration points, assess data quality, and evaluate organizational readiness.

Sometimes the result of this workshop is: “You’re not ready for this project yet.” Maybe the master data needs cleanup first. Maybe the business processes need to be agreed internally before anyone configures a system. Maybe a phased approach over 12 months makes more sense than trying to do everything at once.

Telling a prospect to wait costs us revenue in the short term. But it prevents a failed project — which would cost both of us far more.

What We Learned From Inherited Projects

Some of our best lessons came from projects we didn’t start. We’ve been called in to rescue SAP CX implementations that stalled with other partners. The patterns are consistent:

• Vague scope that grew by 50% during the project with no corresponding budget adjustment.
• Junior teams who built custom code where standard configuration would have worked, creating a maintenance burden.
• No integration testing until the final weeks, when critical data mapping issues surfaced.
• No user involvement until UAT, when the sales team rejected the system because nobody asked them what they needed.
• Big-bang go-live with no fallback plan, no phased rollout, no pilot group.

Every one of these is preventable. Not with better technology — with better project discipline.

The ANWR Approach

When we worked with ANWR Group, the requirement was to connect SAP Sales Cloud V2 with their existing SAP landscape. Complex integration, multiple data sources, specific industry requirements.

We started with a focused pilot: one business unit, one core process. Proved the architecture worked. Validated the integration patterns. Then expanded. The pilot approach reduced risk. ANWR saw value early. The broader rollout built on proven foundations instead of assumptions.

Our Track Record

100% go-live record. Every project. Every time.

That number only stays at 100% because we’re selective about what we take on, honest about what’s realistic, and disciplined about how we deliver.

We’re not the cheapest option. We’re not the biggest firm. But when your SAP CX project absolutely has to go live on time and on budget, track record matters more than slide decks.

Tell us about your project — we’ll be honest about whether we’re the right fit.