In a competitive SAP or ERP pursuit, scope gets written fast. The RFP is long, the deadline is short, and the team is rightly focused on the win themes, the solution and the number. The scope boundary (what is in, what is out, what we assumed and what the client must do) is often pulled together in the final week.
Then the bid team moves on. The delivery team inherits a fixed price, a go-live date and a set of words they did not write. If those words are vague, the first months of the programme are spent arguing about what was meant, and the last months paying for it.
That is why we treat the scope boundary not as a legal defence, but as the first design document of the delivery.
Two jobs, one document
A good scope boundary does two things at once.
It makes the price defensible. It turns an open-ended transformation into units you can estimate: data objects, interfaces, extensions, countries, test cycles, training sessions. The price rests on counted things rather than optimism, and contingency can be tied to named risks instead of a flat percentage that procurement will cut.
It makes the delivery workable. It tells the delivery team and the client who does what, by when, to what standard, and what happens when reality turns out differently. That is what keeps the plan, the team and the relationship intact.
“Data migration” is not a scope item. “Migration of 38 data objects across 4 company codes, with up to 3 mock loads, using client-cleansed data delivered in our templates” is. The second can be estimated, staffed, tested and, if it changes, re-priced. The first can only be argued about.
Where delivery actually gets hurt
The challenges delivery teams face on SAP and ERP programmes are remarkably consistent. Almost all of them were decided, or left undecided, in the bid:
- Data migration turns out bigger and dirtier than assumed, and nobody agreed who cleanses.
- Interfaces multiply once the landscape is properly mapped, and some need another vendor to change their system too.
- Custom code meets “clean core”: the business expects today’s custom functions to survive; the design principle says otherwise, and the gap appears as unpriced extension work.
- “Fit-to-standard” means different things to each side, and every gap becomes a debate about whether it was in scope.
- Testing ownership is unclear: who writes the scripts, who runs UAT, who supplies the test data.
- Client people are not available, because the key process owners are also running the business.
- Training is under-sized: the bid meant train-the-trainer; the client read it as every end user, in every language.
- Responsibilities between SAP, the hyperscaler, the SI and the client blur in cloud and subscription models, and the gaps land on the critical path.
- AI and innovation promises were added to stand out, with no defined outcome, data readiness, budget or owner.
None of these is solved by better delivery alone. Each is cheapest to fix in the bid, with a sentence and a number, and most expensive to fix in month nine, with a change request and a strained relationship.
Why this matters now
SAP’s mainstream maintenance for SAP ERP 6.0 (ECC) ends at the end of 2027, with optional extended maintenance available through 2030 at extra cost, as SAP itself announced. Many organisations are tendering S/4HANA programmes in the same window, competing for the same experienced people, often under deadline pressure. That is exactly when scope gets written in a hurry, and delivery pays for it later.
Three things to do on your next bid
- Count everything you can. If a scope item has no number attached, it is not yet a scope item.
- Write assumptions that can be tested. Each one should be specific, measurable, owned, and say what happens if it proves false.
- Get the delivery lead’s sign-off before you submit. The person who will run the programme should be able to say “I can deliver this” before the client ever sees the price.
Download the playbook
We have put the full approach into a free 10-page guide. It covers the six layers of a complete scope boundary, ten delivery challenges that start in the bid (and the boundary that prevents each one), weak versus strong assumptions side by side, how the boundary becomes the price, the contingency and the change mechanism, and a 12-question scope test to run before you submit.
Draw the Line: a scoping playbook for SAP & ERP bids
10 pages. No sign-up, no email required.
Want a second pair of eyes on the scope before it goes out? Book a free 30-minute discovery call or email sales@dealcraftadvisory.ie.