WPComfy Tell us about your site
  1. WPComfy
  2. Course platforms

WordPress care for online course platforms.

Your courses are sold, accessed and taught on one WordPress site. We keep LearnDash, LifterLMS or Tutor LMS up to date, watch the path from payment to the first lesson, and give you developer hours for whatever the school needs next.

Ask about your platform Read the Edu-Dutch case study

Why course sites need more

A course site can take the payment and still lose the student.

An LMS ties together payments, accounts, enrolment, lessons, quizzes, certificates and emails. Each plugin has its own release schedule, and problems usually reach you as a student who can’t get in, not as an error message.

Paid, but no access

An order status, a payment method or an automation that doesn’t fire can leave a paying student without an account or a course.

One update, many moving parts

The LMS, its add-ons, the payment plugin and the theme all touch lessons and progress. A careless update can break course structure or student records.

Logged-in students are heavy

Page caching barely helps signed-in learners. When a cohort logs in at once, a small hosting plan can run short of memory, however much disk space it has.

From our work

A language school’s LearnDash platform, looked after since launch.

Hosting chosen around the school’s plans, a recovery from an earlier backup, access fixes from payment to course, and custom reports for company clients.

What we look after

The whole journey, from checkout to certificate.

The care routine keeps the platform safe and current. Developer hours cover the fixes and features that keep it useful.

  1. 01Updates in orderLMS, add-ons, payments and theme, with a fresh backup first. Major releases are tried on staging.
  2. 02Enrolment checksA test purchase through to course access, on staging or in test mode, on a schedule agreed in the review.
  3. 03Student emailsWelcome, password and purchase emails, and how they are delivered.
  4. 04Speed for learnersLesson pages and the student area on a phone, plus hosting that fits your cohorts.
  5. 05What’s nextReports, bookings, integrations and UX improvements, planned within your hours.

Which plan

It depends on how you sell your courses.

Both plans include the full care routine, analytics reviews and a direct line to the developer. The difference is the checkout and the time each needs.

Studio

Payments in your LMS

€400/ month

For platforms that take payments through the LMS itself, for example LearnDash with Stripe.

  • Everything in Essential
  • 8 total support and development hours per month
  • Monthly GA4/Clarity review
  • Enrolment checks planned within your hours

The analytics review uses up to one hour from the monthly pool.

Choose Studio

Commerce

Sold via WooCommerce

€975/ month

For schools selling courses, bundles or memberships through WooCommerce.

  • Essential maintenance plus Studio analytics
  • WooCommerce care
  • 20 total support and development hours per month
  • Purchase-flow check through to course access, when a safe test setup is available

Analytics uses up to one included hour. Checkout testing requires a safe test setup.

Choose Commerce

Monthly prices in EUR, per website. Managed hosting can be added: +€15/month with Studio, +€25/month with Commerce. Compare all plans

Before care begins

We review the platform first.

Every school is set up differently. Before regular care starts we look at how yours actually works, recommend Studio or Commerce, and tell you about anything that needs fixing first.

Ask for a platform review
  • LMS and add-onsThe course plugin, quizzes, certificates, drip content and anything built on top.
  • Payments and enrolmentWhere access is granted: order statuses, automations, coupons and test-mode options.
  • Student emailsAccount, purchase and course emails, and the service that sends them.
  • IntegrationsVideo hosting, bookings, CRM, invoicing and analytics connected to the platform.
  • HostingMemory and PHP capacity for logged-in students, backups and staging.
  • Existing problemsAnything broken today is quoted separately, before the plan starts.

Course platform FAQ

Questions course creators ask.

Running something unusual — memberships, cohorts, company training? Tell us about it.

Ask about your platform
Which LMS plugins do you work with?

WordPress course platforms built with plugins such as LearnDash, LifterLMS or Tutor LMS, often alongside WooCommerce or a membership plugin. We review your exact setup before care starts, so the plan reflects the plugins you actually run.

Why Studio for some course sites and Commerce for others?

If payments run through the LMS itself, Studio’s care routine and 8 monthly hours usually fit. If you sell through WooCommerce, the store needs WooCommerce care, purchase-flow testing and more time, which is what Commerce includes.

Will you test enrolments on my live site?

Not with real payments. We use a staging copy or your gateway’s test mode, with a test account that is removed afterwards. How often we test is agreed during the platform review.

A student paid but can’t access the course. Can you help?

Yes. We trace it through the order, the enrolment and the emails, fix the affected accounts and deal with the cause. On a plan, that work uses your included hours; before a plan starts, it’s quoted separately.

Can you build new features, like reports or bookings?

Yes. Smaller features fit into your monthly hours. Larger ones are estimated first, and you decide whether to schedule them within the plan or approve a separate quote.

Can you take over a platform you didn’t build?

Yes, that’s the usual case. We review it first and quote any cleanup separately, so care starts from a known, working state.

Comfy unlocking a padlock with a golden key

Let’s keep your students learning.

Send your platform URL and tell us which LMS and payment setup it runs. We’ll review it and recommend Studio or Commerce before you commit.

Tell us about your platform