Permission-based cold opener that lowers resistance
Use to start cold outreach with an honest, disarming opener that asks for permission instead of pitching.
Write a cold {{channel}} opener using a permission-based approach.
Context:
- I sell: {{offer}}
- Target: {{target_persona}}
- The reason I am reaching out specifically to them: {{relevance_reason}}
The opener must:
- Acknowledge it is a cold message honestly in one line.
- Ask permission to share why I reached out (e.g. "mind if I tell you why you?").
- NOT pitch, NOT book a meeting yet, NOT use fake familiarity.
- Sound like one human texting another.
Output 3 variations with slightly different tones: direct, warm, and curious. Keep each under 50 words.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{channel}}
- {{offer}}
- {{target_persona}}
- {{relevance_reason}}
Related prompts
You are an experienced B2B sales rep who writes short, human cold emails that get replies. Write a first-touch cold email to {{prospect_name}}, who is {{prospect_role}} at {{prospe...
You are a sales copywriter. Create three distinct cold email variations for the same prospect so I can A/B test them. Prospect: {{prospect_role}} at {{prospect_company}} What I sel...
You write natural LinkedIn connection notes that do not feel like a pitch. Write a connection request note to {{prospect_name}}, {{prospect_role}} at {{prospect_company}}. Reason f...
You are a social-selling expert. Build a 4-message LinkedIn DM sequence for a prospect who just accepted my connection request. Prospect: {{prospect_role}} at {{prospect_company}}...
You write follow-up emails that add value rather than nag. Write a follow-up to {{prospect_name}} who did not reply to my first email. Original email was about: {{original_topic}}...
You are a sales cadence specialist. Design a 5-email follow-up sequence for a cold prospect. Prospect type: {{prospect_role}} at companies like {{target_company_profile}} What I se...
0 Comments
Loading discussion...