One mandate per client
Its own brief, population, exclusions and notebook. Nothing shared by default.
For firms
Sell the outcome.Not the seat.
Agencies and resellers are not buying a tool their clients could licence directly. They are buying judgement they can sell.
What you are running
Run it behind an offer of your own.
The difference between software you resell and judgement you own is whether the platform enforces the things you promised your clients — or whether your team has to remember to.
Isolation at the database
The tenant travels inside the foreign keys, not in code that has to remember.
A view above the work
Every mandate read at once, rather than opened one by one to find out.
Reporting you do not rewrite
Who was approached, why they qualified, and who was set aside.
A retainer that stops being hours
The hundredth mandate does not cost what the first one did.
Access granted by role
Five roles and a permission grid your firm overrides line by line.
The arithmetic
What scales, and what never did.
A service business is undone by the parts that need one more person per client. There are three numbers that decide whether a retainer survives its own growth.
The research hour
The stage that consumes a retainer is reading each person well enough to say something true. It is the one that does not get cheaper by hiring more juniors, because the quality is the point of it.
The second client
A new mandate is a definition and a connected account, not a deployment, a template library or a person. What the first client taught the system about running a mandate, the second one inherits.
The thing you sell
Meetings, with the reasoning attached — not seats, not a message count, and not a dashboard the client could have licensed themselves for less than you charge.
Run it for your clients.Under your own name.
Isolated mandates, a portfolio above them, and access granted per person — part of the platform rather than a professional-services engagement.