In this guide 6 sections
Buy a hosted course platform when your courses are recorded videos, quizzes and one payment per learner. Build custom when cohorts with fixed start dates, instalment plans, verifiable certificates and corporate seat management must work together. Many founders start on a hosted platform and build only the parts it cannot do.
What a hosted course platform does well
Platforms such as Teachable, Thinkific or Kajabi host video lessons, quizzes, drip schedules and a checkout page. Launch takes days, not months. For one instructor selling recorded courses, with no live sessions and no group buyers to manage, that is hard to beat.
The trouble starts when the business stops looking like a shop. A cohort that begins on the first Monday needs a roster, a waitlist and a cut-off after which nobody can join. Most hosted plans treat every course as always open.
Plans usually scale by learner count or by a transaction fee on each sale. Check the plan against two years of expected enrolment, because a modest fee can grow heavy once one corporate client enrols three hundred staff.
- Recorded video lessons with a quiz at the end
- One price, one payment, lifetime access
- Discount codes and an affiliate link
- Completion emails sent on a drip schedule
Where payments and cohorts start to strain
Look at your payment terms first. A learner paying in three instalments should lose access when the second card payment bounces, and regain it when the retry succeeds. Stripe or PayPal webhooks can report that event, yet the platform may have no rule to act on it.
Refunds add another layer. A learner who leaves in week two may owe for the live sessions already attended. A spreadsheet beside the platform copes with ten learners. It fails at two hundred.
Invoices differ by buyer country as well. A learner in Germany, a company in Singapore and a student in Brazil each expect a different layout. A hosted checkout may support only a few of those layouts.
Certificates and corporate clients change the answer
A certificate an employer might check needs a serial number, an issue date, an expiry for recertification and a public lookup page. A PDF with a name typed into a template does not carry that weight.
Corporate buyers bring their own demands. One HR manager buys forty seats, assigns them to staff by email, wants a progress sheet each month and expects an invoice carrying a purchase order number. Few hosted platforms handle seat reassignment when an employee resigns.
Reporting is the quiet deciding factor. Founders want completion by cohort, drop-off by lesson and revenue by corporate account in one view. Hosted dashboards rarely join those three without a monthly export to a spreadsheet.
- Seat blocks that can be reassigned
- Progress report by employee and by course
- Invoice with purchase order reference
- Single sign-on with the client’s staff directory
- Certificate lookup page with expiry reminders
A middle path: buy the shell, build the gaps
Keep the hosted platform for lessons and video delivery. Build a small system beside it for the records the platform handles badly: the cohort roster, the instalment ledger, the certificate register and the corporate account sheet.
Connect the two through the platform’s API or webhooks. Each enrolment event creates a row in your system. Lesson content stays where it is, and only the business rules move.
Build only what has hurt you twice. A gap that appears once is a manual task. A gap that appears every cohort, and eats the same hours each time, is a build.
How to decide this month
List the last ten questions your support inbox could not answer, or that your team fixed by hand. Mark each as a content problem or a records problem. Content problems stay on the platform.
Then ask each shortlisted platform for a trial with your real structure: one cohort, one instalment plan and one corporate buyer with ten seats. Watch where your team starts writing workarounds.
If three or more rows on your sheet need a workaround, price a custom build for those rows only.
Build or buy scoring sheet
List each need on a single sheet: cohort start dates, instalments, refunds, certificate lookup, corporate seats, monthly reports and single sign-on. Four columns follow each need. The first records how the hosted platform handles the need. The second notes the workaround. The third counts the hours that workaround costs each month. The fourth carries a mark for build or buy.
Open a blank worksheet to printQuestions owners ask
Can a hosted platform handle cohorts at all?
Some offer scheduled start dates and drip release, which covers simple cohorts. Waitlists, cut-off dates, batch rosters and attendance for live sessions usually need a separate record. Test one real cohort end to end before you commit, including the day a learner joins late.
When does custom software pay for itself?
When staff spend hours each week on a task the platform cannot do, and that task repeats every cohort. Count those hours before you ask for a quote. Track it as a number: hours of manual work per cohort, multiplied by the hourly cost of the person doing it.
Is a mixed setup hard to maintain?
It is simpler than it sounds if only a few events pass between the two systems, such as enrolment, payment failure and course completion. Keep that list short and documented. Write down who is allowed to change either side, and keep a test enrolment you can run after every platform update.