Skip to content
← All articles
9 min read

Customer portal development: what to build, in what order, and what to skip

A customer portal is a login area where clients see their own orders, documents and payments without writing to your manager. Build one when the same questions ("where is my order", "send me the invoice") eat your team's day. It pays off through fewer tickets, not through looks. Below: modules, access control, integrations, stages, version two, and when a ready-made tool is enough.

What does a customer portal take off your support team?

Start from the questions your managers answer today, not from a feature list. In most businesses a handful of repeating requests produce most of the load: order status, a copy of a document, an invoice or act, a payment confirmation, a change of contact details, a repeat order. Each of them is a lookup in data you already have. A portal turns that lookup into self-service.

That is the whole business case, and it is easy to check before you write code. Take a month of emails, chats and calls, tag each by topic and count. If a few topics cover most of the volume and each can be answered from a record in your system, a portal will help. If the requests are unique and need human judgement, a portal will mostly add one more place to look and one more thing to support.

A second, quieter benefit is consistency. When clients see the same status your team sees, the manager no longer retells it by phone, and mistakes from retyping disappear. The portal does not replace the account manager; it removes the clerical part of the job so that the conversation can be about the deal.

Which modules does a client portal need?

Think of the portal as a thin, safe window onto your internal system. It should not be a second system with its own copy of the truth. Pick modules by the questions from the previous step; most portals are a subset of the list below.

Every module needs the same three decisions: which records the client may see, which fields are hidden, and what the client may change. Decide those per module, in writing, before design starts.

  • Orders and requests: a list with statuses, a detail page, history of changes, and a way to repeat or cancel where the process allows it.
  • Documents: contracts, invoices, acts, certificates. Generated on demand or stored as files, with a clear rule for who can download what.
  • Payments: invoices, payment status, receipts. Online payment is optional; showing the status reliably is not.
  • Notifications: email or messenger messages on status changes. Let clients choose the channel, and keep a log of what was sent.
  • Profile and organisation: contact details, delivery addresses, the list of colleagues who have access (important in B2B).
  • Messages or tickets: a simple thread tied to an order, so the conversation does not leave the context. Add it only if your team really works from it.
  • Reports and exports: for B2B, a table with filters and a CSV export is often the most valued feature.

How should login and access rights work?

The portal exposes client data on the open internet, so access control is the part where shortcuts hurt most. Authentication answers who is this; authorisation answers what may they see. Keep them separate.

For B2C, email with a one-time code or a magic link is often enough and avoids password resets. Social login or a messenger login can be added if your audience already uses it. For B2B, expect several people per client company: a buyer, an accountant, a manager. That means an organisation entity, users who belong to it, and roles inside it. The model is the same one described in SaaS roles and permissions: a user, a membership in an organisation, a role that is a set of small permissions.

The rule that matters most: check ownership on the server for every request. A client who changes an order number in the URL must get a refusal, not someone else's order. This class of bug (insecure direct object reference) is the most common one in portals. Filter every query by the organisation of the logged-in user, and write tests that try to read another client's records.

Add the basics early: rate limiting on login, short-lived sessions with refresh, an invitation flow instead of shared logins, and an audit log of who downloaded or changed what. Staff access to a client's view ("log in as client") is useful for support, but it must be logged and limited to named employees.

How do you connect the portal to CRM, 1C and billing?

The portal is only as useful as the data behind it, and that data usually lives elsewhere: orders and clients in a CRM, stock, invoices and acts in 1C or another accounting system, subscriptions and payments in a billing service. The key decision is whether the portal reads from those systems directly or from its own database that they feed.

Reading directly from the source on every page view looks simple, and it works for a small prototype. In production it makes the portal as slow and as fragile as the slowest system, and it breaks when 1C is down for maintenance or an API limit is hit. The more robust pattern is a portal database holding the fields the client may see, updated by a sync service that receives changes from the source systems. The portal then stays fast and keeps working when a source is unavailable, and you decide how fresh the data must be.

Writes go the other way and need more care. When a client places a request or confirms a document, the portal records it, then passes it to the CRM or accounting system through a queue with retries. Make that operation idempotent, so that a repeated delivery does not create a second order; see API idempotency and retries. Webhooks from payment and billing providers need signature checks, covered in webhook security.

Match records between systems with explicit identifiers, not by name or email. A mapping table (portal client, CRM contact, 1C counterparty) is a small piece of work that saves weeks of confusion. The wider architecture of such exchanges is covered in CRM and ERP integration. If part of your data lives in a spreadsheet, plan its migration first.

What are the stages of building a client portal?

The order below keeps risk low because the uncertain parts, data and access rules, are settled before the interface is polished. Skipping the first two steps is the usual reason a portal gets rebuilt.

Release to a small group of real clients first. Their questions will show which module is missing and which one nobody opens. Watch what they actually do (see validation metrics) instead of asking whether they like it.

  • Discovery: count the repeating requests, name the roles, list the data each module needs and where it lives today.
  • Data and access model: entities, ownership rules, roles and permissions, and what each integration provides and how often.
  • Integration prototype: prove that you can read the key records from CRM/1C and map them to portal clients, before any interface work.
  • Core build: login, the one or two modules that cover most requests, notifications, audit log.
  • Pilot: onboard a few clients, collect questions, fix what blocks self-service.
  • Rollout: invite the rest, update your support scripts so managers send clients to the portal, monitor errors and sync lag.
  • Operations: backups, monitoring, dependency updates and a person responsible for the sync. See monitoring after launch.

What should you postpone to version two?

Portals grow by accretion, and each addition has a running cost. The first version should prove that clients use it and that tickets drop. Everything that does not serve that goal can wait, and most of it will turn out to be unnecessary.

A useful test for each idea: if we leave it out, will clients still be able to do the top requests alone? If yes, it is a candidate for later. If you are unsure, the approach from how to scope an MVP applies as is.

  • Native mobile apps: a responsive web portal covers the start. A Telegram bot for notifications is cheaper than an app.
  • Online payment in the portal, if you can show invoice status and give a payment link.
  • Complex dashboards and analytics for clients, before you know which numbers they ask for.
  • Custom workflows and approvals for each client company.
  • Chat in the portal, when email or your messenger already works.
  • Multiple languages and currencies, if all current clients use one.
  • Public API for clients, until someone asks for it.

When do you not need a custom portal?

Often a ready-made solution is the right answer, and a custom build would only add maintenance. If the clients are few, the data is simple and the process is stable, start with what exists.

Several cases where we would advise against custom development: your CRM or accounting vendor already ships a client area that shows what you need (check what its guest or client access really exposes before assuming it does not); a shared Notion page or Google Sheet per client is enough for a few dozen clients, as long as you accept managing each person's access by hand and check how sharing and permissions work on your plan; an off-the-shelf helpdesk or order-tracking service covers the one question that hurts; or you have not yet confirmed that clients will log in at all.

Signs that you have outgrown the ready-made option: you copy data between tools by hand every week, access rules cannot express who may see what, the vendor's branding or limits get in the way, or you need the same data in the portal and in other systems at once. Until then, a simpler tool plus a clear process is cheaper and faster.

When should you hire a contractor to build it?

Bring in a developer when the hard part is not the screens but the data: several source systems, access rules between companies, and sync that must not lose or duplicate records. These are backend design problems, and mistakes in them are expensive to fix after clients are inside.

Prepare a short brief: the top requests by volume, the roles, the systems that hold the data and whether they have an API or an exchange file, and who in your team owns each one. With that, a contractor can say what is realistic for a first release. Ask who will host and maintain the portal afterwards, how the sync is monitored, and who owns the code. If you are comparing options, choosing a development studio lists the questions to ask.

Our SaaS development work covers this kind of build: multi-tenant data separation, roles, billing and integrations. A portal is a close relative of a SaaS product, with your existing systems as the data source.

Questions

FAQ

Didn't find an answer — ask on the call or in Telegram.

How much does customer portal development cost and how long does it take?

It depends on the number of modules, the number of source systems and how clean their data is. The integrations and access rules usually cost more than the screens. A fixed number is only possible after a short discovery. A one-module portal on top of one system is a very different project from a B2B portal with several roles and 1C.

What is the difference between a B2B and a B2C client portal?

B2B has several users per client company, so you need organisations, roles and invitations, plus documents, reports and integration with accounting. B2C usually has one user per account, a simpler login by one-time code, and focuses on orders, payments and notifications. The access model is the main difference.

Do I need a custom portal or is a ready-made one enough?

A ready-made option is enough when you have few clients, simple data and a stable process, or when your CRM already has a client area that shows what you need. Go custom when you copy data by hand every week, need role-based access between companies, or must combine data from several systems.

How do you integrate a customer portal with a CRM or 1C?

Keep a portal database with the fields clients may see and feed it from the source systems through a sync service or webhooks, instead of reading them live on every page. Send client actions back through a queue with retries and idempotency. Map records by explicit identifiers, not by name.

How do you secure a client portal?

Check ownership on the server for every request, filter queries by the user's organisation, limit login attempts, use invitations rather than shared accounts and keep an audit log. Test that one client cannot open another's records by changing an ID. Sign and verify incoming webhooks.

What features should the first version of a client portal have?

Login, the one or two modules that answer most repeating requests (usually orders and documents), notifications and an audit log. Leave mobile apps, in-portal chat, dashboards and a public API for later, once real clients show what they use. This keeps the first release small, cheap to support and easy to measure against the drop in tickets.

Related service

Custom web services and SaaS platforms

A platform for customers or partners is more than an interface: behind it are accounts, permissions, payments and an API. We design those parts so the product can grow instead of being rewritten.

Learn about the service
Other articles
Contact

Shall we discuss your task?

Thirty minutes on a call — and you understand the architecture, timeline and engagement format. No obligations.

Or message us on Telegram →Follow our Telegram channel →

Enter your Telegram or email so we can reply.

We reply within 15 minutes.