Insights · 11 min read
A practical guide to building an online learning platform: the features that matter, what it costs, how long it takes, and what to build first.
By GGP Editorial
A learning platform is one of those projects that looks simple from the outside and gets complicated fast. You upload a video, you charge a student, you track who finished. The demo always looks clean. The hard parts live in the places the demo never shows: how a course stays locked until someone pays, how a video streams without buffering for students on slow connections, how progress is tracked across devices, and how the admin side keeps a hundred instructors from turning the catalog into a mess.
I write this from the vendor side. GlobeSoft is a software company founded in 2018 with 40-plus engineers and more than 300 delivered projects, and we have built enough subscription and content products to know where these projects stall. This guide covers what a learning platform actually needs, what it costs, how long it takes, and what you should build first.
If you are still deciding whether to build at all, our piece on custom software vs SaaS covers the build-versus-buy question in more depth.
The phrase covers three different products, and they have different scopes and different buyers.
A learning management system, or LMS, is the enterprise version. It is built for a company or school to train its own people or students, with structured courses, mandatory assignments, grades, certificates, and compliance reporting. The buyer is an operations or L&D leader who cares about completion rates and audit trails.
A course platform is the creator version. It is built for one expert or a small team to sell courses directly, with a storefront, checkout, and a clean player. The buyer is a creator or coach who cares about selling.
A course marketplace is the platform version. It hosts many instructors and takes a cut, so it needs onboarding, payouts, reviews, and moderation. The buyer is a founder who wants to run the platform business itself.
The three overlap, but they are not the same build. An LMS and a marketplace have almost nothing in common after the video player. Decide which one you are before you write a line of code.
Before you budget a custom build, check whether an off-the-shelf tool already covers you.
Moodle and Canvas are open-source LMS platforms with large communities. Teachable, Thinkific, and Kajabi handle the creator course business out of the box. LearnDash and LifterLMS turn WordPress into a course site. If your needs match one of these products closely, subscribe or self-host and keep your cash.
You should build when one of these is true. You need white-label branding and your own domain and data end to end. The learning product is the business you sell, not a tool you use. You have pricing, packaging, or integration needs the off-the-shelf products will not bend to. Or you plan to grow into something the products cannot become, like a marketplace with your own payout logic or an LMS wired into your own CRM and compliance systems.
The middle path also exists. Run a WordPress or SaaS LMS for the commodity parts and build a thin custom layer for checkout, reporting, or API connections. That keeps the first invoice small and puts your budget into the part that actually differentiates you.
The visible features are the easy ones. Here is a realistic list, split into what you need on day one and what can wait.
| Must have in v1 | Can wait |
|---|---|
| Course authoring and content upload | Gamification and leaderboards |
| Video hosting and streaming | Social feed and community |
| User accounts and login | AI tutoring or chatbots |
| Enrollment and access rules | Advanced analytics |
| Checkout and payments | Offline mobile app |
| Quizzes and assessments | Live class scheduling |
| Progress tracking | SCORM and xAPI imports |
| Certificates | Marketplace with payouts |
| Admin dashboard | Multi-language |
Video is where most teams underestimate the work. Storing and streaming video reliably means encoding, adaptive bitrate, and a CDN, or paying a video provider such as Vimeo or Mux to handle it. You can build the player yourself, but the delivery is usually better left to a service.
Cost in a learning platform is driven by four things, in rough order of impact.
Team. A small senior team of a product manager, a designer, two backend engineers, and one or two frontend or mobile engineers is the typical shape. Where the team sits changes the bill a lot: a senior engineer through a China-based team runs roughly $5,000 to $8,000 a month, against around $12,000 to $16,000 for the same role on a US salary. We cover those numbers in what software development costs in China.
Features. A single-instructor course platform is a smaller build than an enterprise LMS with roles, SCORM, and compliance reporting, which is smaller than a marketplace with multi-vendor payouts.
Media and streaming. Video encoding, storage, and delivery are recurring costs that scale with your catalog and audience, not with your build. They show up in the monthly bill, not the initial quote, and most first-time founders forget to budget them.
Integrations. Payment gateways, CRMs, single sign-on, and analytics tools each add time, and each is a place where scope quietly grows.
As a rough guide, a focused first version built by a small senior team typically lands between $40,000 and $120,000 depending on scope. A single-instructor course platform with checkout and a clean player sits at the low end. An enterprise LMS with roles, integrations, and compliance reporting runs well past that. A marketplace with multi-vendor payouts is its own larger project. Those are ranges, not quotes; the only number that matters is the one from a scoped proposal. We wrote a walk-through on getting a real estimate rather than a guess in how to estimate a custom software project.
A scoped first version usually runs three to six months from kickoff to launch. A single-instructor course platform can land in that window. An enterprise LMS with integrations runs longer, often six to nine months. The spread comes from scope and third-party work, not typing speed. Plan for a round of discovery before anyone writes code, and plan for a soft launch with a handful of real students before you open the doors.
Decide the monetization model early, because it shapes the data model and the checkout.
Subscription. Learners pay a recurring fee for access to the library. This is the cleanest model and the easiest to build well. It rewards a catalog, not a single course.
One-time course sales. Each course is a product with its own price. Simple to build, harder to grow into recurring revenue.
Corporate and B2B licensing. You sell seats or site licenses to companies that train their teams. This usually requires white-label branding, team management, and reporting, which is where the LMS scope comes in.
Marketplace. Instructors sell on your platform and you take a cut. This adds onboarding, payouts, reviews, and moderation, and is the most complex of the four.
Most founders start with one model and add a second later. Pick one and build it properly. Our guide on building a subscription SaaS platform covers the recurring-revenue side in more detail.
Scope the first version down to the shortest path a paying student can walk end to end: find a course, pay for it, watch it, and come back to where they left off. If that loop works, everything else can follow.
Cut these from v1: gamification, a mobile app, an AI tutor, a social feed, and most of the analytics. None of them sell the first hundred seats. What sells the first hundred seats is a course that loads fast, a checkout that does not fail, and a student who can find their place again the next day. Our guide on how to build a SaaS MVP walks through the same trimming logic.
If you sell to individual learners, you build a single storefront with shared course content and per-user progress. Straightforward.
If you sell to companies, you almost always need a multi-tenant design, where each client gets its own branded space, its own users, and its own reporting, with your team managing the whole thing from one admin. That changes the data model and the permissions from the start, and it is expensive to bolt on later. We cover the trade-offs in multi-tenant SaaS architecture.
You do not need to resolve every technical choice up front, but a few of them shape everything else.
Video delivery. Use a hosted provider for encoding and streaming unless you have a strong reason not to. Self-hosting video is a real engineering effort and a monthly cost you should model before you set a price point.
Interoperability. If you are building an LMS that will talk to schools or large employers, plan for SCORM, xAPI, and LTI from the start. They are old, awkward standards, but they are how a lot of corporate and academic content is packaged, and retrofitting them is painful.
Mobile. A responsive web player covers most learners in the first year. Build native mobile apps only when learners tell you they need offline access or push notifications.
AI. The useful AI features in a learning product are narrow: quiz generation, answer grading, a tutor that answers questions about a specific course, and summarization. They are genuinely useful, but they are features to add after the core loop works. If you want to understand where AI actually pays for itself, start with our piece on how to add AI to existing business software.
Building the player before the checkout. You can ship with a decent hosted player. You cannot ship without a checkout that works, and most first-time founders spend their first month polishing video before the payments are wired.
Ignoring the admin side. The student-facing app is the part everyone demos. The admin side is where a small team of instructors gets buried, and it is the part buyers forget to scope.
Under-budgeting streaming. Video delivery is a monthly cost that grows with use. Model it before you commit to a price point.
Treating an LMS as a small app. It is not. Roles, permissions, grading, and reporting are quiet, boring, and necessary, and they are the bulk of the real work.
A focused first version from a small senior team typically lands between $40,000 and $120,000. A single-instructor course platform sits at the low end; an enterprise LMS with integrations and compliance reporting runs higher; a multi-vendor marketplace is a larger project on its own. See where the money goes in a custom build for the full breakdown.
Three to six months for a scoped first version is typical. Enterprise LMS projects with integrations often run six to nine months.
If Moodle covers your needs, use it. It is mature and free to self-host, and it saves you months. Build from scratch when you need white-label branding, a custom checkout, or integrations the platform will not bend to, or when the learning product itself is the business you are selling.
Usually not. A responsive web player covers most learners in the first year. Build the mobile app when learners tell you they need offline access or push notifications, not before.
Ship the shortest paying loop on a lean build, or run a pilot on Teachable or Thinkific first to prove people will pay, then build custom once the demand is proven. Our guide to MVP vs full product covers how to cut scope without cutting the point.
GlobeSoft is a software development company founded in 2018, with 40-plus engineers and more than 300 delivered projects for over 100 clients across the US, Brazil, South Africa, and Singapore. We build custom software, mobile apps, SaaS platforms, FinTech systems, ERP and CRM, and AI products on a stack that includes Java, Spring Boot, Go, Python, React, Vue, and Node.
If you are planning an online learning platform, a course marketplace, or an LMS for your company, talk to us about your project. Send us the rough idea and we will help you scope the first version, estimate the budget, and figure out what to build first.
Tell us what you are building and where you are today. We typically reply within 24 hours.
