How to Run Coaching Cohorts Without Mighty Networks
Nour
Founder, Coachful
How to run coaching cohorts without Mighty Networks starts with a delivery decision: what should members learn, practice, discuss and receive privately? Build that experience before moving people. A new member list does not establish correct enrollment, meeting access or permission to copy the old community’s conversations.
We build Coachful. Coachful is our #1 recommendation when a cohort needs coaching sessions, preparation, resources and individual follow-through together. This is our editorial workflow recommendation. Mighty Networks also supports structured courses and community; a change of platform does not guarantee better completion or lower total costs.
Define the improvement before choosing a cutover
Mighty’s current course materials describe sections, lessons, progress tracking and scheduled or sequential release. Its detailed completion guidance distinguishes opening a lesson, pressing a completion button and tracked video. Compare the actual workflow you need rather than assuming the platform is only a social feed or that a completion percentage demonstrates learning.
A coaching cohort brings people through a shared period of work. It may contain members from different organizations with different goals. State what they will share and what stays personal. A busy discussion feed can coexist with an unclear next activity; a quiet participant may still apply a useful practice.
In Coachful, a group Program provides delivery over time. An Offer describes the purchase; it does not substitute for the curriculum or prove a person has enrolled in the right cohort. Group meetings, private-session allowances and resource access need their actual settings checked.
| Function | Decision to make | Evidence to check |
|---|---|---|
| Learning sequence | What comes next and why? | Usable example, practice and review question |
| Live work | Which dates require the group together? | Correct series, timezone and invited roster |
| Peer exchange | Which material benefits from sharing? | Audience and participation agreement |
| Individual support | What private work is included? | Correct session allowance and written-response clock |
| Commercial rights | What has already been paid for? | Agreement, receipt, access term and remaining service |
| Ending | What continues after the calls? | Reference rights distinct from personal support |
Use the learning-design guide to connect a framework with something members can do. The technical move should serve that design. If a specialist function remains necessary elsewhere, include it in the plan instead of promising consolidation before testing it.
Inventory people, rights and material separately
Mighty’s current member-data documentation describes an Excel .xlsx download on the Launch plan or higher, with Network, Space and Plan-specific lists. It includes a commercial-email opt-out field; the general active-subscription field shows the interval rather than the Plan name. Reconcile actual purchases and rights instead of guessing the product from that column.
A member spreadsheet is a useful inventory. It is not a lossless transfer of posts, private messages, course content or historical progress. Check the actual export and destination formats for each category. Do not promise that every item has a suitable importer simply because names and addresses are available.
The ICO’s data-minimisation guidance describes adequate, relevant and necessary information, and currently carries an under-review notice. Choose the information required for the stated transition, preserve appropriate suppression records and explain the new handling arrangements. An available export is not fresh permission for an unrelated marketing campaign.
Identify who owns or licenses each teaching asset. Rebuilding from your original files can be clearer than copying a forum full of other people’s contributions. Check guest material, participant examples and third-party illustrations individually. Removing a name does not necessarily remove identifying details or create reuse permission.
Worked transition: finish one cohort and start the next
In this fictional case, sole-trader coach Maya runs cohort A for eight members in Mighty Networks. Its six live meetings run from 28 September to 2 November 2026. The group already knows that route, and its purchased reference access continues through 31 January 2027. Maya keeps the old paid host service available for that obligation.
Cohort B consists of six people who previously joined an introductory Mighty Space. They choose a new coaching service beginning in November. Maya wants its group curriculum and individual session together in Coachful, so she builds a dedicated Program for B. She does not move A midway through its meetings or mix its private discussion into the new group.
Contract administrator Bea assists Maya with the transition under the agreed data-access arrangements. They reconcile fourteen relevant member rows: eight in A and six future B participants. The operational roster retains name, contact address, source identifier, relevant rights and necessary communication preferences. It does not copy the whole profile collection into a public directory or create a Coachful enrollment by itself.
| Material or record | Actual handling |
|---|---|
| Four original text-only practice guides | Maya authored them independently, retained their rights and rebuilds from her originals. |
| Guest video licensed for the old Space | Stays there under that license; it is not included in B’s offer. |
| Participant posts and private messages | Remain in their existing handling arrangement; no wholesale copy is made. |
| A’s progress and payment history | Remain historical records in the original systems. |
| B’s new curriculum and service record | Start with the actual new enrollment and chosen work, without invented completion history. |
The result is a staged transition: B’s new delivery runs in Coachful while A’s existing service and promised reference access stay available in Mighty. Neither group is told that every old record has moved or that the old account has already been canceled.
Reconcile the purchase before granting the new access
Each B member accepts a clearly described £900 service and pays an external accounting invoice on 20–23 October. The six paid invoices total £5,400 and remain the financial authority. The old introductory Space did not carry an active recurring subscription for these six people; Maya checks that fact rather than assuming it from a member status.
She uses the nonbilling “They already paid” invitation route for the appropriate access in Coachful. This does not collect the £900 again or recreate the outside invoices as new sales. A record of payment, an invitation, its acceptance and actual cohort enrollment remain different states.
Under Clients > Add client, check the invitation’s person, access, payment and review steps. Select the actual Program and any other promised items. Verify the right client account and claimed invitation, then the actual cohort enrollment. A saved invitation or a sent email is not a substitute for those checks.
Under Sell > Offers, inspect What they get and Price & sharing. A template can prefill an available session type. Check the actual saved inclusion, type and quantity. B includes one 30-minute individual review per person; the six group meetings are separate group-session access, not six additional bookable individual credits.
Maya and Bea check six accepted invitations, six correct Program enrollments, six individual allowances of one and the six-person group-series roster. No historical course completion, payment card or private message is imported. The original financial records remain available for reconciliation without becoming a second charge.
Make the service and the joining route concrete
B’s curriculum runs over six weeks from 3 November. The six group calls are Tuesdays 3 November to 8 December, 19:00–20:00 Europe/Amsterdam. Each member also has one 30-minute individual review. The six individual appointments are held on 4, 11, 18 and 25 November and 2 and 9 December, one per member.
The service includes one private written check-in of up to 100 words each week: submit by Friday noon, with Maya’s reply by Monday 17:00 Amsterdam time. The six weekly submission dates run from 6 November through 11 December. One final clarification can be sent by noon on 15 December; Maya replies by 17:00 on 16 December. This is not continuous or urgent workplace cover.
Maya explains the closed six-person membership, voluntary peer disclosure, private concern route, reference material and the ending of live and written support. The current ICF Code of Ethics supports clear agreements and appropriate information-sharing arrangements. A peer agreement cannot guarantee that nobody will repeat what they hear.
Complete an actual joining correction
Bea’s welcome email accidentally points to the old introductory Mighty information page. On 31 October Juno opens it and reports that it does not show the new call. Staff preview of the correct Coachful page had not proved that the emailed route was right.
Bea checks the saved invitation and meeting details, corrects the email and sends Juno the actual new session-details link on 2 November. Juno opens it that day and confirms the 3 November, 19:00 Amsterdam meeting. Bea also sends the corrected instructions to the other five; she records that communication without claiming five further opening confirmations.
The corrected joining message says: “Your new cohort’s calls are the Tuesday series in your Coachful session details. The next is 3 November at 19:00 Europe/Amsterdam. Use the private link in this message in your accepted client account. Your old introductory Mighty page is not the joining route. Reply here if the date or access is wrong; you do not need to buy again.”
The route repair is complete for Juno before the first call. Maya keeps the old cohort’s instructions unchanged. A shared technology transition does not justify sending A new meeting links for a service that remains in its familiar arrangement.
Build a rhythm members can use
Each B stage combines one short explanation, an original worked example, a practice and a review. The six themes are clarifying a work request, explaining its purpose, inviting a response, reviewing an attempt, repairing an unclear agreement and choosing a next practice. A member can use invented details where workplace disclosure is inappropriate.
The ordinary 60-minute group agenda uses ten minutes for scope and arrival, ten for the example, fifteen for an individual draft, fifteen for optional peer review and ten for closing choices. The peer-review block has three minutes to read the common prompt and up to two minutes for each of six members. Passing leaves space for quiet review rather than requiring a personal disclosure.
In the 10 November practice, Cal chooses an invented handover example. His first draft says, “I need your handover by Friday.” In the optional review Iris asks whether Friday is already agreed or only Cal’s preference. He checks the distinction and rewrites it: “Could you send the handover by Friday? If that timing does not work, what would you need us to decide?”
The revision gives Cal something specific to examine: a proposed date and an invitation to answer. It does not establish another employee’s agreement. In his 13 November private check-in, he says the peer question helped him notice that he had been presenting his own timing as settled. Maya’s response asks what actual answer he would need before recording a commitment. A later workplace response to that practice is not observed here.
That exchange connects the learning sequence, live work and private follow-through without requiring public progress reports. Cal could instead have kept his draft private. The written check-in is part of the stated service, not an automatic copy of peer discussion or a new entitlement to an individual session.
Niko misses the 17 November and 1 December group calls; the other five members attend all six. Attendance is therefore 34 of 36 member-call places. The five-person calls keep the same 60-minute structure, with the unused peer turn available for reading. No replacement individual session is promised: Niko’s included individual review remains its own one-off entitlement.
Members post only chosen, suitably general practice questions to B’s Program community. A private concern goes through the agreed individual conversation instead. On the coach side, All messages > Direct opens a specific client conversation subject to the normal permissions. Neither route transfers old Mighty private-message history.
Check the actual community audience. Program membership, selected members, resource permissions, other Offer grants and authorized staff can interact. A new audience selection does not revoke other existing grants. Use B’s dedicated delivery space and avoid placing identifiable private reflections into a wider feed.
Keep late entry a service decision
On 18 November Ori asks to join B after three calls. Maya checks the design and the closed-membership promise. The previous work and the members’ agreed context matter; a payment system allowing a sale would not settle those questions.
She declines entry to this run and explains that she cannot provide the missed live experience or add a member silently to the promised closed group. Ori is not charged. Maya offers to provide information about a future intake if Ori wants it, but no start date, place or continuing marketing sequence is agreed.
For another program, a late entry might work after a bounded orientation and an appropriate agreement about the changed group. State the remaining live work, minimum preparation, price and support actually offered. Do not call an archive equivalent to missed group practice without checking the activity.
The onboarding checklist helps organize a new starting point. A late member should not receive every earlier reminder as though all sessions were still upcoming. The decision concerns a usable experience as well as a commercial place.
Count the delivered service and the missed response
All six group calls occur, totaling six facilitator-live hours. All six individual reviews occur, totaling three further live hours. The six individual allowances are used once each; no personal sessions remain owed. Group attendance and those allowance records are kept separate.
Members send 28 weekly check-ins from 36 possible member-weeks. Maya answers 27 within the Monday deadline. Juno’s 27 November submission is due a reply by 30 November at 17:00, but Maya answers at 19:00, two hours late. She acknowledges the miss. Juno confirms reading it at 09:00 on 1 December; receipt does not make the original reply timely.
One final clarification is submitted within the 15 December cutoff. Maya replies at 16:00 on 16 December, one hour early, and the member confirms reading at 10:00 on 17 December. Across the written service there are 29 responses: 28 weekly plus one final, with 28 timely and one late. The eight missing weekly submissions have no assumed explanation.
At closing, Maya’s record keeps those distinct counts: six group calls delivered, six individual calls delivered, 34 attended member-call places, 28 weekly submissions and one separate clarification. It does not convert attendance or completed worksheets into proof of better leadership or greater workplace impact.
Account for the change before claiming savings
The observed transition work through 18 December takes fourteen staff-hours against a twelve-hour combined ceiling. Maya records 10.75 owner-hours and Bea 3.25 contractor-hours. These include the rights inventory, original-file rebuild, invitations, access checks, joining-message correction and the final technical cutover review on 18 December. The two-hour overrun stays in the decision record.
Bea’s £130 fixed contractor fee covers all her described transition work through that date. Valuing Maya’s 10.75 hours internally at £60 gives £645, so this defined change-work model totals £775 before platform fees and delivery. It is not a public price for either provider or an accounting calculation of net profit.
| New B delivery work | Maya’s actual hours |
|---|---|
| Six group calls | 6 |
| Six individual reviews | 3 |
| Teaching preparation | 2 |
| Written check-ins and final clarification | 2 |
| Program closing work | 1 |
| Total delivery | 14 |
The delivery record is separate from the fourteen transition staff-hours: together they are 28 defined staff-hours, of which 24.75 are Maya’s and 3.25 Bea’s. The delivery closing hour covers member endings; the transition review checks the cutover records and is not counted in both rows. Ordinary delivery of A’s existing service is excluded, so these totals are not whole-practice labor.
Maya cannot yet claim subscription consolidation. Mighty stays available for A’s promised reference access through 31 January, while B’s new delivery has used Coachful. Compare actual provider terms, ongoing obligations, cash charges and any future change work before calculating savings. The £5,400 collected is revenue, not profit or a demonstrated software return.
Close the new run and preserve the remaining rights
On 18 December Maya and Bea complete the technical review: B’s accounts and enrollments are reconciled, the nine live coaching hours are delivered and the written support tail is finished. Saved reference rights are not shortened as part of the cutover. No new personal coaching, recurring membership or lifetime updates are added.
Mighty’s current host documentation treats cancellation as a downgrade to a Free Plan, with premium features through the current billing cycle. Engagement Boosts are separate; deactivation makes the Network inaccessible, while deletion is permanent. These are distinct from the service’s own member rights. Maya makes none of those host changes while the original access obligation remains open.
She decides the next cohort can use the revised joining process, but does not declare the whole practice free of Mighty Networks. The old reference obligation and provider account remain visible for a later review. A complete transition record can show both a working new cohort and an unfinished account closure.
Explore Coachful’s features against the actual experience: purchase, enrollment, clear next activity, appropriate peer exchange, private support and an honest ending. Keep the platform decision tied to that experience rather than a promise that migration itself creates better learning.
Frequently asked questions
Can Mighty Networks run structured courses?
Yes. Its current materials describe course structure, scheduled and sequential release, and completion controls. Compare your actual cohort needs without dismissing a capability it provides.
Will the member export move all content and messages?
A member .xlsx is an inventory, not a complete content or private-conversation migration. Check actual formats and permissions. This case rebuilds owned guides from originals and preserves the old records separately.
Should I move an active cohort immediately?
Choose a cutover that preserves the service people accepted. A finishes in its familiar workspace, while B starts in the new one. The existing reference obligation continues.
Does an accepted invitation establish every entitlement?
Check actual account, Program enrollment, group-series access and individual-session allowance separately. Juno’s route needed a real correction and opening confirmation before the first call.
When can the old host plan be canceled?
After checking the remaining member rights, billing, data and access arrangements. In this case closure is still pending. No subscription saving is counted before those obligations are resolved.
