Client and partner portals
Your clients see where things stand without asking
We build portals where clients and partners log in to see their orders, documents and status, send requests and upload files. The data comes from your CRM, ERP or project tool, so nobody copies it over.
Client portal
ProjectsDocumentsInvoicesSupport
- Project AAwaiting approval
- Project BIn progress
- InvoicesAll paid
What it is
The answers your team gives by email, available at any hour
A large share of client email is the same few questions: where is my order, can you send that document again, has the invoice been issued. A portal answers them from your own systems. Each client sees only their own records, and anything they send arrives in the right place with the right reference attached.
- Each client or partner sees only what belongs to them
- Status and documents come straight from the CRM, ERP or project tool
- Requests land in a queue with an owner, not in someone’s inbox
- Carries your name and design, on your own domain
Portal · my orders
- OOrder 1042Shipped · tracking availableShipped
- OOrder 1047In production · stage 2 of 3In progress
- OOrder 1051Waiting for your confirmationAction
- SService request 88Technician assignedScheduled
What we deliver
What a portal usually contains
Accounts and access
Login by email link or password, several users per client company, and roles that decide who sees what.
Status and history
Orders, projects, tickets or cases with their current stage and what happened before, read from your systems.
Documents
Quotes, contracts, invoices and reports to download, and a place for the client to upload what you need from them.
Requests and approvals
Forms for new requests, changes and approvals, each one routed to the right person with the context attached.
Notifications
Email when something changes or is waiting for the client, so the portal is visited when there is a reason.
Integrations
Two-way links to your CRM, ERP, project tool and document storage, so the portal never holds a second copy.
How a project runs
From the three most common questions to a full portal
- 01
Map what clients ask
We go through recent client emails and calls and list what people ask for most, and where the answer lives today.
- 02
First version
Login, one or two views and one request form, connected to the real data and tried with a handful of clients.
- 03
Extend
Documents, approvals, notifications and further views are added as clients start to rely on the portal.
- 04
Care
We monitor the integrations, keep the software up to date and add what clients ask for next.
What we build with
- Application
- Next.js, React, TypeScript, PostgreSQL
- Connected to
- Pipedrive, HubSpot, Odoo, Your project tool, Document storage
- Around it
- Email notifications, Role-based access, Audit log, n8n
Do you need a portal?
A good fit when…
- Clients regularly ask for status, documents or invoices by email
- You collect files or approvals from clients and chase them by hand
- Partners or dealers need to place orders or see their own data
- The information already exists in a system, just not where clients can see it
Probably not for you when…
- You have a handful of clients and speak to each of them weekly
- The data clients would want to see is not recorded anywhere yet
- A shared folder and a clear email already cover it
- Your CRM or helpdesk already includes a portal that does the job
Use cases
Where portals are used
Problems a portal is often part of solving.
An assistant that answers from your documents
Staff or customers ask in plain language and get an answer drawn from your documents, with the source shown.
Open use case OperationsBusiness automationCustom softwareNew colleagues ready on day one
Accounts, equipment, documents and first-week tasks set in motion from one form.
Open use caseQuestions about portals
How is client data kept separate?
Access is enforced on the server for every request, so a user can only read records linked to their own company. Roles decide what each user may see and do, and important actions are recorded in a log.
Does the portal store a copy of our data?
As little as possible. Where your CRM or ERP is the source, the portal reads from it and writes back to it. It keeps its own records only for things that live nowhere else, such as portal users and requests.
How do clients log in?
Usually with an email link or a password, with a second factor where the data calls for it. If your clients already have accounts with you elsewhere, we look at reusing those.
Can it carry our brand and run on our domain?
Yes. The portal uses your design and runs on an address of your choice, for example a subdomain of your website.
Can clients use it on a phone?
Yes. Portals are built to work in a phone browser. If clients need offline use, the camera or push notifications, a mobile app may be the better form, and we will say so.
Who owns the code?
You do. The code lives in your repository, the hosting is in your account, and the documentation is written to be handed over.
Show us one process. We will show you what it could look like.
The analysis is free, takes about an hour of your time, and ends with a written summary you keep.
Prefer to read first? See examples