Blended Delivery Isn't Optional Anymore.
Being part of the Services Delivery Alliance, we meet 100s of Senior Delivery Leaders each week. When asked if they run a blended model, most will say something akin to "sometimes”; there is often no formalized version of this play. Typically it appears as the partner on the big implementation, a contractor when the bench runs dry or a specialist for the integration nobody in-house has touched.
That word "sometimes" is [or can become] a big problem. Industry benchmarks show subcontractors now account for roughly a tenth of professional services revenue. At that scale, partners aren't a stopgap, they're part of your delivery model, whether you've planned for them or not.
Yet many still run them like a stopgap. In this blog we’ll show why that costs more than it looks and therefore how you should decide your partner vs. internal mix with purpose, plus pressure test it before you've committed to a customer.
Why blended delivery became the default.
The move for the Services Delivery function from cost-centre to profitable department for most is well into the past. Now the majority see it as a necessity. With that change came obvious challenges, but the changes to the blended model has been an significant outcome of this.
Whether it is hiring which hasn't kept pace with demand (or was frozen completely), or if demand doesn't arrive evenly, or customers wanting faster time to value, turning to partners to “fix” the problem will either be a stipulation or a necessity. It only exacerbates when product roadmaps keep adding specialisms (integrations, data, AI) that a core Delivery team can't staff for year-round.
The one positive is that in most software ecosystems, implementation partners have already been embedded in your customers' buying decisions - this is no new thing.
What's changed is that the gap between "the work we sell" and "the people we employ" isn't closing anymore. Blended delivery is how you close it.
The real problem isn't partners, it's when you decide to use them.
Many Delivery teams are involved during the sales cycle. But being involved in the deal isn’t the same as locking in the mix. Partner availability, skills and rates often aren’t confirmed until after signature, so the final mix still gets settled under time pressure. That’s the gap Precursive AI is built to close, bringing Delivery’s view of capacity into the deal while it’s still open.
How Delivery is measured plays a part too. Most leaders track internal utilization closely, and every hour handed to a partner is an hour their own team doesn’t bill. That makes it tempting to stretch internal capacity first and bring partners in only when their use is overtly signposted.
The bigger problem comes once partners are on the project. To your customer, a partner is an extension of your team, so partner work that falls short reflects on you. Yet many Delivery teams have no consistent way to measure partner quality or see how partner work is progressing until something has already gone wrong.
What teams assume | What's actually happening |
Partners are a capacity buffer | Partners are covering skill gaps you haven't named, so the gap never closes |
Keeping work internal protects margin | Utilization targets hide the cost of delays and rushed partner onboarding |
The partner owns their piece | The customer sees one project and holds you accountable for all of it |
Status calls give us visibility | Partner hours, risks and progress live outside your system until something slips |
How to decide your partner vs. internal mix
Don't decide at the project level. Decide at the workstream level. For each piece of work you regularly sell, run through these questions:
Does it shape retention? Solution design, executive relationships and adoption work stay internal. This is where renewals are won or lost.
Is it repeatable and well documented? Standard configuration, data migration and routine build work are strong partner candidates.
Is the skill rare and the demand lumpy? Use a partner, but pair them with someone internal so the knowledge stays when they leave.
Who owns the customer moment? Kickoffs, go-lives and handovers to Customer Success stay with your team, even if a partner did the build.
Can you see it? If you can't track partner effort, progress and risk in the same place as your internal team, don't scale it yet.
Workstream type | Default owner | Why |
Solution design and scoping | Internal | Sets expectations you'll be held to |
Standard configuration | Partner | Repeatable, easy to quality-check |
Specialist integrations | Partner + internal shadow | Rare skill, knowledge must transfer |
Adoption and value realization | Internal | Directly drives retention |
Pressure test your blended delivery requirements before the deal closes
The best time to find a gap in your mix is before the contract is signed, not after. Before a deal moves to close, Delivery should be able to answer yes to each of these:
Capacity: Is a named partner resource actually available for the forecast start date, not just "a partner"?
Skills: Does the partner's team match the specific skills the scope requires?
Margin: Does the blended rate still hit your margin target once you include the internal time spent coordinating partners?
Access: Do partners have what they need to deliver, without access to things they shouldn't see?
Expertise: Is there a defined route for partners to reach your internal experts? TSIA research found only 49% of organizations have a documented process for this
Handover: Is it clear who owns each customer-facing milestone?
Knowledge capture: What does your team keep when the partner rolls off?
If any answer is to discover the answers at a later time, that's the risk you're signing up for.
How Precursive helps you run blended delivery as one team
Pressure testing only works if partners sit in the same plan as everyone else. That's what our Partner Workspace is built for.
Partner Workspace is a secure, branded portal where you invite your implementation partners, systems integrators and contractors to collaborate on co-delivery projects. Partners are set up as resources in Precursive and added to projects as participants, so they show up in the same plan as your internal team rather than in a separate spreadsheet.
You stay in control of what partners see. You can set default project access levels by role, so a partner gets exactly what they need to deliver and nothing more. Partners can also work from reports and dashboards inside the workspace, which means progress and risk surface in Precursive, not on Friday's status call.
And because Partner Workspace is built on Salesforce Experience Cloud, your blended delivery plan lives where Sales and Delivery already work. When a deal is moving through the pipeline, you can see your full delivery capacity, internal and partner, before you commit to a start date.
Blended delivery isn't optional anymore. Running it as an afterthought is.
Comments