Why a Founder's Job Description Has to Change Every Year

The job that closed your first 10 customers isn't the job that wins the next 100. Selling every deal yourself, writing code beside the engineers, answering support tickets at 11pm: that work built the company. It won't scale it. Keep doing the year-one job at year three, and the company runs at year-one capacity, which by year three is far below what it needs.

The transitions are well mapped and the resistance to them is well documented. Founders love the work that built the company, and that work is operational: selling, building, answering. The work that scales the company is structural: hiring, prioritizing, deciding what not to do, pulling yourself out of the paths the team has learned to route through you. Structural work pays off slowly. Operational work feels productive every single day, even once it's become the bottleneck.

The year-one founder closes deals. The year-three founder hires the head of sales who closes deals. The year-five founder sets the strategy that decides which deals the head of sales is even allowed to chase. Each shift is real, and each one asks the founder to drop the old identity. Most drop it halfway, and you get a company run on hybrid leadership that fits no stage cleanly.

Watch how it fails in practice. At year two the founder has hired a head of sales but still fields procurement questions directly, because the relationship is personal and the customer prefers the founder. The head of sales now operates at half strength, undermined from above. Ask the founder about it and the answer is "I'm helping." It isn't helping. It's the founder refusing to let go of the previous job. This is the same instinct behind delegation that's dumping in disguise, run in reverse.

It repeats across every function. The year-three CTO can't grow while the founder is still in the engineering channels calling architecture decisions. The VP of Marketing can't run marketing while the founder personally approves every campaign. Each function ends up capped at the founder's bandwidth instead of the leader's, so the whole company runs at the founder's bandwidth rather than the sum of the team's. The director who can't delegate is usually a founder who never modeled it.

The discipline that corrects this is the annual founder job description. Every January, write two pages on what your job is for the year. Make it specific. Something like: I'll keep the deals above $500K in ARR on my desk and stay out of anything smaller. I'll spend two hours a week with the head of sales and zero hours in the sales Slack channel. I won't approve marketing campaigns; the CMO will. I'll hire a head of operations by Q2 to take over the operating reviews I run today.

Write it, sign it, share it with the leadership team. Then give the team permission to push back when you break it. "You said you'd stay out of marketing approvals. You're in the marketing approvals. Are we updating the job description, or are you reverting?"

It's uncomfortable because you have to stop doing work that feels productive, and the work you're dropping is usually work you're good at. The work you're adding is work you're worse at: strategic bets, hiring calls, decisions with long feedback loops and a lot of ambiguity.

Founders who make the transitions cleanly build companies that scale. Founders who don't build companies that plateau at the bandwidth of their old job. The plateau almost always gets misdiagnosed as a product problem, a marketing problem, a market problem. Most of the time it's a founder-bandwidth problem the founder has chosen not to solve.

The tells that the transition hasn't happened are consistent. Your calendar still holds operational work the team should own. Your DMs fill with decisions the team routes to you because you never made clear the decision belongs elsewhere. Your anxiety clusters in domains you shouldn't be operating in anymore. If you've read when the CEO should stop hiring, it's the same signal from a different angle.

The tells that it has happened are equally consistent. You're bored on most weekdays, because strategic work comes in discrete chunks instead of a constant stream of decisions. The team stops asking you questions the function should answer. Your calendar has long unstructured blocks for thinking, which feel wrong for a quarter and productive after.

Before your next January, ask:

• What does the company need from you, structurally, that nobody else can do?
• What are you doing now that someone else could do, given the right authority?
• Which of last year's job-description items are you proud you delegated, and which are you embarrassed to still own?
• Who on the leadership team will tell you, to your face, when you break the new job description?

Answer those and most founders find they're still doing year-two work in year four. Writing the new job description takes an afternoon. Acting like it's binding takes the whole year, and that's the part that separates the founders whose companies outgrow them from the founders whose companies stop where they do.