Customer and client portal development
A secure place where your customers check status, download documents, pay invoices and raise requests, built on the records your team already keeps.
Good morning, Jo
Open requests
+ New request- RQ-2481Replace compressor, site 3decision by 16 Octin_review
- RQ-2470Quarterly inspectionThu 17 Oct, 09:00scheduled
- RQ-2466Access badge resetclosed 9 Octclosed
Latest invoice
INV-10482 · due 30 Oct
$1,860.00
Recent documents
- Service report · Sep
- Contract FM-118
- Site 3 asset list
what it’s for
What a customer portal is used for
A portal pays for itself by taking repeat work off your team. Each job below is a question customers currently ask a person.
| the customer asks | in the portal they | what disappears |
|---|---|---|
| statusWhere is my order, request or case? | Sees the current state, the next step and the expected date. | “Any update?” e-mails and status calls. |
| documentsCan you send me the contract, report or certificate? | Downloads current documents for their own account. | Searching inboxes and re-sending attachments. |
| invoicesWhat do we owe, and can we pay now? | Sees invoices and balance, pays by card or bank transfer, downloads receipts. | Statement requests and chasing payment by phone. |
| requestsI need something done. | Raises a request with the right fields, files and priority from the start. | Back-and-forth to collect missing details. |
| accountWho in our company can do what? | Their own account admin adds colleagues and sets their access. | User-admin tickets for your team. |
| messagesI have a question about this. | Messages your team on the record itself. | Context lost across e-mail threads and personal inboxes. |
one record
Same request, two sides
A customer portal isn’t a copy of your data on a separate website. The customer and your team work on the same record, each through the view their role allows. That’s why nothing needs re-typing and the status is always current.
customerWhat the customer sees
RQ-2481
Replace compressor, site 3
- Sent (completed)
- Being reviewed (current state)
- Approved (not reached)
- Visit booked (not reached)
- ops · 10:04Could you send a photo of the unit label?
- you · 10:21Attached: label.jpg
Plain-language state names, the conversation and their files. No cost until approved, no internal notes.
staffWhat your team sees
- quoted_cost
- $3,420.00 from ERP
- assigned_to
- M. Okafor
- internal_note
- Parts at north depot
- files
- label.jpg, 2 photos
The working record: cost from the ERP, SLA clock, assignment, internal notes and the actions their role allows.
Both views read and write the same record. State, messages, files and dates are shared; cost, SLA, assignment and internal notes are visible to staff only.
anatomy
Anatomy of a customer portal
Most portals are built from the same seven areas. In custom customer portal development, what makes yours specific is the data behind each one and the rules about who sees it.
| area | what customers do | data usually comes from |
|---|---|---|
| Dashboard | See what needs their attention: open requests, due invoices, new documents | Summary of the areas below |
| Account | Manage company details, users and notification preferences | Your CRM, plus the portal’s own user store |
| Requests and tickets | Raise, follow and reply to requests, orders or cases | Your operations system or help desk |
| Documents | Download contracts, reports, certificates; upload files you need from them | File storage, document management, ERP |
| Payments | See invoices and balance, pay online, download receipts | Billing or accounting, plus a payment provider |
| Messages | Talk to your team in the context of a record | The portal, mirrored to e-mail where useful |
| Status tracking | Follow progress through clear, customer-friendly states | Workflow states in your systems, mapped to plain language |
security
Is a customer portal secure?
It has to be designed in from the first day, because a portal exposes your data outside the company. These are the controls we build into every portal.
Sign-in that fits the customer
E-mail and password with multi-factor, passwordless links for occasional users, or single sign-on with the customer’s own identity provider for larger accounts.
Account isolation on the server
Every query is filtered by the customer’s organization in the API. The browser never receives another account’s data, whatever the interface shows.
Roles inside each account
Customer admins manage their own users; finance users see invoices; requesters see their requests. Your staff get separate, audited support access.
Audit and data handling
An audit log of views and changes, encryption in transit and at rest, retention rules, and hosting in the region your contracts require.
org: alder-finch
- account_adminCustomer’s portal owner
- financeAccounts payable
- requesterSite or team contact
Created and managed by the customer’s own account admin.
your team
- supportRead access, logged, time-limited
- portal_adminSettings and rules for all accounts
| role | requests | invoices | documents | users | available actions |
|---|---|---|---|---|---|
| account_admin | allowed | allowed | allowed | allowed | Invite userPay invoiceRaise request |
| finance | view | allowed | allowed | not allowed | Pay invoiceDownload receipt |
| requester | own | not allowed | view | not allowed | Raise requestMessage team |
-
account_admin Customer’s portal owner
canrequests, invoices, documents, users
seesInvite user · Pay invoice · Raise request
-
finance Accounts payable
canrequests (view), invoices, documents
seesPay invoice · Download receipt
-
requester Site or team contact
canrequests (own), documents (view)
seesRaise request · Message team
integrations
Built on the systems you already run
A portal is only as good as its data. We connect it to your systems of record through their APIs, decide per field which system wins, and queue changes so a slow or offline system never loses a customer’s update. When the CRM is the main source, the sync work is the subject of our CRM integration service.
-
Identity providerinto the app
whenEach sign-in
movesWho the user is; for SSO accounts, their groups
-
CRMboth ways
whenAccount or contact changes
movesAccounts and contacts in; portal activity and requests out · queued, retried
-
ERP or operations systemboth ways
whenOrder or job changes
movesOrder and job status in; new requests out · queued, retried
-
Billing / accountingboth ways
whenInvoice issued or paid
movesInvoices and balances in; payment confirmations out
-
File storageinto the app
whenDocument published
movesContracts, reports and certificates for the account
-
E-mail and SMSout of the app
whenState changes
movesNotifications with a deep link back to the record
| system | direction | when | what moves |
|---|---|---|---|
| Identity provider | into the app | Each sign-in | Who the user is; for SSO accounts, their groups |
| CRM | both ways · queued, retried | Account or contact changes | Accounts and contacts in; portal activity and requests out |
| ERP or operations system | both ways · queued, retried | Order or job changes | Order and job status in; new requests out |
| Billing / accounting | both ways | Invoice issued or paid | Invoices and balances in; payment confirmations out |
| File storage | into the app | Document published | Contracts, reports and certificates for the account |
| E-mail and SMS | out of the app | State changes | Notifications with a deep link back to the record |
client portals
Client portals for professional and B2B services
When your customers are clients on an engagement (accounting, legal, consulting, agencies, engineering, managed services), the portal centres on the engagement rather than on orders.
- Secure file exchange with requests for specific documents and reminders until they arrive.
- Approvals and sign-offs on deliverables, recorded with who approved what and when.
- Engagement progress as milestones the client can follow without a status meeting.
- Invoices against engagements, with work-in-progress visible where your contracts allow it.
- Client-side users: the partner, the finance contact and the day-to-day contact each see what concerns them.
build or buy
Custom portal or portal software?
Packaged portal products are a good answer for some companies, and customer portal software development isn’t always the right call. A custom portal makes sense when your data, rules or customers don’t fit their model. An honest comparison:
| Compared on | packaged portal software | custom customer portal |
|---|---|---|
| Best when | Your process matches the product and your data already lives in its ecosystem | Your process, pricing or data model is specific, or spans several systems |
| Data | Usually needs data copied into the vendor’s platform | Reads and writes your existing systems through their APIs |
| Experience | Configurable within the product’s screens | Designed around your customers’ jobs and your brand |
| Cost profile | Lower to start; per-user or per-account fees grow with adoption | Higher to start; no per-user fees; you own the code |
| Change | Limited by the vendor’s roadmap | Changes when your business changes |
how it’s built
How we build a customer portal
Customer self-service portal development succeeds when customers use the result. The order of work is designed for adoption as much as for engineering, which is what to ask any customer portal development company or client portal development company about.
-
Step 1: List the questions customers ask
We go through a sample of e-mails, calls and tickets with your team and sort them by job. That ranking decides what the first release covers.
you getA ranked list of portal jobs and the data each one needs.
-
Step 2: Find where the answers live
For every job, the system that holds the truth (CRM, ERP, billing, file store, help desk) and how fresh the portal copy needs to be.
you getA data-source map with sync direction and timing.
-
Step 3: Design identity and roles
How customers sign in, how accounts and their users are modelled, what each role can see, and how staff support customers without sharing passwords.
you getAn access model and sign-in flows.
-
Step 4: Pilot with a few accounts
A working portal for a handful of friendly customers, with the two or three jobs that remove the most contact, and real feedback before the wider roll-out.
you getA live pilot and a list of changes from real use.
-
Step 5: Roll out and drive adoption
Invitations in waves, links to the portal from your e-mails and invoices, and reporting on which jobs are now self-served.
you getUsage reporting and the next increments.
which portal
Customer, partner or supplier portal?
The difference is who is on the other side of the login, and that changes the records, the rules and the integrations.
| Compared on | who signs in | core records | typical integrations |
|---|---|---|---|
| Customer or client portal | Your customers and their colleagues | Requests, orders, documents, invoices | CRM, operations system, billing |
| Partner portal | Dealers, distributors, resellers | Price lists, quotes, orders, deal registrations | ERP, CRM, product data |
| Supplier portal | Your suppliers and vendors | Onboarding documents, purchase orders, delivery notices, invoices | ERP, procurement, accounts payable |
Budgeting a portal? The cost is driven by the number of data sources, the sign-in model and two-way sync, more than by screens. See what drives custom web application development cost.
faq
Frequently asked questions
What is a customer portal?
A customer portal is a secure, signed-in area of your website where customers see and act on their own information: request and order status, documents, invoices and payments, messages and account users. It reads and writes the same records your team works on, so customers can answer their own questions.
What is a client portal used for?
Professional and B2B service firms use client portals to share documents securely, collect files and approvals from clients, show the progress of an engagement or case, and issue and collect invoices, all in one place instead of across e-mail threads.
What features does a self-service portal usually include?
Typical features are account sign-in with single sign-on or multi-factor authentication, a status overview, request or ticket submission, documents, invoices with online payment, messages tied to a record, and user management for the customer’s own administrators.
How do you build a customer portal?
Start from the questions customers ask most, map which system holds each answer, design how customers sign in and what each role can see, then pilot with a few accounts before rolling out. The portal sits on top of your CRM, ERP and billing through their APIs rather than replacing them.
Is a client portal safe?
It is when it is built for it: authentication with multi-factor or single sign-on, every query filtered by the customer’s organization on the server, role-based permissions inside each account, encrypted connections and storage, and an audit log of who saw and changed what.
Can customers pay invoices through the portal?
Yes. The portal shows invoices from your billing or accounting system and takes payment through a payment provider. The payment confirmation updates the invoice status in the portal and in accounting automatically.
Does a customer portal replace our CRM or help desk?
No. Your CRM and help desk remain the tools your team uses. The portal is the customer-facing layer on top of them, reading and writing through their APIs, so nothing is entered twice.
How long does it take to launch a customer portal?
A pilot covering the two or three most common customer jobs can usually go live well before the full scope, because it reuses your existing systems of record. The total timeline depends on the number of data sources, the sign-in model and how much needs to sync both ways.
project brief
Tell us about your customers
Which questions do they ask most, and where do the answers live today? We reply with questions, then a scoped proposal for a first portal release.
- 01
We read it and reply with the questions that decide scope.
- 02
A working session mapping records, roles, rules and integrations.
- 03
A written proposal with phases, assumptions and what each phase delivers.