When to Use Specialist Placement vs Full Service Delivery
When organisations look for external support on a SaaS implementation, they’re usually thinking about who to hire. The more important question is how to structure the engagement, because the model you choose determines where accountability sits, how much management overhead lands on your team, and what capability you’re left with when the project ends.
Two models dominate serious implementation engagements: Specialist Placement, where individual experts are embedded into your existing project team to fill specific capability gaps; and Service Delivery, where an external team takes end-to-end ownership of the implementation programme. Both are legitimate approaches. Neither is universally better. The right choice is contextual, and organisations that choose the wrong model often don’t realise it until the problems that the right model would have prevented have already materialised.
Here’s how to think through the decision.
What Each Model Actually Involves
Specialist Placement means embedding one or more domain experts, such as a QA specialist, a project manager, a business analyst, or an integration architect, into your existing team. They work in your project tools, attend your standups, and operate within your governance structure. The consulting firm they come from provides methodology support and quality accountability. But direction of the work sits primarily with you.
Service Delivery means an external team takes ownership of the implementation programme. They provide the project manager, the QA lead, the business analyst, and the delivery methodology. Your internal team provides business knowledge, stakeholder access, and decision-making authority on business requirements. The external team structures the programme, manages delivery, and is accountable for the outcome.
The distinction sounds straightforward. In practice, the implications for cost, control, risk, and capability transfer are significant, and they diverge from each other in ways that matter most precisely in the situations where implementation is hardest.
When Specialist Placement Is the Right Choice
Specialist Placement works well when your organisation has existing implementation management capability but specific skill gaps in the delivery team.
Filling Domain-Specific Gaps
The clearest use case is a technology organisation that has experienced project managers and product managers who have run internal technology projects, but hasn’t previously implemented a complex enterprise SaaS platform and lacks QA specialists with implementation-specific experience. The programme management infrastructure is present. The gap is domain-specific: implementation QA methodology, integration testing expertise, or SaaS-specific project management experience. Embedding one or two specialists to fill those gaps is both cost-effective and preserves your existing team’s ownership of the programme.
Retaining Direct Control
Specialist Placement also suits organisations that have strong opinions about how implementation work is structured and want to retain direct control of delivery decisions. If your VP of Engineering wants to own the sprint cadence, define the testing approach, and make the prioritisation calls, and just needs more specialist capacity to execute, Specialist Placement gives you that control without the overhead of a managed engagement.
Building Internal Capability
A third scenario where Specialist Placement performs well is capability building. If one of your objectives alongside delivering the implementation is developing internal implementation capability for future projects, embedded specialists transfer knowledge through daily collaboration in a way that an arms-length managed delivery does not. By the end of the engagement, your team has worked through a full implementation cycle alongside experts who can explain both what they did and why, building institutional knowledge that persists after the engagement concludes.
What to Watch For
Specialist Placement places real demands on your internal management capacity. Directing a specialist requires that you know enough about the domain to provide useful direction. An embedded QA specialist without clear direction on what to test, in what priority, and against which requirements, is an expensive resource operating below their potential. If your internal team is already at capacity managing the implementation, adding specialists to direct without adding management bandwidth typically produces suboptimal outcomes from both the specialists and the wider programme.
When Service Delivery Is the Right Choice
Service Delivery is the appropriate choice when your organisation lacks internal implementation management capability, either because you haven’t run complex SaaS implementations before, or because the implementation in scope is significantly more complex than anything your team has previously managed.
When Internal Capacity Doesn’t Exist
The most common scenario is a business function, whether operations, finance, or HR, implementing an enterprise platform that their internal team has never implemented before, in an organisation where the technology team is focused on core product development and has limited capacity for a parallel implementation programme. There’s no experienced implementation PM, no QA methodology, and no one with the availability to build those things from scratch while also delivering the project. Service Delivery provides the complete capability required without placing unrealistic demands on an already-stretched internal team.
High Complexity or Compliance Requirements
Service Delivery is also better suited to implementations where the integration complexity or compliance requirements are high enough that the methodology for managing them is itself a significant part of the value being delivered. An APRA-regulated financial services organisation implementing a new lending platform needs not just a project manager and QA specialist, but a delivery methodology that’s been adapted for regulated environments, one that accounts for vendor due diligence timelines, compliance testing requirements, and audit documentation standards. That methodology is embodied in a Service Delivery team that has done it before. It’s harder to replicate with individual specialists embedded into a team that hasn’t.
Implementation Rescue
Implementation rescue, meaning taking over a programme that is materially off track, is almost always a Service Delivery scenario. A struggling programme typically needs structural changes to methodology, governance, and delivery cadence, not additional headcount doing more of what wasn’t working. Service Delivery allows the external team to assess the programme, recommend structural changes, and own the delivery of a revised plan. Specialist Placement into a struggling programme without structural change typically produces more output of the wrong kind.
What to Watch For
Service Delivery requires genuine business engagement from your side. External teams can own programme delivery. They cannot own business requirements, stakeholder relationships, or go/no-go decisions. Implementations that hand off to a Service Delivery team and reduce internal engagement accordingly tend to produce technically correct systems that don’t match how the business actually works. The external team will ask questions and need decisions. The internal stakeholder group that answers those questions and makes those decisions well is the single biggest determinant of Service Delivery success.
Cost: What the Numbers Actually Look Like
On a per-unit basis, Specialist Placement typically costs less than Service Delivery. You’re paying for individual specialists rather than a managed delivery team with programme overhead. For a two-specialist engagement, such as an implementation PM and a QA specialist, the direct engagement cost of Specialist Placement will be lower than the equivalent Service Delivery scope.
Accounting for Internal Costs
The comparison changes when you account for internal costs. Specialist Placement requires your team to direct the work, manage integration between the specialists and the wider programme, and absorb programme management overhead that a Service Delivery team would carry internally. For a complex 12-month implementation, that internal management overhead, measured in senior staff time, is a real cost that often isn’t captured in the procurement comparison.
A rough framework: if your implementation requires two or more specialists working for more than three months, and your internal team doesn’t have a dedicated programme manager available, the fully loaded cost difference between Specialist Placement and Service Delivery is usually smaller than the fee difference suggests. The management overhead of directing multiple specialists without programme management support is significant, and when it causes delivery problems, the cost of remediation closes whatever gap remained.
The Hybrid Approach: Service Delivery into Specialist Placement
For organisations running large, multi-phase implementations, a hybrid model often performs better than either pure approach.
How It Works
The pattern: Service Delivery for the primary implementation programme, transitioning to Specialist Placement for hypercare and ongoing optimisation after go-live. The Service Delivery team owns the delivery phase, covering requirements, design, build, test, and go-live. As the system stabilises post-launch, the full delivery team rolls off and one or two embedded specialists remain to support the internal team during hypercare, address post-launch issues, and build internal capability for ongoing configuration and optimisation.
This model provides the accountability and methodology of Service Delivery for the high-complexity delivery phase, and the knowledge transfer and cost efficiency of Specialist Placement for the lower-intensity post-launch period. It also creates a natural knowledge transfer point: the embedded specialists remaining post-launch have worked through the entire implementation alongside the delivery team and carry deep institutional knowledge of how the system was built and why.
A Decision Framework
Choose Specialist Placement when: your internal team has experienced implementation management capacity; the gaps are specific and identifiable; you want to retain direct control of delivery decisions; or capability building is an explicit objective alongside delivery.
Choose Service Delivery when: your organisation lacks internal implementation management capability; the complexity or compliance requirements exceed what your team can direct without specialist guidance on the methodology itself; the implementation is in rescue mode; or the programme risk profile warrants having accountability sit with an external team.
Choose a hybrid model when: the implementation is multi-phase, with a complex delivery phase followed by an extended stabilisation or optimisation period; or when you want to build internal capability through a managed delivery rather than acquiring it separately.
Choosing Based on Capability, Not Cost
In both pure models and the hybrid, the most important single variable is not which model you choose. It’s whether you’ve honestly assessed your internal capability and chosen the model that matches it. Choosing Specialist Placement because it costs less, when your internal capability to direct specialists is limited, will produce results that cost significantly more than Service Delivery would have. The model should match your situation, not your budget preference.
