Articles

How many of your own people will an SAP programme need?

Written by Neil How | Nov 18, 2026, 10:03:13 PM

This is a question we get asked a lot. It is also really important - it dictates pace, bandwidth, maturity and also the success rate of the programme. Typically it is always vastly underestimated - much more than most business cases allow for. An SAP programme needs a sponsor, a client-side programme lead, an owner for each major business process, people who know how the work is really done today, data owners, a change lead, super users and testers from the business. Many of these roles take a large share of someone's week for long periods at a time. The people best suited to them are usually the people the business can least spare. The best programmes use the best people, and typically generate the best outcome. 

 

Why the number is usually too low

Business cases tend to count the delivery partner's team in detail and the client's team loosely. The delivery partner's team has names, normally some kind of day rates and a plan. The client's contribution often appears as a single line called "business involvement", with no names attached, or no idea as to what the terms of reference/engagement will be. Everything is typically 'a little vague'.

The instinctive response is that people are 'attached' to the programme on top of their day job. That works for a few weeks. Then month-end arrives, a customer escalates, or a team member leaves, and the day job wins. The programme slows down in ways that are hard to see from the steering committee, because the delivery partner's team is still fully staffed and busy - but the impact on the plan is significant.

 

The roles the business needs to fill

Role What they do How much of their time
Executive sponsor Owns the outcome, chairs the steering committee and makes the decisions nobody else can A few hours a week, more around key decisions
Client-side programme lead Runs the programme on behalf of the business and works with the delivery partner day to day Full time
Process owners Own the design of an end-to-end process, such as order to cash, and sign it off Most of their week during design and testing
Subject matter experts Know how work is really done today, including the exceptions Heavy during design workshops and testing
Data owners Decide what correct data looks like, and sign off migrated data Steady throughout, with peaks before each trial load
Change lead Plans how people move to the new way of working Full time on larger programmes
Super users Test, train and support their colleagues Rising through testing, highest around go-live
Business testers Run user acceptance testing with real scenarios Concentrated in the test phases

 

Signs the programme is under-resourced

There are numerous signs a programme is under resources. Some are more obvious - design workshops get repeated because the right people were not in the room the first time. Sign-offs arrive late, or arrive quickly without much reading. The delivery partner starts testing on the business's behalf. The same few names appear against several roles at once. Joe Bloggs is not available as he was pulled back into the business to help cover some absence or additional workload.

Any one of these is worth raising. Several of them occurring together usually explains why a programme is running late, long before anyone cares to admits it.

 

Backfill is the real cost

The people a programme needs are good at their current jobs, probably the best in the team/department, and someone has to cover their jobs/roles while they are seconded to the programme. That cost needs to be in the business case - a paid individual to replace them day-to-day.

There are several ways to cover it: promoting a deputy, hiring on a fixed term, or bringing in a contractor to cover the day job. Fundamentally though, the expertise of your best person will pay dividends in the future and you need their engagement on the programmes. The 'years of knowledge' about how your business really works is critical for design workshops.

 

A simple way to estimate your own number

Start with the scope. Count the end-to-end processes in the scope of your transformation; each needs an owner and at least one expert who knows the detail. Deep detail. Count the main types of data; each needs an owner. Count the sites and teams that will go live; each needs super users.

Then put names against every role. If a name appears more than once or twice, or if nobody has agreed what that person stops doing to make room, the plan has a gap. It is far cheaper to find that gap now than in the middle of testing.

 

Where Limelight fits

Our LaunchPad engagement builds the resource profile with the business before a programme starts, so the people, the time and the backfill are agreed and costed up front. We also provide senior directors to lead the client side, where the business does not have someone with SAP programme experience to spare.

If you are trying to work out what your business will really need to give an SAP programme, book a Readiness Review. One of our directors will talk it through with you in 45 minutes.