How we work
A defined piece of SAP work, with agreed outputs.
Scoped SAP work under a statement of work, where the output can be specified up front and accountability sits with the deliverable.
How it usually runs.
The steps are the same whether it’s one role or several. The detail inside each one changes with the SAP area.
Scope
Outputs, assumptions, dependencies and acceptance criteria agreed in writing.
Team
Specialists assigned to the scoped work.
Delivery
Work delivered against the plan with agreed checkpoints.
Acceptance
Outputs reviewed against the criteria agreed at the start.
Fits when
- The output can be specified up front.
- You want accountability for a deliverable rather than for hours.
- The work is separable from the rest of the program.
Consider something else when
- Scope is still moving week to week. Consider team augmentation or a delivery pod.
Covers
- Statement of work
- Agreed outputs and acceptance
- Defined timeline
Other ways to work with us.
Most programs use more than one over their life.
Specialist hire
Contract or permanent. One role where the SAP detail decides the hire.
Fits whenA program is blocked on one hard-to-find skill, like an FI-CA lead ahead of cutover.
Team augmentation
Functional and technical capacity inside your own SAP organization.
Fits whenYour practice owns delivery and needs more people on a known plan.
Project team
A connected group around one workstream or phase.
Fits whenSeveral related skills need to start together, like PP, QM and EWM for a plant rollout.
Let’s talk about the difficult SAP hire.
Tell us the process, the landscape and when you need people in place. We’ll come back with questions about the detail.
Requirement received.
We’ll reply to the email you gave us.