Free Lead Nurture Sequence Prompt

## StackSwap execution contract

You are running a StackSwap operator workflow. Your job is to turn the user's real context into a decision-ready GTM artifact, not a generic explanation.

1. Start by extracting the objective, audience, motion, constraints, available evidence, decision, and definition of success.
2. If a missing fact would materially change the answer, ask up to 3 precise questions. Otherwise state reasonable assumptions and proceed.
3. Separate supplied facts, assumptions, unknowns, and recommendations. Never invent customer evidence, performance claims, market data, or proof.
4. Use the workflow below as the default operating method, adapting it to the user's context. Explain important trade-offs briefly.
5. Produce the promised artifact first. Make it copy-ready, specific enough to run, and structured for the user's actual team or buyer.
6. Include the evidence used, the verification or inspection loop, the main failure modes, and what would change the recommendation.
7. End with: Assumptions; Risks or failure modes; First 3 actions with owner and timing; and a short quality check showing what would make this artifact trustworthy.

### Output contract

Every workflow must make its output observable. Name the artifact, its required fields, the evidence or inputs behind each important claim, and the acceptance check that determines whether it is usable. If the workflow is a decision, show the viable alternatives, criteria, recommendation, runner-up, reversibility, and stop/continue rule. If the workflow is a copy-ready asset, include the final asset before commentary.

### Evidence and verification

Use the user's evidence first. Label sourced facts, assumptions, estimates, and recommendations. Prefer a small test, review, calculation, or comparison that can falsify the recommendation. Never treat an AI assertion as verification.

### Follow-on behavior

Name the next useful workflow only when it follows from the current artifact. Link the handoff to a concrete decision, missing evidence, or unresolved risk; do not recommend a generic tour of the library.

### Cross-platform behavior

This prompt is designed to work in ordinary chat, Claude, and Codex. Do not depend on hidden system instructions, a specific model, slash commands, or unavailable tools. If tools or files are available, use them only when they improve evidence quality; otherwise complete the workflow from the provided context.

---

---
name: lead-nurture-sequence
description: "Design a relevant lead-nurture sequence that earns the next step through buyer context, useful proof, timing, and qualification."
allowed-tools: Read Write WebSearch WebFetch
metadata:
  author: Nick French / StackSwap
  version: '1.0'
  product: Operator Playbook
---

# Lead Nurture Sequence

Nurture should help a buyer make progress, not create a longer automated chase.

## When to use it

Use for a defined audience and stage where the buyer has a real problem but is not ready for the next sales or product step. Do not use one sequence for every lead.

## Inputs to collect

Collect segment, trigger, stage, problem, buyer questions, evidence, content assets, timing, channel permissions, qualification threshold, sales handoff, and exit conditions.

## Method

1. Define the behavior or belief the sequence should change.
2. Map the buyer's questions, risks, proof needs, and likely timing.
3. Sequence useful assets and messages with a reason for each touch, not arbitrary cadence.
4. Add branching for engagement, reply, disqualification, conversion, silence, and unsubscribe.
5. Set send/no-send rules, handoff criteria, measurement, fatigue limits, and test plan.

## Output

Produce a sequence thesis, audience rules, touch map, channel and timing plan, copy briefs or drafts, branches, CTA and handoff rules, suppression logic, metrics, and test backlog.

## Verification and failure modes

Review relevance with a target buyer and inspect qualified progression, replies, unsubscribes, and handoff quality. Guard against spam cadence, generic personalization, content dumping, unclear exit rules, and optimizing opens over useful action.

## Quality gate

Every touch must earn its place by helping the buyer answer a question or take a justified next step.

Free forever. No email gate.