Lumo CRM8 minNovember 2026

    What Lumo CRM does, module by module

    A walk through Lumo the way a rep, a support agent and a marketer use it. For every part, what is in it today and what is not.

    Lumo is a CRM for B2B teams where sales, service and marketing work on the same customer. It is made by Sales-Surge B.V., the company behind this site, and it used to be called Surge CRM. This piece goes through the parts in the order you meet them on a working day. No promises about what you will achieve with it, just what it does. If you want the whole picture first, go to lumoheaven.com.

    01

    Your day starts on the Today screen

    You open Lumo and see one screen with what needs you today. Your tasks and meetings, the leads waiting for follow-up, the deals that have sat in a stage too long, the tickets whose response time is nearly up and the campaigns going out today.

    That screen makes nothing up. A deal shows up because it has been in its stage longer than you set for that stage. A ticket shows up because 75 percent of its response target is used. Switch a module off and it disappears from this screen too.

    So you do not walk through five lists in the morning. You start at the top.

    02

    Pipeline, leads and a deal that does its own maths

    You can run several pipelines. Every stage has its own win probability and its own number of days after which a deal starts to rot. The board shows count, value and weighted value per stage. Every stage change is stored with the time the deal spent in the previous stage.

    Products on a deal set the deal value. Each line has a quantity, a price, a discount and a billing frequency, from one-time to annual. A lost deal asks for a reason, so later you see why you lose and not only how often.

    Leads live in their own inbox, with statuses from New to Qualified. A lead converts to a deal exactly once. More on pipeline management in Lumo.

    • Several pipelines with their own stages, win probability and rotting days
    • Totals per stage and a full stage history per deal
    • Product lines with discounts and recurring billing
    • Lost reasons you manage yourself
    03

    Mail and calendar from Gmail

    Connect Gmail and mail with known contacts lands on the person, the organization and the deal by itself. Mail with people who are not in the CRM is never stored, and its body is never even fetched. Per connection you choose whether only you see the mail or your whole team.

    You send from the deal out of your own mailbox, up to 200 mails per user per day. Google Calendar syncs both ways.

    The one catch: if you work in Outlook or Microsoft 365, that connection is not there yet. It is on the roadmap. Until then you use a personal BCC address that works with any mail client.

    04

    From product lines to a signed quote

    You create a quote on the deal. Its lines are a copy of the deal products, so what you discussed is already in it. Lumo numbers quotes per workspace and per year, adds VAT, terms and a valid-until date, and the PDF carries your logo and the customer's.

    The quote leaves through your own Gmail with a link to sign. The recipient gets a six-digit code by email, types their name and ticks agree. After signing, the PDF gets an evidence page and a note lands on the deal.

    What you should know: the quote and the signing page are in Dutch, even when you use Lumo in English. And it is a typed name plus an email code, not a qualified electronic signature. All the details are on quotes and e-signatures.

    05

    After the sale: helpdesk, portal and customer health

    Tickets, the customer portal, the knowledge base and live chat sit in the same system as your deals. Tickets come in from a mailbox, the portal or a chat. Per priority you set a first-response and a resolution target, with business hours and holidays.

    Because it is one database, an account manager sees on the organization how the customer is doing. There is a customer health score from 0 to 100 per organization, based on the tickets of the last 90 days. On a deal you see that customer's open tickets. So nobody calls about an upsell while a complaint is still open.

    How tickets move is described on helpdesk and ticketing.

    06

    Campaigns, forms and calling in a cadence

    You build an email campaign in four steps, to a segment of your own contacts. Consent sits on the person and is checked again at the moment of sending. An unsubscribe applies to the whole workspace. A web form finds or creates a person by email address and creates a lead, with source and consent.

    For calling there is a call mode. You work through a list with the prospect next to you: website, LinkedIn, last contact and an open lead or deal. You pick an outcome and the cadence sets up the next step. An email after the call, a LinkedIn step from your team's own account, a message or a task. Read on at calling campaigns and cadences.

    To be fair: templates are HTML and there is no drag-and-drop editor. If your growth runs on landing pages and content, a marketing platform will serve you better.

    07

    Reports, automations and an AI assistant that asks first

    You build a report in three choices: the source, the measure and the breakdown. There are nine chart types, from a KPI tile to a funnel. Click a bar and you see the deals behind it. There is no separate forecast screen. You build a weighted forecast as a report, using the win probability per stage.

    Automations take the repeat work. A deal changes stage, so you create an activity, set a field or assign an owner. Every rule runs as a dry run first. The AI assistant can search, update records and build an automation or a report for you. It is off per workspace until an admin switches it on, it works with your role and permissions, and anything outward-facing waits for your approval.

    08

    What is not in it today

    Lumo is young, and you see that in a few places. We would rather name them ourselves than have you find out three weeks in.

    If one of these is a hard requirement for you, Lumo is not your CRM right now. A well set up Pipedrive implementation will probably help you more.

    • No iOS or Android app. Lumo is a web app, which you also use in the browser on your phone.
    • No Outlook or Microsoft 365 sync, only the BCC address.
    • No SSO. You sign in with email, password and two-factor authentication.
    • No import from CSV or from CRMs other than Pipedrive. We move that data by hand.
    • No ready-made Zapier or Make app. You connect through the API and webhooks.

    Frequently asked questions