Skool Pricing 2026: Plans, Fees, and Break-Even Math

A practical explanation of Skool’s published plan prices, transaction fees, and the revenue point where an upgrade makes financial sense.

Know Your Break-Even Before You Pick a Plan

Hobby runs $9 a month with a 10% fee, Pro runs $99 a month with a 2.9% fee, and the crossover lands around $1,268 in monthly sales. Get the rest of the launch right and the plan choice takes care of itself.

Get the Done-For-You Build →

Current Skool Details to Verify

Plans and workflows change, so read Skool’s current pricing page before you make a buying decision. Then check Skool’s subscription FAQ against the exact job you want the tool to do.

A review can help narrow the options, but it cannot replace the product’s own documentation. Give Skool’s payment-terms policy a quick read before you commit your team, customer data, or budget.

Where Skool Fits in the Bigger Ecommerce Picture

I have been building and managing ecommerce stores for more than 15 years, and a tool never fixes a vague operating plan. Start with E-Commerce Paradise. Then get clear on what high-ticket dropshipping actually involves.

Choose the business opportunity before you choose more software. Work through the high-ticket niche ideas. Then use the supplier sourcing guide to make the offer operationally sound.

Get the unglamorous foundation in place as well. The business-formation checklist will help you sort out the legal and financial basics before you scale.

What I would do is test one important workflow, measure the result, and only then add more complexity. If you want help with that broader store strategy, E-Commerce Paradise coaching is there for you.

Quick Answer

Skool’s published plans are simple enough to understand, but the right option depends on revenue, not on how many members you hope to have. Hobby is listed at $9 per month with a 10% transaction fee. Pro is listed at $99 per month with a 2.9% transaction fee. Both plans list unlimited members, courses, videos, and live calls.

The important decision is the break-even point. The fixed-price difference is $90 per month, while the fee difference is 7.1 percentage points. At roughly $1,268 in monthly sales, the lower percentage fee on Pro covers the additional subscription cost before per-transaction charges. Below that point, Hobby is typically cheaper. Above it, Pro generally protects more of each additional dollar.

What the published plans include

The attractive part of the Skool model is that creators do not need to unlock basic capacity as their community grows. The listed plans include the core operating pieces: community access, a classroom, video, live calls, a custom URL, and affiliate capability. That lets an operator price the offer around its value rather than around a student seat limit.

Still, unlimited capacity does not mean unlimited operational capability. The real constraints are your time, the clarity of the programme, support expectations, payment geography, and the experience you promise members. Price the membership for the service level you can actually maintain.

The transaction-fee math

Use gross monthly sales, not member count, for the first calculation. A $20 membership with 50 members produces $1,000 of sales. A $100 membership with 10 members produces the same result. The plan comparison is identical even though the support workload and customer expectation may be different.

At $1,000 in monthly sales, the headline difference between 10% and 2.9% is about $71. At $2,000, it is about $142. Subtract the $90 plan-price difference to see why Pro becomes more attractive once the membership has demonstrated repeatable demand. Always include applicable processing charges, refunds, taxes, and promotion costs in your own forecast.

Hobby plan: when it makes sense

Hobby is the practical plan for validating a new paid community. It allows you to sell a real offer without carrying a large fixed software cost before you know whether the audience will buy, activate, and renew. Use it to test the promise, the price, the onboarding sequence, and your live programme.

The higher percentage fee becomes a less comfortable trade-off once sales are dependable. Do not switch only because the member count feels impressive. Switch when actual monthly revenue repeatedly clears the break-even range and you expect it to remain there after normal churn.

Pro plan: when it makes sense

Pro is the better operating choice for a community with meaningful recurring sales. It reduces the published percentage fee and keeps the same broad capacity model, so the financial benefit increases as payments increase. It is also easier to budget for when the group has a known acquisition channel and a stable monthly retention pattern.

That does not make Pro an automatic choice for every higher-priced programme. A $2,000 month followed by several quiet months is not the same as a dependable subscription base. Look at a three-month average and the next renewal cohort before treating the upgrade as permanent.

Payment and tax considerations

Skool’s payment documentation explains that pricing is in US dollars and that payouts are sent to the connected bank account. It also describes a merchant-of-record model for applicable sales tax handling. Those details can reduce administration, but they do not replace your responsibility to understand your own business, tax, refund, and customer-support obligations.

Before launch, test your payment flow in the country where you operate. Check the required identity verification, payout timing, billing descriptors, refund process, and what a customer sees when they cancel. A clear support page and a sensible refund policy are part of the product, not an afterthought.

Budget for the whole offer

Platform fees are only one cost. Include payment charges, ad spend, contractor time, your live delivery hours, software that remains outside the platform, and the cost of acquiring each new member. A low platform fee is not valuable if the offer is expensive to fulfil or hard to explain.

Build a basic monthly model with three cases: conservative, expected, and strong. For each, list new members, renewals, churn, gross sales, fees, delivery time, and net margin. This model makes it much easier to choose a membership price and avoid selling a community that cannot fund its own delivery.

How to make the decision with confidence

Write down the one action a new member should complete in the first seven days, the recurring action that makes them return each week, and the reason they will still be subscribed three months from now. Those answers expose whether the offer needs a simpler community experience or a broader product stack. They also prevent platform selection from becoming a substitute for product design.

Run the same test through the operator’s lens. Identify who publishes the weekly prompt, who answers questions, where payments are reconciled, and how an inactive member is invited back. A good platform removes friction from that routine. It cannot remove the need for an owner, a useful promise, and a deliberate rhythm.

What to check before committing

Use a real trial rather than a feature checklist alone. Create one sample lesson, one discussion, one event, one paid offer, and one welcome message. Then view each step as a member on both desktop and mobile. The important question is not whether the software has a feature, but whether your audience can find the next useful action without being trained to navigate it.

Before migrating an established audience, export the contacts and document the existing access rules. Keep the first launch small enough to answer support questions quickly. A clean first cohort gives you better evidence than a complicated all-at-once migration.

Commercial discipline matters more than the tool

Do not set a membership price by copying another creator. Start with the outcome, the access level, the expected frequency of new value, and the time required to deliver it. A lower introductory price can work when the community has a clear upgrade path. A higher price can work when live feedback, accountability, or specialised expertise genuinely changes the member experience.

Review cancellations alongside sign-ups. The cancellation reason usually points to a gap in onboarding, expectation setting, or the recurring programme. Treat that information as a product signal, not as an argument for adding random features.

Want the step-by-step playbook before you publish the welcome path? Get the Free Guide →

A practical launch sequence

First, publish the welcome path and explain exactly what a new member should do. Second, load enough useful material that nobody joins an empty room. Third, schedule the first live touchpoint before inviting people. Fourth, tell founding members what feedback you need from them. Finally, measure activation, attendance, contribution, and renewal separately. These numbers show where the offer is earning its place.

This sequence is deliberately plain. It gives a small team the chance to improve the member experience before it scales the number of moving parts.

Revenue scenarios worth modelling

Use a simple monthly sheet before choosing a plan. In the first column, enter your membership price and expected active members. In the next columns, enter gross sales, the plan fee, transaction charges, refunds, promotional cost, and the time you spend delivering the programme. The final number should be the margin available after real delivery costs, not only software cost.

Run the same model at three levels: an initial founding cohort, an expected steady state, and a stronger month. The lower-cost plan is usually the sensible start when demand is unproven. The lower-fee plan becomes more attractive only when recurring sales are reliably past the break-even point, rather than during a one-off launch spike.

Also model cancellation. A membership with 100 sign-ups and heavy first-month churn can look more successful than it is. Track how many members activate, renew after their first billing period, and stay long enough for their acquisition cost to be recovered. Those figures matter more than the initial number of purchases.

Revisit the calculation every quarter or when you change price, acquisition channel, or programme format. The correct Skool plan can change as the business moves from validation to a stable membership operation.

Define success before selecting the setup

For a Skool plan and fee model, start with sustainable revenue after transaction fees, delivery costs, refunds, and churn. State the member promise, the first action, the weekly reason to return, and the evidence that shows the programme is helping. This keeps the platform decision grounded in a real offer rather than in feature curiosity.

Ask the person who reviews revenue and changes plans as the business matures to describe the routine required to deliver that experience. If there is no clear owner for onboarding, programming, questions, and member follow-up, simplify the product before adding more software capability.

Validate the first member path

Build a three-scenario revenue model using conservative, expected, and strong membership sales before treating any configuration as final. Walk through it as a new member on desktop and mobile. The test should make it obvious where to begin, how to participate, and what happens next after the first action is complete.

Keep a record of each point where the pilot member hesitates or asks for private help. Those points identify the most valuable improvements to the welcome flow, course organisation, access rules, or event communication.

Protect the commercial model

Calculate the business around actual delivery, not only the listed software fee. Include payment costs, refunds, acquisition spend, preparation time, live delivery, support, and the realistic rate at which members leave. This creates a price and plan choice that can survive a normal month.

Review the figures alongside member behaviour. An attractive acquisition number is less meaningful if customers do not activate or renew. Build a model that rewards a useful ongoing programme rather than a short-lived launch spike.

Use a measured improvement cycle

Pick one change for the next cycle, such as clarifying the start-here path, improving an event format, or removing an unnecessary access rule. Run it long enough to observe the effect on participation and renewal before making the next change.

This approach keeps the member experience stable while the programme improves. It also gives the team a reliable record of what actually creates value, instead of a collection of changes that cannot be connected to results.

A fee model is only useful when it matches retention

For the next thirty days, review your average revenue per member, the actual paid-member base, and the delivery cost behind every subscription. Ask a small group of members to complete a real task and explain, in their own words, what they should do next. Their behaviour will identify friction that a feature list cannot reveal. Capture those observations in a short operating log before changing the programme.

Use net revenue after fees, refunds, acquisition cost, and the time required to serve members as separate measures. A member can buy without activating, activate without participating, and participate without renewing. Looking at these stages independently makes the corrective action clearer. Improve the first weak stage rather than responding with extra content or a new pricing tier.

Set an explicit decision date after the initial test. At that point, compare the expected member experience with the one people actually had, then decide which single change will make the programme more useful. A small documented improvement is more valuable than a broad redesign based on assumptions.

The main risk is upgrading because of a temporary launch spike rather than stable recurring sales. Keep the platform choice tied to real member behaviour and to the work the operator can deliver consistently. That discipline protects both the customer experience and the economics of the community.

Build the operating plan before scaling

For a paid community’s plan selection, begin with the expected recurring revenue and the value retained after all fees. Write the promise in plain language, then map the actions a customer takes between purchase and the first useful result. This sequence should work for a small cohort before you add advanced features, extra categories, or additional sales channels. A clear first experience prevents the platform from becoming a container for unanswered questions.

Document the weekly routine around a financial check against actual sales rather than projected member count. Assign an owner, a deadline, and the expected member action. If a recurring activity cannot be delivered consistently, either simplify it or remove it from the offer. Reliable cadence creates more value than ambitious programming that starts strong and then disappears.

Prepare a short set of member communications: the purchase confirmation, a welcome note, a first-action prompt, an event reminder, and a re-engagement message for people who have not started. These messages should explain the next step rather than merely announce that content exists. That distinction is especially important when the member is busy and has not yet formed a habit.

Track sustainable margin after refunds, delivery, and acquisition separately from raw sign-up volume. A sale is a useful signal, but it does not prove that people understand the offer, use it, or receive enough ongoing value to renew. Review the evidence after each cohort, then improve the weakest point in the path before increasing promotion.

Keep support rules visible. State how billing changes work, where members ask questions, what the group does and does not include, and how live-session access is handled. Clear boundaries make the service easier to operate and reduce the chance that a good-fit customer becomes disappointed by an assumption.

Once the first version is dependable, expand one variable at a time. Test a different price, a new acquisition channel, a second membership tier, or an additional programme only after you can see its effect on activation and retention. This measured approach keeps the member experience coherent while the business grows.

One final operating note

For pricing and plan selection, use monthly recurring sales after refunds and payment costs as the leading signal. It is more reliable than a general sense that the platform feels polished. A decision should make a paying member’s next action clearer and make the team’s recurring work more manageable.

For the next review cycle, compare a rolling three-month average instead of the most exciting month. Keep the offer, price, and member promise stable long enough to see the effect. That produces useful evidence and prevents the programme from changing faster than customers can understand it.

A strong system is not the one with the most settings. It is the one the owner can explain, the team can run consistently, and the member can use without unnecessary friction. Keep that standard visible as the product grows.

Final Verdict

Start on Hobby when you are testing a focused membership and monthly sales are low. Move to Pro when recurring sales are consistently above the fee break-even point and the community has a repeatable renewal engine. Use the platform fee as one input, not as the entire business model.

Want the Store Built and Launched Without the Guesswork?

We handle supplier outreach, the build and the launch, so your hours go into selling rather than configuring software.

See the Done-For-You Build →

Frequently Asked Questions

What is Skool used for?
Skool is used to run a community-centered learning or membership experience where discussions, courses, events, access, and member participation work together in one place.

Is Skool good for a paid community?
It can be a good fit when the paid offer has a clear member outcome and a simple ongoing rhythm. The platform should support the community, not cover up an unclear reason for people to join.

How should I price a Skool community?
Price around the recurring value members receive, the support you can provide, and the cost of operating the programme. Explain what members receive, how often it happens, and how they can manage access.

Do I need a large audience before launching?
You need a defined audience and a useful promise more than a large following. A smaller group of the right members can provide better feedback and retention than a broad launch without clear value.

What should I test before inviting members?
Test payment, onboarding, course access, discussion flow, events, notifications, and support. A simple pilot helps you improve the experience before it reaches a larger paid audience.

If you found this useful, these guides go deeper on related topics:

Trevor Fenner

Trevor Fenner is an ecommerce entrepreneur and the founder of Ecommerce Paradise, a platform focused on helping entrepreneurs build and scale profitable high-ticket ecommerce and dropshipping businesses. With over a decade of hands-on experience, Trevor specializes in high-ticket dropshipping strategy, niche and product selection, supplier recruiting and onboarding, Google & Bing Shopping ads, ecommerce SEO, and systems-driven automation and scaling. Through Ecommerce Paradise, he provides free education via in-depth guides like How to Start High-Ticket Dropshipping, advanced training through the High-Ticket Dropshipping Masterclass, and fully done-for-you turnkey ecommerce services for entrepreneurs who want a faster, more hands-off path to growth. Trevor is known for emphasizing sustainable, real-world ecommerce models over hype-driven tactics, helping store owners build scalable, sellable, and location-independent brands.