○Drawn, not built.
Every screen below is a drawing of what these doors will be, published early so it can be argued with. Coming soon.
Open a door onto your business.
Say who it’s for.
Your customers, your suppliers, your own people — each arriving for their own reason, not through a generic guest pass. You choose which kind when you open the door, and everything they see follows from that one choice.
None of this is built yet. It is drawn end to end so it can be argued with before a line of it is written — which is cheaper here than in the build. Every phase below says plainly where it actually is.
Pick the kind of person who comes through it. You are choosing what they can see and do.
Why doors, and not just more app.
“This would build a whole ecosystem of users using bisbe for their own specific purposes.”
Every door a firm opens brings that firm’s own people into the product — a shop checking what it is owed, a supplier confirming a shipment, a customer watching a claim. They come for their own purpose, they stay because the door fits it, and some of them go on to run their own business in here too. That last step is where the word ecosystem stops being a flourish.
One kind of outside person, one purpose, one fence
A door onto your business, for one kind of person. They see their own rows and nobody else’s — their account’s, their supplier’s, or their own.
A guest login with most of the app hidden
Hiding things from a general-purpose account is how portals normally get built, and it is why they feel like a worse version of the real thing. Purpose-fit is the opposite move.
Five kinds of door. One thing underneath.
These are not five products, and they are not five builds. They are five settings of one portal, chosen when it is created. That is why a sixth kind costs nothing — and if a sixth kind ever needed new code, the settings would be the wrong ones.
Business customers
Shops and businesses that buy from you. The ordering portal that already exists is this kind — the first instance of the one thing, not the first of five things.
- Hang off
- a customer account
- Get in by
- invitation to the address on that account
- They see
- their orders, at their prices
- They can
- place an order · ask a question
Members of the public
People who bought your product and have no account with you. There is nothing to invite them from, so they let themselves in by registering what they bought.
- Hang off
- no record at all, until they make one
- Get in by
- registering the thing they bought
- They see
- what is covered, and until when
- They can
- file a claim · ask a question
Businesses you buy from
Suppliers. The same machine pointed the other way down the trade — and the clearest proof that the settings are doing the work.
- Hang off
- a supplier record
- Get in by
- invitation to the address on that record
- They see
- what you ordered, and when it is due
- They can
- confirm a shipment · flag a delay
Your own people
Staff who need one narrow slice and nothing else — a warehouse, a workshop, a van. Added by an admin rather than invited.
- Hang off
- a person on your team
- Get in by
- being added by an admin
- They see
- the jobs assigned to them
- They can
- update a job
A team who answer people
Customer service. The one shape that hangs off a queue rather than a record — a team’s work, not a person’s.
- Hang off
- a named team
- Get in by
- being added by an admin
- They see
- the queue for that team
- They can
- answer · hand on · close
And the ones nobody has asked for yet
A contractor doing field work. A reseller selling onward. A branch trading under your name. Someone acting on a customer’s behalf. Each is the same settings in a different arrangement.
- Cost
- no new screens, no new build
- Which ones
- a product call, not a technical one
One queue, grouped by the door they came through. A supplier confirming a shipment and a shop filing a claim are different work for different people — so every message carries which portal and which kind of person it came from, and the grouping does the sorting nobody wants to do by hand. See the queue.
Each door gets its own welcome. Nobody builds a second app.
When a portal is created, the firm writes what greets the people who come through it: the line at the top, what it is for, and the one first thing to do. That writing is the whole difference between one persona and another.
Your orders, your prices, and the line sheet as it changes.
Open this season’s line sheetWhat we have ordered from you, when it is due, and where to tell us it shipped.
See what’s outstandingSame screen. Same code. Three pieces of text and one button label are different, and a firm typed all four when it created the portal. That is the entire distance between a customer portal and a supplier portal — and it is the thing the drawings exist to test, because if these two ever needed to be different screens, the architecture underneath would be wrong.
Invitations come from wherever the kind says people live — a customer account, a supplier record, your own team list. For a portal with no records behind it there is nobody to invite, so that one opens with a way in instead of a list, and the screen says so rather than showing an empty table. The invite screen.
Your manual, on your own website.
You have already written the pages that answer your customers. Publishing is choosing which of them a stranger may read, and at what address — not writing them again.
Everything is private until you say otherwise.
Care and returns go out; trade pricing and mill contacts stay in. Choosing is a deliberate, separate act from writing, because the two get confused exactly once and then it is on the internet.
At your address, with our name absent.
Two records added wherever your website is registered, and we show you the exact two lines. A customer who lands there from a search has no reason to learn we exist. Every page carries its version and the date it was last confirmed, because a manual without those is one nobody trusts twice.
Written by Atlantica · every page dated and versioned
What your customer sees without ringing you.
“Is this still covered?” and “what is happening with my claim?” are the two questions that generate the phone call. Answering them on a screen someone can reach at midnight is most of the value of opening the door at all.
On what, until when — and filing from inside the answer
Cover that has ended is said plainly rather than hidden, because a customer who cannot see the end date rings to ask about it. And the claim starts from the answer they are already looking at, so the order, the date and the cover are never asked for twice.
- 01Spring swim · dye-lot and stitching, until 12 March 2027
- 02Linen cover-ups · stitching only, until 4 June 2027
- 03Beach totes · cover ended 2 February 2026
“We’re looking into it” is what makes people ring
Received, inspected, waiting on a decision — due 15 August, then replacement or credit. A state with a date attached is a promise that can be kept, or visibly missed. A state without one is an invitation to chase it.
Every step is told by a word and a shape — filled, ringed, hollow — so nothing on the screen depends on telling two colours apart.
Where this actually is, said here rather than found later.
One phase is moving. The other six are drawn and nothing more. They are in the order they have to happen in, because each one needs the one above it.
One firm’s records are one firm’s records
The fence, in the database itself, before any outside person is let in. Everything else waits on this and it is the least visible work in the programme.
Moving nowThe portal engine, and its persona
Creating a portal, choosing the kind, writing the welcome, and opening the first door by hand for one kind before anything is self-serve.
Drawn onlyThe manual, on the firm’s own website
Choosing the public pages, the firm’s own web address, and the two records that point it here.
Drawn onlyA warranty becomes a real record
What is covered, on what, until when — as a thing the product actually holds rather than a page about it.
Drawn onlyThe person watches the wait
Claim states, the verdict, and the date. The screen the whole promise rests on.
Drawn onlyFirms create and run their own portals
Without us opening each one by hand. This is the step where the programme stops costing us a person per customer.
Drawn onlyA stranger makes their own account and their own firm
The loop closing: someone who came through one firm’s door goes on to run their own business in here. The furthest from being real.
Drawn onlyNone are set, and that is not coyness. The drawings exist so the shape can be argued with before anyone commits to building it, and putting a date on a thing that has not been agreed is how the date becomes the plan. What you can do meanwhile is walk the whole thing and tell us where it is wrong.
Fifteen screens. Walk them and push back.
The whole programme drawn end to end — a firm opens a door, chooses who it is for, writes what greets them, and two different kinds of person come through it. Nothing writes, nothing is live, and every control goes somewhere.
These fifteen are the spine of it. The full set is forty-four — seven acts, nine routes that run end to end, every edge case where the thing goes wrong, and one screen you can re-render as five different kinds of person to see exactly what changes. Same drawings, nothing skipped. It asks who you are before it shows you anything, so you land on the ones that concern you.
ABOUT THIS PAGE · This is the future state of client portals — doors a firm opens onto its own business, one kind of person at a time. None of it is built. Atlantica, Marisol’s Beachwear and Hacienda Textiles are invented, and so is everyone in them. What Bisbe does today is on the main page; the offering that is furthest along is white label.