A founder we worked with last year hired a Head of Customer Support at 18 months post-Series A. The role cost €85K per year. Four months later, they came to us because the Head was spending 60% of their time answering the same 40 ticket types every week - password resets, payment status checks, basic feature questions. Retention work, the reason they'd made the hire, wasn't happening.
The mistake wasn't the hire. It was the sequence. They needed L1 coverage first.
This plays out in both directions. Companies outsource L1 before they have a working knowledge base, the provider fails, and they conclude outsourcing doesn't work. Companies hire a CS lead before they have enough support volume to justify the function. Both mistakes are expensive and both are avoidable. The framework below is built from what we've seen go wrong.
The question you're actually deciding
"Hire or outsource" conflates two completely different decisions:
- CS Lead hire - the internal person who owns customer relationships, builds the support function, and drives retention. Strategic. Culture-critical. This is a people decision.
- L1 support operations - the team handling first-contact resolution across all channels, 24/7 or extended hours. High-volume. Process-dependent. This is an operations decision.
These decisions have different triggers and different thresholds. You can - and often should - outsource L1 while simultaneously hiring a CS lead. Or keep L1 with a founder until volume justifies outsourcing. Conflating them leads to bad sequencing and expensive mistakes.
When to hire your CS lead
The CS lead decision is about ownership and retention. The threshold isn't a headcount number - it's a signal that churn has become strategic rather than incidental.
| Signal | What it means |
|---|---|
| Monthly churn above 2% for 3+ months | You're losing more than product improvements can recover. Someone needs to own renewals. |
| 3+ enterprise accounts with no dedicated owner | At this account size, relationship gaps turn into churn. No one is catching the early signals. |
| NPS below 30 with no structured follow-up process | Passive detractors are leaving silently. No one is in the conversation before they go. |
| Support volume past 500 tickets/month | The founder can't cover this function without it consuming their week. |
| Expansion revenue possible but not being captured | Upsells and upgrades are a CS function. If no one owns it, you're leaving ARR on the table. |
If 3 or more of these are true, you're past the "hire or not" question - you're already late. If fewer than 2 apply, a founder or ops generalist covers this function while you focus on product-market fit. The CS lead hire before these signals are present is almost always premature, and the person you hire will either leave or drift into operational firefighting.
When to outsource L1
L1 outsourcing is an operations decision, not a strategy decision. Two conditions need to be true before outsourcing works:
1. You have a working knowledge base. A provider can't resolve what isn't documented. If your support playbook lives in a founder's head or in a shared Notion that hasn't been updated since your last product release, the provider's first-month closure rate will be poor. You'll blame them. The real problem is yours. We've been called in to fix this situation four times. Every time, the knowledge base was the root cause - not the provider.
2. You have a defined escalation boundary. What does L1 resolve? What escalates to L2 or engineering? If you can't write that criteria down in 20 minutes, the provider won't know either. You'll pay for support coverage and absorb more engineering escalations than before you outsourced.
If both conditions are met, the volume threshold for outsourcing is lower than most companies expect. At 200+ tickets per month with extended or 24/7 coverage requirements, the math looks like this:
- Internal staffing for 24/7: minimum 4–6 agents to cover 3 shifts with overlap. At Eastern Europe rates, that's €15,000–25,000/month in salary, management overhead, and attrition cost before you reach steady state.
- Outsourced dedicated team for the same coverage: €7,000–14,000/month, all-inclusive, with no ramp risk on your side.
For Monday–Friday business hours only, under 300 tickets per month, a single internal hire often costs less and gives you better product context. The crossover point is coverage hours.
The four-scenario matrix
What the wrong decision costs
Hiring a CS lead before L1 is covered: The lead spends 60–80% of their time in the queue. The retention work you hired them for doesn't happen. You've paid €60–100K for a year of strategic nothing. The hire usually leaves within 18 months because the role was never what they signed up for - and you've lost the institutional knowledge they built while answering tickets.
Outsourcing before your KB is ready: The provider agents can't close tickets without documented resolutions. Escalation rate stays high. You blame the provider. The real problem is the documentation gap - which was yours from day one. Net result: 3 months of paying for coverage that performed poorly, your internal team absorbed all the escalations anyway, and trust in outsourcing is damaged internally. Rebuilding that trust takes longer than fixing the KB would have.
Waiting too long to outsource: A founder or senior ops person is answering the same 40 ticket types every week. They know every answer. They've never written them down. Every month this continues, you're paying a €70–100K person to do a €25K job. At scale, this is €4,000–6,000/month in misallocated cost - before you count the opportunity cost of what that person isn't doing.
How IMMIDO fits into this
We run the L1 layer: inbox coverage, first-contact resolution, escalation triage, weekly reporting into your stack. We don't replace the CS lead - we integrate with them. Our escalation notes go into their queue with full context. Their product updates go into our knowledge base.
The setup that works best: one internal person owns the customer relationship and the strategy. We run the operational coverage under them. For most clients, this stabilises at a monthly retainer of €7,000–14,000 for extended or 24/7 coverage, all-inclusive. We quote after scoping - volume, coverage hours, languages, and product complexity all affect the number.
If you're not sure which decision is the right one for where you are now, that's the most common starting point. Book a 30-minute scoping call → We'll tell you honestly whether you need us, need an internal hire first, or need both - and in which sequence.