When customers repeatedly ask for a document, an update or the next approval, the problem is often a fragmented service journey. Information lives across email, shared folders and internal systems, while the customer has no reliable place to check progress.
A B2B customer portal can bring those tasks together. It is a private workspace for an organisation and its authorised users. The useful starting point is one recurring customer job, rather than a long feature list. For many Irish service businesses, that job is submitting a request and knowing what happens next.
Choose one journey for the first version
Map a real request from first contact to completion. Record what the customer supplies, who checks it, what causes delays and how the final result reaches them. A maintenance provider might start with service requests and visit updates; a consultancy might start with document collection and approval.
Write a concrete completion condition. “Customers can upload the requested documents and see which items still need attention” is testable. “Customers can manage everything” is not. Keep an assisted route available for customers who need help during the pilot.
Separate organisations, people and permissions
An account is not always a single person. One customer organisation may have an administrator, staff who submit requests and a finance contact who only needs invoices. Decide who can invite colleagues, approve work and download records. Also decide what happens when someone leaves that organisation.
The OWASP Authorization Cheat Sheet recommends denying access by default and checking permissions on every request. In a portal, this means checking access to each organisation’s records and files on the server. Hiding a menu item does not enforce access control.
Keep sign-in and authorisation as separate requirements. Our passkeys and account recovery guide covers authentication choices; the portal still needs clear rules governing what a signed-in person may do.
Make status useful and specific
Replace vague labels such as “processing” with states customers can understand. A simple sequence might be submitted, information needed, scheduled and completed. Each state should explain whether the customer needs to act, who owns the next step and when an update can reasonably be expected.
Show the latest meaningful update first, with a dated history underneath. Use notifications for changes that need attention instead of emailing for every small edit. Link notifications back to the relevant request, and require sign-in before showing private information.
Connect the systems that own the information
Choose a source of truth for each record. The CRM might own organisation details, an operations tool might own job status, and an accounting platform might own invoices. Document which fields the portal may change and how updates return to the original system.
Plan the failure states too. If an integration is temporarily unavailable, the portal should distinguish an accepted request from one still waiting to sync. Give staff a visible queue for failed updates. Do not let customers assume a request reached the delivery team when it only reached a web form.
Test with two organisations, not just two users
A useful acceptance test creates separate customer organisations with separate documents and requests. Test direct links, downloads, invitations and role changes. A user from one organisation must not gain access to the other’s records by changing an identifier or opening an old link.
Then observe customers completing the main task on a phone and a laptop. Can they identify missing information, recover from an upload error and find an earlier result? For the welcome journey, our SaaS onboarding UX guide explains how to focus on the first useful outcome.
Decide what success means before rollout
Measure completed requests, avoidable status enquiries, missing-document follow-ups and staff handling time. Compare similar work before and after the pilot. Low portal usage may indicate an unclear benefit, a difficult sign-in journey or a customer task that still requires email.
Elephantfly provides web application development in Ireland and application security support. Discuss a portal project with a sample customer journey, the systems involved and the problem your first release needs to solve.
