A client portal that knows more than an inbox.
You build software for clients, and the clients get in touch by mail, phone and chat. A client portal collects those requests in one place. Lalabase goes one step further. The client works in the same project as you, and the project remembers everything that was ever said about it.
What it looks like for your client
Each client gets an area of their own with their own logins. What one client sees, the next never does. All organisations hang off your one account.
The client creates tickets and comments on them. No forwarded mails, no spreadsheet somebody types up.
If you allow it, the client asks the AI about their project or a feature. It answers only from areas they may read, and names its sources.
The client does not see private comments or areas you have not opened to them. Client accounts cost nothing.
What it is not
Not everyone means the same thing by "client portal". Lalabase does not have three of them.
- No invoices or payments in the portal. Lalabase prepares the hours for billing, your accounting writes the invoice.
- No branding of your own, so no logo and no domain of your own per client.
- No simplified client interface. The client sees the same interface as you, with the rights you give them.
What people ask at this point
- Why not just a help desk?
- A help desk answers requests and closes them. With software built for a client, every request hangs on the history before it, on who decided what and why a feature was built that way. That history sits in the same project here.
- Does every client cost extra?
- No. Client accounts are free, you pay per person on your team.
- Does the AI have to be on?
- No. AI is off by default, and you decide per role whether clients may use it.
Look at it
rather than take our word for it.
Productive in under 5 minutes. No sales loop.