How to Hire Your First Support Person (And When You Actually Need To)
Hiring too early wastes money. Hiring too late burns you out. Here is the signal that it's time and how to find the right person.
Most Startups Hire Too Early
The pattern: founder handles support for the first 6 months. Gets overwhelmed. Hires a support person. The support person handles the same password reset questions the founder was handling, just cheaper.
That's not a hire problem. That's an automation problem. If 60% of your support volume is predictable questions with standard answers, automate those first. Then evaluate whether you still need a hire.
Most teams that automate first discover they can handle 2-3x their current volume without hiring. The hire becomes necessary at a much later stage, and the person you eventually hire handles complex issues — not "what are your hours."
The Signal That It's Time
You should hire when ALL of these are true:
1. You've automated the routine stuff. Auto-responses handle 50-70% of volume. What's left genuinely needs human attention.
2. Escalated tickets take more than 15 hours/week. The human-required tickets are consuming a significant chunk of someone's time. If it's the founder, that's time not spent on product or sales.
3. Response time is suffering. You can't respond to escalated tickets within 2 hours consistently. Customers are waiting too long.
4. The work requires consistency. Support quality varies because whoever is available handles it — sometimes the founder, sometimes an engineer, sometimes nobody. A dedicated person provides consistent quality.
If you haven't automated yet and you're overwhelmed, automate first. The overwhelming part is the repetitive volume, and a hire doesn't fix that — they just do the repetitive work for you at $40K/year.
Who to Hire
Not a "support agent." Not at this stage. You want someone who can:
- Handle customer conversations with empathy and clarity - Write and improve auto-response templates - Identify product issues from support patterns - Manage your support tools (routing rules, integrations) - Contribute to FAQ/documentation
This person is part support rep, part ops generalist, part product detective. At a startup, everyone wears hats.
Where to find them: - Other startup support teams (people who've done early-stage support before) - Customer success roles at larger companies (they want more ownership) - Community managers (they already talk to customers all day) - Reddit/Twitter/LinkedIn posts in startup communities
What to pay: $40,000-$55,000/year for a full-time hire in the US. $20,000-$35,000/year remote international. Part-time options: $1,500-$3,000/month for 20 hours/week.
The Interview
Ask these questions:
"Walk me through how you'd handle this ticket: 'I was charged twice and your product deleted my data.'"
You want someone who addresses the emotional part (two scary problems at once), prioritizes (billing is urgent, data loss is critical), and has a clear action plan (investigate the data issue immediately, process the billing refund, follow up with both answers).
"Our most common ticket is [X]. How would you reduce the volume of that ticket?"
You want someone who thinks about prevention, not just response. A good answer involves product feedback, better onboarding, FAQ improvements, or automation — not just "I'd answer it faster."
"Tell me about a time you said no to a customer and it went well."
You want someone who can set boundaries without being rude. This is critical in support — customers ask for things you can't or shouldn't do, and the response matters.
The First 30 Days
Week 1: Shadow your current support setup. Read 100 tickets. Understand the product, the customers, and the common patterns.
Week 2: Start handling tickets with supervision. You review their responses before they send. Feedback daily.
Week 3: Handle tickets independently. You spot-check instead of reviewing everything. They start suggesting improvements to templates and processes.
Week 4: Fully independent. They own the support queue. You get weekly reports on volume, automation rate, and common issues.
By day 30, you should be spending less than 1 hour/week on support. That's the goal of the hire — buying back your time for the work only you can do.
The Cost vs Automation Comparison
The automation + hire combination costs slightly more than either alone but handles the most volume with the best quality. Automation takes care of the routine. The hire focuses on the work that matters.
Most teams reach this combination around 500-1,000 messages/month. Below 500, automation alone usually works. Above 1,000, you probably need both.