Overview<\/strong><\/p>\nPeeriosity hosted a GBS Peercast titled “Comparing Options: Big Firms, Small Firms, Vendors, or Internal Resources.” Discussion and live polls covered four segments: the sourcing landscape, where each partner model excels, hidden risks of a one-size-fits-all approach, and building a hybrid partner ecosystem.<\/p>\n
Note that this document is a summary. Peeriosity-100 members have full visibility to company names, presenters, Peercast attendees, and a recording of the Peercast discussion.<\/p>\n
Key Themes<\/strong><\/p>\n\n- Technology vendors are the most-used partner type.<\/strong> 80% of respondents work with technology vendors or their implementation partners, versus 60% with global consultancies and 40% with niche firms. Participants valued desk-level product knowledge (Concur, Coupa) over a large firm’s claimed expertise, and noted tools now change too fast to build that depth in-house.<\/li>\n
- Maturity increases reliance on partners.<\/strong> 60% said GBS maturity has increased their use of external partners; 20% said it decreased somewhat. As GBS adds services and ERP modules, it brings in more specialists “like spokes on a wheel.”<\/li>\n
- Big firms earn their premium on scale.<\/strong> Enterprise-wide transformation or operating model design (67%), multi-region rollouts (50%) and large technology programs (50%) were where global consultancies proved worth the cost. None chose them for functional process improvement or change management. 67% said small versus big firm performance is mixed and project-dependent.<\/li>\n
- Internal teams keep control of the program.<\/strong> 100% said the internal PMO or transformation office integrates multi-partner programs. Partner and vendor management (67%) is the capability most often kept in-house, followed by process excellence, PMO and data and analytics (50% each).<\/li>\n
- Change management is the recognized weak spot.<\/strong> Only 17% deliberately keep change management in-house. It is often funded only as part of an implementation, treated as a one-off, and hard to justify with hard numbers after go-live.<\/li>\n
- Team turnover is the top single-partner risk.<\/strong> Inconsistent team quality or turnover was the most-cited risk (50%), ahead of lock-in and limited knowledge transfer (25% each). 75% said a partner choice has occasionally proven a poor fit.<\/li>\n
- AI is starting to shift work in-house.<\/strong> Half of respondents said AI is leading them to do more in-house; the other half said it is too early to tell. No one is relying more on external specialists because of AI.<\/li>\n<\/ol>\n
Notable Takeaways<\/strong><\/p>\n\n- Getting it right outweighs a 10 to 20% premium.<\/strong> One participant noted that a failing solution costs more in pain than a higher fee; price only becomes decisive at 50% to 100% more.<\/li>\n
- “Nobody gets fired for hiring a big firm” is real but unspoken.<\/strong> Participants agreed career safety sits in the back of decision-makers’ minds, though it never appears on the pros and cons list. No poll respondent selected it as a criterion.<\/li>\n
- Size brings stability.<\/strong> Another participant cautioned that a niche firm dependent on one key client is a continuity risk on long or critical initiatives, and a large project may exceed a small firm’s bench.<\/li>\n
- Expertise drives selection.<\/strong> Specialized expertise (100%), cost (75%) and complexity and scale (50%) were the top criteria; need for internal ownership afterward drew no votes.<\/li>\n
- Commercial models are split.<\/strong> Fixed fee, outcome-based and “varies by partner” drew 25% each; no one uses time and materials most often. Outcome-based terms can be subjective, since client and partner may judge the outcome differently.<\/li>\n
- Value is measured by results.<\/strong> KPIs tied to business outcomes and budget and timeline adherence (75% each) lead; no respondent runs a formal post-engagement review.<\/li>\n
- Knowledge transfer relies on pairing and playbooks.<\/strong> 75% each pair internal staff with partner resources, require documentation and playbooks, and run train-the-trainer sessions; 50% write transfer requirements into the SOW.<\/li>\n<\/ul>\n
Audience Q&A Highlights<\/strong><\/p>\n\n- Vendor teams versus consultancies<\/strong>: The choice is about expertise, not cost. Vendor specialists know what the tool can and cannot do, including policies, expense types and configuration.<\/li>\n
- Internal versus external implementation lead<\/strong>: A pure technical build can be vendor- or consultant-led; projects heavy on internal alignment and process change lean on internal resources.<\/li>\n
- Why so few keep change management in-house<\/strong>: One participant sees it treated as a one-off for specialized transitions. Another said it is funded only within implementations and ends with an FAQ and a corporate email. A third described it as embedded in transformation delivery through training. A fourth countered that onboarding and new business units make it continuous.<\/li>\n
- Making knowledge transfer stick<\/strong>: Projects start with blueprinting, then use train-the-trainer sessions, a documentation repository, and a hypercare or stabilization phase that refreshes users who have not used the system since training.<\/li>\n
- Integrating multiple partners<\/strong>: It depends on who hired whom. If the consultancy brings in vendor resources, it leads; if the company engages partners directly, it must coordinate them.<\/li>\n
- Leaders pushing a preferred firm<\/strong>: Pressure is rarely explicit, but preferences are known, often tied to a leader’s former consultancy, and those connections can help with escalation. One participant advised documenting requirements clearly in the RFP to create a record of how the decision was made.<\/li>\n<\/ul>\n
<\/span>