The Second-in-Command: How to Hire and Develop a GM Who Actually Runs the Business

Most founders wait too long to hire a general manager. They tell themselves the business is not ready, the margins are not there yet, or nobody could run it the way they do. Then, three years later, they are still answering every question personally, still the only one who can approve a purchase order, still unable to take a real vacation, and they wonder why nothing changed.

The truth is that a strong second-in-command is not a luxury you earn after the business is fixed. Hiring and developing one is often the thing that fixes the business. But most founders get the hire wrong, because they either hire too late, hire the wrong profile, or hire the right person and then refuse to actually hand over the authority that makes the role work.

You Do Not Need a Clone of Yourself

The single biggest mistake founders make when hiring a GM is looking for someone who thinks exactly like they do. That instinct feels safe, but it produces a hire who is either a weaker version of you, competing with your instincts instead of complementing them, or someone who defers to you constantly because they were selected for similarity, not for independent judgment.

What you actually need is someone whose strengths cover your gaps. If you are the visionary who is weak on execution discipline, hire an operator who lives for checklists and follow-through. If you are naturally process-oriented but slow to make people decisions, hire someone with strong instincts on hiring, firing, and team dynamics. The goal is not agreement. It is coverage.

Define the Role Before You Post It

Do not write a job description that says "help run the business." That is not a role, it is a wish. Before you post anything, write down the specific decisions this person will own outright, without checking with you: hiring and firing frontline staff, vendor negotiations under a set dollar threshold, day-to-day scheduling and resourcing, customer escalations that do not involve legal or reputational risk, and operational spend within an approved budget.

Then write down what stays with you, at least initially: major capital decisions, new lines of business, anything touching equity or partnership structure, and relationships with your two or three most important clients or partners. A GM role without clear decision rights is not a delegation, it is a job title with no authority attached, and the person in it will either quietly become a glorified assistant or burn out trying to guess what you actually want.

Hire for Judgment, Not Résumé

Credentials tell you what someone has done. They tell you almost nothing about how someone decides. In the interview process, spend less time on their résumé and more time on scenario-based questions drawn from your actual business: a vendor missed a deadline that affects a client delivery, what do they do in the first hour? A team member is underperforming but well liked, how do they handle the conversation? A number is trending the wrong direction and there is no obvious cause, what is their diagnostic process?

Listen for how they reason, not just what conclusion they reach. A GM candidate who walks you through a clear decision framework, even one you would not have used yourself, is a better bet than one who happens to land on the answer you wanted without being able to explain why.

Give Real Authority, Not Symbolic Authority

The hardest part of this hire is not finding the person. It is what you do after they start. Founders routinely undercut their own GM hire by continuing to answer questions that should now be routed to the new leader, by second-guessing decisions in front of the team, or by staying copied on every email so people default back to seeking your approval out of habit.

If you want the hire to work, you have to actively redirect. When a team member comes to you with something that is now the GM's decision, the answer is "that is a call for [name] now," said consistently, every time, until the habit breaks. This will feel uncomfortable for the first month. It is supposed to. That discomfort is the actual transfer of authority happening in real time.

Build the 90-Day Onboarding Around Decisions, Not Tasks

A GM's onboarding should not look like a typical new hire's. Instead of a checklist of systems to learn, structure the first ninety days around a graduated handoff of decision-making. In the first thirty days, they observe and shadow every major decision category, understanding the business's rhythms before touching anything.

In the next thirty days, they make recommendations on real decisions and you decide together, so you can calibrate their judgment against yours and catch gaps before they become expensive mistakes. In the final thirty days, they make the calls and inform you afterward within the categories you defined earlier. By day ninety, if the handoff has worked, you should be hearing about most operational decisions after they happened, not before.

Know the Signs It Is Working

A second-in-command hire is working when the business runs smoothly during a week you are unreachable, when your team starts routing decisions to your GM by default rather than waiting for you, and when you find yourself with time to think about strategy instead of firefighting operations. It is not working if you are still fielding the same volume of questions six months in, if your GM is asking permission for things that were explicitly in their decision rights, or if you are quietly redoing their decisions without telling them.

The point of this hire was never to have someone who executes your instructions faster. It was to build a business that can run and make good decisions when you are not in the room. Get that right, and you have taken the single biggest step toward a business that does not depend on you to survive.