Customer Portal: Why It Pays and What It Costs

In a single day a salesperson answers twenty identical messages: "when is delivery", "send me the May certificate", "how many sessions are left on my package", "renew my contract". Each one costs five to ten minutes including the loss of focus. That is two or three hours a day for one person — roughly half the salary you are paying, spent on running an information desk.

What a portal actually delivers

First, it takes load off: customers check status, download documents and renew services themselves. Across our projects the flow of routine enquiries drops by 30–50 percent in the first three months. Second, retention: when someone has their history, accumulated bonuses and saved payment details sitting in a portal, moving to a competitor costs more psychologically. Third, data: you can see who logged in, what they looked at and where they stopped, and you can act on that specifically rather than mailing the whole database.

The minimum feature set

• Personal details and billing information the customer can correct themselves.
• Order or visit history with statuses and amounts.
• Documents: contracts, invoices, certificates — downloadable without asking a salesperson.
• The action the customer comes back for: reorder, renew, book, pay.
• Notifications about what has changed, and one clear channel to reach support.

Who needs a portal and who does not

It pays off where customers return: subscriptions, memberships, rentals, regular deliveries, appointment-based services. If you sell a one-off purchase every five years, the portal will stay empty, and a proper order-tracking page linked from an email is a better use of money. A simple test: count how many times a year your average customer contacts you. Fewer than two — you do not need one. More than four — it will almost certainly pay off.

Cost and timeline

A basic portal with login, profile, history and documents is 250,000–450,000 roubles and four to six weeks. With payments, subscriptions and notifications it is 500,000–900,000 roubles and two to three months. If the portal has to show data from your accounting system in real time, add time for the integration: that is usually the most unpredictable part, because it depends on the quality of somebody else's API. We run projects like this as web development; if the portal is part of a larger system it is designed together with the back-office side rather than bolted on afterwards.

Security is not optional

A portal is a door to personal data and should be treated accordingly. The mandatory minimum: passwords stored only as hashes using a modern algorithm, login attempt limits, confirmation for password and email changes, and access separation such that substituting someone else's identifier in the URL does not open their documents. That last flaw is alarmingly common and ranks first in the OWASP Top 10. Add to that the 152-FZ requirement to store Russian citizens' data on servers in Russia. What exactly we check before launching projects of this kind is described in the security section.

Common mistakes

Portals get built beautiful but empty: there is no reason for the customer to log in, and within a month activity drops to zero. The cure is adding that one action — pay, renew, book. The second mistake is complicated registration: if logging in requires inventing a password and confirming an email, half the users drop out; phone number plus a code works noticeably better. The third is the forgotten mobile version: 70 percent of visits will come from a phone, and if it is awkward there, the portal effectively does not exist. There is a good practical collection on mobile speed and usability on web.dev. If your audience is mostly mobile and visits often, it is worth comparing a portal with a mobile app — sometimes the latter is cheaper to maintain.