When the Symptoms Point at Hiring (and When They Don't)

A practical read on the symptoms founders read as "we need to hire," when that read is right, and when it's the wrong fix dressed in convincing clothing.

If you've already identified founder-dependency in decisions, the next question is not "hire or don't hire." The next question is "are we ready to hire well?"

Sometimes that's the right call. Sometimes it isn't. The point of this week is to give you a way to tell.

If your firm is founder-led, still doing real client delivery, and you're somewhere in the bracket of "I'm seriously considering a senior hire in the next 90 days," this week is for you.

We're going to skip the part where we convince you the bottleneck is real. You already know it is. We're going to start somewhere harder, which is the moment you've decided to act.

Three symptoms founders read as "I need to hire"

Founder-led firms tend to name one of three symptoms that finally pushed them toward a search.

Quick note before we continue: unless we clearly say otherwise, examples here are composites based on recurring founder patterns.

Symptom one: the proposal queue is the founder's calendar. New leads come in, they want to talk to you, you can fit two scoping calls a week, and the math on closing $X of revenue this quarter is "how many proposals can the founder write." The founder reads this as a sales-capacity problem and starts thinking about a senior commercial hire.

Symptom two: a senior person on the team is doing good work but every deliverable still routes through you. Quality is fine, the senior person is capable, but you're still the last set of eyes on every meaningful piece of client work. The founder reads this as a delivery-leadership gap and starts thinking about a Director of Delivery or a Head of Quality.

Symptom three: the inbox volume is a wellness problem. It's not any one decision. It's the cumulative ten-hours-a-week of sign-offs, check-ins, and "got a sec?" messages. The founder reads this as a need for an executive-level operator and starts thinking about a COO or a Director of Operations.

Each of these is a real symptom. None of them is automatically a hire problem. Each one can be a hire problem, or a workflow problem, or a positioning problem, depending on what's actually underneath. The work this week is telling them apart before you commit.

The two questions that separate hire from not-hire

There are a lot of frameworks for "should I hire?" Most of them are too general to act on. The version that holds up, in our framing, is two questions, asked in order.

Question one. Is the work the hire would absorb writable down, today, by you?

Not "could be written." Writable today. If you sat down for two hours this Friday, could you produce the document the hire would operate from? The pricing rules. The quality bar. The decision rights. The escalation triggers. If the answer is yes, the hire has a real surface to land on. If the answer is "well, sort of, but it lives in my head," the hire will inherit you, not the role, and three months in you'll be back to where you started with one more salary on the books.

Question two. Would the firm look meaningfully different if the hire stayed for two years and did exactly what's in that document?

If the answer is yes (specific service line launched, specific revenue band reached, specific founder time freed for specific strategic work), the hire is strategic and the spec, comp, and search bar all need to reflect that. If the answer is "I'd be less busy but the firm would look about the same," it's still potentially a useful hire, but it's an operational one, and it should be scoped and priced like one. Both can be right answers. The mistake is hiring against the second answer at the comp band, comp expectations, and search bar of the first.

If both questions get a clean yes, the hire is the right move and we'll spend Wednesday on what the spec needs to contain. If either gets a no, the next move probably isn't the search. It's two to four weeks of writing things down, which is the other thing this week is about.

What to check before any role goes live

Not theory. Five concrete checks to run between now and Friday before the job description gets posted.

1. The job description test. Write the role in three sentences. Title, top three decisions they own, top three metrics by which you'd judge them at 90 days. If you can't do that in fifteen minutes, the role isn't yet a role. It's a wish.
2. The Friday-afternoon-doc test. Could you sit down this Friday and produce the operating doc the hire would use? Pricing logic, quality bar, decision rights. If yes, you have the surface. If no, the next two weeks of work is the doc, not the search.
3. The peer-network read. Send the role description (one paragraph) to two peers who run firms of comparable size and ask them, what role is this? If they come back with two different answers, the spec is compound, and you're hiring three roles into one salary. Tighten before posting.
4. The 90-day metric. Write the single concrete number you'd look at in 90 days to decide whether the hire is working. Pricing turnaround. Proposals shipped without your sign-off. Deliverables that closed at the senior team rather than your inbox. "How it feels" doesn't count. If you can't name the number, you can't tell whether the hire is sticking.
5. The 10-hours test. Find the 10 hours per week, on the actual calendar, in the first 30 days the hire would be in seat. Block them now. If the hours can't be carved out, the hire's first month becomes the founder being too busy to transfer the thing the hire was brought in to absorb.

If three or more of these come back clean, the role is closer to ready than not, and Wednesday's scorecard is the next gate. If two or more come back unresolved, the next move is the spec, not the search.

What's coming this week

Tomorrow's piece runs the cost math, what it actually costs to hire into the wrong gap, the math founders rarely run when the search feels overdue.

Wednesday we publish the diagnostic itself, eight questions, one page, the readiness check that runs in fifteen minutes before any job description goes live.

Thursday is the role-spec piece, what a written role-spec actually contains before you post the job.

Friday closes with the most expensive hire framing in fractional firms, the "I'll just clone myself" reflex and why it produces capable senior people who can't actually do the job they were hired into.

The point of this week isn't to talk you out of hiring. It's to make sure that when you do, the role you've written is hireable, the firm is ready to receive the person, and the 90-day metric exists before the offer goes out.

Continue the series

This is part 1 of a 5-part series on the Pre-Hire Readiness series. The full arc:

• Monday: When the Symptoms Point at Hiring (and When They Don't) (this post)
• Tuesday: What It Costs to Hire Into the Wrong Gap
• Wednesday: The 8-Question Pre-Hire Readiness Scorecard
• Thursday: What a Written Role-Spec Actually Contains Before You Post the Job
• Friday: Why "I'll Just Clone Myself" Is the Most Expensive Hire Framing in Fractional Firms

Run the diagnostic

Eight questions, fifteen minutes, before any job description goes live.

Content and Accuracy Disclaimer

This article was drafted with AI assistance and reviewed by the Altvina team. We rigorously fact-check our content; if you notice an inaccuracy, please contact us so we can correct it.