Start with the sale cycle, not the tool
Every automation project we inherit starts the same way: a platform was bought, a welcome sequence was built, and six months later the open rate has halved. The tool is rarely the problem. The sequence was designed around what the software could do rather than around how the customer actually decides.
Before a single workflow is drawn, map the sale cycle. Where does a prospect first hear about you? What do they need to believe before they book a call? What objections appear right before a deal stalls? Each answer becomes a stage, and each stage gets a job: educate, reassure, or prompt.
A nurturing sequence is a conversation you have planned in advance. Plan the conversation first; the software is just the mouth.
Segment by intent, not by form field
Job title and company size are easy to capture and weak at predicting behaviour. Intent signals are harder to capture and much more useful. Someone who read your pricing page twice and opened a case study is in a different place from someone who downloaded a checklist and disappeared.
We score three families of signals:
- Engagement depth — pages viewed, time on product pages, repeat visits within seven days.
- Content type — awareness content (guides, articles) versus evaluation content (pricing, comparisons, case studies).
- Explicit asks — demo requests, replies to email, contact form submissions.
Scores decay. A visit that happened three months ago should carry a fraction of the weight of one that happened yesterday. Without decay, your "hot" list fills with people who have long since bought elsewhere.
Design the touches around a single next step
Each message in a nurture flow should have exactly one job and one measurable action. A newsletter that links to nine things is not nurturing; it is noise with a logo.
| Stage | Goal of the touch | What we measure |
|---|---|---|
| New lead | Confirm relevance, set expectations | Reply or click on the one link |
| Educated | Reframe the problem using your point of view | Return visit to a product page |
| Evaluating | Reduce risk: proof, process, pricing clarity | Demo or call booked |
| Stalled | Diagnose the blocker, offer a smaller step | Any engagement within 14 days |
Notice that the last stage exists at all. Most stacks have no plan for deals that stop responding, and that silence is where the pipeline leaks.
Close the loop with sales and with data
Automation without a feedback loop from sales produces beautifully formatted guesses. Build two loops: a weekly review of which leads were handed over and what happened, and an automatic write-back from the CRM so the system learns which signals preceded closed deals.
If sales cannot describe, in one sentence, what the marketing system has told them about a lead, the hand-off is broken. Fix the hand-off before you add another sequence.
Finally, budget for maintenance. Sequences age: offers change, products are renamed, and the links in step four of a flow built in 2024 quietly start pointing at a 404. A monthly audit of every active workflow costs an afternoon and saves far more than that in wasted sends.