An estimate is the price of solving a specific problem. If a line in it can’t be traced back to that problem, it is either cost the client doesn’t value or value the bid hasn’t explained. Either way, it is the first line an evaluator cuts.
The failures are rarely in the arithmetic. In Horváth’s study of 200 SAP user companies, projects ran 30% longer than planned on average, only 8% of completed migrations finished on schedule and more than six in ten went over budget. The study director pointed to project set-up: complexity and resource needs underestimated, the organisation’s own capacity overestimated. Estimates fail at the joins.
The chain
- 1PainWhat hurts, in the client’s words
- 2OutcomeA measurable state that removes it
- 3ScopeCounted things that deliver it
- 4AssumptionsWhat must be true
- 5RACIWho makes it true
- 6EstimateBoth sides’ effort
- 7ContractWhat happens when a link breaks
Read it in order, 1 to 7, when you build a bid, and backwards, 7 to 1, when you evaluate one.
The case: an airline group’s revenue
An international airline group runs its airline on SAP. Around it sit subsidiaries and associated companies, several of which the group doesn’t manage. Their revenue reaches group finance as spreadsheets and emailed notes. The pain, in the client’s words: more control over how the subsidiaries report, without managing them.
Airline revenue is hard to begin with. In SAP’s own description, ticket data flows through a separate passenger revenue accounting system and reaches the ledger as aggregated batch files, so finance sees the flight rather than the customer. SAP’s answer for the order-based world is Order Accounting in the ERP, on SAP Billing and Revenue Innovation Management. Valuable, and none of it touches the spreadsheets from the subsidiaries. That pain sits in the group close: data collection from non-SAP entities, intercompany matching and reconciliation, and close governance.
A bid that leads with the revenue platform may be technically stronger and still lose, because the evaluator can’t see their problem in it. A bid that removes the stated pain in phase one, and modernises the platform in phase two, can.
Every assumption hands risk to someone
| Weak: hides the risk | Owned: names it |
|---|---|
| Subsidiaries will provide data in the agreed format. | The 14 non-SAP entities submit monthly revenue through the group template by working day 3, each with a named finance owner. Template build and two onboarding sessions per entity are ours; chasing late submissions is group finance’s. |
| Client resources will be available as required. | Group finance provides a reconciliation lead at 60% and a close manager at 40% from mobilisation to the second parallel month. |
Case anonymised; numbers illustrative.
Test one of your assumptions
Paste an assumption from a live bid, or from a bid you are evaluating, and tick what it already does. Nothing you type leaves this page.
The RACI is half the estimate
Most bids estimate their own people to the half-day and the client’s in one sentence. In the airline case, the work that removes the pain is largely the client’s: agreeing a data standard with each entity, submitting on time, chasing late submissions, resolving intercompany differences, signing off the close. In the whitepaper’s illustration, that is about 357 person-days of client and third-party effort in year one that a supplier-only estimate would leave out.
That is also why two prices can be 14% apart and both honest. One integrator onboards the 14 entities and supports two parallel months; the other assumes the client does it. They are different offers. A buyer can only see that if both bids show their RACI and their client-effort estimate.
- Bid teams: map every estimate line to an outcome, test every assumption, and put the client’s effort in the proposal. It is what makes your own number believable.
- Buyers: compare the RACI before the rate card, and ask each bidder how many of your person-days their price needs.
From Pain to Price
12 pages: the chain, the airline case through every link, three failure patterns and 24 checks for bid teams and buyers. No sign-up.
The Estimate Trace worksheet
One row per estimate line, from pain to client days. Flags lines with no pain behind them, assumptions with no owner and client effort nobody estimated. Includes the airline example priced line by line (with project management, hypercare and contingency shown openly), a full RACI with one-A-per-row checks, and blank sheets for your own bid.
Want a second pair of eyes on the trace? Our Orange Team review follows your estimate from the client’s pain through scope, assumptions and RACI before you freeze the price, and our buy-side support compares bids by what each one asks of you. Book a free discovery call.
Related: Draw the Line (scope boundaries), The Scope Multiplier (counting), How Many Data Runs and The Estimate Changes (AI and partner tools).
Sources: CIO.com on the Horváth study, 24 Mar 2025; SAP, “SAP ERP Next Gen for Revenue Accounting” and “IATA Offer to Cash” (IATA event material); IATA airline retailing registry; SAP product material for group reporting and intercompany matching and reconciliation. Full list in the whitepaper. The airline case is anonymised and its numbers are illustrative. Dealcraft Advisory has no commercial relationship with SAP or any vendor named. SAP and S/4HANA are trademarks of SAP SE.