When build tends to win
- The work is central to your competitive position, not routine support.
- You already have a manager with time to run a technical team.
- Volume is high and stable enough to justify a full-time hire or more.
Both routes can produce a working delivery lane. They differ in how long it takes, what the cost looks like month to month, and what happens the week one person is out.
| Factor | Build a team | Add a delivery partner |
|---|---|---|
| Time to capacity | Recruiting, hiring, and ramp before the first request is handled. | Starts once a client group and lane are defined and accepted. |
| Cost shape | Fixed salary and overhead, independent of ticket volume. | Reference rate scales with the user count actually in the lane. |
| Management overhead | Your practice manages performance, coverage, and training directly. | Delivery manages its own staffing; your practice manages the relationship and exceptions. |
| Coverage risk | A single hire is a single point of failure for absence or turnover. | Coverage depends on the delivery organization's own staffing, set out in the agreement. |
| Standards and documentation | Built from scratch, at your practice's own pace. | Inherits an existing operating structure — service profile, request record, exception path. |
| Flexibility to scale down | Reducing headcount is a management decision, often a difficult one. | Reference band and lane can be renegotiated as a commercial change. |
Many practices run a small internal team for judgment-heavy or client-facing work, and add delivery capacity for the recurring lane — rather than treating build and buy as all-or-nothing.
"Buy" still covers several different arrangements — white-label delivery, subcontracting, staff augmentation, and referral are not the same thing.