The tell is simple. When something goes wrong, is the client's first instinct to raise a ticket, or to call someone by name? Everything else follows from that.
We have built these both ways over the years. What follows is what we have learned about getting into the second category, drawn most recently from standing up a procurement operation in Hyderabad for a US manufacturer.
Start with the work, not the team
The instinct is to hire first and learn second. It produces a team that is technically capable and operationally lost.
We invert it. Discovery first: how the work actually happens, what the systems hold, where the process crosses from one to another, which exceptions matter. Only then do you know what the team needs to be — not headcount and job titles, but the specific shape of the capability.
That mattered here. The obvious team for a procurement operation is buyers. What the work actually needed was wider: supplier management, logistics coordination, ERP support and reporting each carried enough weight to justify dedicated people. The team we built included procurement specialists, planners, logistics coordinators and reporting support. Had we hired to the obvious shape first, we would have staffed a buying desk and then spent a year discovering what else the operation required.
4
months of discovery, training and implementation
1
month of validation before go-live
5
months before anyone relied on the team
That is not slow — it is the cost of the team being right when it starts.
Dedicated means dedicated
A team split across three clients is a supplier. A team that works only on your account learns your business, which is the entire value.
It costs more and it is worth it. The people on this engagement work on this client and nothing else. They know the suppliers. They know which exceptions are normal. They know who to call.
What that buys you
A shipment from a critical supplier was at risk of delaying production. Because the team held direct relationships with both the supplier and the logistics provider, they assessed the situation themselves, secured revised shipment commitments, and went to the client's stakeholders with mitigation options rather than with a problem.
That sequence is only available to people who already know which suppliers are critical, what the production schedule depends on, and who to call to change it. A transactional support function would have raised a ticket and waited.
Solve the time zone problem properly
The usual answer is an overlap window — a few hours where both sides are awake — and it is a compromise that satisfies nobody.
For a business buying from suppliers across every time zone, the overlap window is not really the issue anyway. The issue is that a question sent to a supplier at 6pm their time waits until tomorrow, and a shipment that waits a day arrives a day late.
What works is assigning ownership by function rather than by shift. Team members hold specific suppliers, categories and workflows, and that ownership does not change hands at the end of a working day. What changes hands is the current state of the work — through daily status updates, open action trackers, and escalation points that are written down rather than improvised.
A shift roster gives you coverage without accountability. Ownership by function, with a disciplined handover of state, gives you both.
Build the reporting the client does not have
A capability center has an advantage worth using: you are rebuilding the process anyway, so you can instrument it properly.
On this engagement we built executive dashboards in Power BI giving leadership a live view of the operation — what was on order, from whom, and what was at risk. The client had not had that before. Routine handling moved into Power Automate, with Copilot supporting day-to-day work, all on Azure.
Make the ownership visible
Every major area of responsibility has a named owner, and that person is the contact for both the client's stakeholders and the external suppliers in their area. Around that sit regular review meetings, status updates and documented escalation channels, so that when something needs attention nobody has to work out who owns it first.
It sounds administrative. In practice it is the difference between a team that feels present and a team that feels remote.
What we would tell someone considering this
Do not treat the transition as the project. The transition is the beginning. Budget attention for the twelve months after go-live, not just the five before it.
Expect the learning curve to be the risk. Not the hiring, not the infrastructure. Whether the team genuinely understands the work.
Measure what the client cares about. For a manufacturer that means supply continuity first. Cost matters — this operation runs at 60% lower cost than the function it replaced, and renegotiating with existing vendors took another 20% off material costs — but a cheap procurement function that lets a production line stop has not saved anyone anything.
Accept that it is slower to start. Five months before go-live feels long when a staffing firm can have people in seats in three weeks. Those are different products, and they fail in different ways.
The point
The point
A capability center is not offshore staffing with better marketing. The difference is whether the team understands the work well enough to make decisions, and that comes from how you build it: work first, dedicated people, real ownership, and reporting the client can see.
Get that right and the client stops thinking of them as the offshore team. They become the procurement team, who happen to be in Hyderabad.
Written by
Director of Procurement, Modern Signal
Modern Signal's procurement practice, running dedicated operations from Hyderabad.
