How to Host Client Masterminds Without Mighty Networks

You can host client masterminds without Mighty Networks when you can deliver the actual peer-learning arrangement: appropriate members, fair case opportunities, moderated discussion, usable meeting access and a clear finish. A busy feed does not establish that anyone received help with a decision. The useful test is whether a member can bring a bounded question, hear relevant contributions, retain their own judgment and report what happened afterward.

Coachful is our #1 recommendation for coaches who want that work alongside their existing client relationships. A selected-member community channel can hold group discussion; group sessions provide the meeting arrangement; individually assigned worksheets and client conversations can support private preparation and follow-through. Those audiences need separate checks. Creating a channel does not automatically create a meeting roster or isolate every other shared space.

This guide develops an original six-week mastermind with six members and three calls. It follows one case from an incomplete invitation through an actual counterproposal, acceptance, delivery and review. All names, dates, figures and events in that example are fictional. The structure is a practical design, not a validated intervention or a promise that masterminds improve business results.

Decide whether the work really needs a mastermind

A mastermind, as used here, is a facilitated peer group in which members work on their own current decisions and contribute to other members' thinking. It is different from a course whose main work is learning a common curriculum. It also differs from a consulting panel that supplies expert recommendations, and from a community where people participate whenever a topic interests them.

These formats can coexist, but their promises should remain legible. If buyers expect individualized expert diagnosis and a written solution, a peer discussion is an inadequate substitute. If they want occasional networking, a demanding case rotation may be unnecessary. Ask what members should leave with: a clarified question, examined alternatives, an action they choose and a later account of the result. Then ask what the facilitator can responsibly support.

Peer experience has limits. A member's successful launch in one market does not establish that another person's similar offer will sell. A personal account of managing illness is not treatment advice. The facilitator must distinguish an observation, an interpretation and a recommendation, and redirect questions that need a qualified professional or an authorized workplace decision.

Compare the actual service requirements fairly

Mighty Networks' current owner documentation describes events inside Spaces, including repeated events and RSVP options. Its Plans can gate access to a Network, Spaces or both, with payment, screening questions or approval. It therefore deserves evaluation as a community and event platform. Do not justify switching by claiming that it cannot organize private experiences or charge for access.

Instead, compare the member journey you need with the current features and plan terms of each service. Can the intended person enter the right discussion, open the next meeting and understand where a private question belongs? Can the host see an unanswered request and provide the promised response? Does the exit arrangement match what members bought? Avoid relying on old price comparisons, retired plan names or assumptions about an existing subscription.

Coachful is especially useful when the mastermind sits inside an established coaching practice and members also have individual work, sessions or resources. A standalone community platform may suit a large network whose primary activity is community participation. The choice should survive a practical rehearsal with a test account, not merely a comparison of feature lists.

Build a group around an appropriate reciprocal task

Selection should consider both relevance and participation conditions. Members need enough shared context to understand one another, yet differences can expose assumptions. Ask about the decisions they want to examine, the experience they can contribute, available time, access requirements and commercial conflicts. A high income threshold does not establish fit, generosity or capacity.

Explain the workload before acceptance: preparation, meetings, optional written contributions and the response arrangement. Agree what happens if someone misses a case opportunity or chooses to pass. A person who declines public case work may still contribute thoughtful questions. They should not have to disclose private material to justify remaining in the group.

The ICF Code of Ethics requires ICF professionals to establish roles, responsibilities and other engagement terms before coaching, and to agree how information is exchanged. For a peer group, explain what peers can see, what the authorized coach team can see and the limits of the facilitator's control over another member's behavior. An agreement is not a technical guarantee that information cannot be copied.

Use anonymized or synthetic material when identifying information is unnecessary. Do not invite client documents into a group simply because its channel has restricted membership. Check the person's right to share the material, and offer a different route when the real issue cannot be discussed appropriately in that audience.

Complete the fictional six-week service brief

Facilitator Rin invites six existing coaching clients: Asha, Benji, Cleo, Dara, Emil and Fran. Each has an independent professional project and wants help making a bounded work decision. The mastermind is an expressly included part of their existing service, with no additional payment or new recurring subscription. Rin checks the existing agreements rather than describing access as a new purchase.

All six accept those terms. Fran requests the written agenda in advance and permission to contribute in writing. Rin provides an accessible text version, includes a break and checks the actual meeting connection and caption option with participants. The W3C accessible-events checklist supports planning around participants' requirements, accessible advance materials and meaningful alternatives to inaccessible activities. A recording is not the only possible accommodation; an appropriate arrangement still needs agreement and testing.

Set up the delivery routes in Coachful

1. Create the intended discussion audience. Use a standalone community channel with Selected members containing only these six people. Selecting a shared Program as its audience could admit other eligible participants. Check other Offer or resource grants too, rather than assuming the selected list is the only access route.
2. Check the surrounding spaces. A Program's community and other shared channels remain separate. Rin tells participants which space holds mastermind discussion and checks the actual member experience. A restricted channel does not make their whole account private to this group.
3. Create and verify each group session. Add the correct date, time zone, duration, members and joining arrangement. If using an external meeting room, configure the supported custom link and test it from the participant side. The community member list is not proof that all six received session access.
4. Share a small resource set. Provide the service brief, case-preparation prompts and meeting schedule. Assign private preparation individually when it includes personal information. State its real authorized staff audience.
5. Post the support arrangement visibly. Repeat the checking times, response deadline, final cutoff and administrative contact. An ordinary group discussion does not enforce the service promise for you. Use the waiting-question view where appropriate, but check the actual thread and reply.
6. Rehearse with representative accounts. Confirm a member can open the channel, an intended meeting and the relevant resource, while an unrelated client cannot open the restricted channel. Repair failures before requesting substantive case submissions.

During onboarding, Emil can open discussion but not the first session. Rin finds that the session invitation omitted him, adds him and asks him to reopen the session. Emil confirms the correct joining information is now visible. This consumes ten extra onboarding minutes. Rin does not ask him to solve an invitation problem by posting his case publicly.

Give each meeting a fair, usable structure

Rin uses ten minutes for arrival and orientation, thirty for the first case, a five-minute break, thirty for the second case, ten for member choices and five as timing margin. That totals ninety minutes. The five-minute margin is not an additional case slot, and the break is not reclaimed because a discussion becomes interesting.

Inside each thirty-minute case, the owner has three minutes to frame the decision; peers have ten minutes for clarifying questions; eight minutes are available for experiences and ideas, with permission; six minutes belong to the owner's interpretation and choice; and three minutes capture the chosen next step. This original allocation is a starting arrangement, not a universal mastermind formula. Adjust it with members when its actual use shows a problem.

Questions should help establish the problem before offering solutions. “What has the organizer already agreed?” is useful when an invitation is incomplete. “Why don't you just say no?” carries a proposed answer and may close exploration prematurely. During the ideas period, a member can ask, “Would an example from my experience be useful?” The owner can decline.

Accountability then means revisiting the chosen action and what actually happened. It does not mean forcing compliance with the group's favorite suggestion. A member may discover that the action is inappropriate and choose a defensible change. Record that reasoning instead of marking every change as avoidance.

Work Asha's decision through the first case

On 4 March, Asha brings an invitation to speak on 24 March. The organizer asked for forty-five minutes of content but has not specified questions or technical preparation. Asha can allocate at most four hours total, including preparation. She will use only her own original fictional examples, with no client material.

Her case question is: “What do I need to clarify before I accept this invitation within four hours?” Benji begins to recommend a personal productivity system. Rin pauses that advice and returns to the missing terms. Cleo asks whether the forty-five minutes includes questions. Dara asks whether Asha already has material she can legitimately reuse. Asha has an original outline but needs three hours to prepare a usable session.

With permission, Emil describes how an uncounted rehearsal once changed his own commitment. He does not tell Asha how long hers must take. Asha chooses to obtain the actual live requirements before deciding. Her completed message that afternoon reads:

Thank you for the invitation. Before I confirm, could you specify the question period and required technical check alongside the forty-five-minute talk? I can commit four hours total including three hours of preparation. I would use original fictional material on writing a clear internal handoff request, with no client examples.

On 5 March, the organizer answers: forty-five minutes of content, fifteen minutes of questions and a fifteen-minute technical check. That is seventy-five minutes in addition to three hours of preparation, or four hours fifteen minutes. The original invitation fails Asha's four-hour limit. Peer encouragement cannot remove those fifteen minutes.

Show the counterproposal, acceptance and actual result

Asha proposes a narrower session on 8 March: thirty minutes of content, fifteen minutes of questions and a fifteen-minute technical check. The audience is first-time team leads. The content covers the minimum fields in an internal handoff request, how to ask for an owner's acknowledgment and one original fictional example in which a missing deadline is corrected. Three hours of preparation plus sixty minutes of live and technical time fits exactly four hours.

The organizer accepts that complete scope on 9 March, including the reduced content time and no client examples. Asha confirms it in writing. At the 18 March call, her update distinguishes agreement from delivery: the revised session is accepted, but it has not happened. The group does not report her talk as completed or claim that a future audience will find it useful.

On 24 March, Asha completes the agreed technical check, thirty-minute session and fifteen-minute questions. Her preparation actually takes two hours fifty minutes. Her total is therefore three hours fifty minutes, leaving ten minutes within her cap. The organizer confirms that the agreed session was delivered. No new client acquisition or audience-performance outcome is inferred from that confirmation.

At the final call, Asha says the clarification prevented her from accepting an undefined commitment. She also remains nervous about public speaking. Her final record contains the original request, actual requirements, rejected total, accepted narrower proposal, delivered times and continuing concern. A useful commercial boundary and continuing discomfort can both be true.

Complete the rotation without turning passing into failure

Rin uses Fran's released time for an optional review of learning, not a demand for a substitute case. Fran can leave that discussion; Rin remains available to the others until the scheduled finish. Across the cycle, six opportunities were offered and five full cases were used. Describing this as six completed cases would hide Fran's actual choice.

Fran submits a written reflection on 1 April at 15:40 UTC: “I noticed that I treat a collaborator's interest as agreement. My next invitation will ask for a yes, a different date or a no.” Rin replies at 16:10: “That separates interest from commitment. What exact answer do you need before reserving the time?” Fran chooses an explicit date and confirmation request for her next invitation. The invitation itself remains future work.

Dara's between-call request also tests the service rhythm. She posts on Thursday 18 March at 16:20 UTC: “My draft deadline depends on a reviewer. Should I promise Friday before she confirms?” It enters the next check, Monday 22 March at 16:00. Rin replies at 16:10: “The review slot is still a dependency. Ask whether she can review by your required time, and describe Friday as conditional until she answers. What latest answer would let you make another plan?” Dara chooses Tuesday noon. Rin has answered before the Tuesday 17:00 response deadline; the reviewer has not yet accepted anything.

Count delivery effort and close the actual promise

Rin's planned staffing was 270 minutes live, sixty preparing cases, 180 for twelve moderation windows, sixty onboarding, thirty technical setup and thirty closure. The total was 630 minutes, or ten hours thirty minutes, within a twelve-hour allocation. Members' own preparation time is separate and was disclosed in admission discussions.

Actual work is 270 minutes live, seventy-five preparing cases, 195 moderating, seventy onboarding, thirty technical setup and thirty closure: 670 minutes, or eleven hours ten minutes. The extra forty minutes comprise fifteen case-preparation minutes, fifteen moderation minutes and Emil's ten-minute access repair. All twelve moderation checks are complete through 1 April. Fifty minutes remain from the twelve-hour allocation. This is a staffing account, not a profit calculation or proof that every cohort will fit it.

Rin stops taking new included questions at the agreed 1 April cutoff. On 5 April, after the term ends, Rin completes the counted closure administration and sends the closing note: three calls delivered, six opportunities offered, five used, no renewal or new charge. The note explains that mastermind facilitation has ended; it does not claim that a date automatically canceled other contracts or removed every independent access grant. Rin checks the channel and resource access against the agreed retention arrangement separately.

For this cohort, members may retain the brief and their own written work for personal reference; shared discussion remains readable to the same authorized audience for thirty days after 4 April, with no new facilitated responses promised. Rin checks the actual grants and communicates the later access review date, 4 May. That future review is scheduled, not claimed complete. No member is enrolled in another cycle without a new decision.

Troubleshoot the group process before adding features

• Advice overwhelms the owner. Pause the recommendations, ask the owner what kind of help they want and return the choice to them. More comments can worsen an already unclear decision.
• A member becomes a sales prospect. Stop the pitch, restate the agreement and address repeated boundary breaches directly. A disclaimer in the welcome document does not replace facilitation.
• Written questions grow beyond the allowance. Clarify scope and obtain an actual service decision. Do not silently absorb unlimited work or leave members believing their question has entered a promised queue.
• Private information reaches the wrong audience. Follow the applicable incident and confidentiality process, limit further exposure and inform the appropriate people. Deleting a visible post is not proof that no copy exists.

The related community delivery guide examines a broader ongoing space. For this finite peer group, start with the case rhythm and service capacity. Review the coaching package guide when changing what the contract includes, and the Coachful features for the supporting workflow.

Frequently asked questions

How many members should a client mastermind have?

Work backward from meaningful opportunities and facilitator capacity. Six members with three calls and two offered cases per call gives one offered case each in this example. It does not establish a universal ideal size. Recalculate when meetings, preparation or participation needs differ.

Can a mastermind work without a community feed?

Yes, if members have clear meeting access, preparation and follow-through routes. A discussion channel helps when asynchronous peer work is part of the promise. Do not add one merely to create an appearance of activity.

Should every member receive a recording?

Decide purpose, consent, rights and accessibility needs before recording. This fictional group agrees not to record and tests other participation arrangements. A genuine access need deserves a workable discussion, not an automatic refusal or an assumption that all peers consent.

Does creating the channel invite everyone to the calls?

No. Check channel audience and session invitations separately. Emil's repair illustrates why a person who can read discussion may still lack the correct session access.

How should I measure whether the mastermind was useful?

Look at offered versus used opportunities, actual responses, decisions examined, chosen actions and reported results. Preserve refusals, missing answers and unresolved questions. Attendance and comment counts alone cannot establish improved judgment, revenue or wellbeing.