One place for every client, from the first proposal to the handover.
Everything about a client in one place they log into and you run from one screen: the proposal, the agreement, the onboarding, the work in flight, the handover and the library. Your client needs a browser. You and your team work with AI inside it, on the same record the client is looking at.
It is two-sided on purpose. Your client sees their own garden and no one else's, and your plan stays withheld until they agree to it. That one wall is what the whole portal is built around.
Where the work stands, the moment they sign in. What is on the board, what has been logged, what is waiting on a signature, and nothing they have to hunt for.
What you are proposing, read in the garden rather than as an attachment that gets forwarded. It is theirs to read as often as they like, and yours to change until they agree.
What was agreed, signed in place, with the payment plan attached to it. The plan unlocks the moment they agree and stays withheld until then.
The start, as a checklist rather than an email thread. Each step opens when the one before it is done, so nobody is chasing and nobody is guessing what comes next.
The board, and both sides can see it move. Cards arrive from the page itself or from your sessions, and the calls and the record sit underneath, so what was said and what is owed live in the same place.
What they built with you, gathered in one place and theirs to keep. The end of an engagement stops being a folder you assemble by hand.
The shelf everything sits on: guides, recordings, templates, how things are done here. They come back to it the whole way through.
Every client from one screen, the journey from first contact to staying close, and a visibility toggle per step, so a step is shown to a client when you decide and not before.
The owner seat. Every client from one screen, AI on all of it, and the system is yours to extend.
A seat on the gardens they work in. With an AI seat or without one, decided per person.
A browser. Their own garden and nothing else, nothing to install, and never an AI account.
Your own database project, in your region. Client data lives there and nowhere else. The files, the code and the data are handed over, and what each seat can see and do is tested from a real login before that happens.
It replaces the client portal, the proposal tool, the e-signature tool, the CRM, and the course host if you deliver a programme inside it. Named so you can check your own bills: Dubsado, HoneyBook, PandaDoc, HubSpot, Kajabi.
Who needs an AI account?
Nobody has to have one. You decide per person. Your clients never do.
Where does our client data live?
In your own database project, in the region you choose. Nothing is shared between clients, and nothing is shared with us after the handover.
Can a client see anything but their own garden?
No. That is the one wall the whole portal is built around, and it is tested from a client's own login before handover.
Can we deliver a programme inside it?
Yes. A course or programme runs inside the garden, so a client's sessions, materials and progress sit in the same home as everything else.
Who fixes it when something breaks?
Your own people, with the course that comes with the build. Or we hold it for a year, on a schedule, and you can end that at any point.
Half an hour. You tell us where the organisation is, we tell you whether AI helps, and if it does, what we would build first. Nothing is booked on that call.
Or write to maaria@purposedriven.ai
