Selling a white-label client portal: pricing, payback and who buys it
The four ways to package a portal you license, payback arithmetic for a one-time fee with the assumptions stated, where the first ten customers come from, what you take on as first-line support, and the cases where licensing is the wrong move.
- A licensed portal is a product you sell, not a feature you add. The decision that matters is how you package it: one-off setup, monthly subscription, bundled into a retainer, or a mix.
- With a one-time licence and no revenue share, payback is simple division: $15,000 over what your customers pay you each month. The table below does the arithmetic and prints the assumptions.
- The first ten customers almost never come from advertising. They come from the clients you already serve, who have the problem and already trust you.
- A licence gives you a product, not demand. If you have no customer base and no way to reach one, it is the wrong purchase.
Reading about licensing a portal is the easy half. The harder half is the Monday after you have one: someone has to be told it exists, a price has to be said out loud on a call, and a customer has to decide it is worth paying for. This is about that half.
A caution up front. Nothing here is a market rate or a promise about what you will earn, because we do not have a dataset that would support one. What follows is a method: how to package, how to do the arithmetic with your own numbers, and where first customers tend to come from. The figures are yours to supply.
Who buys it, and why from you
The customer for a branded portal is a professional-services business that exchanges documents, approvals and invoices with its own clients and does it badly: architecture and interiors practices, engineering and surveying firms, accountants, lawyers, consultants. Their problem is not a missing feature. It is that the work is scattered across email, a shared drive and a messaging app, and nobody can say with confidence what was sent, which version is current or whether it has been paid for.
They are unlikely to buy it from a software company they have never heard of. They will buy it from you, because you already understand their business, already have their attention and can set it up in their own terms. That is the whole commercial logic of white-label, and it only works if you are the kind of business those customers already listen to: an agency, a consultancy, an integrator, a body with a client base.
Pick one vertical to start. A pitch that says "a portal for architecture practices" is easier to sell, easier to demo and easier to find referrals for than one that says "a portal for professional services". You can widen later. The platform is built around clients, documents, approvals and payments, which fits well beyond architecture, but your first ten customers will not care how wide it could go.
Four ways to package it
You set the price. We do not take a cut of what you charge or sit in the payment flow, so the commercial model on your side is entirely yours. There are four broad shapes, and many sellers mix two.
| Model | How it works | Good when | Watch for |
|---|---|---|---|
| Monthly subscription | Each customer pays you a recurring fee for their branded workspace. | You want revenue that compounds and a clear price anchor for customers. | You are now a software vendor: support, uptime and renewals are yours. |
| Setup fee plus subscription | A one-off charge to configure and onboard, then a smaller recurring one. | Onboarding takes real effort, such as importing documents or training staff. | A high setup fee can slow the first sale. Say what it covers. |
| Bundled into a retainer | The portal comes with a service you already sell, such as ongoing design, accounting or advisory work. | You have retainer clients already and the portal makes the service stickier. | It is hard to see what the portal earns. Track it separately or you will not know. |
| One-time sale | The customer pays once for their own deployment. | The customer wants to own it, and you can price the work properly. | No recurring revenue, and a second deployment is a separate quote on our side. |
Whichever you choose, you bill your own customers and payments settle to your own gateway account. The licence fee is the only money that moves between you and us.
A useful anchor is the thing the customer does today. Compare your price to the hours they spend reconstructing what was sent, and to the fees they collect late because documents went out before payment, not to other software. The cost of the current arrangement is rarely nothing, and it is a much more persuasive comparison than a feature list.
Payback arithmetic, with the assumptions showing
With a one-time licence and no revenue share, payback is a division. The licence is $15,000. Divide it by what your customers pay you per month and you have the months until it is covered.
Months to cover the licence = licence fee ÷ (monthly fee per customer × number of paying customers).
| Paying customers | $100 a month each | $250 a month each |
|---|---|---|
| 10 | 15 months | 6 months |
| 25 | 6 months | 2.4 months |
| 50 | 3 months | 1.2 months |
This is arithmetic, not a forecast. It assumes every customer is paying from month one, which they will not be, and it says nothing about how many customers you will sign or what your market will pay. Replace both inputs with yours.
Three things the table does not include, and you should put on your own version. Your hosting, if you run it yourself rather than taking managed hosting as an add-on. Your support time, which is real. And your own sales effort, because the first customers cost more to win than the later ones. A setup fee shortens every figure in the table; a free pilot lengthens it.
The first ten customers
The honest answer is that they are already in your phone. The first ten customers of a licensed portal are overwhelmingly existing clients, and people those clients know, who have the problem the portal solves and already trust you to fix it. Advertising to strangers is the expensive way to reach customers you could have asked.
Start with the clients you already invoice
List the ones who exchange documents with their own customers. They are the ones who feel the problem, and they are the easiest to demo to because they know you.
Demo it under your brand, not ours
Show your logo, your domain and a realistic client workspace. A customer who sees your name on it stops thinking of it as software and starts thinking of it as something you do.
Offer one customer a proper pilot
Pick the most forgiving client, set it up carefully and learn what is awkward before you meet the one with opinions. Their experience becomes your first real case study, which you may then describe in their own words and only with their permission.
Write down the problem, not the product
A short page about the specific mess in your vertical, such as drawings issued before the fee arrives or no record of who saw what, brings in the people searching for the problem. The portal is the answer further down the page.
Ask for referrals at the moment of relief
The best time is when a customer has just found something in the portal that would have taken an hour to dig out of an inbox.
What you own after launch
Licensing a platform does not make support disappear. It moves the first line of it to you, and a seller who understands that going in has a much better first year.
- Customer support. When a customer cannot find a file, the call comes to you. Our side covers you with updates and support for the first 12 months, but your customers will never know we exist, so they will always ring you first.
- Your own terms and privacy policy. You are the one customers contract with and the one handling their data. Have them written for your business and your market, and take legal advice rather than copying someone else's.
- Tax on what you charge. Where your jurisdiction applies tax to software subscriptions, charge it correctly. Confirm the rules with your accountant before the first invoice rather than after the tenth.
- Onboarding. Setting up a customer's workspace and bringing their documents across is work, and it is the work that decides whether they use the portal in month two.
- Renewals. After the first year of updates and support, renewal is optional and priced annually. Decide early whether you will take it, so it does not arrive as a surprise.
When not to do this
We would rather you decided this before the call than after.
- You have no customers and no route to them. A licence gives you a product. It does not give you demand, and a branded portal with nobody to sell to is an expensive logo.
- You want to build and own a technology asset. If holding a codebase you wrote is part of the plan, building it yourself is the honest route.
- You are not willing to be first-line support. Your customers will ring you, every time.
- Your customers are not document-and-approval shaped. If the portal does not map onto how they work, no amount of branding will fix that.
If you are on the fence about the build-or-license question itself, the maths on building a portal versus licensing one sets out a worksheet for running it with your own numbers. If you are thinking of selling to architecture practices in particular, what a studio runs on today describes the customer's side of the problem in detail.
Talk it through before you commit
A thirty-minute licensing call: tell us the brand, the market and the customers you already have, and we will walk you through the live platform and say plainly if it is not a fit. The licence is $15,000, one time, with no revenue share.
Questions, answered
The questions agencies and consultancies ask before they license a portal, in plain language.
Ask us anythingStart from what the customer does today and what it costs them, in hours spent reconstructing what was sent and in fees that arrive late, rather than from other software. Then choose a shape: a monthly subscription per customer, a setup fee plus a smaller subscription, the portal bundled into a retainer you already sell, or a one-time sale. You set the price and keep all of it, because there is no revenue share, and payments settle straight to your own gateway account.
It is a division: the $15,000 licence over what your paying customers pay you each month. At $100 a month each, ten customers cover it in 15 months, twenty-five in 6 and fifty in 3. At $250 a month each the same three figures are 6, 2.4 and 1.2 months. That is arithmetic on stated inputs, not a forecast. It assumes every customer pays from month one and leaves out your hosting, support and sales time, so run it again with your own numbers.
Businesses that already have clients and credibility but not the engineering time: digital and design agencies, resellers and integrators taking a platform into a market or language the vendor does not serve, industry consultancies, and any business whose clients need documents, approvals and invoices in one private place. It is the wrong purchase for a business with no customer base, because a licence provides a product rather than demand.
No, but you do need to be willing to be first-line support, because your customers will never know the platform came from anywhere else and will ring you whenever something is unclear. The vendor's updates and support cover you behind that, for the first twelve months on the AtelierLab licence and optionally after.
Yes. You decide what to charge, whether to sell it as a subscription, a one-time setup or part of a larger retainer, and which markets to sell into. The commercial model on your side is entirely yours, and the licence fee is the only money that moves between you and us.
Your branding assets and your domain, a payment gateway account of your own, and your own terms of service and privacy policy written for your business and market. Take legal and tax advice for your jurisdiction before the first invoice. The licence includes admin training, a technical walkthrough and written documentation, and two to three weeks from signed agreement to launch is typical.