E-learning platform development.

Selling courses without a platform stalls at the twentieth student

Most courses start out improvised: the recordings sit in a Google Drive folder or an unlisted YouTube playlist, payments arrive by bank transfer, and access is granted manually, by email, when you get to it. For the first ten or so students that works. Then someone forwards the link to a group chat, someone pays on a Saturday and waits for access until Monday, and you no longer know who bought which course or how far they got. Every sale needs your hands, so the course that was meant to be a product becomes a second job.

An e-learning platform does those three things for you: it charges for the course and opens access the same instant, plays the video only for a signed-in student who has paid, and keeps a record of who has watched what. A purchase at ten in the evening goes through without you, and in the morning you see the sales, the new students and how far each group has come. It runs in the browser, on phone and computer, with nothing to install.

It also matters what a platform is not. If you sell your knowledge primarily one on one, through consultations and booked sessions, you need a booking calendar rather than a course platform. An e-learning platform makes sense when you sell the same knowledge many times: recorded once, charged for every time.

Video lessons and access control, not a playlist with a link

A course on a platform is not a folder of recordings but a structure: modules, lessons within them, downloadable materials next to each lesson, a short test after each module. The student always sees where they are, what comes next and how much is left. Lessons can unlock in sequence, only once the previous one is finished, or week by week, which keeps a group's rhythm and reduces the drop-off a third of the way in. You choose those rules per course, not once for the whole site.

The video does not sit on the site's hosting. Hosting is for pages and the database; video needs a streaming service that delivers the recording in multiple resolutions, adapts to connection speed and does not buckle when thirty students press play at once. The platform connects to such a service, and access runs through signed links: the video URL is valid only for the signed-in student and only for a limited time, so a copied address opens nothing once it expires.

An unlisted YouTube link, the most common "protection" we come across, is not access control: whoever gets the link watches, without paying and without a trace. The same goes for shared folders: the download ban on a Drive folder is a checkbox any mildly persistent user gets around. Access control begins only when an account on your platform stands between the student and the video.

Video protection: what is achievable and what is a sales story

First the part you will rarely be told: one hundred percent video protection does not exist. Whatever gets built in, a student can record the screen, and that is where technology stops. This holds even for the expensive DRM systems the big streaming platforms use to protect films, and those films still turn up online the same day. Anyone guaranteeing you complete protection is selling a story.

What is achievable is something else, and it is the goal worth paying for: making sharing inconvenient, unprofitable and visible.

• Signed links that expire, so a forwarded video address does not work.
• Video bound to the platform's domain, so it cannot be embedded on someone else's site.
• A watermark with the student's name or email across the picture: nobody is keen to share a screen recording carrying their own email.
• A limit on simultaneous sessions, so one paid account cannot serve five people at the same time.
• Per-account viewing logs, so an account that "watches" the entire course overnight from three devices gets spotted and shut down.

How much of this to build in depends on the course's price and audience: a broad, affordable course does not justify every measure, while an expensive program for a narrow profession justifies both the watermark and the session limit. The strongest protection sits in the model anyway: a course that keeps growing, with answers from the author and a community of students, is pointless to watch from a pirated copy, because precisely the most valuable part cannot be copied.

Student accounts, progress and a certificate that can be verified

Every student has an account, and the platform remembers completed lessons and test results, so the course continues exactly where it stopped, from any device. As the author you get an overview no spreadsheet gives you: how many students reached which module, on which lesson people give up, and which course gets finished while another is bought and abandoned after the intro module. A lesson where everyone stalls is a lesson to rework, and without a platform you would never know which one it is.

The certificate issues itself: when a student completes every lesson and passes the final test, they receive a PDF with their name, the course title, the date and a unique code, and anyone they show it to can check the code on the platform and see the document has not been altered. Honesty here too: it is confirmation that the student finished your course, not a state-recognized diploma. Whether your field also requires accreditation is a question of your profession's regulations, not of technology.

To be open about it: we do not yet have a course platform under its own name in our portfolio, and we will not claim otherwise. What the portfolio does have are web applications with accounts, roles and status tracking, which is the core of every course platform: Certiwa Portal, a client portal where the client follows the status of every document and the progress towards an audit, with a publicly available demo; Kore, where drivers and management each see their own part of the job; and a clinic system with an account per doctor, minimal role-based access and two-factor authentication. Account, role, status, progress: the same tools, a different vocabulary.

Charging for a course: card opens access instantly, bank transfer once it clears

Card payments run through a bank's payment processor: the student pays and access opens the same instant, which is the main reason cards pay off, because a purchase at ten in the evening must not wait for your morning. We have built that kind of checkout before: a cart and checkout with NestPay integration run in our Demo E-Commerce CMS, which you can try live. Online card payments require a merchant agreement with a bank; the procedure is not complicated, but it takes time, so it starts at the beginning of the project, not just before launch.

Bank transfer is still alive, and that is not a flaw: part of the audience does not pay by card online, and companies often prefer not to. The student receives a pro forma invoice by email with a payment reference, and once the payment clears, you activate access with one click from the panel. Companies get a pro forma and an invoice for multiple seats at once, along with a list of which employees have finished the course: for many authors it is precisely a company that becomes the single largest customer, and that is exactly where off-the-shelf solutions most often fall short.

A one-off course purchase is the simplest model. A monthly subscription for access to all courses requires recurring billing, which not every processor supports, so that gets checked with the bank before choosing the model, not after. And the obligatory disclaimer: we are not accountants, so before you start, check with yours what applies to selling courses online in your country in terms of invoicing and tax. We build the platform so it issues pro forma invoices and purchase confirmations exactly the way your accountant specifies.

WordPress LMS or a custom platform: two routes and what each costs

For a first course and a test of whether demand exists at all, WordPress with an LMS plugin (LearnDash, Tutor LMS and similar) is often the right choice, and we say so openly even though we build custom platforms ourselves. Courses, lessons, quizzes, certificates and WooCommerce checkout all exist ready-made, go live in weeks rather than months, and cost noticeably less. If that covers you, do not pay for more.

The plugin's ceiling shows later, and always in the same three places.

• Special rules. A company buys thirty seats and wants its own report on employee progress, enrollment runs in cohorts with deadlines, moving to the next module has conditions. Everything the plugin never anticipated becomes a fight with someone else's code.
• Student numbers. Once students number in the hundreds, an LMS plugin on shared hosting slows down, and every plugin update becomes a risk for a live system that takes payments.
• Integrations. Connecting to a CRM, pushing data into an email marketing tool, reports the plugin does not offer.

When two of those three appear, the plugin has outgrown its role and a custom platform gets built. In scope it sits in the range of custom web applications, which start from €2,000; the frameworks for all project types are on the pricing page. We deliberately do not print a specific figure for a platform here, because it would be invented: the scope depends decisively on the number of courses, the payment model, the video protection and the integrations. Describe through the contact form what you teach, to whom and how you charge, and we come back with a proposed route, price and timeline, in black and white. The estimate is free and carries no obligation.