PSI · Week 20 · AI Prompt
Three inputs in — offer name, ICA pain point, urgency mechanism. Out comes a complete 5-email sales sequence using the PASTOR launch countdown: subject lines, hooks, body structure, and CTAs mapped to each stage. Paste straight into Claude.ai.
Every email has a stage-job. Miss a stage and the sequence doesn't reach orbit. The prompt fires every stage in order, with a deliberate handoff between each.
Paste the prompt below into Claude.ai. Replace the three bracketed inputs with your own. Output is a complete labelled sequence, ready to paste into your ESP.
You are an expert email copywriter specialising in sales sequences for coaches, consultants, and service-based business owners. Your job is to write a complete 5-email sales sequence using the PASTOR framework. Here are my three inputs: - OFFER NAME: [paste your offer name here] - ICA PAIN POINT: [one sentence, in your buyer's exact language — what keeps them up at night] - URGENCY MECHANISM: [what makes NOW the right time — a real deadline, a competitive window, an opportunity cost] Write a complete 5-email sequence with the following structure: EMAIL 1 — PROBLEM (P): Subject line: [specific, names the pain] Opening hook: [first 2-3 sentences — must create immediate recognition] Body: Name the problem so precisely they think "that's me." Open a loop. Don't resolve it. CTA: Soft — "tomorrow I'm going to show you what this is actually costing you" EMAIL 2 — AMPLIFY (A): Subject line: [names the cost, not the problem] Opening hook: [picks up where email 1 left off] Body: Show the arithmetic. What does staying in this problem cost them annually? Monthly? Per week? Not exaggerated — real numbers based on industry data or logical inference. Make the consequence of inaction specific and unavoidable. CTA: Soft — "tomorrow I'm going to show you how [NAME] fixed this" EMAIL 3 — STORY/PROOF (S): Subject line: [names the transformation, not the person] Opening hook: [opens with the before state, immediately relatable] Body: One client or example. Before state → the turn → after state. Specific numbers. Named outcomes. The story is a mirror — they should see themselves in the before. CTA: Medium — "tomorrow I'll show you exactly how they did it" EMAIL 4 — TRANSFORMATION (T): Subject line: [paints the after — their specific desired state] Opening hook: [opens in the transformation — they're already there] Body: The after state, described in vivid, specific detail. Calendar. Relationships. Revenue. Time. What stops being a problem. What becomes possible. The offer hasn't been mentioned yet. CTA: Medium — "tomorrow I'm opening the door" EMAIL 5 — OFFER + RESPONSE (O + R): Subject line: [names the offer and the deadline] Opening hook: [direct — you've earned this] Body: Make the offer once, directly. What they get. What it costs. What makes this the right time (use the urgency mechanism I gave you — keep it real, not manufactured). One CTA. One link. One instruction. CTA: Direct — one link, one action Format each email clearly labelled. Keep each email under 300 words. Write in a direct, warm, non-corporate voice. No jargon. No passive voice. Every sentence earns the next.
Thin inputs = bland output. The sequence is only as sharp as the three lines you give it. Tighten each one before you paste.
Run the list before you schedule. If something doesn't tick, send the prompt back with a sharper input.
The sequence isn't the end product. The repeatable prompt that builds the sequence is the end product. What you paste into Claude today is the same architecture that runs as an autonomous agent in six weeks. April 8 launch. April 23 memory. End of May orchestration. The operators who build the blueprint in April run the agent in June.