CRM & SYSTEMS
CLIENT PORTAL
- 10+ projects
- from 1 week
- built around your processes
An account area for your clients or partners: orders, contracts, statuses, invoices and tickets without phoning a manager. It takes the steady stream of “where is my order” off your support desk.
WHO IS IT FOR?
Three situations where an account area pays for itself fastest
- .01
SUPPORT ANSWERS THE SAME QUESTIONS
“Where is my order”, “send me the invoice”, “when does it ship”, “repeat my last order”. A manager opens the system, finds it, copies it, sends it — dozens of times a day. The cost of that work shows up only in the payroll: people are busy relaying information that is already in the system and that the client could have looked up themselves.
- .02
THE CLIENT CANNOT SEE WHAT IS HAPPENING
The order is accepted and then silence. The client does not know what stage the work is at, and the only way to find out is to write or call. Some of them do not write — they simply leave. Being opaque costs more than it looks: it not only loads the support desk but erodes trust at the very moment everything is going fine and nobody has said so.
- .03
WHOLESALE AND PARTNERS ARE HANDLED BY HAND
Every client has their own prices and terms, orders arrive by email and messenger, price lists go out as files, and stock is confirmed on the phone. The manager is a mandatory link in every deal. Hence the ceiling: the number of partners is limited not by demand but by how many orders the team can process by hand.
WHAT'S INCLUDED
We do not build below this line
- - Registration and sign-in.01
- - Custom design, never a template.02
- - Orders and their statuses.03
- - Documents and invoices.04
- - Support requests.05
- - Notifications on events.06
- - A link to your system.07
- - Admin panel by LUNO.08
- - Launch on our servers.09
- THIS IS THE FLOOR, NOT A PACKAGE
Everything listed ships in every project — even the simplest and cheapest one. There are no stripped-down versions.
- ONE SET OF DATA, NOT TWO DATABASES
The account area shows what is already in your system. An order, a status and a document are entered once — otherwise a second version of the truth appears, and it will have to be reconciled by hand.
- WE START WITH WHAT GETS ASKED MOST
An account area pays off not through the number of sections but through whether it took real enquiries off your desk. During discovery we look at what people come to you with every day, and put that in first.
WHAT'S INSIDE
THIS IS AN INTERFACE, NOT AN ADMIN PANEL
A website gets five minutes of someone’s attention. An internal system gets eight hours, every day, for years. So it is drawn by the same designers who do our sites: grid, typography, states, light and dark themes, tables you can actually read, forms where you can see where you are and what happens next. This is not about looks. It is about a person not being worn out by their own working tool by the end of the day, and not making the mistake the interface invited. Systems assembled as a pile of forms over a database all end the same way: the team goes round them and returns to spreadsheets and chats.
THE PATH TO AN ACTION IS SHORTER THAN IT LOOKS
A system is measured not by how many features it has but by how many actions the thing done a hundred times a day takes. We look at the order people actually work in and build the interface around it: search that finds on any fragment, filters that survive between sessions, bulk actions instead of one-by-one, keyboard shortcuts where the work is fast, and no page reload on every move. The difference between two clicks and seven is invisible in a demo and very obvious in the second week.
EVERYONE SEES THEIR OWN SYSTEM
A role is not a set of checkboxes over one shared screen but an interface of its own: a manager sees their deals, the warehouse sees shipments, a director sees the numbers, a client in their account sees only what is theirs. Nobody has to hunt for what they need among somebody else’s work, and data they are not entitled to never reaches the screen at all. Alongside it lives the history: every record shows who changed it and when. In systems holding money and documents, that is the first thing people ask for the moment the numbers stop agreeing.
A SYSTEM THAT DOES NOT FALL APART ON THE SECOND THOUSAND RECORDS
Internal systems break not on handover day but a year later: there are a hundred thousand records, the list takes ten seconds to load, the quarterly report will not open, and the search is still thinking. That is not the server — it is how the data and the queries were designed. We plan for the volume with room to grow: heavy calculations are computed ahead of time, lists load in parts, reports do not block everybody else. Plus an export of whatever is on screen — because at some point every director wants it in a spreadsheet, and it is better if that button already exists.
CATEGORIES
Three levels of scope. Yours is the one you recognise yourself in
A CLIENT ACCOUNT
WHEN IS THIS YOUR CASE?
Clients come to you for the same handful of things: the status of an order, documents, repeating a previous order, the history. It needs to live somewhere they can look it up themselves. The whole base build: registration and sign-in, design made for you, orders and statuses, documents and invoices, support requests, notifications, a link to your system, admin panel, launch on our servers. Nothing stripped out — just without the extras you do not need yet.
A B2B ACCOUNT
WHEN IS THIS YOUR CASE?
You work with companies, wholesale or partners, and each has their own prices, terms and payment windows. Individual price lists and contract discounts, ordering against live stock, several people from one client each with their own rights, invoices and closing documents, shipments and settlements, repeat orders from the history. Plus an integration with your accounting system, so stock and prices are never entered twice.
A PARTNER PLATFORM
WHEN IS THIS YOUR CASE?
It is not only clients using it: dealers, suppliers, contractors, referral partners — each with an interface and a logic of their own. A role model by type of participant, commission calculations and figures for every one of them, data access over an API, several languages and currencies, heavy load and large volumes. The logic is designed around your processes rather than bent to fit someone else’s limits.
FAQ
Answers to the most popular questions
From $3.000 for a client account to $12.000 and up for a platform with several kinds of participant. The figure depends on how many sections move into it, on whether it needs individual pricing and documents, and on which system it has to exchange data with. After the first call you get a plan rather than a guess: what makes up the total, and what can wait for a second stage.
A client account takes 1–4 weeks. A B2B account with pricing, documents and an integration, 2–6 weeks. A partner platform, from 4 weeks. What usually takes longest is not the account area itself but the link to your system: the cleaner the data there, the faster the work goes.
It depends who uses it. For shoppers on an online store the account is part of the site: the same sign-in, the same cart, the same database. For wholesale buyers, dealers and partners it is more often a separate entrance with its own rules: their prices, their documents, their logic. We settle it on the first call — both the architecture and the price follow from the answer.
That is the usual situation: the account area does not replace it but gives clients access to the part of the data they need. We connect through an API where there is one, or through a data exchange where there is not. Orders, stock, prices and documents stay where they are already kept — no second database appears.
Access control goes into the foundations: everyone sees only their own data, and different people at the same client can hold different rights. Every action is journalled — you can see who looked at what and who changed it. The project lives on our infrastructure with monitoring and backups, run by someone with twenty years behind them. For sensitive data it can be hosted inside your own perimeter instead.
That happens when the account area was built as a box to tick rather than around the enquiries you actually get. So we start with discovery: we look at what people come to you with every day and put exactly that in first. After which small things help — a link in the order email, in a manager’s signature, in a status notification. A client goes in once for something they needed, and after that comes back on their own.
Yes. We connect payment providers that have an API — cards, wallets, invoicing for companies. For B2B it is more often payment against an issued invoice with the status tracked; for retail, an ordinary card payment. Which suits you depends on how you take money today.
You do. The sources, the rights and the documentation are handed over with the project — this is not a subscription and not a tie to us. There is no per-user fee: the number of clients in the account area does not change what it costs.
The account area can stay on our infrastructure: monitoring, backups, updates, further work. After launch it almost always becomes clear what clients are missing — usually one or two sections nobody had thought about before. The arrangement is agreed separately.