You're hiring senior employees and expecting mini-founders

Two people across a kitchen table mid-conversation, one gesturing while talking, the other listening with a cup in hand
TL;DR

Founders at the ten-to-fifty-staff stage often hire senior people expecting mini-founder behaviour while briefing the role as a senior-employee position. The candidate performs the role they applied for; the founder is privately disappointed; neither names the gap. The fix is the explicit pre-offer conversation about which kind of role this actually is, and the founder's own honest answer to whether they want a mini-founder or a competent function lead.

Key takeaways

- Founders at the ten-to-fifty-staff stage carry four unspoken expectations of senior hires: ownership of firm-level outcomes, adaptability over experience, emotional resilience under chaos, and mission belief when the data is ambiguous. None of them goes in the job description. - Both sides have an incentive to skip the conversation. The founder thinks it sounds unreasonable written down. The candidate doesn't know what they don't know about founder-mode work. The mismatch shows up six months later as quiet disappointment on both sides. - The fix is a pre-offer conversation in plain language: "in this role I expect you to behave more like a co-founder of your function than a senior leader at a larger firm." Said cleanly, the cost is nothing. The benefit is mutual selection. - The honesty test for the founder runs in three questions about ownership, deference, and presence in difficult conversations. Most founders find they want different answers for different functions. A Head of Sales might need full mini-founder mode. A Head of Finance might be fine as a senior professional.

Twenty-five-person firm, three rounds of growth in eighteen months, hired a Head of Operations with twenty years’ experience from a much larger company. On paper a great hire. Six months in, the founder was telling people privately that the hire wasn’t working out. The hire was telling people privately that the founder seemed impossible to please.

When I sat with both of them, the disconnect was clean. The founder wanted someone who’d wake up worrying about cash, hiring decisions, and which clients to fire, the same way the founder did. The hire had taken on a senior operations role at a high-growth services firm and was performing it competently. Different jobs, same title.

What expectations are founders carrying without saying?

Founders at the ten-to-fifty-staff stage carry four expectations of senior hires that almost never appear in the job description. Ownership of the firm’s outcomes, not just the function’s. Adaptability over experience. Emotional resilience under chaos. Belief in the mission when the data is ambiguous. Each is a real expectation that founders feel viscerally. None of them ends up in the offer letter or the first conversation.

Ownership is the largest of the four. The founder wants the senior hire to feel personal responsibility for the firm itself, across revenue, runway, and culture. They want the same intuition for what matters and the same urgency for what’s slipping. They don’t say any of this in the interview because, said out loud, it sounds like they’re asking for unreasonable commitment from a senior employee.

Adaptability over experience is the second. The founder values the senior hire’s twenty years of experience and also wants them to bin most of the playbooks that experience produced when speed matters. The corporate playbook says run a six-week consultation before changing the org structure. The founder needs the change in two weeks. The hire defaults to the playbook. The founder reads it as slowness. The hire reads the impatience as immaturity.

Emotional resilience is the third. Founders absorb a lot of weight: angry clients, cash crunches, departures, internal fights. They expect senior hires to absorb their share of the weight. Most senior hires from larger firms have never run that kind of weight, and read escalating as what good operators do.

Mission belief is the fourth. The founder wants the senior hire to back the firm’s strategy when the data is ambiguous, the way the founder does. The senior hire treats ambiguity as a signal to slow down and gather more. Both are reasonable. They’re just different jobs.

Why doesn’t anybody say it out loud?

The reason the conversation doesn’t happen is that both sides have an incentive to skip it. The founder doesn’t say the expectations explicitly because, written down, they sound unreasonable. They emerged organically from the founder’s experience and feel like “what good looks like”. The candidate doesn’t ask because the language used in the interview (“ownership”, “scrappy”, “we move fast”) sounds reasonable from the outside without meaning what the founder means.

On the founder’s side, saying it out loud feels like it would deter half the candidate pool. That’s actually the point. The half who would be deterred are the ones who would resent the role inside three months. The half who lean in are the ones the role is built for. The selection function works correctly when the expectations are visible.

On the candidate’s side, the silence is partly courtesy and partly inexperience. The candidate hasn’t experienced founder-mode work and doesn’t know what they don’t know. The offer is attractive. The founder is impressive. They don’t want to look like they’re hesitating, so they accept the language at face value and assume that “we move fast” means whatever they’re used to it meaning.

What both sides miss is that this is a translation problem with predictable consequences. The founder will be quietly frustrated in three months. The hire will be quietly working harder on the wrong things. Neither will know why the relationship has gone cool. Most expensive hiring mistakes in services firms in the ten-to-fifty-staff range come from this gap, not from candidate quality.

What conversation actually fixes it?

The conversation that fixes the misalignment happens before the offer, in plain language. The honest version sounds something like this: in this role I expect you to behave more like a co-founder of your function than a senior leader at a larger firm. That means feeling personal responsibility for the firm’s growth across the whole picture. It means moving fast on imperfect information when you have to. It means absorbing emotional weight where it lands.

The next sentence is the one that does the work. “Some people thrive in this kind of role and some find it exhausting. Both responses are reasonable. I’d rather we both find out before you sign than three months in.” Said cleanly, the cost is nothing. The benefit is mutual selection.

The conversation also has to happen with the founder’s own clarity in place. Most founders haven’t sat down and named which of the four expectations they actually carry, in what intensity, for which roles. A Head of Operations role might need full mini-founder mode. A Head of Marketing role at the same firm might be fine as a competent function lead. Naming the expectations role by role is the prerequisite.

After hire, the unspoken expectations have to become spoken expectations within thirty days, in writing, jointly. What does ownership look like in this role specifically. What kinds of decisions do you make alone. What comes to me. Most senior hires are entirely capable of meeting the bar once they know where the bar is.

Should every senior hire be a mini-founder?

The honest answer is no. Some founders genuinely want a competent professional running a function, with the founder still holding the strategic weight. That’s a defensible model. The right question is which kind of hire fits this specific role at this specific stage. Most founders haven’t asked themselves that question. They brief the recruiter for a senior employee and inwardly expect a mini-founder, and the gap shows up six months in.

The honesty test runs in three questions. Do I want this person to feel personal responsibility for the firm’s outcomes beyond their function, or am I fine with someone who optimises their function within the strategy I set? Am I willing to spend the time to back them when they make calls I disagree with, or do I want them to defer to me when our judgement diverges? Do I want them in the room for the difficult founder-level conversations, or do I want them running their function while I run the firm?

If the answers are all “mini-founder”, the next hire needs the explicit pre-offer conversation. If the answers are all “senior employee”, the brief and the role description should reflect that, with no implicit mini-founder expectation contaminating the early relationship. If the answers are mixed, the role itself probably needs splitting or sequencing differently.

The pattern that fails most often is the founder who answers “mini-founder” privately and “senior employee” in the brief. The candidate who arrives is well-suited to the brief and ill-suited to the inner expectation.

Most founders, asked these three questions in good faith, find they want different answers for different functions. A Head of Sales might need to be a mini-founder. A Head of Finance might be fine as a senior professional. Both can be honest answers. The work is doing the answering before the brief goes out.

The Head of Ops case I started with had a happy ending. Once both parties named what each had expected, they renegotiated the role into something closer to what the founder actually wanted. Six months later, the hire was operating in mini-founder mode and visibly enjoying it. The relationship had been recoverable. Most aren’t, by the time the disappointment is six months in. The earlier the conversation, the wider the recoverable zone.

If you’re about to brief a recruiter for a senior hire, book a conversation.

Sources

  • Coffeespace, "What startup founders expect from early hires but don't say" (coffeespace.com/blog-post/what-startup-founders-expect-from-early-hires-but-dont-say), the four unspoken expectations framework, mini-founder framing, ownership and emotional-resilience quotes.
  • Fortune, Peter Duris (Kickresume CEO), competence hangover framing for experienced corporate hires in founder mode. Source.
  • McKinsey & Company (2025). The State of AI Global Survey. 88 per cent of organisations now use AI in at least one function but only 39 per cent report enterprise-level EBIT impact. Source.
  • Boston Consulting Group (2025). Are You Generating Value from AI, The Widening Gap. Five per cent of future-built firms achieve five times the revenue gains and three times the cost reductions of peers. Source.
  • Standish Group, CHAOS Report (2020). 31 per cent of IT projects succeed on contemporary definitions; 50 per cent are challenged; 19 per cent fail. Source.
  • ICAEW. Business Performance Management, technical guidance. UK SME-relevant reference on KPI selection and performance dashboards. Source.

Frequently asked questions

Why does my senior hire seem disengaged six months in?

The most common cause is expectation misalignment. You hired someone expecting mini-founder behaviour (ownership of firm outcomes, urgency on cash, willingness to absorb emotional weight) while briefing the role as a senior-employee position. The candidate is competently performing the role they applied for. Both sides feel let down without naming why.

What are the four unspoken expectations founders carry?

Ownership of firm-level outcomes beyond the function. Adaptability over experience, especially when speed matters. Emotional resilience under chaos rather than escalation. Mission belief when the data is ambiguous. Each is a real expectation that emerged from the founder's own experience and almost never makes it into the offer.

What's the conversation that fixes this before the offer?

A direct one. 'In this role I expect you to behave more like a co-founder of your function than a senior leader at a larger firm. Some people thrive in that and some find it exhausting. Both responses are reasonable. I'd rather we both find out before you sign than three months in.' Said cleanly, the cost is nothing.

What if I genuinely don't want a mini-founder?

That's a perfectly defensible model. Brief the recruiter accordingly and run the role as a senior-employee role with the founder holding strategic weight. The expensive failure mode is wanting a mini-founder privately while briefing the role as a senior employee, then being disappointed when the candidate matches the brief.

This post is general information and education only, not legal, regulatory, financial, or other professional advice. Regulations evolve, fee benchmarks shift, and every situation is different, so please take qualified professional advice before acting on anything you read here. See the Terms of Use for the full position.

Ready to talk it through?

Book a free 30 minute conversation. No pitch, no pressure, just a useful chat about where AI fits in your business.

Book a conversation

Related reading

If any of this sounds familiar, let's talk.

The next step is a conversation. No pitch, no pressure. Just an honest discussion about where you are and whether I can help.

Book a conversation