You just closed a round. Headcount is green. First thing on the list — hire someone to "handle support."

Totally reasonable. Completely normal. Almost always a mistake.

Not because hiring is wrong. Because of what you're actually handing off.

You, the founder, have been doing support for 18 months. In your head, you carry everything. Why customers get confused at step three of onboarding. Which error message is actually a billing bug in disguise. Which type of complaint means the customer is about to leave, and which one just means they're having a bad Tuesday.

None of that is written down anywhere.

So your new hire shows up, eager, ready to go. And you point them at the inbox.

That's it. That's the handoff. An inbox and a vague "you'll figure it out."

Two weeks later, tickets are taking longer to resolve than when you were doing it yourself.

Customers are getting generic answers. The same questions keep coming in and nobody's noticing the pattern. Your new hire is drowning and too afraid to say so.

And you're confused, because you hired someone good.

You did. That's not the problem.

The problem is you handed them chaos and called it a job. No playbook. No escalation path. No definition of what a good answer even looks like. Just an inbox, a password, and a ‘good luck’.

The hire didn't fail. The setup did.

This is the most common mistake I see at seed stage. Not hiring too late. Not hiring the wrong person. Hiring the right person into a system that doesn't exist yet — and then wondering why things got worse.

Before you post that job spec, write down what you know. Even badly. Even in a Google Doc at midnight. Because right now that knowledge lives only in your head, and the moment you step away from the inbox, it walks out the door with you.

Next time: what happens when the inbox never clears — and why throwing more people at it makes it worse.