In short
Lumo CRM is different because sales, service and marketing run on one database. A customer exists once, and mail, deals, quotes, tickets and campaigns all hang off that one record. With four separate tools, the same customer lives in four places and six integrations hold them together. Your AI agents work through the API and the MCP server in the same data as your team.
Source: Sales Surge and lumoheaven.com, checked on 16 November 2026As of: 16 November 2026
In this article
- Why does Lumo use one database?
- What does it mean that a customer exists only once in Lumo?
- What does one database save over four separate tools?
- When does one database beat separate tools?
- What is a headless CRM, and what do AI agents do with it?
- Is Lumo GDPR compliant?
- Is it a drawback that Lumo belongs to Sales Surge?
- When should you not switch to Lumo?
- Frequently asked questions
Set up enough CRMs and you see the same pattern. The CRM handles the pipeline well. But next to it sits a tool for support, a tool for newsletters, a form builder, a service to get quotes signed and a spreadsheet for reporting. Every tool keeps its own version of the customer. Across more than 150 CRM implementations, we built the integrations in between. Lumo is the other route: one database instead of another integration. This article is about that choice and the trade-offs behind it. What Lumo does module by module is in what Lumo CRM does.
Why does Lumo use one database?
Lumo uses one database because most CRM problems do not start inside a tool. They start between tools. Each separate tool does its own job fine. It goes wrong at the seams. A customer unsubscribes from the newsletter and still shows as opted in on the CRM. A rep calls about an upsell without knowing two complaints are open. A sales manager asks how many quotes were signed this month, asks three people and gets three numbers.
Integrations close those seams, until someone renames a field. Then something breaks quietly, and you only notice when the customer calls. We see the same thing in CRM implementations that fail: dirty data kills trust, and separate tools make dirty data close to inevitable.
So the question is not which tool is best. The question is where the truth about your customer lives.
What does it mean that a customer exists only once in Lumo?
It means a person, an organization and a deal each have exactly one record in Lumo, and every module works on that record. Attached to them are the mail from Gmail, the activities from the calendar, the lead from the form, the deal with its products, the quote with its signature, the ticket from the portal and the campaign someone received.
That sounds like a detail, but it changes a few things you feel every week. A report counts what is really there, and you click through to the records behind it. An account manager sees the customer's open tickets on the deal.
How the parts connect is shown in the overview of the Lumoverse.
What does one database save over four separate tools?
One database mostly saves integrations, duplicate customers and maintenance hours. The maths is simple. If four tools all need to talk to each other, you need six integrations. With five tools it is ten. Every integration is a place where a renamed field, a permission change or a vendor update can quietly break something.
With four tools, the same customer lives in four places. When they change their email address, that change has to land correctly four times. Miss it once and you have two versions of the same person, and the report counts both.
For cost we count hours, because vendor prices change often. Here is a worked example with one assumption you fill in yourself. Four tools that all talk to each other means six integrations. Say each integration takes two hours of upkeep a month: checking it, fixing a broken field, absorbing a vendor update. That is twelve hours a month, or 144 hours a year. The four licences and the integration platform come on top. With one database those integration hours go away and you pay one licence.
Swap in your own number. If an integration takes you one hour a month, it is 72 hours a year. The gap often sits in those hours more than in the licences, because hours never show up on an invoice.
| Four separate tools | Lumo, one database | |
|---|---|---|
| Integrations if everything talks to everything | Six | None |
| Places where the same customer lives | Four | One |
| An unsubscribe applies to | The tool it came in through | The whole workspace |
| Renaming a field | Can quietly break an integration | Applies everywhere at once |
| Report across sales and service | Export and spreadsheet | One report, click-through |
| Licences and upkeep | Four licences plus integration hours (at two hours per integration a month: 144 hours a year) | One licence, no integration hours |
When does one database beat separate tools?
One database wins as soon as more than one team works with the same customer. Sales, support and marketing on their own tools each see a slice of the customer. More teams means more integrations, and more reports that come back with two numbers.
Three signs you are there. You run four or more tools that share customer data. Someone on your team spends time every week on integrations that misbehave. And a question like 'how many tickets does this customer have open' needs an export. If two of the three sound familiar, it is worth doing the sum.
Separate tools win when one tool does something the rest cannot, and your team mostly lives in that one tool. A support team that relies on a feature-rich helpdesk will not want to trade it for a simpler helpdesk inside a CRM. Connect it, and keep the customer itself in one place. How Lumo blocks dirty fields and duplicate records is covered in what Lumo CRM does. How to get the team working in it is in our piece on CRM adoption.
What is a headless CRM, and what do AI agents do with it?
A headless CRM works without anyone opening the screen: software and AI agents read and write through an API in the same data as your team. In Lumo, your own agents talk to the same people, organizations, deals, leads and activities through the REST API and the MCP server. An agent looks up an account, logs a call and creates a lead. What it does shows up on the customer's record straight away.
Here is what that looks like in practice. Overnight, an agent enriches yesterday's new leads and sets up a call activity for the ones that fit. On Monday morning your rep sees that list on their own deals and can pick up the phone. Nothing needs copying from another system, because the agent never worked in a corner of its own.
That comes with limits. Every agent works with its own API key, with read or write rights and an expiry date, and you revoke it with one click. A key can never do more than the person who created it. Actions that email a customer or delete data need an explicit confirmation. Every write through the API lands in the audit log. And when something new happens, Lumo sends a signed webhook, so an agent does not have to keep asking.
Which tools the MCP server has today is listed on headless CRM and AI agents. Check there before you build anything.
Is Lumo GDPR compliant?
Yes, with two caveats. Data is stored in London, the UK has an adequacy decision from the European Commission, and there is a data processing agreement with a list of sub-processors. Watch out for the AI assistant, and for the lack of ISO or SOC certification. That adequacy decision has applied since June 2021, so under the GDPR the UK counts as a country with adequate protection.
Every table with customer data carries a workspace and row-level security, so workspaces never see each other's data. There are four standard roles plus custom roles, two-factor authentication, an append-only audit log and a daily backup. For data subject requests, an admin exports everything about a person as JSON and CSV, or anonymises or deletes that person. Those requests go into a register that cannot be edited.
Now the two caveats. If you use the AI assistant inside Lumo, your question and the data it looks up go to the AI provider, which is outside the UK and the EU. And Lumo does not claim ISO or SOC certification. If your procurement team requires one, Lumo is not the right choice today. The details are on security and privacy.
Is it a drawback that Lumo belongs to Sales Surge?
It comes with one upside and one risk. Lumo is owned by Sales-Surge B.V., the same company that sets it up, which is not how most software vendors work. They sell a licence and leave setup to a partner or to you.
The upside shows up in two places. The people who design your pipeline also know how the product is built. If you ask whether a report can work a certain way, you do not wait for a support ticket with a vendor in another country. And what we run into at clients comes back into the product. When we see the same manual step at three clients in a row, it becomes a candidate for Lumo.
The risk is that you depend on one party for both product and setup. You can always export your data, see the questions below. How Sales Surge and Lumo relate is explained in why Sales Surge is a Lumo Elite Partner. Coming from Pipedrive? Switching from Pipedrive to Lumo covers what comes along and how long it takes.
When should you not switch to Lumo?
Not when your team only works a pipeline and your integrations hold up. Then switching is often not worth it. A better setup of what you already have helps more, and we say so in the demo. Weighing up platforms? Lumo, Pipedrive or HubSpot helps with that choice.
And a messy process does not tidy itself up in one database. If nobody knows when a lead is really qualified, that confusion will simply live in Lumo instead of in four tools. Start with the process. Our CRM implementation always starts there too.
Finally, Lumo is young. There is no mobile app, no Outlook connection and no SSO. What is and is not in it is listed in what Lumo CRM does.
Frequently asked questions
Can I keep using a tool I already have?
Yes. You connect it to Lumo through the REST API and outgoing webhooks. There is no ready-made Zapier or Make app, so a connection takes some building. If a tool really does something Lumo cannot, keep it. The point is not that everything has to live in Lumo. The point is that the customer exists in one place.
What does headless CRM mean?
That the CRM also works when nobody opens the screen. Software and AI agents read and write through the API and the MCP server in the same data as your team, with their own keys, rights and an expiry date. Actions that email a customer or delete data need an explicit confirmation, and every write through the API lands in the audit log.
How well is the data separated?
Every table with customer data carries a workspace and row-level security, so workspaces never see each other's data. On top of that there are four standard roles plus custom roles, two-factor authentication, an append-only audit log and a daily backup. Data is hosted in London. Inside a workspace, roles apply to the whole workspace, so anyone with access sees all records in it.
Is Lumo GDPR compliant?
Data is stored in London, and the UK has had an adequacy decision from the European Commission since June 2021. There is a data processing agreement, a list of sub-processors and a register for data subject requests. Two caveats: the AI assistant sends your question to a provider outside the UK and the EU, and Lumo does not claim ISO or SOC certification.
Can I export my data if I leave?
Yes. During the contract you export your data with the export functions in Lumo, such as a CSV export of every report and an export of everything about a person as JSON and CSV. Under the data processing agreement, we delete your personal data after the contract ends at your request. So make your export before the agreement ends. Backups rotate out on the database provider's schedule.
What does Lumo cost?
There is no price list. The price depends on the number of users, the modules you switch on and how much of the setup you hand to Sales Surge. After a demo you get a written quote with every part listed separately. Compare that quote with the sum of your current licences, your integration platform and the hours your integrations take today.
