Client portal
Clients see their orders, documents, statuses and balance in one place. The «any news on this?» messages all but stop.
- Buildfrom $2,850
- Timeline4–7 weeks
- Supportfrom $570/mo
Who this suits: Businesses where the same questions arrive by chat every day, documents are re-sent on request, and a manager is a search interface to a folder.
What is in the first version
- sign-in and roles
- orders and statuses
- documents and invoices
- change notifications
The figures above are the package this sits on: CRM or client portal. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
Signing in is not a barrier
A link, a code or a company account, whichever fits your clients; a forgotten password is not a support ticket.
- 02
The same status you see
The portal reads the system that is already the truth rather than keeping a second copy that drifts by Thursday.
- 03
Changes reach them without a manager
Shipped, signed, paid, delayed: whatever they would have asked about arrives as a notification with a link to the order.
What decides whether this works or annoys people
Who is allowed to see what
Two people from one client company rarely need equal access, and never another company’s data: that is a rule in the data.
An empty portal is worse
If half the documents still go by chat, nobody logs in twice, so the first version covers the questions that get asked.
It works on a phone
The person checking whether the delivery left is standing somewhere, not sitting at a desk.
What to measure once it is live
- questions no longer asked by chat
- clients who log in twice
- documents downloaded without a request
- manager hours returned
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- FrontendTypeScriptReactNext.js
- Backend and dataNode.jsPostgreSQLPrismaRedisS3
- Integrations and monitoringTelegram Bot APIn8nDockerSentry
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- Hosting, servers and document storage
- The domain, registered to your business
- Email and SMS notifications
- Payment provider fees on invoices paid
Asked before the first call
- Can it live inside our existing site?
- Yes, as a section behind sign-in, and that is usually cheaper than a separate product. What decides it is where your data already lives.
- Will clients actually use it?
- They go where the answer is. The link to the exact order sits inside every status notification, so the message they already read is what takes them into the portal.
- Who manages access when the client’s staff change?
- An administrator on the client side adds and switches off their own people from inside the portal. Otherwise it becomes a letter to your manager and an account nobody closes.