A coaching engagement becomes productive when everyone understands what the coach is being asked to do, who the coach is working with, and how information will move. Without a clear scope, coaching can become too private to affect the company, too broad to manage, or too ambiguous to maintain trust. Founders often underestimate this step because they are used to informal problem-solving. They find someone smart, start talking, and expect value to emerge. Sometimes it does. But in a scaling company, the scope itself is part of the intervention.
Defining scope does not mean making the engagement rigid. The best coaching relationships evolve as the coach learns more about the founder, the team, and the organization. But the starting agreement matters. It tells the founder what to bring to the work. It tells executives whether they are participants, observers, or sources of feedback. It tells employees whether the coach is a safe listener, a leadership advisor, or an evaluator. Most importantly, it prevents the coach from becoming a vague presence with unclear authority.
5.1 The Founder-Only Scope
Founder-only scope: a coaching engagement in which the coach works primarily with the founder or CEO, usually through recurring one-on-one sessions. This is the simplest and often the safest place to begin. The founder gets a confidential space to think through pressure, difficult decisions, interpersonal concerns, leadership habits, and the transition from direct operator to organizational leader.
Founder-only coaching is useful when the founder knows they are part of the pattern. They may be struggling to delegate, reacting too sharply to bad news, becoming the bottleneck for decisions, avoiding hard conversations, or confusing urgency with constant intervention. They may also need support processing the emotional load of scale: board pressure, cash concerns, senior hiring mistakes, cofounder tension, or the fear that the company is becoming something they no longer understand.
The value of this scope is depth and discretion. The founder does not have to edit themselves for the executive team. They can say the unsaid, test an uncomfortable hypothesis, or admit uncertainty without immediately creating organizational consequences. A strong coach helps the founder slow down, examine their assumptions, and choose more effective actions. The work often moves between live situations and recurring patterns: a difficult executive conversation this week, a long-standing tendency to rescue teams next week, a habit of changing direction after customer calls the week after.
A founder-only scope should still be connected to observable behavior. Coaching that remains only reflective can become satisfying but low-impact. The founder may feel understood, but the company sees little change. The coach and founder should identify a small number of behaviors or leadership outcomes to work on, such as clearer delegation, calmer response to risk, fewer decision reversals, better one-on-ones with direct reports, or more explicit communication of priorities.
The limitation is information quality. The coach is largely dependent on the founder’s description of events. Even honest founders see through their own lens. They may describe a meeting as passive without noticing how quickly they shut down debate. They may describe an executive as weak without recognizing that authority has never been truly given. They may describe the team as unclear without seeing that their own messages have changed several times. A good coach will challenge the founder’s interpretation, but without broader input, the coach is still working with partial data.
Founder-only coaching works best when the founder is willing to bring real material. Sanitized updates do not create change. The founder should bring moments where they felt triggered, avoided, confused, proud, disappointed, or uncertain. They should be willing to examine both what happened and how they contributed to it. The coach should help convert insight into practice: what will the founder say differently, decide differently, stop doing, start doing, or repair?
A practical founder-only scope might include a weekly or biweekly session, limited availability for urgent situations, and a review every two or three months. The review should ask whether the work is changing anything visible. Are direct reports getting clearer direction? Is the founder escalating less? Are hard conversations happening earlier? Is the founder reacting in ways that create more candor rather than less?
5.2 The Cofounder or Founding-Team Scope
Cofounder scope: a coaching engagement focused on the relationship, roles, decision rights, communication patterns, and unresolved tensions among founders. This scope is often necessary when the company’s leadership issues cannot be separated from founder dynamics. Cofounder relationships carry more history than ordinary executive relationships. They include shared sacrifice, equity, identity, loyalty, status, and sometimes years of unspoken resentment.
In the earliest stage, cofounders can often operate through trust, speed, and informal agreement. One person handles the product because they naturally do. Another handles customers because they are good at it. A third handles operations because someone has to. As the company scales, informal arrangements become insufficient. The company needs clarity on who owns what, who decides what, how disagreements are resolved, and how founders show alignment to the rest of the organization.
Cofounder coaching becomes important when there are signs of misalignment. Employees receive different messages from different founders. Decisions are reopened after one founder privately objects. One founder feels overburdened while another feels excluded. A founder who once had broad authority now struggles to operate beneath a more formal executive structure. A technical founder feels the company is becoming too commercial. A commercial founder feels the technical organization is moving too slowly. These tensions may be understandable, but if they are not named directly, the company absorbs them.
Founding-team scope: a broader version of cofounder coaching that may include early executives or long-tenured leaders who are not formal founders but carry founder-like influence. In many scaling companies, the founding team includes people who joined early, built core systems, or embody the original culture. They may not have founder equity or title, but employees see them as keepers of the company’s story. Their alignment matters.
The coach’s job in this scope is not to force artificial agreement. It is to create a setting where founders can say what has become hard to say and then convert that honesty into working agreements. The work may include clarifying roles, naming decision domains, identifying old wounds, negotiating communication norms, and deciding what the organization needs to hear from the founders as a group.
This scope requires careful confidentiality. If the coach meets individually with each founder and also facilitates joint sessions, everyone must understand how private information will be handled. A useful rule is that individual sessions may be confidential, but material that affects the joint work should eventually be brought into the room in an agreed way. The coach should not become the holder of secrets that prevent direct conversation. Nor should the coach become a messenger between founders who are avoiding one another.
Cofounder work often includes a mix of emotional and operational topics. The emotional topics may involve trust, respect, disappointment, recognition, or fear of losing influence. The operational topics may involve titles, reporting lines, budget authority, board communication, product direction, hiring decisions, or public representation of the company. Treating the work as only emotional can make it feel therapeutic and disconnected from the business. Treating it as only operational can miss the history that makes the same decisions so charged.
A strong cofounder scope should end in explicit agreements. Who owns which decisions? Which decisions require founder consensus? What happens when founders disagree? How will founders avoid triangulating through executives? How will they communicate changes in roles to the company? What behaviors will signal unity without suppressing healthy differences? The coach helps the founders move from implicit expectations to explicit commitments.
5.3 The Executive-Team Scope
Executive-team scope: a coaching engagement focused on the senior leadership team’s ability to operate as an integrated enterprise leadership body rather than a collection of functional heads. This scope is appropriate when the founder’s effectiveness depends on the team becoming more aligned, direct, accountable, and capable of making decisions without constant founder arbitration.
Many executive teams in scaling companies are not really teams at first. They are a group of leaders reporting to the founder. Each person runs a function, attends leadership meetings, and shares updates. But they may not yet share responsibility for the whole company. They may avoid challenging one another. They may escalate cross-functional tradeoffs to the founder. They may leave meetings with different interpretations of the same decision. They may communicate to their teams in ways that protect their own function rather than reinforce enterprise priorities.
An executive-team scope can include individual interviews, meeting observation, team sessions, offsites, operating-rhythm design, and follow-up coaching. The coach may begin by speaking privately with each executive to understand how the team actually works. Then the coach may share themes, facilitate discussion, and help the team build new norms. The best work is not a one-time offsite where everyone feels better for two days. It is a change in how the team meets, decides, disagrees, commits, and follows through.
The founder’s role is central. If the founder treats team coaching as something the executives need while exempting themselves, the engagement will fail. The leadership team watches whether the founder is willing to hear feedback, change meeting behavior, delegate real authority, and stop reopening decisions casually. Team coaching often reveals that executives are adapting to the founder more than leading with one another. That does not mean the founder is the only issue. It means the founder is part of the system being coached.
A clear executive-team scope should define what the team is trying to improve. Vague goals such as “better alignment” or “more trust” are not enough. Better goals are observable: the team makes cross-functional decisions in the room; executives challenge one another directly; decision owners are clear; priorities are communicated consistently; escalations decrease; leadership meetings shift from status reporting to tradeoff resolution; commitments are tracked and revisited.
The team may also need a simple charter. This does not have to be a long document. It can define the team’s purpose, the decisions it owns, the behaviors members expect from one another, and the commitments that must be upheld outside the room. A coach can help write the charter, but the team must own it. Otherwise, it becomes another artifact that people admire and ignore.
Executive-team coaching also needs boundaries around performance management. The coach may identify patterns, help executives improve, and provide feedback themes. But the coach should not become a secret evaluator whose private impressions determine someone’s future. If the founder has serious concerns about an executive’s performance, those concerns should be handled directly through leadership, HR, or board processes as appropriate. Coaching can support difficult feedback, but it should not replace managerial responsibility.
The scope should also address cadence. Some teams need monthly facilitated sessions, supported by founder coaching and individual executive check-ins. Others need an intensive reset followed by quarterly follow-ups. In moments of rapid change, such as reorganization, executive turnover, or post-funding scale-up, the cadence may be more frequent. Whatever the rhythm, the work should connect to real business issues. Team coaching is most powerful when the team practices new behavior on actual decisions, not hypothetical exercises.
5.4 The Organization-Sensing Scope: Interviews, Feedback, and Pattern Recognition
Organization-sensing scope: a coaching engagement in which the coach gathers structured input from selected people across the company to identify themes, patterns, and gaps that may not reach the founder through normal channels. This scope is especially valuable when the founder suspects filtered information, low candor, cultural drift, morale issues, or recurring cross-functional friction.
Organization sensing is not a gossip collection. It is not an anonymous complaint box. It is not a substitute for employee engagement surveys, HR investigations, or performance reviews. Done well, it is a disciplined way to hear how the leadership system is experienced by people close enough to see its effects. The coach listens for patterns that matter: confusion about priorities, fear of raising bad news, inconsistent executive messages, unclear decision rights, founder behaviors that create unintended consequences, and places where trust is weakening.
The scope should define who will be interviewed and why. In some cases, the coach speaks only with the founder’s direct reports. In others, the coach includes key managers, high-potential leaders, long-tenured employees, or people at cross-functional pressure points. The list should be small enough to manage and broad enough to reveal patterns. The founder should not handpick only loyalists or only critics. The purpose is not validation; it is accurate sensing.
Confidentiality must be explained before interviews begin. Participants should know what will and will not be shared. A coach can promise not to attribute comments by name without permission, but should not promise absolute secrecy in cases involving legal, ethical, safety, or serious misconduct concerns. The coach should report themes, examples, and implications in a way that protects candor while giving the founder enough specificity to act.
A typical interview might explore several questions: What is clearest and least clear about the company’s direction? Where do decisions slow down? What topics are hard to raise with the founder or executive team? Where does cross-functional work break down? What founder behaviors help the company? What founder behaviors create confusion or fear? What would improve trust, speed, or accountability?
The coach’s skill is pattern recognition. One person’s feedback may reflect a personal frustration. Several independent comments pointing to the same issue deserve attention. If multiple leaders say priorities shift after every customer conversation, that is a pattern. If managers say bad news is softened before it reaches the founder, that is a pattern. If executives say decisions are made in meetings but reopened later through side channels, that is a pattern.
Organization sensing should be framed as a snapshot, not surveillance. The coach is not permanently roaming the company to monitor people. The purpose is to help leadership see patterns that are difficult to see from the top, then decide what to do about them.
The founder must be ready to receive the themes without turning the process into a search for who said what. If people believe candor will lead to exposure or retaliation, future sensing will become useless. The coach should help the founder stay focused on learning, not defending. Some feedback will be unfair or incomplete. That is normal. The question is not whether every comment is perfectly accurate. The question is what the founder needs to understand about how the organization is adapting to leadership.
Organization sensing should lead to visible action. If people are asked for candid input and nothing changes, trust declines. Action does not require addressing every comment. It does require closing the loop. The founder or leadership team can share themes at an appropriate level, name what will be addressed, clarify what will not change, and demonstrate behavior change where needed. The coach can help prepare that communication so it is honest without overexposing confidential input.
The four scopes described in this chapter are not mutually exclusive. A founder may begin with founder-only coaching, add cofounder sessions, expand to executive-team work, and use organization sensing to understand how leadership behavior is landing. The scope should match the problem and evolve with the work. Clear scope protects trust, focuses effort, and gives the coaching engagement a better chance of changing not only how the founder thinks, but how the company actually operates.
