SAP Resource Models: Dedicated Consultant, Project Team or Managed Service
Three ways to buy SAP capability, and the single question that decides between them: who holds delivery direction?
- Choose a dedicated consultant when work is continuous and needs deep system knowledge of your configuration.
- Choose a project team when scope has a definable finish line and you want a single accountable outcome.
- Choose a managed service when the system is live and someone must own it every day, including the days nothing breaks.
- The deciding question is not cost. It is who holds delivery direction.
- Mixed models work; undeclared mixed models do not.
The question that actually decides it
Buyers usually open this conversation by asking which model is cheapest. That is the wrong first question, because all three can be made to look cheapest over a short enough horizon.
The question that decides it is: who holds delivery direction? If you hold it — you set the priorities, you sequence the work, you accept the trade-offs — you want people, not an outcome. If you want to hand the outcome over and be told when it is done, you want a project or a service, and you should stop asking for daily control of it.
Almost every disappointing engagement we have been asked to rescue was the right work bought in the wrong shape: an outcome bought as day-rate people, or a stream of unpredictable work bought as a fixed-scope project.
Dedicated consultant
A named consultant, allocated in days per month, working inside your processes and governance. They accumulate knowledge of your configuration — which is the real asset here, and the reason day rate is the wrong lens to judge it by.
This is right when the work is continuous but unpredictable in shape: month-end problems, small enhancements, the questions nobody else in your team can answer about why FI posts the way it does.
It is wrong when you need an outcome by a date. A single consultant with no scope and no acceptance criteria will be busy and you will not be able to say what was delivered.
Project team
A scoped piece of work with inclusions, exclusions, named consultants and acceptance criteria per deliverable. OMAV holds delivery direction and is accountable for the result.
This is right when the finish line can be written down. Implementations, migrations, rollouts to a new plant, a Fiori app set — all have a state that is either reached or not.
It is wrong when the requirement will genuinely change every fortnight. Then you are buying change requests, and the governance overhead exceeds the value of the fixed price.
Managed service
A defined service with severity levels in business terms, separate response and resolution targets, and a written boundary between support and change agreed before work begins.
This is right once the system is live and someone has to own it every day — including the days when nothing breaks, which is when the drift accumulates.
It is wrong as a way to get project work done cheaply. If enhancement demand is real, fund it explicitly as a retained pool or an approval threshold, rather than letting it compete with incidents for the same hours.
Mixing models
Most mature SAP estates run two or three of these at once: a managed service for the live system, a project team for the S/4HANA conversion, an embedded consultant for the module nobody else understands.
That works when the boundaries are declared. It fails when they are not — when the AMS team is quietly doing project work, or the project team is absorbing incidents, and neither has a defensible view of what was delivered for the money.
On a distribution client in 2025 we were asked to quote a fixed-scope project for what turned out to be eighteen months of unpredictable month-end fixes. We declined the fixed price and proposed an embedded consultant with a monthly review instead. The client’s procurement team pushed back on the day rate; the finance director agreed after we showed the change-request volume the fixed-scope version would have produced.
Frequently asked questions
Which SAP resource model is cheapest?
Over a defined project with a stable scope, a fixed-price project team is usually cheapest because the risk is priced once. Over continuous unpredictable work, an embedded consultant is cheaper because you are not paying a change-control overhead on every small item. Cost comparisons that ignore change-request volume are not comparisons.
Can we start with an embedded consultant and move to a project?
Yes, and it is often the right sequence. Use the embedded period to understand the work, then scope the project once the finish line can actually be written down. We will suggest the switch when the shape stops fitting.
What happens if our embedded consultant leaves?
Replacement includes a handover overlap at our cost. The practice behind the individual is what you are buying, so continuity is our problem rather than yours.
Do managed services include enhancements?
Only if enhancement funding is defined — as a retained pool of hours or an approval threshold. Without that, enhancement demand competes with incidents for the same hours and incidents win, which is how systems stagnate while the SLA is green.
Marked up as FAQPage structured data, matching the visible text exactly.