A CRM built by people who set up CRMs

Sales Surge sets up CRMs for B2B companies. Mostly Pipedrive, but also HubSpot and Zoho. Across more than 150 CRM implementations we kept seeing the same pattern. The CRM handles the pipeline well. But next to it sits a tool for support, a tool for email marketing, a form builder, an e-signature service for quotes and a spreadsheet for reporting. Each tool has its own version of the customer, and we built the integrations in between.

Those integrations work, until they do not. An unsubscribe that never reaches the other system. A ticket sales cannot see, while the account manager is sitting with the customer. A quote signed outside the CRM that never makes it back to the deal. A leadership report stitched together from three exports every month. Small things, but they come back at almost every client.

So we decided to do it the other way round. Not another integration, but one database that sales, service and marketing all work on. That is Lumo. Deals, leads, email, quotes with e-signatures, campaigns, forms, tickets, a customer portal, live chat and reports sit on the same people and organizations. You switch on what you use per workspace. See the whole platform.

We built Lumo on what implementations taught us. A Today screen, because reps start their day in the inbox and forget things there. Data quality rules that can actually block a save, because a report is only as good as the fields under it. A duplicates queue with undo, because merging without review goes wrong. And an import wizard for Pipedrive, because that is where most of our clients come from.

We are plain about what it is. Lumo is young. There is no mobile app and no self sign-up, and the connection with Outlook and Microsoft 365 is on the roadmap. What is included is described exactly on this site, and so is what is not. That is the same attitude we bring to implementation work: say what works, what does not and what you can do about it tomorrow.

Most software vendors sell a licence and leave setup to a partner or to you. With Lumo the product and the implementation sit in the same company. That has two consequences.

The first is that the people who set up your CRM also know how it 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. The same people who design your pipeline can tell you what the product does and does not do.

The second is that 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 the product. That is also why Lumo exists.

An implementation runs in the same phases as the rest of our work. We start with an intake: your current situation, your goals, your systems and who struggles with what. Then a blueprint, the design of pipelines, fields, integrations, permissions, dashboards and migration, on a board you can read yourself. Then the build: setup, migration and testing, with a delivery per phase instead of one big one at the end. Then the handover, explained on your own data. And after that aftercare with a fixed point of contact.

If you come from Pipedrive, migration runs through the import wizard. Pipedrive can also stay the source for a while, as your team moves over in stages. Data from other systems we move by hand. Read more about implementation and onboarding or having the migration done for you.