Your customers call
because they see nothing.
Where is my order, has that invoice been processed, which quote was it again. The same question every time, someone looking it up and calling back every time. A client portal takes that work away: your customer logs in and sees their own file, you see who looked at what.
Why companies start on this.
The same question, every week
Status, planning, invoices, documents. Every one of them data you already have, but that your customer can only reach through you.
Everything goes through email
Attachments that get lost, versions that do not match, and afterwards no trace at all of who approved what and when.
Everyone sees too much or too little
A shared folder or spreadsheet has no roles. One wrong link and customer A is looking at customer B's file.
Your team works in three systems
Planning here, invoices there, client details in a third tool. Nobody knows which source is right anymore.
Growth means more manual work
Twice as many customers currently means twice as much looking up and forwarding. That does not scale with your revenue.
Your customers expect it
Everyone knows a portal from their insurer or supplier. Not having one now stands out.
From first call to a portal that actually gets used.
Work out who may see what
Which roles exist, which data belongs to which customer, and what an employee may do that a customer may not. This decides the rest of the build.
Connect to what you already have
Your accounting, CRM or planning stays the source. The portal shows that data; it does not become a fourth place where someone retypes the same thing.
Build with permissions in the database
Row-level security in Supabase, so every customer can only reach their own file. Even if someone skips the front end.
Roll out with a few customers
A pilot with a handful of users first, then everyone. Including a short walkthrough so your team can manage it themselves.
- ✓Customers who see their own file
- ✓Login with roles and permissions per user
- ✓Integration with your accounting, CRM or planning
- ✓An admin side where your team manages everything
- ✓Repository and hosting in your name
The price depends mostly on the number of integrations, not the number of screens. After a half-hour call I know enough for an indication, and after Discovery you get a fixed number.
What does a client portal cost?
How long does it take?
Can it connect to our current system?
How safe is it when customers can log in?
What if we want to extend it later?
We already built something with an AI tool. Can that come along?
Tell me what you
want to build.
A half-hour call. You get an honest answer about what it costs, how long it takes and whether building it is smart at all.
The overview your team gets.
A working example, not a screenshot: change the period and hover over a bar. In a real portal this data comes from your accounting or planning, and every customer only sees their own rows.
| Month | Revenue | Orders |
|---|---|---|
| Feb | €18,400 | 42 |
| Mar | €21,900 | 51 |
| Apr | €19,700 | 46 |
| May | €24,300 | 58 |
| Jun | €27,800 | 63 |
| Jul | €25,100 | 55 |
| Aug | €22,600 | 49 |
| Sep | €29,400 | 68 |
| Oct | €31,200 | 74 |
| Nov | €35,800 | 86 |
| Dec | €41,300 | 97 |
| Jan | €33,500 | 79 |
More working examples are on the demo page.