Which outsourcing model should you choose?
| Model | How it works | Best for |
|---|---|---|
| Dedicated team | Full-time people who work only for you, managed by the provider | Ongoing work where product knowledge and consistency matter |
| Shared team | Agents split across several clients, often billed per contact | Simple, low-volume or overflow work |
| Project-based | A defined deliverable with a start and end | Backlogs, migrations, one-off clean-ups |
| Employer of record | The provider only employs; you manage day to day | A few individuals you will lead yourself |
What should be written down before go-live?
- Scope: which work the team does and what it escalates
- Procedures and a knowledge base the team can trust
- KPIs with definitions and targets
- Access rules: which systems, which permissions, who approves
- Escalation paths and contacts on both sides
- Reporting: what is reported, how often and to whom
What goes wrong most often?
- Undocumented exceptions that only one person in-house understands
- Going live on full volume on day one instead of ramping up
- Measuring only speed, which teaches people to close rather than solve
- No named owner on the client side to answer questions quickly
- Treating the team as outsiders rather than including it in product updates
Continue reading
How do contracts and data protection fit in?
A typical set of documents is a master service agreement, a statement of work per service, a data processing agreement for personal data and, for data leaving the EU or UK to a country without an adequacy decision such as Kosovo, Standard Contractual Clauses. Agree security requirements and audit rights at the same time, not after go-live.
How long until the team performs at full level?
It depends on the work. Simple, well-documented processes can reach target quality within the first weeks of live work; complex technical support or regulated work takes longer. Plan for a ramp-up period in your business case rather than assuming full productivity from day one.