Cold email sequence prompt

When to use it

Use this when you need a cold email sequence and want a concrete starting point rather than generic advice. Replace the fictional details with your own confirmed facts before using the result in a real setting.

The prompt

## Role
Act as a B2B outbound copywriter. Apply professional judgment while keeping your reasoning understandable to someone who is not a specialist.

## Context
Dockline sells appointment scheduling software to independent freight warehouses. Dispatch managers often coordinate arrival slots by telephone. The product offers a shared booking page and configurable slot limits. No quantified case study exists. The proposed next step is a 15-minute workflow discussion, not a demo disguised as research.

## Objective
Write four concise emails for a credible, low-pressure first contact with an operations manager.

## Audience
The primary users are founder-led sales teams. Make the deliverable usable in their day-to-day work, with enough explanation to support decisions but no unnecessary background lecture.

## Requirements
Use days 1, 4, 9, and 15. Supply a subject line and body under 100 words for each. Give each follow-up a different operational angle. Include a simple opt-out sentence and explain which prospect facts a seller must verify before personalizing. Add a short personalization checklist and a stop rule for replies, opt-outs, or evidence of poor fit.

## Constraints
Do not fabricate familiarity, claim to have inspected private operations, use fake reply threads, or promise reduced costs. Do not present the sequence as legal compliance advice. Work only with the scenario and any material explicitly supplied. Label assumptions and distinguish proposed actions from confirmed facts.

## Tone & style
Be direct, thoughtful, and specific. Prefer plain English, concrete examples, and short paragraphs. Match the language to the intended reader rather than relying on jargon or generic motivational phrasing.

## Output format
Present the requested deliverable first, using descriptive headings and tables only where they improve usability. Keep supporting notes separate from copy intended for publication or direct use. Finish with a short checklist of outstanding decisions or verification steps.

## What to avoid
Avoid filler, unsupported certainty, and details invented to make the result seem more complete. Do not let a polished presentation conceal missing information or conflicting requirements.

## Success criteria
Every email has one answerable question, a plausible reason for contacting this role, and no invented proof. Check the result against the stated constraints before presenting it and correct any inconsistencies you find.

## Clarifying questions
Ask up to three focused questions only if missing information would materially change the result. Otherwise proceed with the fictional scenario, state any necessary assumptions briefly, and identify what a real user should confirm before relying on the output.

Why it works

• The scenario gives the model concrete facts and boundaries instead of asking it to invent a brief.
• The requirements specify the actual deliverables and the important edge cases for this task.
• The constraints make unsupported claims and unapproved commitments harder to slip into the result.
• The success criteria turn review into a practical check: every email has one answerable question, a plausible reason for contacting this role, and no invented proof.

Make it yours

Build a tailored version with PromptDeck by replacing the fictional scenario with your own context, audience, and constraints. Keep the verification steps so the final result reflects what you actually know.