There's a specific kind of exhaustion that hits a solo founder around $10,000 MRR.
You've proven the model. Customers are paying, they're staying, and a few of them have even referred other customers without being asked. By every objective measure, it's working.
But you're doing customer support at 11 PM, fixing bugs at 2 AM, and running sales calls at 9 AM. You're missing things that used to be easy — responding to emails same-day, thinking clearly about product direction, taking a Saturday off without guilt. The bottleneck is you, and you know it.
You also know you need to hire. And you've been "almost ready to hire" for four months.
This isn't laziness. It's a specific psychological friction that almost nobody talks about honestly. Here's what's actually happening — and how to get through it.
#The Illusion of Faster
The most common rationalization for delay: "It will take me longer to train someone than to just do it myself."
In the micro, this is true. Formatting a weekly newsletter takes you 25 minutes. Training someone to format it exactly the way you like it — with the right image sizing, the correct font hierarchy, the specific tone adjustments you make at the end — takes four hours of documentation, a Loom walkthrough, and two rounds of feedback.
But the math founders run stops at the 4-hour training cost. It doesn't run the other direction.
If you spend 4 hours training someone today, and they do this task for the next 24 months, you've permanently bought back 50 hours of your own time — roughly two full workweeks. The hourly rate on that training investment is extraordinary. And the compounding accelerates: the better they get, the less you review, the more time returns to you.
The error isn't in perceiving that training is expensive. It's in treating training as a cost without calculating the return.
#The 80% Rule Is a Prerequisite
The psychological challenge underneath most hiring delays is perfectionism — the same trait that made the product good enough to have paying customers is the trait that makes you reluctant to let anyone else touch anything.
Here's the rule you have to internalize before you make a first hire, not after: if someone can do a task 80% as well as you, you must delegate it immediately.
Not eventually. Not after they get better. Immediately.
Your customers will not notice the missing 20%. Not on a support ticket, not on a social post, not on a routine monthly report. The 20% gap you're obsessing over is almost always invisible to everyone but you. What is visible to the market is that your product development stalled because you spent 12 hours a week on tasks that a competent generalist could handle.
The perfectionism that serves you in product decisions actively hurts you in delegation decisions. Knowing which mode you're in — and when to switch — is one of the most important skills in scaling.
#The Dopamine Shift (This One Is Real)
This is the transition that blindsides most founders, because it's genuinely uncomfortable and nobody warns you about it in advance.
For the first 12–24 months of your company, your brain's reward system is calibrated to shipping. Writing code, closing a deal, publishing a piece of content, solving a customer problem directly. These activities produce a clear, immediate feedback loop: you do the thing, the thing is done, you feel the satisfaction of completion. Your dopamine is coming from making.
When you hire someone and start managing them, your day looks completely different. You write an SOP. You review their work. You answer their questions. You have a 30-minute weekly check-in. At 5 PM, you look at your screen and feel an unnerving thought: "I didn't actually do anything today."
You did. You maintained the system that builds the product. But your brain hasn't been calibrated to reward that yet.
The founders who get through this transition are the ones who explicitly rewire what counts as a win. When your new hire closes a support ticket without asking you, that's a product you shipped — you built the process that produced the resolution. When they run the weekly newsletter without any input from you, that's output you generated — you built the system that generates it.
Management is making. It just doesn't feel like it until your brain catches up.
#Before You Post the Job: The Two Diagnostics
Diagnostic 1: Can you write the job description from memory in 20 minutes?
If you can't describe exactly what this person will do, what success looks like in 90 days, and what information or access they need to do it — you're not ready to hire. You're ready to think more clearly about what you need.
The inability to write a clear job description is almost always a sign that the role isn't well-defined yet, which means the hire will fail because the person won't know what they're supposed to be doing. Define the role before you recruit for it.
Diagnostic 2: Is this the right bottleneck to solve?
Before you hire your first human, you should have genuinely exhausted the AI automation options for the tasks you're considering hiring for. Customer support can be partially handled by a well-configured Claude workflow. Newsletter formatting can be automated. Research tasks that used to take hours now take minutes with Perplexity and Claude.
The question isn't "am I overwhelmed?" It's "what, specifically, requires a human in the loop that I can't get AI to handle reliably?" That specific thing is what you hire for.
#Who to Hire First
Not a visionary. Not a specialist. Not a mini-you.
Your first hire should be a generalist operator — someone who is organized, execution-oriented, and thrives on the feeling of clearing a checklist. They don't need to be creative. They don't need to set strategy. They need to take a clearly defined scope of work, execute it reliably, and flag you when something outside their parameters comes up.
This person's job in the first 90 days: take all the execution tasks that drain your energy — inbox triage, data entry, basic research, scheduling, formatting — and own them completely. Not "help you with them." Own them. You review the output, not the process.
That's the unlock. Not a new function, not a new capability. Just your energy back — which you redirect to the highest-leverage work only you can do: sales conversations, product direction, and key customer relationships.
#The First 30 Days
The temptation is to throw everything at them at once. Don't.
Pick one category of tasks for the first 30 days. Document it. Record a Loom walkthrough of yourself doing it. Give them access. Have them shadow you once, do it themselves once with you watching, then do it on their own with async feedback for two weeks.
At 30 days, do an honest assessment: not "are they doing it exactly as I would?" but "is the work good enough that my customers and business are not suffering?" If yes, expand their scope. If no, figure out whether the issue is the person, the documentation, or the role definition — in that order.
The founders who have a bad first hire experience almost always made one of three mistakes: hired before the role was defined, delegated tasks without delegating the decision authority to handle them, or applied a perfectionism standard to work that didn't warrant it.
Get those three things right and the first hire becomes one of the most obviously good decisions you've made.
Where should we send it?
You'll also get the weekly briefing.