Your ERP Will Be Implemented by Junior Consultants. Here’s Why That Matters.

The gap between who sells the project and who delivers it is one of the biggest risks in enterprise technology today.

Slava Pisanka, an ERP consultant with over 20 years of implementation experience, sparked a conversation recently on LinkedIn. His message was direct: the polished senior consultant who wins the deal is rarely the one doing the work.

The pre-sales team is sharp, knowledgeable, and responsive. The implementation team that shows up after the contract is signed? Often junior consultants and offshore resources, with senior staff stretched thin across multiple projects.

This is not a secret. It is the standard business model for large consulting firms, including the Big 4. Margins drive the staffing decisions. Junior resources cost less. Senior consultants rotate between engagements as supervisors, not doers.

The results are predictable. Longer timelines. Poor quality. Fragile system architecture. And clients left spending months after go-live fixing what should have been built correctly from the start.

Pisanka shared a firsthand example. A supply chain planning module was so poorly implemented that his team spent six additional months reimplementing it after go-live.

The boutique advantage

Compare that with a boutique ERP firm Pisanka worked with later. The same people who ran discovery were present at kickoff. They stayed through go-live and post-launch support. The client never had to ask “who are you again?”

That continuity matters. When the team that understands the business context is the same team configuring the system, fewer assumptions get lost. Fewer handoffs mean fewer errors. Feedback loops are faster.

Several practitioners echoed this in the comments. Barry Callaghan, founder of a boutique consulting firm, shared that his team was twice replaced by Big 4 firms for “risk mitigation,” only to be invited back later to rescue both projects. Richa Thakur, a Business Central consultant, pointed out that smaller firms often deliver better outcomes because the same experienced people stay involved from start to finish. They just struggle to compete with brand power.

Brand names do not guarantee quality

The old logic of choosing a big firm to reduce risk is breaking down. Winnie Nguyen, a CEO focused on business transformation, put it well: big brands used to de-risk decisions. Now they have become the risk themselves. Clients are getting smarter and asking for outcomes, not logos.

Sascha Wind added another layer. A well-known firm name often serves as cover for the CIO. If the project fails, they can say they chose the top supplier. The real failure, he argued, goes unrecorded and simply shows up as an extra line item in the finance department.

It is not just about seniority

The conversation went deeper than “juniors bad, seniors good.” Several commentators stressed that the real issue is governance and delivery structure.

Carol Sloan, a senior ERP integration leader, made a point that drew 30 reactions on its own: whether the team is junior, senior, offshore, or boutique, success depends on who owns architectural decisions and who is accountable when trade-offs are made. Talent distribution is a risk. Lack of structural ownership is a failure.

Yvonne Baloyi, an SAP transformation leader, agreed. Challenges arise when discovery, design, and build are fragmented across different teams. When continuity of business context and architectural intent breaks down, quality suffers regardless of firm size.

Hasan Khan Jadoon went further. He spent months reimplementing GL structures built by junior consultants who had never experienced a month-end close in the industry they were configuring. His advice: make sure the consultants have lived in the function they are configuring, not just studied the module.

The client’s role matters too

Several voices pushed back on placing all blame on consulting firms. Zaid Al-Qassab argued that the client company plays an equally big role. Without an experienced internal team that understands business needs, follows the project closely, and tests the system before go-live, even good consultants will struggle.

Tanya W., who works at a Big 4 firm, offered a balanced view. Not all large firms offshore the majority of work. Her firm uses experienced senior managers to lead workstreams. Her advice to buyers: do not decide on cost alone. Define the delivery team early. Vet them. Set minimum experience requirements for key roles. And do not accept a blended bill rate that hides five junior analysts behind 0.1 FTE of a senior.

Alper Aladag raised the budget question directly. Many companies push for the lowest implementation cost possible. That pressure naturally leads to junior-heavy delivery models. You cannot expect a senior-only team on a junior-level budget.

What you should do

The takeaways from this discussion are clear and practical.

First, ask the question before signing: will the people in this room be the ones at go-live? If there is hesitation, that is your answer.

Second, get named resources written into the contract. If the proposal uses “representative bios” instead of actual names, expect a different team on day one.

Third, watch for blended bill rates. Break down who is doing the work and at what allocation. A low average rate often masks a team weighted toward junior resources.

Fourth, build internal capability. Do not outsource all knowledge to the integrator. Your own team should understand the system well enough to hold the partner accountable.

Fifth, consider boutique firms seriously. They may lack brand recognition, but they often deliver tighter teams, more accountability, and better continuity from discovery to support. As Christine Blyth put it: smaller firms have more to prove because they cannot rely on their logo.

The conversation Pisanka started is not new. But the scale of agreement, from Big 4 insiders, boutique founders, independent consultants, and clients, signals that the industry is ready for a different standard. One where who does the work matters as much as who signs the deal.

---

What has your experience been with ERP implementation teams? Did the team that sold you the project stick around for delivery? Continue the discussion on the global supply chain community Chain.NET at www.chain.net, where you can ask questions, join events and discussions, and access exclusive resources.