When people hear “platform,” they often picture one big account with folders for each company. That model leaks. The same plumbing company in the public record can be an insurance opportunity for one business and an operations prospect for another. Mixing those meanings is how software gets generic — or worse, unsafe.
On Mako, each company is a tenant. A tenant is an isolated workspace: people, pipeline, drafts, approvals, and results stay there. The platform is shared. The memory is not.
Public signals once. Meaning per tenant.
Market data — a new registration, a renewal window, a license — should not be copied into every workspace. It lives once. Each tenant overlays its own context: who they serve, what counts as a fit, what they are allowed to say.
That is why two tenants can look at the same company and come to different next steps without ever seeing each other’s notes.
Dashboard, mobile, and Tower are different jobs
- The web Dashboard is the command center for one tenant.
- Mako mobile is the action companion: capture, approve, see what needs attention now.
- Mako Tower is the operator view across tenants. Customers do not log in there.
Mako Core runs as a normal tenant on the same walls. We do not give ourselves a special path. If isolation is a product rule, it has to hold for us too.
Access is provisioned on purpose
There is no public signup. A workspace is opened for a business because we are going to set it up around how that business runs. That is slower than a self-serve funnel. It is also how you keep someone else’s context out of yours.