Your course platform breaks when the buyer becomes an organisation

The break is structural, not a missing feature. Kajabi, Teachable and the platforms around them are built on one account with one audience: a list of individual people who each bought something from you. An organisation is not a list of individuals. It has an administrator who is not you, its own branding, usually its own domain, and someone who wants a completion report before they renew. No amount of tagging turns a customer list into that.

The moment it changes

The first organisational deal rarely announces itself. Someone from a training department buys twelve seats, pays by invoice rather than card, and everything looks normal for a fortnight. Then three questions arrive, usually in the same email.

• Can our L&D manager have a login that shows our twelve people and nobody else's?
• Can the course pages carry our logo instead of yours?
• Can you send us a completion report each quarter, or better, can we pull it ourselves?

Each of those asks for something the platform does not model. Not a feature it is missing, a shape it does not have. In a creator platform a learner record hangs off your account. There is nothing in between for the organisation to be. So the organisation gets simulated, and the simulation is where the work starts.

The three workarounds, and where each one stops

Almost everyone tries the same three, roughly in this order.

One account per client

The cleanest-looking option. Client two gets their own account, their own branding, their own admin. It works, and it keeps working until about the third or fourth client. Then two things happen together. Subscriptions multiply — Kajabi's published pricing starts at $71 a month billed annually and rises through tiers at $143, $199 and $399, so five clients means five bills at whichever tier you need. And the content forks: a correction to module 4 has to be made five times, and by the second quarter the five copies are not the same course any more.

It fails on content maintenance rather than on price. Price is annoying. Drift is dangerous, because it is silent — nobody notices that Client Three has been taught the old procedure until someone asks why their certificate says something different.

Tags and segments in one account

Keeps the content single, which fixes the worse problem, and it survives longer than people expect. Every buyer is tagged with their company; reports get filtered by tag. It dies on one specific request: the client's manager wants a login. A tag describes a person. It does not describe who may see whom. You cannot hand out a tag as a permission, so the manager either gets your admin login — which shows every other client — or gets nothing, and you become their reporting department by hand, permanently.

There is a quieter failure underneath it. In a single member list, an export is one wrong filter away from showing Client One the names of everyone at Client Two. That is not hypothetical for anybody who has sent a CSV in a hurry.

The spreadsheet of who belongs to whom

Whatever the platform will not record ends up here, and this sheet quietly becomes the system of record.

learner_email,client_org,seats_paid,course,started,completed,cert_sent
a.person@client-one.example,Client One,12,Fire Safety L2,2026-03-04,2026-03-19,yes
b.person@client-one.example,Client One,12,Fire Safety L2,2026-03-04,,chase
c.person@client-two.example,Client Two,6,Fire Safety L2,2026-04-11,2026-05-02,yes

The columns that matter are exactly the ones the platform has no field for: which organisation, how many seats they paid for, and who still needs chasing. Once the real membership map lives outside the platform, every number the platform reports has to be joined by hand before anyone can act on it. The sheet fails at renewal, or on the day whoever maintains it is on leave — the two worst days available.

All three break at roughly the same threshold, and the threshold has nothing to do with learner numbers. A creator platform will happily hold ten thousand of your own customers. It struggles with sixty learners split across four companies, because the difficulty is administrative rather than technical.

What the organisation is actually asking for

Strip the politeness out of those emails and the list is short, and it is the same list every time.

• An administrator on their side who can add and remove their own people, and who sees only their own people.
• Their name and logo on the pages their staff use, and often their own domain.
• Groups inside the organisation — by department, site, intake — because a 400-person client is not one audience either.
• A record of who completed what, and when, that they can export without asking you.
• Certificates that name the organisation and that a third party can verify.
• Seats they can move to someone else when a person leaves.
• A boundary they can point at in a procurement questionnaire: whose data is separate from whose, and enforced how.

None of that is exotic and none of it is about teaching. It is administration: who may see whom, who may act on whose behalf, whose name is on the certificate. Creator platforms answer those questions once, for you, because that was the right design for their buyer.

The last item is the one creators underestimate. Once a client is large enough to have a procurement process, somebody will ask how another client's data is kept separate. We filter by tag is a true answer that does not survive the follow-up question.

What creator platforms genuinely do better

For selling to individuals, these platforms beat anything built for institutions, and it is not close.

They sell. A buying flow with order bumps, upsells, affiliate tracking, abandoned-cart email and a landing page you can change without a deployment is a serious piece of engineering, and institutional platforms have nothing like it. Kajabi's published pricing carries no transaction fee. Teachable acts as merchant of record, which means it handles sales tax and VAT for you — a real burden removed — from $29 a month billed annually, with a 7.5% transaction fee on its Starter plan.

An institutional platform gives you tenants, roles, grading queues and audit logs, and usually no checkout worth the name. Those are answers to different questions. If most of your revenue is individuals paying by card, stay where you are. Trading a system that sells for a system that administers, and losing revenue to make your reporting tidier, is a bad trade.

The arrangement that works for a lot of academies is two systems on purpose: consumer sales stay on the creator platform, organisational contracts move somewhere with tenants. That is not indecision. The two halves have different buyers, different price points and different renewal conversations.

A five-question test

Answer these about the last ninety days, not about your plans.

1. Has anyone outside your own team needed an administrator login?
2. Has a buyer needed to see their own people and specifically not everyone else's?
3. Has anyone asked for their logo, their domain, or their name on the certificate?
4. Do you get paid by invoice more often than by card?
5. Do you re-key completion data into a spreadsheet or a slide before a renewal call?

One or two yeses: keep the workarounds, keep them tidy, and write down who maintains the sheet. Four or five: the platform has become the thing generating your admin work, and that work grows faster than the revenue does, because every new client adds a full set of it rather than a share of one.

If you move, move early

The shape you would be moving to is unglamorous. Content is authored once and lives in one library. Organisations sit underneath the platform, each with its own members, branding and administrators. People get roles rather than tags, and a role means something enforceable: this person may see this organisation's learners and no others. Reporting is scoped by organisation by default, so a client admin pulling their own numbers is the normal path rather than a favour you do on a Friday.

Lurno is built on that shape. Organisations nest, so a client with three sites is one tenant with three branches under it, and a role granted at a branch cascades down it. A corporate academy can run training for 15 client companies from a single tenant. Each organisation can carry its own branding and its own custom domain with automatic TLS, so a client's staff need never see your name. Separation between organisations is enforced underneath the platform — a cross-organisation read is refused there, rather than by the screens on top remembering to filter.

The plain limitation, said here rather than buried: payments and checkout are in development, and so is self-serve signup — accounts are created by invitation today. For organisational sales that is often survivable, because companies buy by invoice and purchase order anyway. For card sales to individuals at the moment of impulse it is not, and Lurno does not replace a creator platform's checkout yet. If both halves of your business are real, run both and be deliberate about which one owns what.

The operational side of the change — what stops landing on your desk once a client's admin can do their own work — is written up for training providers. If Kajabi specifically is where you are today, the comparison page covers what carries across and what does not.

Two things get more expensive the longer you leave this. The migration, which grows with your library and your learner history. And the sentence you have to say to a buyer who asked for their own admin login and got a spreadsheet instead. The first is a project. The second costs deals.