What does Lumo cost? It depends on three things

We get it. You would rather see a table with amounts. Everyone comparing CRMs wants that. But with Lumo, a price per user says little until you know what you switch on and who sets it up.

Lumo has fourteen modules that you switch on or off per workspace. A team of five reps using only deals, leads and Gmail has a different package from a team that also runs the helpdesk, customer portal, live chat and campaigns. Those are different situations, so they get different prices.

Then there is the question of who sets it up. You can configure Lumo yourself. Pipelines, fields, roles and rules are set up without code. Or you can have Sales Surge do it, the agency that built Lumo, is a Pipedrive Platinum Partner and has done more than 150 CRM implementations. That is an implementation with setup, migration, training and guidance, and its size varies a lot between companies.

If you come from another CRM, migration plays a part too. From Pipedrive there is an import wizard you can run yourself, with a dry run first. From HubSpot, Salesforce, Freshsales or spreadsheets we do it by hand, because Lumo has no import from other CRMs or from CSV. Read about our migration service for what that involves.

A price list would be right for almost nobody. So in a demo we look at your team, your process and the modules you will actually use. After that you get a quote in writing, with every part listed separately. You are not committed to anything until you have seen it and signed it.

An implementation with us is not an installation with a manual attached. We work in three phases that Sales Surge also uses in other CRM projects: Align, Automate and Accelerate.

Align. We start with your process, not the screen. What kinds of deals do you have, who does what, when is a lead really qualified, and what information does your team need at each step. From that follow the pipelines, the stages with their win probability and the number of days before a deal starts to rot, the fields and which of them are required.

Automate. Next we set up what takes work off your hands. Automations on triggers such as deal won or lead stale, with a dry run before they go live. Data quality rules with the severity tip, warn or block. Forms that create a person and a lead with the source attached. Where it matters, also the helpdesk with SLA targets per priority, or campaigns with a verified sender domain.

Accelerate. Then the switch and the adoption. We move your data, have every user connect their Gmail and calendar, and train the team on their own deals. After go-live we stay involved: who is really working in it, where does it go wrong, which rule needs adjusting. The adoption score and the list of rule violations help with that.

Not every company needs all three phases. If your process is already clear on paper and you only want help with the migration, the implementation is smaller. If you want to do everything yourself, there is no implementation. All of that is listed separately in the quote, so you see what you pay for.

The quote you get after the demo is built from separate lines. That way you see exactly where each part of the price comes from, and you can drop a line to see what it saves.

• Users. The number of people working in Lumo, and in which role.
• Modules. Which of the fourteen modules are switched on for your workspace.
• Implementation. Per phase, what we do and what you have at the end. Align, Automate and Accelerate are listed separately, so you can cut a phase or do it yourself.
• Migration. Separate, with the source named: Pipedrive through the wizard, or another system by hand.
• Training and guidance. How many sessions, for whom, and how long we stay involved after go-live.

For implementation work Sales Surge invoices per phase, before that phase starts. So you never pay up front for work you are not ready for yet. The term, how users and modules are billed and the conditions are in writing too, so nothing new turns up after you sign.

If you see something in the quote you do not think you need, tell us. Sometimes you are right and we take it out. Sometimes we explain why we put it in, for example a cleanup round for duplicate records before your data moves over. Then you decide.

Imagine a wholesaler with ten account managers, two people in inside sales, a customer service team of four and a sales director who mainly wants to read along. This made up company runs its sales in spreadsheets and its customer questions in a shared inbox.

In the demo four things come up. They want one pipeline for new accounts and one for reorders and expansions. Customer service wants tickets with a target per priority, because a key account should hear back faster. The director is fine with the viewer role and a shared dashboard. And there is no system to import from, so the customer list has to move by hand.

The quote then has these lines. Seventeen users, one of them a viewer. The modules sales, quotes, helpdesk and reports. An implementation with an Align phase for the two pipelines and the ticket priorities, an Automate phase for the helpdesk mailbox, data quality rules and a few automations, and an Accelerate phase with the manual migration, separate training for sales and customer service, and a few weeks of guidance.

If the same company also wanted to send campaigns, a module would be added along with setup for the sender domain and templates. If it wanted no help at all, the implementation would disappear and only users and modules would remain. That is exactly why a single amount on a website would say little here.