Website portal development for customer, partner and supplier portals
Website portal development is what happens when a website has to know who is visiting. A portal puts each customer, partner, supplier or member in front of their own orders, documents, invoices, cases and data, lets them act on them without emailing your team, and keeps every action secure and recorded. We build web portals on top of the ERP, CRM and other systems you already run, with secure login, permissions by company and role, and accessibility built in. Hosting is in the EU, and your company owns the code.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
The portals we build
| Portal | Who logs in | What they do there |
|---|---|---|
| Customer portal | Business or consumer customers | Orders, deliveries, invoices, contracts, support cases, documents |
| Partner or dealer portal | Resellers, installers, agents | Price lists, quotes, leads, registrations, marketing material, training |
| Supplier portal | Suppliers and subcontractors | Purchase orders, confirmations, delivery schedules, invoices, certificates |
| Member portal | Members of an association, club or cooperative | Membership, fees, events, voting, member directory |
| Client reporting portal | Clients of a service company | Live reports, work done, hours delivered, incidents, approvals |
| Tenant or resident portal | Tenants and owners | Service requests, notices, documents, bookings |
A portal is different from your public site and from your internal tools. The public site sells, and is covered on our website development page. Internal tools are for your own staff, see internal tools development. A portal is for people outside the company who have a relationship with you, which is why identity, permissions and integrations matter more than design flourishes.
When the application is not a login area added to a site but the product itself, such as a booking engine, a quoting tool or a SaaS service, see web app development.
Why companies build a portal
The trigger is usually the inbox. Customers email to ask where an order is, request a copy of an invoice, ask for a certificate or check the status of a case, and someone looks it up in a system the customer cannot see. Partners wait for a price list in a PDF. Suppliers confirm orders by replying to an email. Each request takes a few minutes; together they fill days. A portal answers those questions directly from the source systems, at any hour, and leaves your team the requests that need a person.
The second reason is control. When documents travel as attachments, nobody knows which version a customer has. In a portal, every document has one current version, access can be withdrawn, and every download and change is logged.
Login and identity done properly
Identity is the heart of a portal, and it is where most of the risk sits. We use proven standards rather than home-made login code. OpenID Connect is, in its own specification's words, a simple identity layer on top of the OAuth 2.0 protocol (OpenID Connect Core 1.0), and it lets business customers sign in with their own Microsoft or Google work accounts or their company's identity provider, so their IT team removes access when someone leaves. SAML is supported for enterprise customers who require it.
For users with their own portal accounts, we follow current guidance. The United States NIST digital identity guidelines, revised in 2025, require that passwords used as a single-factor authentication mechanism be a minimum of 15 characters in length, and recognise syncable authenticators, commonly known as passkeys, which can be copied to a user's other devices through a sync fabric (NIST SP 800-63B). (Both read on 11 November 2026.) In practice we offer passkeys first, a second factor for password logins, and national electronic identification where your market uses it.
Companies, roles and permissions
Business portals need more than individual users. A customer company has its own administrator, who invites colleagues and decides who may order, approve, see invoices or manage users; a dealer may manage several shops; an accountant may need read access for a client. We model companies, roles and delegations explicitly, so your team does not become the help desk for every new user.
Permissions are checked on the server for every request, not just hidden on screen. The OWASP Top 10 API Security Risks list broken object level authorization, where a user can reach another user's data by changing an identifier, as the first risk in its 2023 edition (OWASP API Security Top 10, 2023, read on 11 November 2026). It is the classic portal flaw: invoice 1043 belongs to someone else, but the address bar says 1044 is yours. Our tests try exactly that for every object type before launch.
Self-service and personal data
A portal is also a good answer to data protection duties. The GDPR's recital on the right of access says that, where possible, the controller should be able to provide remote access to a secure system which would provide the data subject with direct access to his or her personal data (Regulation (EU) 2016/679, Recital 63), and the right to data portability gives people the right to receive data they provided in a structured, commonly used and machine-readable format (Article 20). (Both read on 11 November 2026.) A portal can show users the data you hold about them, let them correct it, and offer a download, which turns a manual request into a button.
Connected to the systems behind it
A portal is only as good as the data in it. We connect it to the systems that hold the truth: the ERP for orders, deliveries and invoices, the CRM for contracts and cases, the document archive, the ticketing system and your own databases. Data is read live or synced on a schedule, depending on what the source system can handle, and actions in the portal, such as a new order, a change request or an uploaded certificate, are written back through interfaces rather than emailed to someone to retype. For the integration work, see API integration; for ordering portals for business customers, see B2B ecommerce solutions.
Intranet development for employees
An intranet is a portal for your own staff: the place where they find news, policies, handbooks, forms, the people directory and the tools they use every day. Intranet development follows the same principles as any portal here, with login through your company identity provider, permissions by team and site, and content from the systems behind it, but the users and the measures of success are different. A good intranet is the first page staff open in the morning, on a laptop or a mobile, including for people without a company email address, such as warehouse, care or field staff. We build intranets as their own system or on top of Microsoft 365 or Google Workspace, with search across documents and pages, targeted news by site and role, a mobile app for deskless staff, and links into HR, scheduling and IT requests. Documents are managed in a document management system with versions and retention, and the intranet is also the natural home for the link to a confidential whistleblowing channel. Internal sites have users with disabilities too, so the accessibility work below applies to intranets as well.
What an intranet costs depends mostly on the route, SharePoint, a ready-made product or a custom build, and on content work; our guide to intranet cost compares them without prices of our own.
Accessible by design
Portals are full of forms, tables and documents, which is where accessibility usually fails. If a portal is used to sell products or services to consumers, the European Accessibility Act applies to it as an e-commerce service, which the Act defines as a service provided at a distance, through websites and mobile device-based services, by electronic means and at the individual request of a consumer, with a view to concluding a consumer contract; the obligations apply to services provided to consumers after 28 June 2025 (Directive (EU) 2019/882, read on 11 November 2026). We build every portal to WCAG 2.2 level AA either way, and our accessibility audit checks existing ones: keyboard use, clear labels and errors, readable tables on phones and documents that screen readers can open.
Ready-made portal or custom?
Many systems include a portal: CRM platforms offer customer and partner portals, ERP vendors offer supplier portals, and ticketing tools offer help centres. If the portal in your existing system covers what your users need, using it is usually right, and we will say so. A custom portal pays off when users need data from several systems in one place, when your permissions or processes do not fit the built-in model, when the built-in portal is priced per external user and your user count is large, or when the portal is part of your product.
| Situation | Built-in portal | Custom portal |
|---|---|---|
| Data from one system, standard roles | Usually enough | Rarely worth building |
| Data from ERP, CRM and archive together | Limited or add-ons | One view built for your users |
| Company accounts with delegated administrators | Depends on the product | Modelled on your relationships |
| Many external users | Often priced per user | Your hosting, your cost model |
| Data location and ownership | The vendor's platform and region | Your account, EU data region |
Our guide to client portal cost compares a built-in portal priced per external user with a custom portal over five years, without prices of our own.
How we build a portal
- Start from the requests. We read a few weeks of what customers, partners or suppliers actually ask for, and pick the top tasks the first version must handle.
- Scope and fixed price in writing. User types, login methods, roles, the systems to connect, the screens and what the first phase leaves out.
- Clickable design with real users. A prototype tested with a handful of real users before building, so the portal speaks their language rather than your system's.
- Build, connect and test. Integrations, permissions and security tested on every object type, accessibility checked, performance measured.
- Launch to a pilot group. A few friendly customers first, then everyone; the inbox volume is compared with the baseline, and the next tasks are added.
Portals often follow from other systems we build, such as client reporting for security guard scheduling or the customer self-service of an ecommerce subscription platform.
You own it
As a standard term, the source code sits in a repository in your company's own account, and the database and hosting are in your name in an EU data region. You can keep us for maintenance, run it yourself or hand it to another team. See prices.
Questions we get
What is the difference between a website and a web portal?
A website is mostly public and the same for every visitor. A portal is behind a login and different for every user: each customer, partner or supplier sees their own orders, documents, invoices, cases or data, and can act on them. That makes a portal closer to an application than to a website, with accounts, permissions and integrations at its core.
Can customers log in with their company accounts?
Yes. Business customers can sign in with their own Microsoft or Google work accounts, or with their company's identity provider through OpenID Connect or SAML, so their IT team controls who has access. Consumers can use passkeys, email and password with a second factor, or a national electronic identity where one is used in your market.
Can one company have several users with different rights?
Yes. Portals for business customers usually have company accounts with their own administrators, who invite colleagues and decide who can order, approve, see invoices or manage users. Every request is checked against those rights on the server, not only hidden in the screen.
Which systems can the portal connect to?
The ones that hold the data customers want to see: ERP for orders, deliveries and invoices, CRM for contracts and cases, the document archive, the ticketing system and your own databases. The portal reads and writes through their interfaces, so there is one source of truth and no copying by hand.
Does a portal have to be accessible?
If it is used to sell products or services to consumers in the EU, the European Accessibility Act applies to it as an e-commerce service. We build every portal to WCAG 2.2 level AA regardless, because business users have disabilities too and accessible forms are faster for everyone.
Who owns the portal?
Your company. The source code sits in a repository in your own account, and the database and hosting are in your name in an EU data region. You can keep us for maintenance, run it yourself or hand it to another team.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.