Scoping the authorization workstream
A guide for bid and pre-sales teams. The questions to ask before you price security on an S/4HANA bid, the effort drivers that actually move the number, and the assumptions worth writing into your proposal.
What is inside
Sixteen pages, no gate, no form.
Twelve qualification questions
What to ask a client before you price security
Effort drivers, ranked
Org complexity first, user count last
Starting effort bands
Indicative day ranges by programme size
Red flags at qualification
Six signals that the estimate will not hold
Why we give this away
Authorization effort does not scale with the size of the SAP footprint. It scales with organisational complexity, the state of the existing role model, and how much Fiori is in scope. Two clients with identical user counts can differ by a factor of three.
When that is missed at bid stage, the gap lands on the integrator's margin rather than the client's budget. We would rather be brought into a programme at blueprint than called during integration testing, so the questions that prevent it are not worth charging for.
Use it freely. Copy it into your own bid material if it helps.
Who it is for
- Bid and pre-sales teams pricing an S/4HANA programme
- Delivery managers inheriting a thin security estimate
- Practice leads deciding whether to build or borrow the capability
One caveat on the numbers
The effort bands in section 4 are indicative starting points, not a quotation. They are there to be argued with and replaced by your own actuals. Every figure should be validated against the twelve questions in section 2 before it goes into a bid.
Have a live bid?
We will scope and size the authorization workstream for you at no cost, before any commercial relationship exists. You decide afterwards whether we deliver it.