Buying workflows
Selling training seats to companies: the buyer-to-learner workflow

Selling seats to a company is four roles, not one checkout. A buyer signs and pays, a client manager allocates and replaces people, learners get invited and complete, and your admin reports back. Vendors blur three separate things: the purchase order and invoice, the payment, and the seat allocation. Get all three clear before you promise a company anything, because a course store is not a seat-selling platform.
Walk the path with named roles
Follow one deal from signature to report. Each handoff is where platforms differ.
- Buyer (procurement or L&D): signs the contract and pays. Wants an invoice, maybe a purchase order, and a clean receipt. Does not use the courses.
- Client manager: allocates seats to named employees, replaces someone who leaves, resends invitations that were ignored. Runs their people without touching yours.
- Learner: receives an invitation, claims a seat, completes the course. Should never see billing.
- Your admin: reports completion back to the buyer, flags outstanding learners, exports the record the client asked for.
If any handoff forces you to do the client manager's job by hand for every employee change, the platform is selling you a course store dressed as a seat system.
Three things vendors blur
Separate these before a demo, because a single word like sell hides all three.
- Purchase order and invoicing: can you issue an invoice the buyer's finance team will accept, against a PO? Thinkific opens invoicing along with group and B2B selling at Grow. Confirm the invoice format meets your buyer's requirements.
- Payment: how the money actually arrives, card, bank transfer, or an offline invoice paid later, is a separate question from allocation. A platform can take a card and still not manage seats.
- Seat allocation: the client manager assigning, removing and replacing named learners. This is the feature that distinguishes B2B platforms.
What each platform publishes
From the registry, seat-selling capability is documented on some platforms and simply absent from others' published grids.
- Thinkific: group and B2B selling plus invoicing from the Grow plan.
- LearnWorlds: client groups from Pro Trainer (one group) and Learning Center (up to ten groups), which support selling seats to companies.
- LearnDash Elite: group course management and seat selling inside your own WordPress site.
- Teachable and Podia: publish no group or seat-selling workflow. Treat B2B seat sales as absent unless sales confirms otherwise.
| What you need separate | Thinkific | LearnWorlds |
|---|---|---|
| Custom branding per client | Partial, shared school Branding removal from Grow applies to one school, one brand. Per-client branding is a Plus conversation. | Partial, shared school Full white label from Learning Center covers your school; client groups share that brand unless you go Corporate. |
| Custom domain per client | Partial, shared school One custom domain per school. Per-client domains are not published below Plus. | Partial, shared school One school domain; per-group domains are not published. |
| Separate catalog per client | Partial, shared school Group selling from Grow shares one catalog; you scope access, not the catalog itself. | Partial, shared school Client groups (1 on Pro Trainer, up to 10 on Learning Center) receive assigned courses from one catalog. |
| Separate user pool per client | Partial, shared school Groups segment one shared student base inside the school. | Partial, shared school Groups are segments of one user base, not separate schools. |
| Client admin rights | Not published, ask in a demo Delegated client-admin rights below Plus are not documented publicly. | Not published, ask in a demo Per-group admin delegation is not itemized publicly. |
| Separated client data | Not published, ask in a demo No public commitment on per-client data separation; confirm the multi-account scenario in a demo. | Not published, ask in a demo No public isolation commitment; verify cross-group access with test accounts in a demo. |
Count the manual actions during a trial
Do not take our word on effort, and do not trust a feature label. During a trial, run the real motions yourself and count how many manual steps each takes. We have not measured timings, so measure them on your own account.
- Invite twenty fictional learners as a client manager would. Count the steps.
- Replace one learner with another mid-contract. Note whether the seat frees cleanly.
- Resend an invitation that was never claimed. Check it is one action, not a rebuild.
- Export a completion report the buyer would accept. Open it and check the fields.
Recurring pains show up here. Seat replacement mid-contract is the classic one: can the manager swap an employee without paying for a new seat? Unclaimed invitations pile up and skew your completion numbers. And the worst surprise is the client asking for a report your platform cannot export. Find all three in the trial, on fictional data, not in month two of a real contract.
Once the deal is signed, the next step is the client manager's side: how a client manager assigns seats and sees progress without full admin access, platform by platform.
Frequently asked questions
Which platforms actually sell seats to companies?
Can a client manager replace a learner mid-contract?
Do Teachable or Podia support B2B seat sales?
What report should I be able to give the buyer?
Keep deciding
From seat assignment to reporting: the client manager's side of a B2B deal
After a B2B seat sale: who assigns seats, which client role sees progress without full admin access, and what five LMS platforms document.
Running a B2B training account: onboarding to reporting
Run a B2B training account after the sale: kickoff data, invitation waves, tracking completion without nagging, the monthly client report, and renewal signals.
Best LMS for a training company selling to businesses
Selling training seats to companies? A grid that separates seats, client autonomy, per-client reporting and data separation across the main platforms.
White label LMS versus client portals: what is actually separate?
White label hides the platform's brand. A client portal separates catalog, users, admins and data per client. The matrix shows what each platform publishes.
SSO and client admin access: a procurement checklist
SSO, provisioning and delegated rights are three different things vendors blur. A procurement questionnaire and the demo scenario to demand before you sign.