Check the next step
Read the agreed contact date and look for an existing open task.
Your CRM knows the stage. Does it know the next step?
The quote is sent. The deal looks tidy. The follow-up is somewhere in a notebook. Put that next action on the deal itself, with an owner and a due date. Then automate the reminder where your CRM supports it. Start with one stage and keep customer messages in human hands while you test.
One promise. One next action.
A suggested workflow for a deal entering “Quote sent”.
Keep one useful task
Include the deal, owner, reason and due date. Agreed timing comes first.
Review, then contact
Open the latest conversation. Act only if the follow-up is still appropriate.
Record what changed
Log the outcome and next date, or close the deal when that is the right result.
A reminder should carry a decision
Start with one rule: when a deal reaches your chosen stage, make sure it has one named next action, one owner and one due date. Use a date agreed with the customer first; use a stage-based default only when there is no agreement.
A stage tells you where a deal stands. A task tells someone what to do. A reminder brings that task back at the right time. You can test this habit manually before paying for automation.
The quote that disappeared into “sent”
Illustrative example, not a client case study: a small commercial cleaning company sends a proposal after a site visit. The office manager moves the deal to “Quote sent” and writes “chase Friday” in a notebook.
The prospect then emails: “Our facilities meeting is next Wednesday. Could you call on Thursday?” The stage still says “Quote sent”. A blanket three-day reminder now has the wrong answer.
The useful task is specific: “Call after the facilities meeting; ask whether the cleaning schedule needs changing.” It belongs on the deal, assigned to the account owner, due on the agreed Thursday. After the call, that owner logs what happened and sets the next step.
This is the test for your setup: would a colleague covering an absence understand the action without finding the notebook?
Map the next action for one stage
Use this fictional service-business map as a starting point. These are suggested operating rules, not product defaults or a proven best follow-up cadence. Choose timings that match your sales cycle and the promises you make.
| Deal stage | Useful next action | Due date or stop rule |
|---|---|---|
| Site visit completed | Prepare the proposal, or request the missing measurements. | Use the promised quote date; name who will supply any missing detail. |
| Quote sent | Review the latest conversation, then call or email with a specific question. | Use the agreed contact date. If none exists, choose a default the owner can change. |
| Decision pending | Check the outcome of the buyer’s decision meeting. | Use the meeting date and agreed follow-up; avoid daily “any news?” tasks. |
| Won or lost | Retire the sales follow-up. Create a separate handover task if needed. | Check outstanding tasks when the deal closes; do not assume they disappear. |
Write the rule before opening the automation builder
For a first pilot, use “Quote sent”. The steps below are the behaviour to design and test; your CRM may need separate conditions or a manual check to achieve all of them.
- Start on a real stage change. Watch the chosen pipeline and entry into “Quote sent”, rather than every edit to the deal.
- Check whether the next action is already covered. If a relevant open task exists, review or update it instead of creating another one.
- Assign a useful task. Include the deal link, the reason for the follow-up, the responsible person and the due date. If the owner is missing, send that exception to a named backup.
- Review before contacting the customer. Open the latest conversation when the task is due. A reply, changed date or closed deal may make the original reminder obsolete.
- Close the loop. After acting, record the outcome and set the next date, change the stage, or close the deal. Completing a task should leave the deal in a state the next person can understand.
Use what HubSpot or Pipedrive already gives you
You do not need a new CRM to try the habit. HubSpot tasks can be linked to deal records and given an assignee, due date, reminder and notes. Pipedrive activities can be linked to deals and contacts to hold the next call, meeting or task.
Automatic creation is a separate capability. HubSpot documents Professional or Enterprise requirements for creating tasks through workflows. Pipedrive documents Automations on Growth and higher plans. Check your actual subscription and permissions before designing around either feature; basic task access is not the same as workflow access.
If your plan does not include the automation you need, run the pilot with manually created tasks. You will learn whether the rule helps before comparing an upgrade with a separate integration.
HubSpot: create tasksPipedrive: activitiesHubSpot: create workflowsPipedrive: automations, first steps
Three settings that can quietly spoil the result
A workflow that creates a task is easy to demonstrate. A workflow that creates the right task, once, deserves a closer look.
- Trigger precision. Pipedrive lets an update trigger watch selected fields and apply conditions such as the target deal stage. Use that precision to avoid a new follow-up whenever someone corrects an unrelated field.
- Stage re-entry. HubSpot workflows enroll a record only once by default; re-enrollment needs configuration. Decide what should happen if a deal leaves your stage and later returns. Re-entry should not silently produce two tasks for the same promise.
- Dates and changes. Pipedrive says an automated activity without a configured date defaults to the day it is created. Set the due date deliberately. Separately test whether an existing task needs manual adjustment when the buyer replies, the owner changes or the deal closes.
Pipedrive: automation triggers based on updatesHubSpot: re-enrollment triggersPipedrive: automations, first steps
Where n8n and AI can earn their place
Consider n8n when the missing step crosses tools: a site-visit record is elsewhere, for example, or the team needs an internal notification outside the CRM. Its Pipedrive node supports reading a deal’s activities and creating or updating activities. Those operations provide building blocks; matching the right task, dates and ownership still needs workflow logic and testing.
A stage change plus a known date does not need AI. AI may help when someone must read a messy conversation and suggest the next action. A useful design would show the proposed action beside the source message, so the owner can correct a misunderstood date or promise.
For that later AI step, n8n supports human approval on selected agent tools. Keep customer-facing messages behind review during the pilot. Ordinary internal task creation can run automatically under the agreed rule; it does not need an approval ceremony every time.
n8n: Pipedrive node and supported operationsn8n: human review for AI toolsChoosing between AI and ordinary automation
Try these cases before using real customer records
Use clearly marked test records with no real recipients. Check the task on the deal and the workflow history, rather than relying on a “run succeeded” indicator. These are acceptance checks for the proposed pilot, not claims that every CRM handles them automatically.
- A deal enters “Quote sent”: exactly one relevant task appears, with the right owner and due date.
- An unrelated field changes: no extra follow-up is created.
- A relevant open task already exists, or the stage is entered twice: the original next action is preserved without a duplicate.
- The buyer has agreed a later date: the task respects it, including your working-day and time-zone rules.
- The buyer replies or the deal closes before the task is due: the owner can see that the old action needs updating or retiring.
- The owner is missing or the automation fails: the named backup sees an actionable exception. Retrying does not create a second task.
Give one stage a week, then decide
Before starting, inspect a small sample of recent deals in the chosen stage. Note which had an owner and a useful dated next action. Keep the comparison in the CRM where possible; the pilot should not require a new permanent tracking spreadsheet.
For the next week, use the same rule on new deals in that stage. At the end, review missing actions, duplicate tasks, overdue follow-ups and reminders that owners had to correct. Ask whether the task gave enough context to act without hunting through messages.
Treat one week as a usability check, not proof of higher sales. If reminders are noisy, revise the trigger or due-date rule. If the team ignores them, fix ownership or workload before adding more stages. Expand only when this small loop is useful.
Keep the Monday check for what slips through
Stage-based reminders handle the next expected action. A weekly CRM review catches the exceptions: a task never created, an owner who left, or a proposal with no agreed next date. They serve different jobs.
If your stages and ownership are unreliable today, start with that cleanup. If they are already usable, choose one stage and give its next action a home.
Sources
Which follow-up keeps slipping?
Tell forvertz which CRM you use, where deals stall and what your team currently does next. We can scope one workflow around your tools, ownership and the exceptions that matter.
Discuss one CRM workflowUpdated