Glossary
What is sales automation?
Sales automation is software handling the repeatable parts of a sales process, so that logging, routing, reminders, follow-up sequences, and record updates happen without anyone doing them by hand.
The three kinds, from most to least useful
Capture automation removes data entry: email and calendar sync that files activity against the right company, a browser extension that creates a contact from a profile, a form that creates a record. This is where nearly all the value is, and it is the kind teams turn on last.
Process automation moves work along: routing a new lead to an owner, creating a task when a stage changes, raising an alert when a deal goes quiet, starting an onboarding checklist when a deal is won. Reliable, low risk, and easy to explain.
Outreach automation sends things: sequences, follow-ups, drip campaigns. This is the kind people mean when they say "sales automation", and it is the one that damages a relationship business fastest when it is set to run unattended.
What not to automate
Anything the recipient would be embarrassed to discover was automated. A referral introduction, a message to a former client, a note after a difficult meeting. In a firm that sells on relationships, one obviously templated message to the wrong person costs more than the whole sequence saved.
Also not: qualification decisions, discount approvals, and anything that closes a record. Automation is very good at doing a thing repeatedly and very bad at noticing that this time it should not.
Automation does not fix a process, it repeats one
A stage that nobody agrees on, automated, produces disagreement faster. The order is always: agree the process, run it manually until it is boring, then automate the boring part.
The other failure mode is silent automation. If a rule fires and nobody can see that it fired, the CRM starts doing things people cannot explain, and trust in the data goes with it.
How sales automation works in a CRM
- Automatic capture first. Email, calendar, and meeting notes landing on the right record without anyone logging them. Everything else depends on this being true.
- Triggers on real events. Stage changed, deal won, no activity for thirty days, form submitted. Not "every Monday", which fires whether or not anything happened.
- A visible audit trail. Every automated change should say what rule made it. Otherwise the record is full of edits nobody made.
- A human gate on anything that sends. Drafted automatically, sent deliberately. That one boundary prevents most of the damage.
How we do it in Lumenbase
Lumo drafts outreach from what is on the record and puts it in a queue. Nothing sends until a person approves it, which is a deliberate limit rather than a missing feature: our users sell to people they will meet again, and a wrong message sent at scale is not recoverable.