Leave with a three-message outline with a purpose and stopping rules.
Start with a real buying situation
For the worked example, the audience is an operations lead at a professional-services firm. Their problem is that client deadlines live in different spreadsheets and dependency changes arrive late. The desired practical outcome is a single view of owners, dependencies and delivery dates.
The example is deliberately bounded: client teams must retain access to an export of their work. That condition should influence the promise, scope and next step rather than disappear from the marketing copy.
| Illustrative offer | a shared project planning workspace |
|---|---|
| Buyer question | Which handover creates the most rework when a delivery date changes? |
| Possible evidence | a sample project with one late dependency and the resulting schedule change |
| Useful asset | a project dependency mapping worksheet |
How to complete your lead nurture sequence
- Define why the person asked to hear from you.
- Identify the next decision or uncertainty.
- Choose useful evidence for each message.
- Use a clear, proportionate next action.
- Stop or change the sequence when the person responds, declines or asks to unsubscribe.
Worked example
These entries are illustrative planning material, not research findings or customer results. Keep the structure and replace the content with verified details.
| Reason for the relationship | The person requested information about a shared project planning workspace. Record the actual source and their communication preferences. |
|---|---|
| First unresolved question | Message 1: clarify their question. “Which handover creates the most rework when a delivery date changes?” Include a project dependency mapping worksheet if it helps. |
| Evidence to share next | Message 2: explain a sample project with one late dependency and the resulting schedule change. Connect it to a single view of owners, dependencies and delivery dates, with limitations. |
| Decision invitation | Message 3: ask whether it would be useful to run one internal project for two weekly planning cycles. Offer a clear way to pause or decline. |
| Stop and handover rules | Stop automated follow-up when the recipient responds, declines or opts out. Route substantive replies to a named owner. |
Review before using it
A useful operational measure in this example is time spent preparing the weekly delivery update. That does not automatically make it a marketing attribution metric. Define the source, period and owner before drawing conclusions.
- Would each message still be useful if the recipient did not buy immediately?
- Check the delivery assumptions: Agree who imports data, maintains the plan and owns exit exports.
- Use evidence rather than promises. Do not present feature count as proof of adoption.
- Discuss the draft with someone who understands the buying situation. Start with: “Which handover creates the most rework when a delivery date changes?”
- If the next step is a trial, define its purpose. One possible starting point is to run one internal project for two weekly planning cycles.
Common mistakes and a better review
Do not fill a missing fact with an impressive-sounding number. Mark it as an assumption, explain how you will check it and give that check an owner. A short, honest document is easier to use than an elaborate plan built on unknowns.
| Watch for | A sequence that ignores replies behaves like a broadcast rather than a conversation. |
|---|---|
| A real buyer concern | Another tool will just add more administration. |
| Useful response direction | Let us time the current weekly update and compare the same update on one sample project before asking everyone to move. |
| Evidence to collect | The buyer’s own account, a sample project with one late dependency and the resulting schedule change, and records relevant to time spent preparing the weekly delivery update. |
Your working sheet
Write your own version below. Notes are saved on this browser when local storage is available. Use Download to keep a separate copy; avoid adding confidential information on a shared device.
Example: The person requested information about a shared project planning workspace. Record the actual source and their communication preferences.
Example: Message 1: clarify their question. “Which handover creates the most rework when a delivery date changes?” Include a project dependency mapping worksheet if it helps.
Example: Message 2: explain a sample project with one late dependency and the resulting schedule change. Connect it to a single view of owners, dependencies and delivery dates, with limitations.
Example: Message 3: ask whether it would be useful to run one internal project for two weekly planning cycles. Offer a clear way to pause or decline.
Example: Stop automated follow-up when the recipient responds, declines or opts out. Route substantive replies to a named owner.
Review your work
Tick only what you can support with your answer or practice. This is a reflection checklist, not an automated assessment.
Questions about this resource
How do I adapt this for my project management software business?
Replace the audience, offer and evidence with your actual information. Begin with a recent buyer conversation about why client deadlines live in different spreadsheets and dependency changes arrive late, then check which assumptions match your business.
Is the filled example ready to publish?
No. It is a working example. Verify claims, permissions, prices, current capabilities and any customer information before using it externally. Do not present feature count as proof of adoption.
What should I do after completing the worksheet?
Use it to make one decision or have one focused conversation. The intended output is a three-message outline with a purpose and stopping rules. Set a review date and update it when the evidence changes.
Illustrative business worksheet. No customer results, market rates, traffic volumes or performance benchmarks are implied. About these resources.