Portals, B2B and customer areas
Price lists, orders, customer areas and dossiers: self-service portals that generate revenue instead of another PDF via email.
Price lists, orders, customer areas and dossiers: self-service portals that generate revenue instead of another PDF via email.
There is a precise moment, in many companies, when the customer asks for a simple thing — “can I see my prices?”, “can I place my usual order?”, “what’s the status of my file?” — and the answer is an email attachment. A PDF of the price list, an Excel of the orders, a shared folder with the documents. It works, in a sense. But every attachment is a piece of work you are doing instead of the customer, and it’s margin you are leaving on the table: back-office hours, pricing errors, lost orders, customers getting tired of waiting. This guide collects the articles on how to turn those attachments into a portal: a restricted area where the customer does by themselves what today they make you do, and you stop being the bottleneck.
The word “portal” is abused. For many agencies it’s a restricted area where the customer downloads an invoice and that’s it — a login in front of an archive. That’s not what we’re talking about here. A portal worth its money is self-service that generates revenue or removes cost: the reseller who places the order again at 10 PM without calling you, the agent who sees the right price list for that customer, the anxious customer who uploads documents and sees the status of the file instead of writing you three emails. The difference is not aesthetic: it’s that the portal makes the customer work instead of you, and they do it gladly because it’s faster than the old round of emails.
The thread that ties all the articles in this guide is this: a portal is not a storefront with access, it’s a piece of software that holds a state — who you are, what you can see, at what price, what stage you are at. And the state, when done well, is worth real money: orders coming in at night, pricing errors disappearing, files closing instead of bogging down in attachments.
Every company arrives at the portal topic from a different pain. The most common:
As the articles come out, you’ll find them listed at the bottom of this page.
Under every working portal there are three things the storefront doesn’t have, and that’s where you win or lose. The first is identity: who you are when you log in. Not “a user”, but that customer, with their price list, their orders, their documents. The second is permissions: what you can see and what you can’t. The reseller sees their prices, not the competitor’s; the customer of the file sees their dossier, the office sees everyone’s, the partner sees only theirs. The third is state: what’s the status of the order, the file, the renewal — because it’s the state that removes the phone calls and reminder emails.
When these three things are done badly, the portal becomes the most dangerous place in the company: a customer seeing another’s data is damage you don’t repair with an apology. That’s the reason a portal isn’t “assembled” with a plugin: it’s built, with the same rigor used to build the data model of an internal app, because it’s the same discipline — except here the customer sees the data, and the mistake is seen outside.
There is a rule that applies to every portal in this guide: if it isn’t connected to where the real data lives, it’s theater. An order portal that doesn’t talk to the ERP is a second place to re-enter everything by hand — you moved the copy-paste, you didn’t remove it. A price list on the portal that doesn’t update with the ERP’s is a ticking time bomb: sooner or later the customer orders at a price that no longer exists. The value of a portal lies entirely in the fact that it shows the real data, now, and sends it back in without re-transcription.
This is also the reason why the portal and the numbers dashboard are two sides of the same job: underneath there is always the data layer — clean, updated, with agreed definitions — and on top is the interface, whether it’s the one the owner looks at or the one the customer orders with. If the two layers are done by two different suppliers, they blame each other and you pay two invoices for a portal that gets prices wrong.
Start from the article describing your pain — you don’t need to read them in order. Each one includes the calculation of what you’re leaving on the table, the description of what the customer sees on screen, the honest timeline of a real project, and the “it’s for you if / it’s not for you if” section — because sometimes a ready-made SaaS is enough, and saying so is part of the job.
When you want to see what it would be like to solve it for real on your customers and your ERP, the starting point is the project portfolio or two lines in contacts: we start from how you work today and what your customers ask for, not from a demo.
Below you will find all the articles in this guide.
The treasurer keeps members on a spreadsheet, renewals get forgotten, dues disappear. How to run members, renewals an...
An attachment is always missing, the file stalls, days pass and the margin shrinks. Here is the portal with checklist...
Your agents spend their days copying the same property onto five portals, instead of doing visits and closing. Here i...
You sell courses, content or subscriptions on an American platform that takes a cut and holds your customers and data...
Spoken discounts that don't match the invoice, PDFs that age, agents who get the price wrong in front of the customer...
Your best customer wants to order on their own, at night, with their prices. You send them an Excel «don't forward it...
Antonio Trento — System Architect & AI Integrator
I design and build data, backend, interface and AI agents end-to-end. No slides: systems that run and stay yours.
If a process costs you hours, clients or margin, it can probably be built. Let's talk.
Book a call