For agencies, studios and freelancers
You are very good at front ends. Stop quoting the back one.
Every client project rebuilds the same auth, payments, permissions and admin screens. It is the least differentiated work you do, and you charge for it every time as if it were new.
The economics of a build shop are strange. The part a client falls in love with — the design, the flow, the feel — is maybe a fifth of the hours. The rest is plumbing you have written many times, cannot show anyone, and get argued down on because it looks like “setup” on a quote.
And it is the part that comes back. The client hires someone and needs permissions. Takes a deposit and needs books. Grows and needs a customer portal. Every one of those is a small project you did not want, on a system only you understand.
What you rebuild every time
Sign-up, sign-in, password reset, sessions
Roles and permissions that survive the client hiring someone
Taking a payment, and the books behind it
A customer list that is more than a form submission
Booking or scheduling, without double-selling a slot
Transactional email and SMS from the client’s own brand
A logged-in area for the client’s own customers
The admin screens the client actually runs the business in
None of that is why a client chose you.
What happens instead
Every client is its own organization
Separate data, separate brand, separate members — under one login for you. Switch between them without logging out, and see across the whole family when you need to.
White-label the whole stack
Your clients experience your brand. We are not in the room, on the invoice, or in the interface.
Their money, their account
Each client’s payments settle directly into their own processor account. You are not in the flow of funds — which is a liability you do not want and a conversation you should not have to have.
The front end is still your work
Design it, generate it, hand-build it. That is the part clients see, judge and pay for, and it stays entirely yours.
New capability arrives for every client at once
Upstream releases land across the family instead of becoming a quote per client for the same feature.
Commission what a client genuinely needs
When one needs something that does not exist, it can be built as a custom service — and where it is broadly useful it becomes part of the base rather than a one-off you maintain forever.
The objection that kills retainers
Sooner or later a client asks what happens to them if they stop working with you. If the honest answer is “your site is on our stack and your payments run through our account”, they have learned something about the relationship they will not forget — and the more sophisticated the client, the earlier they ask.
Here the answer is genuinely good. Their money already settles into their own account. Their data is theirs and exports. Their site is code they own. You keep the relationship because you are useful, not because leaving is expensive — and being able to say that out loud, early, wins more work than the leverage ever did.
When this is the wrong call
If a client needs a genuinely bespoke data model — something the business is built around and nobody else would want — the constraint that the data layer is not yours to invent will fight you the whole way. Take that project somewhere else, or commission the piece that does not exist. And if your differentiator isbuilding backends, this removes the thing you sell rather than the thing you tolerate.
Try it on one project
The front-end template is open source and free. Point your next build at the API, or generate the front end however you already do and connect it. The fastest way to judge this is to do it once on a real project rather than to read more pages.