Skip to content
Learnomy
Get Learnomy Pro

Industry playbook

How to Build a Customer Academy for Your SaaS Product

To build a customer academy for a SaaS product, publish product training as courses on your own domain, make them free or tie access to a plan or account status inside your app, enroll customers automatically when your app decides they qualify, and give finishers a badge they can share. Learnomy covers the courses, the access rules, the incoming and outgoing webhooks and the credentials. Your product data decides whether the academy pays off.

How to See Each Student's Learning Journey in Learnomy3:18Chapters and transcript

Watch it on a real seeded site, or read the steps below. More video tutorials →

This page is for the person running product training or customer education at a software company. Customers learn how to use the product, enrollment is driven by what happens in the app rather than by a checkout on a training site, and a completion badge is worth showing off. Nobody pays you directly for a course. The training supports the product.

Key points

  • Make training Free if any signed-in customer can take it, or Closed if access should follow a plan or account status in your app.
  • Use the incoming access webhook to grant and revoke access the moment your app changes a customer's status.
  • Use Open Badges for a portable, verifiable badge on LinkedIn. Add Credly only if your customers' employers expect it there.
  • Keep only the training courses private, and leave the rest of your marketing site public.
  • Send completion events to your CRM, then compare trained and untrained accounts on a product metric.

This is Run an invite-only private classroom with Learnomy and Run a certification body with Learnomy with some adjustments. Read both for the full walkthroughs. This page covers what a SaaS customer academy does differently.

How do you build a customer academy for a SaaS product?

Start from the customer's first week and work outward.

  1. Find where customers get stuck. Support tickets, onboarding calls and cancellation reasons all point at the lessons worth writing first. Don't write a course for every feature.
  2. Pick one outcome per course. "Set up your first workflow" is a course. "Everything about the product" is a library.
  3. Keep lessons short. A task-focused lesson with a short video or annotated screenshots and a clear next step beats a long lecture.
  4. Decide who gets in. Everyone, or only customers on certain plans. See below.
  5. Decide how customers arrive. A link in the product, an email after signup, a button in the help center. Plan the entry points before you build.
  6. Decide what finishing earns. A certificate, a badge, a tag in your CRM, or all three.
  7. Choose one metric. Activation, support tickets, feature adoption or renewal. Pick one before you start, so you know what you're testing.
  8. Pilot with one course. Ship the course that addresses your top support topic, then measure.

If your product changes often, plan for maintenance. Out-of-date training erodes trust faster than no training. Give each course an owner and a review date.

What's different for a SaaS customer academy

  1. Pricing model: free training, or access tied to the product. Run an invite-only classroom, Phase 1, lists invite only, closed, free and the five paid models. A product academy typically wants Free: any signed-in customer can self-enroll with no payment, since the training itself isn't the product. Pick Closed instead when access should follow a paid tier or an account status inside your own app rather than being open to anyone who signs up, for example training reserved for customers on a specific plan. See Closed Course Pricing.

  2. Enrolling a customer from inside the app. For a Closed academy, the app needs a way to grant access the moment it decides a customer qualifies. Learnomy gives you two mechanisms, and they answer different questions:

    • The incoming access webhook. Your app sends one signed POST to /wp-json/learnomy/v1/webhooks/enrollment with op: grant, the customer's user_email, the course as item_id, a purchase_type of course and an external_ref such as your account or subscription ID. Sending op: revoke with the same external_ref takes that access back, for a downgrade or a cancellation. The request is signed with the secret from Learnomy Settings > Webhooks, and Learnomy creates the account if the person doesn't have one. It records access only: no sale, receipt or commission is written. Pick this for event-driven enrollment, since your app already knows the moment eligibility changes.
    • The admin bulk-enroll REST route. POST /learnomy/v1/admin/courses/{id}/bulk-enroll takes a batch of emails and enrolls (or invites) each one, admin-only. Pick this for a scheduled sync, such as a nightly job that reconciles your customer list against the academy, rather than a real-time reaction to a single event.

    A SaaS company wiring training into its own signup or upgrade flow usually wants the webhook. Always send external_ref, so a retry grants once. See Incoming Access Webhook and Bulk Enroll from a List.

  3. A certification badge worth sharing. Run a certification body, Phase 4, covers three credential forms that stack: PDF, Open Badges 3.0 and a Credly push. A product academy's badge is usually Open Badges: once the Open Badges extension is active it needs no setup beyond issuing the certificate, and it gives the customer a portable, machine-verifiable credential they can add to LinkedIn. That's the natural way a customer shows off "Certified [Your Product] User". Add Credly on top only if your industry's employers already expect credentials to show up there. It's the one form of the three that needs you to connect an external account.

  4. Keeping training off the public catalog. Run an invite-only classroom, Phase 2, covers per-course Visibility versus the site-wide Require login for all course content toggle. A SaaS company's main site is usually public marketing content, so the right choice is per-course Visibility: Private on the training courses only, not the site-wide toggle. A logged-out visitor gets a plain not-found result for the training course while the rest of the site stays reachable.

  5. Telling the rest of your stack when training happens. Two more integrations point the other direction from the incoming webhook in item 2, notifying your CRM or backend instead of receiving from it:

    • Outgoing webhooks. At Learnomy Settings > Webhooks, add a delivery URL and subscribe it to events such as course completion or certificate issued. Learnomy POSTs a signed JSON payload the moment the event fires, so your own backend or Zapier hears about it in real time. Up to 3 outgoing webhooks work without extras. A webhooks extension lifts that limit, covers 140+ events and adds retries and a delivery log.
    • WP Fusion. If your CRM connects through WP Fusion, the bridge writes Learnomy tags back to the contact record as a customer enrolls, completes a course or earns a certificate, and can also grant course access from a CRM tag the other way. It auto-enables once WP Fusion is active, with no separate toggle.

    A SaaS company usually wants both: the outgoing webhook for a real-time backend reaction, WP Fusion when the CRM itself should reflect training progress. See Outgoing Webhooks and WP Fusion.

How do customers get from your product to the academy?

A good academy has more than one front door, and each can land the customer on a specific course.

  • A link in the product. Place a "Learn how" link on the screen where customers get stuck, pointing at the course or the lesson that fixes it.
  • A welcome email. After signup, send a short email with one link to the first course.
  • The help center. Link from articles to the matching lesson. Support teams can paste the link into replies.
  • An automatic grant. For a Closed academy, your app grants access when the account qualifies, and the customer sees the course in their dashboard.

Learnomy sends one "Your access is ready" email per grant, which lists what the person got and, if the grant created their account, includes a Set your password button. You can turn that email off under Learnomy Settings > Emails, for example when your own product already sends one.

Decide how the customer logs in. Learnomy has its own accounts, so a customer needs a login on the academy. The grant creates the account from their email, and the set-password email gets them in. Don't promise a smooth handoff from your product login unless you've built and tested one yourself.

Measuring whether the academy pays off

Completion rate is the number every LMS shows first, and for a customer academy it's the least useful one on its own. A customer who finishes every lesson and still opens three tickets a week didn't get what you built the academy for. The questions that justify the budget are about the product: do trained accounts activate faster, file fewer tickets, adopt the feature the course covers and renew more often?

Learnomy can't answer those by itself, because the answers live in your product analytics, help desk and billing system. What it gives you is the training side of the join, per person:

  • Who enrolled, who finished and who passed. Course reports and the student lists show this, and both export to CSV.
  • Events as they happen. Outgoing webhooks fire on enrolment, lesson and course completion, quiz results and certificates, so your CRM or data warehouse can tag the account the moment a customer finishes. See Outgoing Webhooks.
  • Trends over time. Learnomy adds analytics for enrolments, completions and revenue by period.

A simple setup that works: send course completion to your CRM as a tag or property on the customer's account, then compare trained and untrained accounts on ticket volume and renewal after a quarter. Pick one course and one product metric to start, rather than trying to prove the whole academy at once.

Be careful with causation. Customers who take training are often the ones who were already going to succeed. A fair comparison matches accounts by plan and size, or tests a nudge on a random half of new signups.

What does it cost to run a customer academy?

Your costs are hosting, a domain and the Learnomy licence (see the pricing page). If training is free, there's no payment processor fee. Learnomy has no per-learner fee and takes no share of anything you charge, so a customer base that grows doesn't raise the licence. The time to produce and update the content is the larger cost. Add an SMTP plugin so access emails arrive, and if you send webhooks, plan a little engineering time to sign requests and handle retries. For the full list, see how much it costs to run a WordPress course site.

If you have a hosted customer-education platform today, compare before you move. Hosted platforms can win on built-in in-app widgets and managed hosting, and you'd be taking on a WordPress site. See self-hosted versus hosted platforms.

What mistakes do SaaS academies make?

  • Building a course per feature. Start from customer problems.
  • Making all training public. If it should follow a plan, use Closed and the webhook.
  • Using the site-wide private toggle on a marketing site. Hide only the training courses.
  • Forgetting external_ref. A retry without it can grant twice.
  • Not revoking access. Send op: revoke when a plan is downgraded or cancelled, or customers keep access you meant to remove.
  • Measuring completion alone. Tie it to a product metric.
  • Letting content go stale. Assign owners and review dates.
  • Skipping the test account. Run the whole path as a customer: signup, grant, email, course, badge.

A launch checklist

  1. The first course targets your top support topic and has one clear outcome.
  2. Pricing is Free or Closed, chosen on purpose.
  3. Per-course Visibility: Private is set on the training courses.
  4. The incoming webhook secret is created, requests are signed, and a Send test grant worked.
  5. external_ref is sent on every grant and revoke.
  6. The certificate template is designed and the Open Badges extension is active, if you want a shareable badge.
  7. Outgoing webhooks or WP Fusion send completion to your CRM.
  8. A product metric is chosen and a baseline recorded.
  9. An SMTP plugin is installed and the access email arrives.
  10. You've walked the full path as a test customer.

What this can't do

  • It doesn't embed inside your product as a widget. You link to the academy.
  • It doesn't share your product's login. Customers have an academy account, created from their email.
  • It doesn't tell you whether training changed a product metric. Your analytics do.
  • It doesn't write the courses. Your team knows the product.

Frequently asked questions

Can we sell some courses and give others away? Yes. Pricing is per course, so a free onboarding course and a paid advanced one can live together.

Can a customer's access end when they cancel? Yes. Send op: revoke with the same external_ref when your app cancels or downgrades.

Can customers get a LinkedIn badge? Yes, with Open Badges. The certificate carries a public verification page, and a LinkedIn share link.

Can we use a custom domain? Yes. The academy runs on your WordPress site, so you choose the domain. A subdomain such as learn.yourproduct.com is a common choice.

Can partners or resellers take the training? Yes. Use a separate course, or a Learning Space if a partner manages its own people.

Keep reading

Build this on your own site

Everything above runs on your WordPress server. Everything here is part of Learnomy.

Sandbox demo

Try it on a live demo academy

Enter your name and email and we build you a private copy of the Learnomy demo site. Nothing to install, nobody else sees what you change, and the copy lasts about four hours.

Prefer to watch first? See the tutorials.

What to try in the demo

  1. Open Learnomy Settings > Webhooks and look at the Incoming access panel for the endpoint URL and signing secret.
  2. Open a course, then Pricing and Access, and compare Free with Access granted externally (no on-site checkout).
  3. Open Learnomy > Certificates to see issued certificates and the public verification link each one carries.

What customers say on Trustpilot

Prompt and Professional Support

I recently had a fantastic experience with the Wbcom Designs support team. They were incredibly prompt, warm, patient, and friendly as they helped me resolve an issue with my website. I truly appreciate the complexity of troubleshooting website-related issues, as each one is unique, and users often…

Boris PetrovTH