How do I give a client a dashboard without building one?
The short answer
Use a platform that provides the content layer and keep your own design on top. Building an editing interface yourself means owning authentication, permissions, media handling, validation and security forever — for a feature the client sees as basic. The build is the easy part; it is the decade of maintenance afterwards that makes it a bad trade for a freelancer.
On this page
Why clients ask, and why you hesitate
The client wants to change a price without emailing you. Reasonable — and it is also better for you, because those emails are the least profitable work you do.
The hesitation is that giving them that means building an admin area, and you know what that involves. So the request gets deferred, and everyone keeps emailing.
What building it yourself actually costs
Not the first version. The first version is a satisfying weekend: a login, some forms, a save button.
What it costs is everything after:
- Authentication, done properly — sessions, resets, lockouts
- Permissions, once there are two people with different access
- Media handling — uploads, resizing, storage, formats
- Validation, so a client cannot paste something that breaks the layout
- Security, indefinitely, because you have built a login page on the public internet
- Support, whenever they cannot find the field they want
And you own all of it for as long as the client exists. For a per-project freelancer, that is an unbounded liability attached to a fixed fee.
The version that hurts most is the one you built five years ago for a client who is still using it, on a framework you no longer work in.
The three routes that avoid it
A platform that provides the content layer. Your design, their editing interface, their maintenance. You keep what makes your work distinctive and stop owning the plumbing.
An established CMS. Long-lived, well-understood, and someone else patches it. The cost is that you inherit its conventions and its update treadmill, and the client inherits an interface with far more in it than they need.
A hosted content service behind your own front end. More flexible, and you are back to gluing systems together and explaining a second login.
Which is right depends on how much your design matters and how technical the client is. What they share is that you stop being the security team for a login page.
What to look for, whichever route
- Only the fields the client should touch. A dashboard exposing everything is how a design you were paid for gets dismantled in month three.
- Layout that cannot be broken by content. If a long headline breaks the page, it is not really editable.
- Roles, because an owner and a part-time manager do not need the same access.
- A path back to you. You want them self-serving the small things and calling you for the real work — that is the whole point.
- Something you can hand over. If you stop working with the client, the site should keep working. Anything else makes you a dependency, and dependencies get replaced.
The pricing conversation this changes
The instinct is that self-editing removes your recurring revenue. It removes the unprofitable part.
What is left is work that needs expertise: new pages, integrations, design changes, advice, the thing that broke. That is defensible at a real rate, and it is the work you would rather be doing.
Clients also tend to value you more, not less. Being the person who made them independent reads as confidence. Being the bottleneck for a price change reads as a business model, and clients notice.
What Helm Partners is, concretely
Helm is the third of those routes, so here is the shape of it rather than a pitch.
You bring the client. Helm builds or attaches the site and gives them a dashboard carrying their branding, not ours — the client never sees the word Helm. You keep the relationship. Helm runs the hosting, the certificates, the backups, the updates and the 3am outage.
Two things are worth knowing before you assume it is a referral scheme. First, you do not have to be a developer — most partners are not; anyone who ends up introducing businesses to a supplier can be one. Second, commission has two parts: a one-off share of the build, and a share of the client's subscription for a set number of months. Both, along with the hold period before commission clears and the minimum before a payout runs, are written into your own agreement rather than set by a published rate card — so the honest answer to "what does it pay" is that it is negotiated, and we would rather say that than quote a number that is not yours.
Payouts run in your own currency, including by Whish and OMT, which matters if you are working from Lebanon and have watched an overseas programme's payment terms make the whole thing theoretical.
The portal is at partners.usehelm.host — a pipeline for the clients you are tracking, an earnings view with downloadable statements, and a place to submit a client with the repo attached if you have already built something.