Pricing

Built around your systems.

We do not publish a number, because the honest one depends on things we have not asked you about yet.

Mako is not a seat licence and it is not a per-message meter you have to reverse-engineer. What a deployment costs follows what it actually does for you.

What shapes a deployment

The things we need to know before a number means anything.

These are the real variables. A published price would have to assume all of them.

The systems you connect

Which CRM holds your record, and whether an adapter for it already exists or needs building.

The channels you run

Text, web chat, a public marketplace listing. Each carries its own rules about what may be said.

How much you want it to do

Draft-only, where your team sends everything, is a different operation than fully handled replies.

Conversation volume

What actually flows through it in a month, not the size of your database.

Workflow complexity

One job answered well, or several jobs running against the same business identity.

Your requirements

Compliance posture, escalation rules, data handling, and whatever your industry demands.

How we work

What you can expect from the conversation.

We will tell you if it does not fit

Mako suits businesses losing real money to slow, inconsistent or unstaffed follow-up. If that is not your problem, a pilot wastes your quarter and our reputation.

You start in draft mode

The intended path is that Mako writes and your team sends, until the drafts stop needing edits. You judge it on its own output before it is allowed to act on its own.

Your CRM stays your CRM

There is no migration and no replatforming. If you later stop using Mako, your system of record is exactly where it always was.

No self-serve checkout

There is no signup button on this site because connecting an intelligence layer to a live customer database is not a thing anyone should do unsupervised.

Tell us what you want handled.

We will scope it honestly, including whether it is worth doing at all.