A cook group can contain several businesses in one: paid information, a community, software access and a service delivered by staff. A buyer needs to know which parts are owned, which are rented and which depend on a person or third-party permission.
Inventory the offer members actually receive
List the paid products and what each includes: release information, alerts, training, community access, tools or direct support. Compare that promise with current delivery. Old sales copy may describe services that have stopped; identify the gap before a buyer discovers it. Separate paying members from free community members and complimentary staff access. Add an as-of date and explain annual plans, trials and canceled subscriptions that still have access until their paid period ends.
Put bots and information feeds under scrutiny
| Item | Evidence to prepare | Do not assume |
|---|---|---|
| Original bot code | Repository ownership and deployment notes | Every dependency is transferable |
| Rented bot licence | Contract and renewal terms | A licence can be resold with the group |
| Third-party feed | Supplier permission and ongoing cost | Access survives a change of owner |
| Staff alerts | Work schedule and responsibilities | Staff will remain without agreement |
Check the rules of services and platforms the business relies on. Do not promise that tools can evade platform restrictions, deliver guaranteed purchases or continue indefinitely. Identify dependencies that a buyer must replace or obtain directly.
Explain the revenue pattern
Cook-group demand may vary with events and the usefulness of the offer. Present completed monthly periods and annotate relevant changes without rewriting the figures. Show refunds separately from gross volume and distinguish revenue from member resale results, which are not the group’s revenue. Hypothetical example: a group has 2,400 Discord members but 160 active paying memberships at the reporting date. Its sale materials should not describe 2,400 customers paying the monthly fee. If 30 paid members are on annual plans, explain their remaining access obligations rather than assuming another monthly cash receipt from each.
Plan continuity with the team
Document moderator coverage, information sourcing, support and escalation. Discuss availability with staff before promising their continued involvement. Record whether compensation is fixed, commission-based or informal; any buyer agreement with a contractor may need to be made separately. Create a short test of the operating process: can another authorized person publish an alert, handle a member-access problem and respond to a refund question using the runbook? Record unresolved gaps as transition tasks.
Coordinate the assets, not just the server
Discord has a server-ownership transfer process. That is only one part of a sale using Whop billing, bots and external services. Check each relationship separately and agree the order of changes so existing members are not unexpectedly locked out. Prepare your BizAcquir listing around the whole business, supported revenue and what can transfer. Keep private member information and credentials out of the listing. Buyers should be able to understand the offer and its limitations before seeing sensitive handover material.
Before you describe the cook group as ready to transfer
- Separate owned bot code from rented access and show the renewal terms for each.
- Confirm who can maintain access roles when the current founder leaves.
- Record moderator availability and agreed compensation rather than assuming volunteers will stay.
- Check that the paid offer still matches the alerts, tools and support members receive.
A useful handover test is for the buyer’s authorized account to follow the runbook for an access problem in a permitted test setting. Passing that test does not prove that a third-party licence can be sold; resolve that permission separately.
Check the relevant provider guidance
These official references support the platform-specific steps. Your own contracts, account configuration and agreed sale terms still need to be checked.
Separate owned tools from access members borrow
Create a list of each bot, monitor, feed and service included in the member offer. Record the owner, recurring cost, permitted user access and what a buyer would need to continue. A group can own its brand and content while only licensing an essential tool.
If a licence cannot be assigned, identify the replacement task and cost assumption rather than describing it as included. Explain how paid access is maintained during a supported handover. This is a sale of a genuine business—not a promise of profitable reselling results for members.
Your next practical step
Use the WHOP selling checklist to turn the gaps into a preparation plan. You can start a private listing draft or explore a free valuation; signup or login is required to view valuation results.
Continue with Selling a Paid Discord Community That Uses Whop and Build a Buyer Information Pack for Your Whop Business.
