Should my customers have logins on my website?
The short answer
Only if there is something worth logging in for. An account with nothing behind it is friction that costs you sales. But once a customer has one, everything about them stops being anonymous — you can see who buys, who returns, who has drifted, and what each person is actually interested in. That shift, from counting visitors to knowing customers, is the real reason to do it.
On this page
The rule that decides it
A login is a cost before it is a benefit. Every account you ask someone to create is a decision point where some proportion of people leave, and that proportion is larger than anyone expects.
So the rule is simple: there has to be something behind the door that the customer wants.
Not something you want. Not "so we can market to you". Something they would be annoyed to lose — their session credits, their programme, the members' price, their order history, the course they paid for, the loyalty balance they are four stamps into.
If you cannot name that thing in one sentence, do not add logins. You will have built a wall in front of your own business.
When they clearly earn their place
- You sell something delivered over time — a course, a coaching plan, a membership, a training programme
- Customers have a balance of something — session credits, loyalty stamps, points, a package of visits
- There is member-only pricing or member-only access
- People need to see their own history — past bookings, past orders, past appointments
- You want repeat business rather than transactions, and you need to know who your repeat customers are
When they cost you money
- A one-off purchase with nothing afterwards. Guest checkout exists for a reason.
- An enquiry form. Nobody creates an account to ask a question, and asking them to is how you lose the enquiry.
- A restaurant menu, a price list, an article. Gating information that helps someone choose you is choosing not to be chosen.
- "So we can build a database." That is a reason for you and not for them, and customers can tell the difference immediately.
What actually changes once they log in
This is the part that gets undersold, and it is the strongest argument for doing it when it fits.
Without accounts, your website reports numbers. Four hundred visits, eighty from search, a bounce rate. Useful, vaguely, in aggregate.
With accounts, the same website reports people. Not "eighty visitors this week" but: this customer has ordered nine times and not in the last two months. This one has been on the site four times without buying anything. This one holds the coaching plan and the community access. This one is your highest spender and you did not know their name.
That is a categorical change rather than a better version of the same thing. Aggregate analytics tells you what happened. Identified analytics tells you who it happened to, which is the only version you can act on. "Traffic is down eight per cent" is a fact you can do nothing with. "These eleven regulars have not been back since the price change" is a phone call.
For a small business that runs on repeat custom, the second is worth considerably more than the first.
What that looks like in Helm
Customer accounts are a module, and the things worth logging in for are the other modules — so the two sides fit together rather than being integrated.
Customers is the record: who they are, what they hold, what they have spent, when they were last active. There is an overview with new customers this week, returning rate and who is active today, plus a leaderboard you can rank by spend, orders or visits. Each person has their own profile page with their order history, the entitlements they have been granted, and any quiz they have completed.
Offerings define what a customer can hold, and holding one grants an entitlement — permanent or expiring, granted automatically on purchase or by hand when you would rather approve people yourself. Entitlements cascade, so someone with the course also gets the community without you keeping two lists.
Then the things behind the door: Courses, Community, Coaching, PT Sessions, Loyalty, Bookings. You enable the ones your business actually uses.
One detail that matters more than it sounds: the login renders on your own site, through a widget embedded in your own pages, rather than redirecting to a portal with our name on it. Your customers never leave your domain and there is nothing for them to install. Most standalone systems — a separate loyalty app, a separate course platform — cannot offer that, because sending people to their own domain is how they work.
The honest recommendation
Do not add logins because a platform offers them. Add them the moment you have something a customer would be annoyed to lose, and not a week before.
But when that moment arrives, take it seriously — because the change is not that customers get an account. It is that you stop guessing about the people who pay you.