The first-hire tax.

Here’s the thing nobody tells you about your first hires. The math you expected: I do 100 units of work today, I hire one person, I now have 200 units of capacity. The math you got: I do 100 units of work today, I hire one person, I now do 80 units of work because I’m spending 20 unlearning how to do everything myself plus onboarding plus 1:1s plus reviewing their work plus a thousand small judgment calls a week. The new person does 60 units. Total output: 140. Less than the two of you should produce. Way less than what you needed to justify the hire to your spouse.

The full picture: This is one operator-type cut of the 5-folder LEGOS system. The framework is the same. The application changes at the moment your business stops being only you.

This is the first-hire tax. It is real, it is universal, and it does not pay itself back automatically. You pay it back by changing how you operate, not by hiring harder or working longer. The fix is structural.

The problem was never that your first hires aren’t pulling their weight. The problem is that you don’t have a frame yet for what work belongs to you versus what work belongs to the team.

Why “doing the work” got harder, not easier, after the hire.

When you were solo, every input came in and went straight to your hands. There was no translation step. You felt the urgency, you did the thing, you moved on. The cycle was tight.

Then you hired. Now every input comes in and your brain runs an extra question: do I do this, or does someone on the team do this? That question is silent. It’s microscopic. It happens dozens of times a day. The cumulative cost is enormous. By Friday you’ll have made about 400 of those micro-allocation calls and you won’t remember a single one, but you’ll feel them.

The folders solve this by making the allocation explicit. A piece of work has a folder. The folder tells you who owns it. The micro-question stops firing.

The 5 folders, with ownership encoded.

The same five folders apply. The shift: every Launch and Guard item gets an explicit owner tag. Yours, theirs, or shared. That tag is what makes the system survive a team.

Launch — owned by you or owned by them.

Every named project with a finish line. The hire for the next role. The customer acquisition test. The product feature. The pricing change. Every Launch gets a single owner. If a Launch has no owner, it has no chance of finishing.

Your Launches (where you are the owner) cap at 3 to 5 once you have a small team. Every Launch you take on personally is one your team isn’t getting from you. The first-hire tax is paid back when you can hand a Launch to someone and they can carry it.

Guard — the heartbeat, mostly theirs.

This is where the first-hire tax actually pays back. Almost every Guard item should be team-owned within the first 90 days of the hire. Customer support response. Standard delivery rhythm. Reporting cadence. Compliance items. The team’s standup. Most of the recurring rhythm.

You retain Guard oversight (you check the rhythm, you intervene when it breaks) but you stop being the owner. Most first-time CEOs make the mistake of treating their first hire like a contractor and never actually handing them Guard ownership. The hire never gets the trust they need to grow into the role. You never get the time back.

Elevate — you alone.

The CEO skills. The leadership reading. The therapy. The marriage. The new craft you need to grow into to lead the company you’re trying to build. This folder belongs entirely to you and cannot be delegated. Most first-time CEOs let Elevate go empty for the first 18 months of having a team and end up burning out exactly when their team finally needs the version of them that’s been growing in Elevate.

Orbit — ideas you keep batting around in 1:1s.

Most ideas a first-time CEO has end up half-floated in a Slack channel, half-explained to a team member who interprets it as a directive, and half-lost. Orbit is the place those ideas go to be safe and held without becoming team chaos. You write them down. You don’t tell the team yet. You revisit quarterly. If an idea survives a quarter, it earns a real Launch with a real brief.

This single discipline (holding ideas in Orbit instead of broadcasting them) is one of the largest gifts you can give your first team.

Storage — the team’s playbook.

Every onboarding doc you’ve written, every playbook, every standard operating procedure, every won deal description, every postmortem. Storage becomes the asset that lets your second hire ramp in 4 weeks instead of 12. The hires you make after this one will be much easier because Storage is now real.

The Sunday Operator Review, in the first-team era.

1. Launch. Each Launch: owner, status, next move. Your Launches: 3 to 5 max. Theirs: as many as the team can carry.
2. Guard. Is the team owning the heartbeat? Is anything you secretly took back from them this week? (You did. You always do.) Hand it back.
3. Elevate. The version of me leading this team in 12 months needs what, this week?
4. Orbit. Anything you’ve been broadcasting that should have stayed in Orbit?
5. Storage. One playbook to write or update this week so the next hire ramps faster.

The brick for tonight.

Open a doc. Five folders. Tag every Launch and every Guard item with an owner: yours, theirs, shared. Be honest. The Guard items where you’re still the owner three months after the hire are the leak. Move ownership.

Pick one Guard item you currently own that you should not. Tomorrow, hand it over. Not “let me explain how I do it” hand it over. Actually hand it over, with the bar slightly lower than yours and the right to mess up the first three rounds. That’s the brick. The brick is the move that costs you 20 minutes and pays back 5 hours a week.

OOPS. Adjust. Continue. You’re not bad at managing. You haven’t given the team folders yet. Once they have folders, they can hold the work. Once they can hold the work, you can build instead of fight.

Common first-time-CEO questions.

My first hire is an EA. Same folders?

Same folders, different distribution. An EA primarily lives in Guard (inbox, calendar, vendor relationships, recurring rhythm). Hand them ownership of Guard items as fast as they can carry them. Your Launch and Elevate folders don’t change. The EA helps protect the time those folders need.

What if my first hire isn’t ready to own Guard?

Then you hired the wrong person, or you hired the right person and you haven’t trained them. Both have fixes. The folder system surfaces which it is fast. If a Guard item should be theirs by month 3 and it’s still yours at month 6, you have a coaching gap, a hiring gap, or a willingness-to-hand-it-over gap. Usually the third.

How do I manage my first 1:1s without them feeling pointless?

Lead with their Launch folder. Each 1:1 is a walk through their Launches and their Guard rhythm. Status, next move, blockers. Twenty minutes max. Once the LEGOS frame is shared, 1:1s stop being open-ended check-ins and start being status reviews on the work that’s been pre-categorized.

Will hiring more people fix this?

No. Hiring more people without the folder system multiplies the tax. With the folder system, the second and third hire are dramatically cheaper because Storage already exists, and you’re not learning how to delegate on every hire.