Contracting, Confidentiality, and Ground Rules

9.1 Defining Who the Client Is: Founder, Cofounders, CEO, Team, or Company

Client: the person, group, or system the coach is primarily responsible for helping. In ordinary business language, the client is often the person who signs the contract or pays the invoice. In coaching, that definition is too narrow. The company may pay, the founder may select the coach, HR may administer the agreement, the board may sponsor the work, and the executive team may participate. Unless the client relationship is made explicit, people will fill the gap with assumptions.

In a founder-only engagement, the founder or CEO is the client. The coach’s primary obligation is to help that leader become more effective, self-aware, and constructive in their impact on the company. The company may pay for the engagement because the work serves the business, but the sessions are not a reporting channel to the company. This distinction matters. If the founder believes every thought might be summarized elsewhere, they will not bring the real material. Founder-only coaching requires enough privacy for honesty.

In a cofounder engagement, the client is not simply whichever founder initiated the search. The client is the cofounder relationship or founding-team system. This means the coach must maintain credibility with each founder and avoid becoming an ally of one founder against another. The initiating founder may have legitimate concerns, but once the engagement becomes joint work, the coach must be clear that they are there to help the founders build a workable relationship, not validate one person’s narrative.

Cofounder-system client: a coaching relationship in which the health, clarity, and effectiveness of the founding relationship is the object of the work. Individual conversations may be confidential, but the purpose is to help the founders speak more directly, make clearer agreements, and reduce the organizational cost of unresolved tension. The coach should not become a private messenger carrying one founder’s frustration to another.

In an executive-team engagement, the client is the leadership team as a collective body. This can be difficult for executives to understand at first, especially if the founder selected the coach. The coach may have a strong relationship with the founder, but the work is not only about helping the founder manage the team. It is about helping the team become more capable of leading the company together. The coach’s loyalty is to the quality of the team’s conversations, decisions, commitments, and accountability.

In some situations, the company is described as the client, especially when the engagement concerns culture, succession, leadership capacity, or broad scaling readiness. But “the company” is an abstract client unless the parties define who represents its interests. Is it the CEO? The board? HR? The executive team? The phrase should be used carefully.

A clear contract should define several roles. Sponsor: the person or body authorizing the engagement, such as the founder, CEO, board chair, or chief people officer. Participant: the person or group receiving coaching, being interviewed, or joining facilitated sessions. Payer: the entity responsible for fees. Decision owner: the person who can change scope, renew, pause, or end the engagement. These roles may overlap, but they should not be assumed.

Ambiguity becomes especially risky when an investor or board member recommends the coach. A board-referred coach may be excellent, but the founder must clarify whether the coach reports to the founder, the board, or both. The safest default is transparency: if the coach will ever speak with the board about the engagement, the founder should know what topics may be discussed and at what level of specificity. Secret back channels damage trust.

Defining the client also helps manage conflicts of interest. If the coach is advising the founder privately while also facilitating a team session, the coach must be clear about how insights from one context may inform another. If HR wants the coach’s view on an executive’s performance, but the coach has promised developmental confidentiality to that executive, the coach must protect the integrity of the role. A coach is useful only when people understand which hat the coach is wearing.

9.2 Confidentiality With the Founder, Direct Reports, Board, and HR

Confidentiality: the agreed rules for what information is protected, what may be shared, with whom, at what level of detail, and under what exceptions. Founders often use the word casually: “Everything is confidential.” That sounds reassuring, but it is incomplete. In a multi-stakeholder coaching engagement, absolute confidentiality is neither practical nor always appropriate. The better standard is specific confidentiality.

The founder needs confidentiality to think clearly. Founders may use coaching sessions to process anxiety, anger, disappointment, uncertainty, or unformed hypotheses. They may be considering whether a senior leader can scale, whether a cofounder role must change, whether the company is moving in the right direction, or whether their own behavior has damaged trust. These thoughts may not be ready to become company messages. The coach should protect the founder’s ability to speak in draft form.

At the same time, coaching confidentiality has limits. A coach should not agree to hide serious legal, ethical, safety, harassment, discrimination, fraud, retaliation, or misconduct concerns. The exact limits should be written and discussed before sensitive work begins. The coach is not a lawyer, and coaching confidentiality is not attorney-client privilege.

Direct reports need a different form of confidentiality. If the coach interviews executives or employees, participants need to know whether their comments will be attributed. Most organization-sensing work depends on non-attribution. The coach may report themes, patterns, examples, and implications, but should not say, “Your chief revenue officer told me this,” unless that person has explicitly agreed. Without non-attribution, interviews become guarded and politically careful.

Non-attribution: a confidentiality standard in which the coach may use input to identify themes but does not link comments to specific individuals without permission, except where agreed exceptions apply. Non-attribution does not mean every comment disappears into a vague summary. It means the coach translates individual input into patterns that leadership can act on without exposing the person who offered the input.

The board requires careful handling. Boards may have a legitimate interest in CEO development, succession risk, leadership-team effectiveness, culture, or governance. But the board should not receive private coaching content unless the engagement is explicitly designed that way. A healthy board update might include the scope of the work, cadence, broad themes, and progress indicators. It should not include private session details, unapproved quotes from executives, or personal material the founder shared in confidence.

HR or the people leader can be an important partner, especially when the engagement touches culture, leadership development, employee relations, or executive-team effectiveness. But HR involvement must be defined. HR may help coordinate interviews, administer contracts, or support follow-up actions. HR should not automatically receive transcripts of coaching themes, private feedback, or the coach’s personal impressions of executives. If HR needs to become involved because a matter requires formal process, the coach should be clear about that transition.

Confidentiality also requires the founder’s discipline. A founder who hears a theme from the coach and immediately tries to identify who said it will damage the entire process. The founder may feel tempted to ask, “Was that sales?” or “Did this come from my COO?” The coach should resist that pull and redirect toward the pattern. The founder’s job is to learn from the information, not investigate the source.

The coach should explain confidentiality in plain language to every participant. People should not need to infer the rules. A simple statement at the start of interviews can prevent confusion: the conversation is confidential and non-attributed; themes may be reported; individual names will not be used without permission; serious legal, ethical, or safety issues may require escalation; and the purpose is to improve the leadership system, not collect complaints for punishment.

9.3 What Can Be Shared, What Cannot Be Shared, and How Themes Are Reported

Once confidentiality is defined, the next question is how learning moves through the engagement. Coaching must protect trust, but it must also create usable insight. If nothing can be shared, the work may become private reflection with limited organizational impact. If too much is shared, candor disappears. The right design allows the coach to bring forward meaningful patterns while protecting individuals from unnecessary exposure.

Shareable information: themes, patterns, observations, process recommendations, agreed commitments, and participant-approved comments that can help the founder or team improve. Protected information: private coaching content, personally sensitive material, unattributed interview comments, untested allegations, and identifying details that participants reasonably expected would remain confidential. The contract should distinguish these categories before feedback is gathered.

Theme reporting is one of the most useful tools in coaching engagements that include interviews or team observation. A theme is not a single complaint. It is a repeated pattern heard across multiple conversations or observed in multiple settings. For example, “Several leaders are unclear on which decisions require founder approval” is a theme. “One executive is frustrated about last Tuesday’s meeting” is not yet a theme. The coach’s judgment lies in knowing the difference.

Theme report: a structured summary of recurring patterns, leadership impacts, and practical implications gathered through interviews, observation, and coaching conversations. A theme report should be specific enough to help leaders act, but careful enough to protect confidentiality. It may be delivered verbally, in writing, or through a facilitated session. The format matters less than the integrity of the process.

A useful theme report often includes four elements. First, it names what is working, such as commitment, customer orientation, speed, loyalty, or resilience. Second, it names recurring friction points. Third, it explains the likely leadership or system implications. Fourth, it suggests the conversations, decisions, or behavior changes that should follow.

The coach should avoid weaponizing quotes. A vivid quote can help a founder understand impact, but it can also trigger a search for the speaker. In a small executive team, even anonymized details can reveal identity. The coach should paraphrase when possible, combine examples, and remove unnecessary identifiers. If a direct quote is important, the coach should obtain permission or make clear that the quote has been altered to protect attribution.

The founder and coach should also agree on how themes will be shared with the executive team. Sometimes the coach first debriefs the founder privately, especially if the feedback concerns founder behavior. This gives the founder time to process defensiveness before responding publicly. But the founder should not use private debriefs to suppress uncomfortable feedback. In many cases, the next step is a facilitated executive-team conversation where the themes become shared material for change.

There are categories of information that should not be casually shared. Private emotional disclosures, personal family issues, health concerns, unverified allegations, compensation complaints, or comments about someone’s possible termination require careful handling. The coach should not convert every piece of sensitive input into a leadership theme. Some information belongs in private coaching. Some belong with HR or legal. Some belong in a direct conversation between the relevant people. Some should not be used at all unless it can be validated responsibly.

The founder’s response to reported themes is part of the intervention. A founder who argues with every theme, demands names, or explains away impact will teach the organization that feedback is unsafe. A founder who receives themes thoughtfully, asks what needs to change, and communicates follow-up actions will increase trust. The coach can help the founder prepare before themes are shared more broadly.

A simple reporting protocol can be agreed at the start:

• Individual coaching content: remains private unless the participant chooses to share it.
• Interview themes: may be summarized in non-attributed form.
• Team observations: may be discussed with the team as shared behavior in the room.
• Serious concerns: may be escalated through agreed legal, HR, or governance channels.
• Progress updates: may describe scope, cadence, and broad movement without exposing private content.

This protocol does not remove all judgment. Coaching involves human complexity, and not every situation fits a neat category. But written principles give the coach and founder a shared basis for decisions when sensitive information appears.

9.4 Fees, Cadence, Access, Cancellation, Duration, and Renewal Points

The commercial and operating terms of a coaching engagement are not separate from the work. They shape expectations, seriousness, access, and boundaries. A vague commercial arrangement can create resentment or confusion later: the founder assumes urgent access is included; the coach assumes sessions are scheduled only; the company assumes team facilitation is part of the fee; the coach assumes it is additional. These issues are easy to prevent and awkward to repair.

Fees: the agreed compensation for the coach’s time, expertise, preparation, interviews, facilitation, travel, materials, and availability. Coaches may charge by the hour, by the month, by phase, by project, or through a retainer. Founder-only coaching may be a monthly retainer or per-session fee. Executive-team or organization-sensing work is often priced as a phase because it includes interviews, synthesis, facilitation, and follow-up.

Founders should ask what is included. Does the fee cover only scheduled sessions? Are brief calls or messages between sessions included? Are stakeholder interviews included? Is meeting observation included? Does written synthesis cost extra? Are travel expenses billed separately? Are team offsites priced differently from one-on-one coaching? Clear terms prevent both parties from feeling taken for granted.

Some coaches may accept equity, advisor shares, or success-based arrangements. Founders should approach this carefully. Equity can align incentives, but it can also complicate independence. Cash compensation is usually cleaner for coaching work that depends on neutrality and trust. If equity is involved, the conflict should be acknowledged and documented.

Cadence: the rhythm of sessions, interviews, team meetings, check-ins, and review points. Cadence should match the scope. A founder-only engagement may involve weekly or biweekly sessions. Cofounder work may require alternating individual and joint sessions. Executive-team work may involve monthly facilitated sessions plus individual check-ins. Organization-sensing work may include an initial interview period, a synthesis meeting, and a follow-up operating plan.

The cadence should also match the company’s moment. During a leadership crisis, reorganization, cofounder rupture, or major strategic transition, more frequent contact may be needed. During a steadier development phase, monthly or biweekly work may be enough. The founder and coach should avoid both extremes: sessions so frequent that the founder becomes dependent, and sessions so sparse that no behavior change can build.

Access: the ways the coach may interact with the founder, team, documents, meetings, and organization outside scheduled sessions. Access can include email, text, Slack, short calls, board materials, leadership meeting attendance, stakeholder interviews, or offsite facilitation. Access should be intentional. A coach who is always available may become a crutch. A coach with too little access may lack enough context to be useful.

Access also includes boundaries around response time. Is the coach available for urgent calls before difficult conversations? Can the founder send voice notes? Should executives contact the coach directly? Are messages confidential? The clearer the agreement, the less likely the coach becomes an informal channel for unresolved leadership issues.

Cancellation: the rules for rescheduling sessions, pausing the engagement, ending the work, or changing scope. Coaching depends on rhythm, so repeated cancellations by the founder or team usually indicate a weak commitment or an overloaded system. The contract should specify notice periods, missed-session policies, and termination terms. More importantly, the coach should name the pattern if cancellations become a sign that the work is being avoided.

Duration: the expected length of the initial engagement and the point at which continuation will be reviewed. Many founders benefit from an initial three-month phase. This is long enough to build trust, gather context, identify patterns, and test early behavior changes. Six months may be appropriate for deeper founder, cofounder, or executive-team work. Open-ended engagements can be useful, but they should still include review points so coaching does not continue by inertia.

Renewal point: a planned moment to assess whether the engagement should continue, change scope, expand, pause, or end. Renewal should not be automatic. The founder and coach should ask what has changed, what remains unresolved, whether trust is strong, whether the scope still fits, and whether the coach is still the right person for the next phase. Sometimes the best decision is to continue. Sometimes it is to shift from founder-only work to executive-team work. Sometimes it is to pause because the founder has enough practice. Sometimes it has to end because the work is complete or the fit is no longer right.

A practical contract does not need to be long, but it should be clear. It should cover client definition, scope, confidentiality, reporting, fees, cadence, access, cancellation, duration, renewal, conflicts of interest, data handling, and escalation exceptions. The founder should read it as carefully as any agreement that touches trust, power, and sensitive information.

The best ground rules create freedom. When people know what the coach is doing, who the coach serves, how confidentiality works, and what will happen with what they say, they can participate more honestly. When the founder knows the rules, they can use the coach without suspicion or ambiguity. Contracting is not the opposite of trust. In a scaling company, it is one of the conditions that makes trust possible.