Customer portal development: features, security and cost
A customer portal saves phone calls and emails: customers see orders, invoices, documents and the status of their jobs themselves, around the clock. Done well, it noticeably relieves sales support and accounting. Done badly, it's another password nobody uses. This article shows which features pay off, what's needed technically and legally, and how to estimate the cost.
Start with the most common requests
For two weeks, count why customers call or write. For most businesses it's a few reasons: where is my order, send me the invoice again, what's the status of my job, I need a document. The portal should answer exactly these questions first.
Typical first-version features:
- Job or order status with history.
- Invoices, delivery notes and contracts to download.
- Uploading documents, for example material for a job.
- Maintaining company details and contacts themselves.
- New requests or reorders with pre-filled data.
A portal lives on its integrations
A portal is only as current as the data behind it. Most of the work is therefore in interfaces to CRM, inventory, accounting or ticketing. Clarify early which system is the source of truth for which data and whether it has a documented API. If the portal has to read data from a system without an API, it gets more complex and error-prone.
Security and privacy
The portal holds invoices, contracts and contact data. Article 32 GDPR requires appropriate technical and organisational measures that reflect the state of the art. In practice that includes:
- Secure login, optionally with a second factor, and protection against automated password guessing.
- Strict separation: every customer sees only their own data; for business customers with several users, a role model.
- Encrypted transfer, logging of access to sensitive documents, regular backups.
- A process for disabling access when a customer contact leaves.
Off-the-shelf or custom-built?
Many CRM and accounting systems offer simple customer portals as an add-on. If the add-on covers your most common requests, it's usually the cheapest route. Custom development pays off when data from several systems comes together, your process is industry-specific, or the portal is part of your offering that customers choose you for.
What a customer portal costs
A first version with login, job status, documents and one integration with a leading system typically takes 120 to 300 development hours, depending on the quality of the API. With us an hour costs €30; we estimate every feature up front and deliver in stages, so customers use the first features while the next are built. Hosting and maintenance add roughly €20 to €50 a month.
Frequently asked questions
- Do customers actually use a portal?
- If it answers questions faster than a phone call, yes. What matters is easy login, current data and your team consistently pointing customers to the portal.
- Can the portal be integrated into our website?
- Yes, usually on a subdomain such as portal.your-company.com with your design and a login link on the website.
- Who is responsible for the data in the portal?
- You as the business. Hosting and development providers act as processors; you sign an Article 28 GDPR agreement with them.
Sources
Tell us the three most common reasons customers contact you, and which systems you use. We sketch the first portal version and estimate it in hours.
Plan a customer portal