Your first hire isn't another you. It's whoever's been picking up what you keep dropping.
Most solo designers frame the first hire as a capacity decision. They're at capacity, they need help, they bring someone in. That part is right. But capacity is the presenting symptom, not the problem.
The problem is continuity.
When everything the studio knows lives in one person's head - every client preference, vendor relationship, open thread, pending decision - hiring a second person doesn't scale the knowledge. It scales the exposure. The new hire needs context they don't have. The founder stops doing work to provide it. That's not leverage. That's overhead.
Here's what that looks like in practice. The hire starts. The first two weeks are rough but expected. By week three, the founder realizes most of what they're doing is explaining things that should already be written down somewhere. Context that exists in their own head but nowhere a second person can access it.
That's not a staffing problem. That's an infrastructure problem the hire just made visible.
If you're thinking about your first hire, the real question isn't who. It's: what will this person have access to on day one? If the answer is mostly you - meaning they need to ask for everything - you haven't gained capacity. You've added a communication task.
The studio's knowledge needs to live somewhere that isn't the founder. Not a long onboarding doc written the week before the hire and already out of date. The actual record: what's active, what was decided, what's in motion, and why.
Archen builds that record from the communications already happening. The new hire gets context that was captured as the work was done, not assembled for their first morning.
Your first hire works best when the studio is ready to be understood by someone who isn't you.
If your next hire started tomorrow, what would they have access to that isn't you?
