The right buyer for a paid community needs to be able to deliver what members are paying for. Price matters, but so do moderation, expertise, tools and the ability to retain a working team. Compare buyers against the operation they would inherit rather than treating every enquiry as interchangeable.
For asset preparation, use the existing cook-group sale guide or paid Discord community guide. This checklist focuses on assessing a prospective buyer's plan.
Start with the promise to members
Write down the recurring activities, support commitments, access rights and any prepaid service periods. Include quiet but essential work such as onboarding, billing questions and removing inappropriate content. A buyer who understands only the headline activity may underestimate what keeps the community useful.
For a cook group, distinguish educational resources, alerts, moderation and third-party tools. Do not describe a tool licence, external data feed or personal account as transferable until its terms permit the proposed arrangement. A buyer's enthusiasm does not resolve that dependency.
Ask for a practical operating plan
| Area | Question for the buyer | Useful evidence of preparation |
|---|---|---|
| Delivery | Who will provide the scheduled service? | A named role and realistic weekly plan |
| Moderation | How will member issues be handled? | Coverage, escalation and conduct expectations |
| Tools | Which licences or services need approval? | A dependency list with unresolved items |
| Team | What arrangements do you propose for staff? | A plan to discuss consent and continuing responsibilities |
| Transition | What help do you need from the founder? | Specific training and handover deliverables |
These are discussion points, not a request for the buyer to prove they already run your business. A realistic plan can include hiring or training, provided the costs and timing are acknowledged.
Compare two offers beyond the headline
Illustrative example: Buyer A offers a higher headline price but expects the founder to keep delivering daily sessions for an undefined period. Buyer B offers less, has an identified delivery team and proposes four scheduled training sessions. You cannot compare these offers properly until the ongoing workload, compensation and conditions are explicit.
Prepare a side-by-side table of price, payment schedule, conditions, founder commitments and unresolved dependencies. Do not turn it into an automatic ranking formula. The founder's priorities and the feasibility of each plan matter.
Protect member continuity during diligence
Share aggregate retention and activity information where appropriate rather than exporting private conversations or member identities to every prospect. Use the applicable NDA and access process before protected disclosures. A seller introduction attached to a confidential listing does not bypass that process.
Discuss how existing promises would be honoured before deciding when to announce a sale. Premature announcements can confuse members, while an unexplained change after completion can create support problems. The member-announcement guide helps plan the communication.
Know when the next step is clarification
- If the buyer assumes the founder will stay indefinitely, define the proposed support.
- If a key moderator has not agreed to remain, describe that as unresolved.
- If a tool cannot transfer, cost and plan an authorised replacement.
- If the buyer wants to change the service immediately, discuss existing member obligations first.
- If a community is inactive, assess the restart plan separately from historical engagement.
Do not promise member retention after a sale. Instead, prepare the information and transition work that help a buyer make a considered decision.
Browse buyers' acquisition requests and use the Whop buyer-finding guide to start relevant conversations.
