You already have the customers: you're missing the customer area (courses, files, renewals) and you're leaving money to Teachable and company

The customers are there, the digital product is not

There is a category of companies and professionals sitting on a treasure without knowing it. They already have the customers. They have a list, an audience, a community, a base of people who trust them and who buy. A trainer with thousands of students. A company selling a method. A consultant with a following. A firm providing refresher courses. A manufacturer who wants to train their resellers. The audience is there, and that’s the hard part — building trust takes years. What’s missing is the digital product around which to revolve that trust: a place where customers log in, access content, renew, stay.

Today, almost always, that place is rented. It’s an American platform — Teachable, Kajabi, Thinkific, Podia, one of many — where you have uploaded the courses, where customers log in, where payments go through. It works, it’s set up quickly, it allowed you to start. But there is a price you pay every month that goes beyond the subscription: that platform takes a cut of your revenue, keeps your customers inside its house, and owns the data of the relationship you’ve built. You did the hard work — the audience — and they collect the rent.

This article is for those who already have customers and feel that the customer restricted area on a ready-made platform is getting tight: for the margin it leaves, for the limits it encounters, for the feeling of not truly being the master of one’s own house. Let’s look at what a restricted area really does (it’s more than “a place where I put videos”), make an honest comparison on the margin between a ready-made platform and a custom solution, and — because I want to be fair — also see when staying on the platform is the right choice. Because switching to custom makes sense under certain conditions, and before those it’s a waste.

What a real customer area does

First of all let’s clear up a misunderstanding. A restricted area is not “a password-protected folder with videos inside”. If it were only that, a shared drive would be enough. A restricted area worth its salt as a product is a small software that manages a relationship over time, and has four pillars.

Users and access. Who has logged in, who can see what, who has paid and who hasn’t. Not all subscribers have access to everything: there are those who bought the basic course and those the complete package, those on trial and those who have been customers for years. The area knows, for each person, exactly what they are entitled to — and shows it to them, hiding the rest.

Deadlines and subscriptions. If you sell by subscription or with timed access, the heart is the deadline: when it ends, what happens, how it renews. A serious area knows that John’s access expires on the 15th, sends him the invitation to renew in time, and if he doesn’t renew gracefully suspends his access (it doesn’t kick him out brutally, but neither does it leave everything open forever). This piece — managing the subscriber lifecycle — is where money is made or lost.

Content and files. The videos, PDFs, audios, materials. With their permissions (who sees what), their organization (paths, modules, levels), and their protection (so they don’t end up all over the internet the next day). Managing heavy content — videos especially — well and safely is not trivial, and I’ll come back to this.

Payments and renewals. The initial collection and, above all, the recurring ones. The card that renews, the one that expires, the reminder when a payment fails. In a subscription business, health is made by the renewal, not the first sale — and the restricted area is the place where the renewal lives or dies.

Put together, these four pillars make it clear that a restricted area is, in fact, a close cousin of the B2B portal customers use to order: the same discipline of identity, permissions and state, applied to content and subscriptions instead of orders. And as with the portal, the value is not “having a login”: it’s managing well a relationship that’s worth money over time.

Minimum features: where to start without inflating

A frequent mistake, when building a custom area, is wanting it “complete” right away: gamification, forums, certificates, dedicated mobile app, a thousand functions. It’s the best way to make the project last a year and spend triple. The truth is that a working restricted area starts from a few essential functions, the ones covering the customer’s lifecycle, and grows later, when real customers tell you what’s really needed.

Here are the minimum features to start from, in order of priority:

Registration/login and password recovery. Obvious, but it must be done well: getting in must be simple, and forgetting a password shouldn’t be a drama making you lose a customer.
The content catalog with permissions. The courses/modules, with the rule of who sees what based on what they bought. The core.
The content player with progress. Videos/PDFs that start well, and the “where we left off” bringing the customer back to the right point.
Initial payment and subscription. Buying and activating access, with the deadline managed.
Automatic renewal and reminders. The function that pays for everything: warning before expiration, managing the card that fails, recovering those about to leave.
The customer’s personal dashboard. What I have, what’s expiring, what’s new. The screen they see as soon as they log in.

Everything else — community, certificates, gamification, quizzes, native apps — is “nice to have” and is added later, if and when needed, based on what real customers ask for. Starting from these six things, doing them very well, and launching: it’s the way to have a live area in a few months instead of an endless construction site. The same logic of “five screens, not fifty” that applies to internal apps — fewer functions done well beat many functions done halfway.

The math: how much the platform takes from you

Let’s get to the economic reason, because that’s what makes the difference. Ready-made platforms have a model that seems cheap at the beginning and becomes expensive as you grow, and it’s designed exactly like that. There are three ways they take margin from you.

The percentage on transactions. Many platforms, especially in accessible plans, keep a percentage on every sale — sometimes several percentage points, in addition to payment fees. It seems like little as long as revenue is small. But let’s do the math: if you make 200,000 € a year in courses and the platform keeps even just 5% between platform fees and surcharges, that’s 10,000 € a year. Every year. Forever. On a growing business, that percentage quickly becomes more than the cost of having built your own area.

The tiered subscription. The “serious” plans — those without transaction fees, or with more features — cost hundreds of euros a month. And the more you grow (more subscribers, more content, more features), the higher you go in the plan. It’s a cost that increases precisely when you are doing well, meaning when it hurts most.

The hidden cost: data and relationship. This isn’t on the invoice, but it’s the biggest. On the platform, your customers are their customers. The emails, the behaviors, who watches what, who is about to cancel: those data live in someone else’s house, and you only have a partial view of them. If tomorrow the platform raises prices, changes the rules, or you simply decide to leave, you realize how little you control. You are building the relationship with the customer — your most precious asset — on rented land.

	Ready-made platform	Custom restricted area
Initial cost	Low (start immediately)	Project investment
Recurring cost	% on sales + rising fee	Hosting + maintenance (fixed, low)
As revenue grows	Costs more and more	Stable cost
Ownership of customer data	The platform’s	Yours
Customization	Within their rails	As you need
Risk	They change rules/prices	No hostage

The turning point is clear: as long as you are small, the platform is convenient — you start immediately, spend little, validate the idea. But there is a revenue beyond which the percentage you leave every year abundantly exceeds the cost of your own area, and from then on every month on the platform is a gift you make to a company across the ocean. The time to sell courses without the US SaaS is not “as soon as you start” (that would be premature), it’s “when the numbers say that the rent you leave pays for your product on its own”.

Why ready-made platforms hold you hostage

Besides the margin, there is the issue of control, and it’s worth understanding because it’s structural, not a flaw of this or that platform. The business model of a membership platform is keeping you inside. It’s not malice: it’s how they are built. And it shows in some concrete things.

Your brand is a guest. Even with a custom domain, you are inside the experience they decided. The pages are their pages, the flows are their flows, the emails leave from their systems. The customer, ultimately, is using Teachable with your logo, not your product. For some businesses that’s fine; for those who have built a strong brand, it’s a gilded cage.

The features are the ones they offer. Do you want a particular renewal flow? A type of access they haven’t foreseen? An integration with your ERP or CRM? You can have it if the platform offers it, period. The day your business model needs something outside their rails, there is no “let’s ask the developer”: there’s “let’s wait and maybe they’ll add it”. It’s the same 80% wall you meet with any ready-made solution: you get as far as they got, and not a step further.

The data is only half yours. You export the email list, sure. But the rich graph of the relationship — who watched what, who is slowing down, who is about to cancel, the patterns that would tell you how to keep customers — that is the platform’s fuel, and they give you a limited view of it. In a business where renewal is everything, not clearly seeing who is about to leave is a serious handicap.

Leaving is painful by design. The more you grow on the platform, the scarier leaving gets: accounts, active subscriptions, saved cards, history. I’ll talk about this later because it’s the real psychological brake, but know that that difficulty is not by chance: an easy exit is not in the interest of your host.

None of this makes the platforms “bad”. It makes them what they are: excellent for starting, tight for those who have grown. Recognizing the moment of transition is the job.

UX: if it’s ugly, they don’t renew

Watch out for a mistake I see people make who get a custom area for the first time: thinking that, since “I already have the customers”, the experience can be mediocre. It’s the mistake that kills renewals. In a subscription business, the experience of the restricted area IS the product — not a side dish. The customer renews if entering, finding content and using it is pleasant and easy; they cancel if every time it’s a struggle.

What does a restricted area with good UX mean concretely? That the customer, when entering, immediately sees where we left off: the last lesson, the next step, what’s new. That they find what they are looking for in two seconds, without getting lost in menus. That videos start immediately and look good even from a phone on a train. That their progress is clear (at what point they are in the path). That renewing, when needed, is one click, not a treasure hunt.

It’s exactly the same principle of internal apps that people use only if they remove friction: if the tool is more uncomfortable than the alternative, people abandon it. Only here the alternative is not “going back to Excel”: it’s canceling the subscription. Every frustration in the restricted area is a small push towards the “cancel” button. And the beauty of custom, compared to the platform, is precisely that you design the experience around how your customers use your content — you don’t suffer it from a template designed for everyone and no one.

Content, videos and files: weight and permissions

A technical but concrete chapter, because it’s where the “I’ll have any web agency do it” often crashes: managing heavy content, videos foremost. A course restricted area is, underneath, a small private Netflix — and serving video well is not like putting an image on a website.

Videos must be served so they start quickly, adapt to the viewer’s connection (fiber or shaky 4G on a train), and are protected — meaning not downloadable with a right-click and put back around the next day. This requires thoughtful infrastructure: where the files sit, how they are delivered, how piracy is (reasonably) prevented. It’s not impossible, but it’s not “I’ll upload the video to the website”: it’s an architecture choice, and whoever hasn’t done it underestimates it.

Permissions on content are the other half: whoever bought module 1 sees module 1 and not 2; whoever expired no longer sees anything but their data remains for when they renew; “free preview” content is visible to everyone, the rest is not. This matrix of who-sees-what must be modeled well, because an error here is double damage: you either give away what you sell, or you deny a paying customer what they are entitled to (and they cancel).

Then there’s the issue of weight and costs: videos and files take up space and bandwidth, and serving them costs. A well-designed area keeps these costs under control and predictable, instead of making you discover a traffic bill at the end of the month. These are the details a ready-made platform manages for you (and it’s part of what you pay for) and that in custom must be done — well — by those who know how. One more reason not to entrust a serious restricted area to those who “make websites”, but to those who build products.

Renewals and reminders: process, not spam

If I had to point out the single function that pays for a custom restricted area, it’s renewal management. In a subscription business, the difference between growing and sinking is the renewal rate, and renewal is not an event: it’s a process that must be designed with care and a bit of grace.

What does a good renewal process do? It warns the customer before it expires, in advance and with a message recalling the value (“you are about to lose access to X, here is what awaits you if you continue”), not with a cold “your subscription is about to expire”. It gracefully handles the card that fails: it doesn’t cut access at the first failed attempt, but retries, warns, gives a few days — because an expired card is not a cancellation, and treating it as such makes you lose customers who wanted to stay. It distinguishes those who chose to cancel (and maybe asks them why, to learn) from those “expired by accident” (who must be recovered differently).

And here the keyword is process, not spam. The reminder that works is personal, well-timed, useful — not five identical annoying emails. The difference between a reminder that recovers and one that alienates lies entirely in the design, and it’s something that on custom you can calibrate exactly on your customers, while on the platform you take the standard flow. This theme of “renewal as a human process” is the same I address for managing members of an association, where quotas lost to poorly managed renewals are often more than new entries. The principle is identical: retaining costs less than acquiring, and well-done renewal is the cheapest way to grow.

When to stay on the platform (the honesty I owe you)

Now the honest part, the one software sellers usually don’t tell you. It’s not always convenient to get a custom area. In fact, in several cases the ready-made platform is the right choice, and switching to custom would be throwing money away. Here is when to stay where you are.

If you are still validating the idea — you don’t know if courses sell, how many customers you’ll get, if the model holds — the platform is perfect: you start in days, spend little, and discover if there is a market before investing. Building a custom area to validate is like buying the shed before knowing if the product sells.

If your volume is small, the percentage you leave to the platform is a trifle in absolute value, and doesn’t pay for the cost of a custom one. The math must be done in euros, not percentages: 5% of 30,000 € is 1,500 € a year, and doesn’t justify a project.

If the standard features are enough for you and you need nothing outside the rails — no special integration, no strange flow, no need for a strong brand — then you are paying the platform precisely for what you need, and that’s right.

Custom makes sense when three things align: a volume large enough to make the percentage weigh, a need for functions or experience the platform doesn’t give, and the desire to truly own your customers and your data. When all three are there, the switch pays for itself and you free yourself. When any is missing, wait: it’s smarter to grow on the platform until the leap is convenient. Telling you this is part of the job — whoever pushes you to custom “always and anyway” is selling you a project, not a solution.

Migration: the terror of accounts

We come to the real brake, the one keeping companies stopped even when custom has been convenient for a long time: the fear of migration. “And the customers already inside? The active subscriptions? The saved cards? If I move everything, will I lose someone?”. It’s a legitimate fear, and must be faced head-on because it’s almost always bigger than the real problem.

Migrating a restricted area means moving three things: the accounts (who the customers are, their credentials or a painless way to recreate them), the active subscriptions (who paid until when, so nobody loses the access they are entitled to), and the recurring payments (the cards, which almost never technically “move” and must be managed with a thoughtful transition). Done badly, migration is a nightmare: blocked customers, lost accesses, angry people. Done well, it’s a planned operation where the customer, in the best case, only notices the area is now nicer.

How is it done well? With a thoughtful cutover plan: the complete new area is prepared, users and subscriptions are imported, everything is verified on a pilot group, and a transition moment is chosen with clear communication to customers (“from Monday you’ll find the courses here, here is how you log in”). Active subscriptions are respected to the day: whoever paid until March, has access until March, no arguments. Renewals are moved as they expire, not all together. It’s a job of direction more than technology, and it’s exactly the kind of thing where you need someone who has done it before and knows where the traps are. The fear of migration is real, but manageable — and it mustn’t become the excuse to leave 5% of your revenue forever to whoever hosts you.

A typical case: from rented platform to own academy

A typical profile, architectural, no names. A business selling training — a method, courses — with a few thousand paying students and steady growth. It started, rightly, on a ready-made platform: in a few days it had courses online and was collecting. After a few years, though, the math had changed: revenue had climbed, and between platform fees and the “pro” plan it was leaving a five-figure sum a year to a foreign company, with the growing feeling of not being the master of its own house. It wanted a particular renewal flow the platform didn’t allow, it wanted to integrate students with its CRM, and it wanted the experience to be its own, not a template with an attached logo.

What was done. First the honest math: it was verified that yes, the volume now justified the leap — the rent left to the platform abundantly paid for hosting and maintaining a proper area. Then it started from the minimum features — access, catalog with permissions, player with progress, subscriptions, renewals, dashboard — without chasing community and gamification right away. Videos were placed on an infrastructure serving them protected and fast. And the piece worth most was designed with care: the renewal process, with early warning recalling the value, polite handling of the failing card, and distinction between those canceling and those “expiring by accident”.

Migration was the feared part, and was faced with a plan: new area ready and tested on a group of pilot students, import of users and subscriptions respecting deadlines to the day, clear communication (“from Monday courses are here”), and renewals moved as they expired instead of all together. No student lost the access they were entitled to. Fully operational: the business stopped leaving the percentage, took back its customer data (discovering, among other things, who was about to cancel and recovering them), and was able to build the experience it wanted. It wasn’t “changing software”: it was stopping renting the relationship with its audience. The honest note: the project cost money and took a few months, but paid for itself in a predictable horizon precisely thanks to the percentage no longer leaving.

Why a single hand is needed

Like for the other portals in this guide, a custom restricted area is data, backend and interface together — and they must come from the same head. Data are users, subscriptions, accesses, history. The backend are the rules: who sees what, when it expires, how it renews, what happens if a payment fails. The interface is the experience making them renew or cancel. If you entrust the interface to a web agency and the “system” to another, you get a beautiful area handling subscriptions poorly, or a solid system with an experience driving customers away. The product is the meeting of the two, and managing videos, permissions and recurring payments is too intertwined to be split between suppliers who then blame each other.

There is also the AI piece, inevitable today: in a restricted area it can have a useful and concrete role — an assistant helping the student find the right lesson, answering questions on the content citing your materials, summarizing a module. But even here the rule is the usual: AI enriches the experience on content, it doesn’t decide who has access or who paid — those are precise rules an engine wants, not a model that “usually” guesses.

Where to start

If you recognize yourself in the problem, the first step is not choosing a technology: it’s doing some math and a list, and you can do them yourself this week.

The math is simple: take the annual revenue of the area and calculate how much you leave to the platform between transaction percentage and plan fee. Put it in real euros, not percentages. That number is your “freed” annual budget: it’s what you would stop giving away, and must be compared with the hosting and maintenance cost of your own area. If the first stably exceeds the second, custom pays for itself.

The list is: what the platform does not let you do and you would like. A renewal flow of your own? Integration with the CRM or ERP? A type of access they haven’t foreseen? A coherent brand experience? If the list is short or empty, maybe the platform is still enough for you. If it’s long and there are things holding back your growth, you have the second reason (besides the margin) to make the leap.

With math and list in hand, the conversation with whoever should build it becomes concrete: not “I want a restricted area” in the abstract, but “here is how much I leave today, here is what I miss, here are my numbers”. From there the right thing is designed — which sometimes is staying where you are for another year, and that’s perfectly fine. The point is not changing for fashion: it’s changing when your numbers say that staying costs more than moving.

It’s for you if / it’s not for you if

It’s for you if: you already have an audience and sell (or want to sell) courses, content, subscriptions; you are on a ready-made platform and revenue has grown to the point that the percentage you leave really weighs; you need features, integrations or a brand experience the platform doesn’t give you; you want to own your customers and their data instead of renting them.

It’s not for you if: you are still validating the idea and don’t know if it will sell (stay on the platform, it’s perfect for this); the volume is small and the percentage in euros is a trifle; standard functions are enough and you have no needs outside the rails; you don’t have the desire or structure to manage a product of your own, with its maintenance. In these cases custom is premature, and saying so is part of the job.

Frequently asked questions

How much must a business invoice to justify a custom area? There is no magic threshold, but the reasoning is: when the percentage + the fee you leave to the platform, in euros, stably exceed the hosting and maintenance cost of your own area, custom pays for itself. On small revenues it’s not convenient; when the rent you leave becomes four or five figures a year, it’s time to do the math seriously.

Will I lose customers if I migrate? Not if the migration is planned. Active subscriptions are respected to the day, accesses aren’t interrupted, customers are clearly notified. Done well, migration is almost invisible to the customer, who only notices a nicer area. The risk is not in the migration itself, it’s in doing it without a plan.

What about recurring payments with saved cards? It’s the most delicate technical point, because cards almost never “move” between systems. It’s managed with a thoughtful transition: renewals are migrated as they expire, with a communication to the customer. It’s a job of direction, and must be entrusted to someone who has done it before — but it’s a known problem, with known solutions.

Isn’t it cheaper to stay on the platform? At the beginning yes, and it’s right to start there. It becomes more expensive as you grow, because the percentage on revenue increases while the cost of your own area stays fixed. Custom is not “always better”: it’s better beyond a certain size. Below, the platform wins.

What happens to my videos? Are they safe? A custom area serves videos in a protected and high-performing way: they start quickly, adapt to the connection, and are reasonably defended from copying. No protection is absolute (true for platforms too), but a well-made infrastructure raises the bar enough to discourage easy piracy. It’s one of the reasons you need someone who builds products, not someone who “makes websites”.

Can I keep my domain and my brand? Yes, and it’s one of the advantages. The area is yours: domain, brand, experience, everything consistent with the rest of your presence. You are no longer a guest with a logo on someone else’s house.

How long does it take to build it? It depends on the functions, but a focused restricted area (users, content, subscriptions, renewals) is built in a few months, not years. The most delicate part is not technical: it’s designing access and renewal flows well on your customers. Testing on a pilot group, as always, brings out real cases before launch.

Do customer data really become mine? Yes, and that’s the point. Users, behaviors, subscription history: everything in your house, under your control. You can analyze them, use them to improve renewals, integrate them with your CRM. It’s the end of renting the relationship with the customer.

In one line

If you already have customers and sell courses or content on an American platform, every month you leave a slice of margin on the table and — worse — the ownership of the relationship with your customers. A custom customer restricted area makes sense when three things align: volume making the percentage weigh, need for features or experience outside the rails, and the desire to truly own customers and data. When they are there, the transition pays for itself and frees you; when they are missing, the platform remains the right choice — and telling you so is part of the job. The core is not “a login with videos”: it’s managing accesses, protected content and renewals well, because in a subscription business that’s where you win.

If you want to understand if for your revenue custom is already convenient and what it would be like to migrate without losing a customer, look at the projects I’ve built or drop me a couple of lines: we start from your true numbers, not from a promise of “freedom from platforms”.