The seats are the easy part.
The first fifteen people are not.
We help enterprises build an SAP quality function inside their own capability centre in India — design it, hire into it, set the testing and automation standards, then hand it to your leadership. You own the capability rather than renting it.
Real estate, entity, payroll and IT are solved problems with known suppliers. The part that is hard to undo is the shape of the function — who was hired first, what they considered normal, and which standards were set before anyone was watching.
A quality function staffed early with execution-only testers will keep producing execution volume. One that starts with a test lead who thinks in business processes, and an automation engineer who has maintained a suite through an SAP upgrade, will produce coverage and evidence. Both cost roughly the same to hire. Only one of them still works two releases later.
That is the window we are useful in — before the habits set, not after.
Design it, hire it, set the standard, hand it over.
Design the function
What the quality function is actually accountable for, how it sits alongside your SI and your business users, and which roles the first wave needs — in what order, and why.
Hire into it
From the mapped network rather than a job board, screened by consultants who have done the role. Leadership first where it matters, because the first lead hires the next ten.
Set the standards
Test strategy, coverage and traceability, defect and severity definitions, entry and exit criteria, the reporting the steering committee sees. Written down while the team is small enough to adopt it.
Lay the automation foundation
The regression suite, the framework, and the maintenance discipline — established early, when the scope is small, rather than retrofitted onto a year of manual scripts.
Hand it over
To your own leadership, with the standards documented and the team running them. Our involvement is designed to reduce. If it is not reducing, something has gone wrong.
Who you need first, roughly in this order.
Set the direction
- Quality or test manager
- Test architect
- Automation lead
- Test data owner
Do the work
- Business-process testers by module
- SIT and integration testers
- Automation engineers
- Defect and release coordinator
Keep it honest
- Environment and cutover support
- Reporting and evidence owner
- SAP functional depth per module
- Vendor and SI interface
The exact shape depends on your landscape and your release cadence. What does not change is the order: the people who set the standard come before the people who follow it.
Both are honest answers. They just suit different companies.
Build if SAP is permanent for you, if you have more than one release a year, and if you want the knowledge to stay when a contract ends. It costs more attention in the first six months and less of everything afterwards.
Rent if you have one programme in front of you, if the timeline is the binding constraint, or if you are not yet sure the volume justifies a permanent function. A managed delivery pod gives you the capability without the hiring.
We can do either. We would rather tell you which one fits than sell you the larger one — a capability centre built for a company that did not need one is a bad outcome we would be attached to for years.
Tell us where the capability centre is up to.
Whether that is a board paper, a signed lease or the first four hires already made. The advice is different at each point, and there is no charge for the conversation.