How to Sell Courses to Businesses With LifterLMS (B2B Guide)
How to sell courses to businesses with LifterLMS: seats with vouchers or the Groups add-on, invoice and purchase-order payments with the Manual…
Read articleIf you are a WordPress agency or freelancer and a client asks for an online course platform, LifterLMS is a natural fit: it runs on the stack you already know, the core plugin is free, and add-ons cover payments, marketing and advanced learning features. Running it profitably as a LifterLMS agency is another matter. LMS sites carry live payments, student records and recurring billing, and the mistakes cost more than on a brochure site.
This playbook is for agency owners, project managers and developers who build LifterLMS sites for clients. It covers what to ask before you quote, who should own the licenses, a build process you can repeat, how to keep staging from charging real students, and how to hand the site over so the client can run it without calling you for every enrollment.
LMS projects go over budget when requirements surface after the build has started. Ask these in the discovery call:
Then sort every requirement into four buckets: core setting, add-on, custom development, or out of scope. The custom bucket is where your estimate risk sits; price it separately.
Paid LifterLMS add-ons are sold as individual products and as bundles. According to the LifterLMS pricing page at the time of writing, the bundles differ mainly in the add-ons included and the number of active sites: one site, five sites, or unlimited. Staging, development and test sites do not count towards the limit, and a license can be moved by deactivating it on one site and activating it on another. Check the current terms before you advise a client.
The question that causes friction later is ownership. Two models work:
| Model | Advantages | Watch out for |
|---|---|---|
| Client buys the license in their own name | Clean handover, client keeps updates and support if they leave you, no billing for you to manage | Client must renew; lapsed licenses mean no add-on updates |
| Agency uses its own multi-site bundle | One key, one renewal, cheaper per site across many clients | If the client leaves, their add-ons stop updating unless they buy their own license; write this into the contract |
Our default recommendation is that the client owns the license, and you are added as a support user on their account so you can download files and raise tickets. The pricing page describes support accounts on the multi-site bundles that can do exactly that without access to payment details.
Agencies make money on LMS projects by doing the same things the same way each time. A sequence that works:
LifterLMS bundles its WP-CLI commands in core, including commands for licenses and add-ons. A provisioning script saves time on every new build and removes clicks you might forget:
#!/usr/bin/env bash
set -e
# Activate the client's license key on this site.
wp llms license activate "$LLMS_LICENSE_KEY"
# Install and activate the add-ons in scope for this project.
wp llms addon install lifterlms-groups lifterlms-assignments --activate
# Confirm versions for the build log.
wp llms version
wp llms addon list --fields=title,status,version
Add-on slugs vary, so run wp llms addon list once to get the exact names available to the license. The full command reference is in the LifterLMS CLI documentation, and our article on LifterLMS WP-CLI commands covers course and enrollment commands as well.
This is the mistake that generates the angriest client calls. If you copy a live site with active subscriptions to staging, the copy could try to process renewals. LifterLMS protects against this: it stores the site URL, and when it detects that it is running on a different URL it treats the site as a clone and disables automatic recurring payments until someone confirms what to do.
Do not rely on detection alone. On every staging and development copy, add this to wp-config.php:
define( 'LLMS_SITE_IS_CLONE', true );
Also switch gateways to test mode on staging, and disable outbound emails or route them to a mail catcher so students do not receive duplicate notifications. When you move a site to a new domain for go-live, you will need to tell LifterLMS the new URL is the real site. The LifterLMS staging documentation explains the notice and its options, and our guide to staging sites and recurring payments walks through the go-live switch.
Every customization you make is something you maintain. Keep them in places that survive updates and that the next developer can find:
Our guide on customizing LifterLMS without breaking updates goes deeper.
A good handover means the client's team can run courses day to day without administrator access. LifterLMS has roles for that:
| Role | Give it to | What they can do |
|---|---|---|
| LMS Manager | The client's course or operations lead | Run LifterLMS: courses, students, orders, reporting and settings, without full site administration |
| Instructor | Subject experts | Create and manage their own courses and see their students' progress |
| Instructor's Assistant | Markers and support staff | Help on courses they are assigned to |
| Administrator | Your agency and one named client owner | Everything, including plugins and updates |
Instructors and Instructor's Assistants cannot enroll or unenroll students; if the client expects instructors to do that, plan for it. The detail is in our guide to LifterLMS user roles and capabilities.
Include in the handover pack: a short video per routine task (add a lesson, enroll a student, issue a refund, export a report), the list of customizations and overridden templates, the license owner, gateway account owners, and who to call when a payment fails.
LMS sites need more care than brochure sites, which makes a maintenance plan easier to justify. A sensible plan includes plugin and add-on updates tested on staging first, daily backups that include the LifterLMS custom tables, uptime and cron monitoring, a monthly check of failed payments and stuck orders, and a small block of hours for content and configuration help. Our article on a LifterLMS maintenance plan lists what to include.
The pricing page we checked does not describe a dedicated agency plan. Agencies typically use the unlimited-site bundle for their own builds, or have clients buy their own license and add the agency as a support user.
Students see your client's brand, not LifterLMS, on a well-themed site. Admin screens still say LifterLMS. Plan which student-facing emails, labels and pages need your client's wording.
According to LifterLMS, staging, development and test sites are not counted towards the active site limit.
Turn this article into your own checklists: a discovery questionnaire, a build checklist, a go-live checklist and a handover pack. The second LifterLMS project you run with them will take noticeably less time than the first.
When a client needs something outside your usual work, such as a custom payment gateway, a migration with active subscriptions or a bespoke reporting tool, we work with agencies as a specialist partner behind the scenes. See our LifterLMS plugin development and LifterLMS support services, or send us the client brief and we will tell you how we can help.
How to sell courses to businesses with LifterLMS: seats with vouchers or the Groups add-on, invoice and purchase-order payments with the Manual…
Read article
A practical plan to reduce membership churn on LifterLMS: recover failed payments with automatic retries and reminders, keep members engaged, handle…
Read article
How LifterLMS currency settings work, why there is one store currency, what Stripe, PayPal and manual payments mean for international buyers, and…
Read articleSkip the trial and error. Get specialist LifterLMS help and ship faster.