Skip to main content
Mako Core

Platform

Isolated tenants. One shared core. Operators in Tower.

Each business is a tenant with its own workspace. Public signals live once. Mako Tower is how our team runs the platform across those tenants — you never have to.

Book a callSee how it is structured
A multi-story building at night, each floor lit separately
One building. Separate floors. That is the tenant model: the platform is shared, the businesses are not.

Tenants

Your business is a tenant, not a folder in someone else's account

A tenant is an isolated company workspace. People, pipeline, drafts, and results stay there. The same platform can run an insurance agency, a home-services company, and Mako itself without mixing their memory.

  • Provisioned on purpose — there is no public signup.
  • Mako Core runs as a normal tenant. We use the same walls customers do.
  • Modules turn on per tenant. You do not inherit another company's setup.

Isolation

The same market looks different in every tenant

A newly registered plumbing company is one public fact. What it means depends on who is looking. That difference is stored as tenant context, not as a hard-coded exception.

Who can see what

Tenant-owned data stays put. Public signals are shared once.

Tenant-owned data stays in the workspace. Public market signals are shared. Tower sees enough to operate, not a copy of your Dashboard.

  • Your people, pipeline, and wins

    This tenant
    full
    Other tenants
    none
    Tower
    limited

  • Your tenant context

    This tenant
    full
    Other tenants
    none
    Tower
    limited

  • Public market signals

    This tenant
    full
    Other tenants
    full
    Tower
    full

Bars show who can use the data, not a volume of records. Tower sees operational health — not a second copy of your workspace.

Context

Agents reason from this tenant, not a generic prompt

Every task walks a stack: global policy, then tenant, then module, then the record in front of you. If context is missing, Mako slows down instead of inventing a preference.

  1. 1

    Global policy

    Safety, privacy, tenant isolation, and approval requirements. These do not change per customer.

  2. 2

    Tenant context

    Who you are, who you serve, what you sell, how you talk, and what counts as a win.

  3. 3

    Module context

    Lead Intelligence, Network, Social, and the rest each know what they are trying to move.

  4. 4

    Task context

    The specific person, company, draft, or recommendation being worked on right now.

Surfaces

Dashboard for the business. Mobile for the moment. Tower for us.

These are different jobs. Mixing them is how products get confusing. Mako keeps them apart on purpose.

A business owner reviewing a single-company dashboard on a laptop

You and your team

Web Dashboard

The command center for one tenant. Pipeline, approvals, analytics, and setup live here.

Someone capturing a note on a phone after a meeting

You, away from the desk

Mako mobile

The action companion. Capture a person, approve a draft, see what needs attention now.

An operations room with multiple screens used to oversee tenant workspaces

Mako operators

Mako Tower

The view across tenants. Used to provision, support, and keep the platform healthy — not a customer screen.

Modules

Capabilities turn on per tenant

The platform has a shared catalog. A workspace only runs what that business needs. This is a model of how that looks — not a promise that every tenant has the same set.

Modules are enabled per tenant. Not every workspace runs the full set.
TenantLead IntelligenceSocialNetworkWebsite
Insurance tenant
Home-services tenant
Mako (internal)

Filled is on. Empty is off. Capabilities turn on for a tenant when they are useful — not because the platform has them.

How work moves

Understood in tenant context. Approved by a person.

The loop is the same for every tenant. The meaning of each step is not.

  1. 1

    Observe

    Signals, relationships, and work already happening.

  2. 2

    Understand

    Interpreted through that tenant's context — not a generic prompt.

  3. 3

    Recommend

    The next useful move, with the reason attached.

  4. 4

    Approve

    A person on that tenant decides before anything goes out.

  5. 5

    Measure

    Results stay on the tenant scoreboard Tower can see in aggregate.

Operators in a control room reviewing multiple tenant screens
Tower is a support and operations surface. It is not where a customer runs their business.

The rules it runs by

Isolation is a product rule, not an admin setting

These are how the platform behaves by default — for every tenant, including ours.

  • Your data stays in your tenant

    People, pipeline, drafts, and wins are not visible to other companies.

  • Public signals are shared once

    Market data is not copied per tenant. Each workspace overlays its own meaning on top.

  • Tower is not your Dashboard

    Operators can support and provision. They do not run your business from Tower.

  • Access is provisioned

    There is no public signup. A workspace is opened for a business on purpose.

30 minutes · a Mako team member joins

We'll look at how your business runs and show you what we'd set up first

No product tour of everything Mako can do. A specific recommendation for your business — and an honest answer if it isn't a fit.

Book a 30-minute callRead the blog