> Source: https://brendanlevin.com/insights/how-to-hire-someone-to-run-your-business/ > Most founders hire a number two too early, into a business with no operating structure to inherit. This page explains what has to exist before that hire works, and what fails when it does not. For founders, owners, and operators # How Do I Hire Someone to Run My Business Day to Day? By Brendan Levin. 20+ years scaling businesses, from teams of 8 to 600 and budgets from startup to $100m. You can hire someone to run day-to-day operations only after the business has a documented operating structure they can inherit. That means written direction, defined decision rights, and a standing operating rhythm. **Hiring before those exist relocates the dependency onto the new hire** rather than removing it. Start with [structure, then staffing](/insights/should-i-hire-a-coo-or-fix-my-operating-structure-first/). Key takeaways - A second-in-command needs an operating system to inherit, not a blank canvas to build from scratch. - Without written decision rights, every real call still escalates to the founder regardless of the hire's title. - The honest test: take a full week away with no contact and watch what stalls. That is what still runs on you. - Most founder-led businesses under about fifty people have a structure gap, not a staffing gap. ## Why this hire fails more often than it should The pattern is consistent. A founder is exhausted by being the person everything routes through. They hire a smart, senior operator. Six months later, that person is overwhelmed, making calls without context, and the founder is pulled back in to fix things. Or the hire leaves. And every call routes straight back to the founder again. The hire was not the problem. The business was not ready for the hire. There was no documented direction for the operator to execute against, no written decision rights telling them what they could own without asking, and no operating rhythm keeping the team accountable. The new second-in-command had to invent all of that while also running the business. That is not a job. That is three jobs. Hiring a senior operator into a business with no operating structure does not remove the founder dependency. It relocates it onto the new hire at a senior cost. If they leave, the dependency routes straight back to the founder, but now with months lost and a hiring process to repeat. ## What has to exist before the hire works Three things must be documented and working in the business before a second-in-command can succeed. Not in the founder's head. In writing, visible to the team. First, a single direction sentence: the one outcome the whole business is organised around this year, with the two or three numbers that prove it moved. Without this, every priority call is a judgment only the founder can make, because no one else knows what winning looks like. Second, written decision rights with real thresholds. Not vague guidance about who is responsible for what. Actual lines. Something like: any spend under $2,000, the owning person acts and tells the operator after. Any new client commitment outside the current scope, the operator decides and tells the founder after. Any spend or commitment above $10,000, the founder is consulted before the call is made. Without thresholds like these written down, the operator cannot know what they genuinely own, so they hedge and escalate, and the founder is back in every conversation. Third, a standing weekly operating rhythm where the leadership team walks the numbers and surfaces what is stuck. Without a rhythm, the founder is the rhythm, and work stalls every time they stop pushing. ## The decision-rights test you can run this week Pull up the last ten decisions that required your input. For each one, write down the answer to this question: could this have been made by someone else if they had known the direction, had a clear threshold, and trusted that acting was expected of them? If more than six of the ten come back yes, you do not have a staffing problem yet. You have a structure problem. The role of a second-in-command is to run a business that has decision rights built into it, not to guess what the founder would have done. The fuller version of this test is simpler to run and harder to argue with: take a full week away with no contact, no message checking, no quick calls. What stalls is what still runs on you. What keeps moving is what genuinely lives in the business. Most founders who run this test find out that far more stalls than they expected. ## What kind of person actually fits this role The person you are describing, a number two who runs daily operations so you can focus elsewhere, is essentially a COO role. But the title matters less than the conditions. A [fractional COO](/insights/what-does-a-fractional-coo-do/) runs operations on an ongoing retainer and is the right fit if you need someone in the role over time but cannot justify a full-time hire yet. A full-time COO is a permanent operator and the right fit if the business is large enough to warrant the cost and the structure is already there to support them. Neither option works without the structure underneath. A great operator inherits a system and improves it. They do not invent the system while running the business at the same time. If you are not sure which role fits your situation, the more useful first question is whether the gap is structural or staffing. [Most of the time, it is structural.](/insights/should-i-hire-a-coo-or-fix-my-operating-structure-first/) What you need The right fit What breaks it **Someone to run daily operations long-term** Full-time COO No operating structure for them to inherit **Operational leadership without a full-time hire** Fractional COO on retainer Decision rights still live with the founder **The structure itself built and installed** Operating advisor (short engagement) Confusing this with a coaching relationship **Direction, decisions, and rhythm built fast** Operating advisor before any hire Skipping this step and hiring first ## The founder condition most people skip There is a condition for this hire that has nothing to do with the business and everything to do with the founder. The hire only works if you are genuinely willing to stop making the calls you have agreed to hand over. Not in theory. In practice, every day. Most founders intellectually want a second-in-command and emotionally undermine them. They approve decisions the operator should own. They answer direct reports who should be going to the operator. They jump in when something looks like it is going sideways, which removes the operator's authority exactly when it matters most. The operator either gets demoralised and leaves or learns to wait for the founder to decide anyway. Either outcome puts you back where you started. This is not a character flaw. It is a predictable result of running a business where every call has routed through you for years. The fix is structural: the written decision rights create a visible line so you can hold yourself to it, and so your team can hold you to it too. [Scaling past yourself requires the structure to exist before the hire arrives.](/insights/how-to-scale-past-the-founder/) ## The sequence that actually works Structure first, then staffing. Document the direction. Write the decision rights with real thresholds. Install the operating rhythm. Run the week-away test. Then assess what you genuinely still need from a hire. Often the answer changes once the structure is in place, because several things that looked like they needed a senior person turn out to need a clear owner and a threshold, which costs nothing. When the structure is there, the hire has something real to inherit. They can read how decisions are made, understand what the business is trying to achieve this year, and run the weekly rhythm without reinventing it. That is the version of this hire that works. That is the number two who actually frees a founder. If you want to understand what [a founder operating system](/insights/what-is-a-founder-operating-system/) looks like before it is built, that is the right place to start. Before you write a job description, find out exactly what still runs on you: the free Founder Dependency Diagnostic maps it in one read. [Take the free diagnostic](/executive-diagnostic) ## Common questions Can I hire a COO before my business has any documented processes? You can, but the hire is likely to fail or underperform. A COO without documented direction, decision rights, and an operating rhythm has to build all of that while running the business. That is not one job. It is three. The structural gap that made the business depend on you will transfer to the new hire, and if they leave, the dependency routes straight back to you. What is the difference between an operating advisor and a COO? An operating advisor installs the operating structure and hands it back to you in a short, defined engagement. A COO runs the business day to day on an ongoing basis. If the business runs through you because the structure was never built, that is a structure gap an advisor addresses. Once the structure exists, a COO has something real to inherit and run. How do I know if my business is ready for a second-in-command? Run this test: take a full week away with no contact and no message checking. What stalls is what still runs on you. If most things stall, the business is not ready for the hire because the hire will face the same stall. If your direction is documented, decision rights are written with real thresholds, and the operating rhythm runs without you pushing it, the business is ready. What does a good decision-rights threshold actually look like in writing? Concrete thresholds work better than titles. For example: any spend under $2,000, the owning person acts and tells the operator after. Any new scope commitment with an existing client, the operator decides and tells the founder after. Any spend above $10,000 or any new hire decision, the founder is consulted before the call is made. The threshold is a dollar amount or a risk line, not a description of the type of decision. Is a fractional COO the same as hiring someone to run my business? A fractional COO runs day-to-day operations on a part-time, ongoing retainer, which is functionally similar to a full-time second-in-command but at a lower time commitment and cost. The same condition applies: the operating structure needs to exist for them to inherit. Without it, a fractional COO spends most of their time building the structure rather than running the business. What if I hire someone great but they keep coming back to me for decisions? That is a decision-rights problem, not a people problem. If the thresholds are not written down, a capable operator will hedge and escalate because they cannot tell what they genuinely own. Write the thresholds. Define what they can act on without asking. Make it explicit that acting within those thresholds is expected, not just permitted. Then hold the line when they bring you something that sits inside their threshold. Related: [should i hire a coo or fix my operating structure first](/insights/should-i-hire-a-coo-or-fix-my-operating-structure-first/) · [what does a fractional coo do](/insights/what-does-a-fractional-coo-do/) · [what is a founder operating system](/insights/what-is-a-founder-operating-system/) · [how to scale past the founder](/insights/how-to-scale-past-the-founder/) · [how to set decision rights in your business](/insights/how-to-set-decision-rights-in-your-business/) · [operating advisor vs fractional coo vs hiring a coo](/insights/operating-advisor-vs-fractional-coo-vs-hiring-a-coo/) · [more insights](/insights).