Scope & disclosure
This is a planning worksheet, not a tested review. The example is hypothetical: a creator sells a freelance proposal template pack and offers a free proposal checklist. There are no affiliate links or paid placements in this article.
Use this worksheet before opening a pricing page.
1. What job should this workflow do?
Choose one outcome you can observe. "Improve email marketing" is too broad. "Help new buyers find the templates and complete their first proposal" gives you a workable scope.
Separate delivery from promotion. A receipt, product-access instructions, onboarding help, and an offer for another product serve different purposes. Decide which belong in this first workflow rather than bundling everything together.
Fill in
For people who ___, this workflow should help them ___, beginning when ___ and ending when ___.
For our hypothetical creator: help template-pack buyers start one proposal, beginning after a confirmed purchase and ending after the onboarding sequence or an earlier exit.
2. What purchase signal can you trust?
"Connects to my checkout" is a starting point, not an acceptance test. Before choosing a tool, verify the specific connection in the checkout and email platform's current documentation.
Check:
- Does it pass the purchased product or variant, not merely "customer"?
- What counts as a completed purchase rather than a pending or failed payment?
- Can repeat purchases or duplicate events trigger the sequence twice?
- What happens if checkout uses a different email address from the original signup?
- Are refunds and cancellations passed through, and what should they change?
- What happens to missed events, and can you reconcile orders with subscriber records?
Use a supported test mode where available. Otherwise, plan an authorized test purchase and inspect the resulting records. Do not assume a connection works because its setup screen says "connected".
Fill in
My trusted event is ___. I will check it by ___. If it fails, I will ___.
3. How should buyer and nonbuyer paths differ?
Draw the branches before writing ten emails.
Hypothetical nonbuyer: Someone requests the free checklist and separately opts into the relevant marketing emails. They receive the checklist and a short educational series that includes an offer for the template pack.
Hypothetical buyer: A confirmed template-pack purchase removes them from that product's sales sequence. They receive access instructions, followed by help choosing a template and adapting it to a project. An existing buyer requesting the free checklist should not be treated as a new prospect for the product they already own.
A purchase near a scheduled send can create a timing problem. Verify when the workflow checks purchase status and whether messages already queued can be stopped.
Fill in
Buyers receive ___. Eligible nonbuyers receive ___. A purchase changes ___.
4. What can stay manual for now?
You can draft onboarding messages, review orders, reconcile missing purchase records, and send appropriate individual support replies without building a complex automation. A simple internal checklist may be enough while order volume is manageable.
Manual work still needs boundaries. Respect unsubscribe status, avoid uploading everyone into a marketing sequence, and keep product-access support distinct from promotional outreach.
Record how often the task happens, the time it takes, and the consequences of a miss. Do not invent a universal subscriber threshold for upgrading. Frequent delays or inconsistent handling are more useful signals than list size alone.
Fill in
For now, I will handle ___ manually. I will reconsider when ___ becomes a recurring problem.
5. When must messages stop, pause, or change?
Write exits for purchases, unsubscribes, refunds, duplicate entry, and completed onboarding. Treat a tag as a label, not proof of permission: "buyer" and "eligible for this marketing sequence" answer different questions.
Check which events update tags, which workflows honor unsubscribe status, and how consent records are preserved across connected systems. These are practical workflow checks, not legal advice; confirm the requirements that apply to your business.
Fill in
Stop when ___. Pause for review when ___. If records disagree, ___ will check ___ before more messages go out.
Ready to compare software?
Take your completed map to our research-based Kit buy-or-not guide, and apply the same questions to any other tool on your shortlist.