In short
Source: Sales Surge price list, November 2026As of: 16 November 2026
In this article
- Sales automation that actually feels human
- What to automate vs what to keep manual
- Twelve Pipedrive automations every B2B team needs
- What can you automate in Pipedrive without Make?
- How many automations can Pipedrive run per plan?
- Pipeline automation: stage transitions and deal-rotting alerts
- Activity automation: follow-ups, reminders and sequence triggers
- Lead automation: scoring, routing and enrichment
- How many hours does a rep save?
- Sales automation consultant: when do you bring one in?
- Communication automation: cadences, calling and messaging
- AI sales agents as the next layer
- The Sales Surge sales automation tool stack
- Mistakes that kill response rates the day automation goes live
- Frequently asked questions
Sales automation that actually feels human
Sales automation should take over every task that repeats and adds nothing to the relationship, and leave everything that changes how the buyer sees you with a person. Done well, the buyer does not notice it. The follow-up arrives because the deal moved stage, not because someone remembered. The lead reaches the right rep within minutes of the form.
Sales automation has a bad name because many teams automated the wrong half. They put the first message to a key account in a sequence and kept the data entry manual. We do it the other way round.
What to automate vs what to keep manual
Decide per task whether it belongs to a workflow or to a person before you pick a tool. Is the work repeatable and of no value to the relationship? Automate it. Does it change how the buyer sees you? Keep it with a person.
- Automate the admin. Data entry from forms and email, call and email logging, new deals once a condition is met, lead routing, documents and calendar work.
- Automate the signals. Reminders, alerts on deals that stall, follow-up tasks and the small status changes that should happen when a field changes.
- Keep the judgement with people. The discovery question that decides whether a deal exists, the framing of a proposal, a move in a negotiation, and the choice to let a deal go.
- Let the system draft and a person approve. A first proposal draft, the summary after a call, a win-back message. The rep still presses send.
Twelve Pipedrive automations every B2B team needs
These twelve recipes cover most of what a B2B sales team needs in Pipedrive. Each one has a trigger, a condition and an action. The last column says whether Pipedrive can do it on its own or whether we add Make.com. Native first, because every workflow outside the CRM adds upkeep. Numbers of days are starting values. Set them to the real dwell time of your own stages.
| Recipe | Trigger | Condition | Action | Native or Make |
|---|---|---|---|---|
| 1. Stalled deal alert | Deal has no activity | Longer than the normal dwell time of its stage, for example 10 days | The deal turns red and the owner gets a task to call | Rotting is native, a daily digest per rep via Make |
| 2. Follow-up after a missed call | Call activity marked as done | Outcome is no answer | Create a follow-up call two working days later and send a short email | Native |
| 3. Round-robin assignment | New lead or deal from a web form | No owner yet | Assign the next rep in the rotation and notify them | Native routing on the higher plans, otherwise Make |
| 4. Stage entry tasks | Deal enters the proposal stage | None | Create the tasks for this stage: send proposal, follow up on day 3 and day 7 | Native |
| 5. Required fields per stage | Deal moves to proposal or negotiation | Value or expected close date is empty | Block the move until the fields are filled in | Native, as a pipeline setting |
| 6. Proposal opened | Buyer opens the proposal in PandaDoc | Deal is still open | Task for the rep on the same day, with a link to the proposal | Make |
| 7. Won to onboarding | Deal marked as won | None | Create a deal in the onboarding pipeline, assign customer success and schedule the kick-off | Native, Make for tools outside Pipedrive |
| 8. Lost, but not forever | Deal marked as lost | Lost reason is timing or no budget | Create a check-in activity 90 days later | Native |
| 9. Meeting booked | Prospect books a slot in the planner | Deal exists for this person | Move the deal to the meeting stage and add the meeting as an activity | Native with Pipedrive's scheduler, Make for other planners |
| 10. Inbound lead with enrichment | Form submitted on the website | Business email address | Create the lead, add company size and industry from Apollo, then route it | Make |
| 11. Large deal alert | Deal created or won | Value above your threshold | Post a message in the sales channel in Slack | Native with the Slack integration |
| 12. Duplicate check | New person or organisation created | Email domain or name already exists | Flag the record for review, merge only after a person checks it | Make |
Start with recipes 1, 2, 3 and 4. They touch every deal and need no other tools. The rest follows once those run cleanly for a few weeks. We build these as part of Pipedrive workflow automation.
What can you automate in Pipedrive without Make?
Inside Pipedrive you can automate most things that happen within the CRM: stage changes, activities, field updates, new deals, owner changes, emails from templates and alerts to Slack or by email. You need Make.com as soon as a workflow touches a second system without a native integration, needs branching logic with several paths, or has to wait for something that happens outside Pipedrive.
As a rule of thumb, around two thirds of the recipes above run natively. The rest sits in Make.com, where we can see every run and catch errors. That split keeps the number of moving parts low.
How many automations can Pipedrive run per plan?
According to Pipedrive's help centre at the time of writing, in November 2026, the limit applies per company. Lite has no automations. Growth allows 50 active automations, Premium 150 and Ultimate 250. Deactivated automations do not count. Older plans had other limits, and Pipedrive adjusts these numbers regularly, so check the current overview in your account under Tools and apps, then Automations.
In practice the limit rarely bites when the set-up is tidy. Teams that hit it usually have dozens of near-identical automations per pipeline. Combining those, or moving the complex ones to Make.com, frees up room.
Pipeline automation: stage transitions and deal-rotting alerts
Pipeline automation keeps every deal in the right stage without anyone clicking a dropdown, and flags the deals that sit too long. A proposal goes out and the deal moves to the proposal stage. A contract is signed and the deal moves to won, with onboarding starting. Every stage gets an expected dwell time, and a deal that sits past it shows up in the rep's daily list and the manager's weekly review.
Once stages move on their own, the pipeline review is about decisions instead of working out what is going on. Recipes 1, 4, 5 and 7 above are the core of this layer.
Activity automation: follow-ups, reminders and sequence triggers
Activity automation decides what happens next on every open deal, so it no longer depends on a rep's memory. Four kinds of trigger do most of the work. Stage entry adds the tasks that stage needs. Time-based triggers bring a stalled proposal back after a few days. Behaviour triggers react to the buyer, such as an opened proposal. And hand-over triggers move a deal from SDR to AE with a brief built from the activity history.
The rep's day then starts with a list of what to do, in order, with the context attached.
Lead automation: scoring, routing and enrichment
Lead automation covers everything between a lead entering the system and a rep talking to them. The target is simple: during office hours, an inbound lead hears from you within five minutes. A person cannot keep that pace on every form, so routing has to fire the moment the form lands.
- Routing. Round robin, or assignment by industry, company size or region. Fixed owners for named accounts. It runs within seconds.
- Enrichment. Company size, industry and job titles from Apollo, Lusha or Cognism, added on creation so the rep never opens an empty record.
- Scoring. Fit plus behaviour. Above the agreed threshold the lead becomes a deal. How to build the model is in the marketing automation guide.
- Dedupe. Rules on creation stop one company from appearing as three organisations because three reps used three forms.
How many hours does a rep save?
It depends on how much manual work there is today, so measure it before you build instead of trusting a general number. List the tasks that repeat, count how often each one happens per week and estimate the minutes per time. Ten deal updates a day at three minutes each is two and a half hours a week, for one task and one rep.
At Evans & Watson, a premium tea brand that sells B2B, automated hand-overs and reporting saved more than ten hours a month, with 30% more engagement on leads. That is one case and not a promise. What we see across builds is that the hours come from three places: data entry and stage updates, follow-up tasks nobody has to remember, and reporting nobody has to rebuild on Monday.
What the team does with those hours decides the outcome. Put them into more conversations and the pipeline grows. Skip that step and you mostly get a quieter inbox.
Sales automation consultant: when do you bring one in?
Bring in a sales automation consultant when the automations touch more than one system, when nobody in the team has time to build and maintain them, or when earlier automations broke and nobody knows why. For a handful of native Pipedrive automations in a clean CRM, a capable admin in the team is often enough.
A good consultant starts with the process, not with the tool. Expect questions about stages, hand-overs and lost reasons before anyone opens the automation builder. Expect documentation and an internal owner at the end, so the team can change things after the consultant leaves.
Sales automation
from €2,200
Audit
€2,200
Retainer
Priced in the quote
Prices exclude VAT. More on the sales automation service page.
Communication automation: cadences, calling and messaging
On deals that a rep already owns, communication automation means three things: reply detection that stops a sequence the moment the buyer answers, calls that log against the deal with a recording, and reminders that cut no-shows. Cold outreach to people who did not ask for it is a different job, with its own rules for volume, domains and LinkedIn limits. That lives in the outbound guide.
AI sales agents as the next layer
AI sales agents sit on top of these workflows and take narrow jobs that used to need a person, such as qualifying inbound leads or writing the CRM update after a call. They need the workflows underneath to work first. What they can and cannot do, and what they cost, is in the AI sales agent guide.
The Sales Surge sales automation tool stack
Our default is Pipedrive with its own automations, and Make.com for everything that crosses two systems. Everything else connects to that, and each part has its own guide so this page stays about the pipeline.
| Topic | What it covers |
|---|---|
| Pipedrive | Deals, stages, activities and the native automations |
| Make.com | Workflows between Pipedrive and the other tools, with error handling |
| Outbound tools | Prospecting data, cold email at volume, LinkedIn and deliverability |
| RevOps | Definitions, KPIs and the full stack as one system |
How the whole stack fits together as one system is in the RevOps guide.
Mistakes that kill response rates the day automation goes live
- Automating a broken process. The process hurt by hand, and now the same broken process runs faster. Fix the stages and hand-overs first.
- Sequences without reply detection. The buyer answered message two, and message three still goes out the next morning.
- Tokens that fail in public. If a token can be empty, it will be. Use fallbacks and fewer tokens.
- Routing that takes hours. A manual triage queue between the form and the rep undoes the five minute rule.
- Workflows nobody owns. A field name changes and the workflow breaks quietly. Without a monthly check by an owner, every workflow has a shelf life.
Each of these can be fixed, but it usually costs weeks of pipeline. That is why every build we do has a soft launch with part of the team before everyone goes live.
Frequently asked questions
What is the difference between a CRM and sales automation?
The CRM is where your deals, contacts and activities live. Sales automation is what happens to them without someone clicking: a deal moves stage when the proposal goes out, a task appears after a missed call, a new lead gets an owner within seconds. You can have a CRM without automation, but then every one of those steps depends on someone remembering it.
What can you automate in Pipedrive without Make?
Most things that happen inside Pipedrive itself. Stage changes, new activities, field updates, new deals in another pipeline, owner changes, emails from templates and alerts to Slack all run natively. You need Make.com when a workflow touches a system without a native integration, needs several branches, or has to wait for an event outside Pipedrive, such as a proposal being opened.
How many automations can Pipedrive run per plan?
At the time of writing, in November 2026, Pipedrive's help centre gives a limit per company: no automations on Lite, 50 active automations on Growth, 150 on Premium and 250 on Ultimate. Deactivated automations do not count. Pipedrive adjusts these limits regularly and older plans had other numbers, so check the overview under Tools and apps in your own account.
What does sales automation cost?
At Sales Surge a sales automation project starts from €2,200 and is live in 2 to 3 weeks. It covers routing, follow-up, pipeline priorities and the recipes that fit your process. An audit of an existing set-up costs €2,200, and a retainer for changes afterwards is priced in the quote. Prices exclude VAT. Licences for Pipedrive and Make.com come on top.
Which tools automate the full B2B sales workflow?
No single tool does it all. A common set-up is Pipedrive as the CRM with its own automations, Make.com for workflows between systems, Apollo for prospecting data and enrichment, PandaDoc for proposals and signatures, and CloudTalk for calls that log against the deal. What makes it one workflow is that every tool writes back to the CRM, so the deal always shows the latest state.
Will sales automation replace my sales reps?
No. It replaces the admin around selling, not the selling. Data entry, logging, routing and reminders move to workflows. Discovery, proposals, negotiation and the relationship stay with people. The teams that get the most out of it put the hours they get back into more conversations with buyers, and they agree on that before the first workflow goes live.
What should a sales automation consultant leave behind?
Four things you can check on the last day. A list of every automation with its trigger, condition and action. A named owner in your team who can switch each one off. A test record for each workflow that shows it works. And an error alert that reaches a person, not an inbox nobody reads. If one of these is missing, the team cannot change anything once the consultant has gone.
