← All skills
  • Sales
  • v1.0.0
  • outreach

Email 1 variations

Use this skill when crafting the first email in a sequence, testing different opening structures, or building complete email cadences. Seven Email 1 variations from the Frontal core framework — observation, question, poke-the-bear, trigger, stat, and role-pain openers — plus Email 2 and Email 3 templates.

SKILL.md

7 Email 1 Variations (Frontal Core Framework)

Variation 1: Observation → Solution → Proof → CTA

[Observation question about their situation?]

[Solution statement.] [Social proof with specific number.]

[Soft CTA question?]

Variation 2: Question → Problem → Solution + Proof → CTA + PS

[Observation question?]

[Problem statement they likely face.]

[Solution + social proof combined.]

[CTA]

PS - [Additional social proof]

Variation 3: First Line → Poke Bear → Value Prop → CTA

[Relevant personalized first line]

[Poke the bear question about their pain?]

We help companies like {{similar_company}} achieve {{result}} without {{obstacle}}.

[CTA]

Variation 4: Trigger → Problem → Solution → Calculation → CTA

[Personalized trigger reference]

[Problem statement]

[Solution]

[Specific calculation showing impact]

[CTA]

Variation 5: Stat → Question → Value CTA

[Industry statistic]

[Question linking stat to their specific problem?]

[Value-based CTA offering resource/insight]

Variation 6: Trigger → Achievement → CTA

[Relevant trigger observation]

[Social proof achievement we delivered for similar company]

[Direct CTA]

Variation 7: Role Pain → Solution → Answer Objection → Soft CTA

What {{title}}s hate about their job: [common pain]

[How we solve it]

[Pre-answer their likely question]

[Very soft CTA]

Email 2 Template (Send 3 Days Later)

Subject: RE: (same thread)

[Lead magnet offer]

[Social proof]

[Value prop restated differently]

[CTA]

Email 3 Template (Send 14 Days Later - New Subject)

Subject: [New subject line]

[New Email 1 variation - different angle]

[Very soft CTA asking for right person]
"If this isn't you, who should I be talking to about {{topic}}?"

Combines with

Skill Why
cold-email-4-sequence Slot variations into Email 1 position
email-writing-frameworks Each variation uses different framework
personalization-hooks Add hooks to first line of each variation
atl-btl-messaging Adjust variation for seniority

Example prompts

Write Email 1 using Variation 4 (Trigger → Problem → Solution → Calculation) for a hiring signal.
Give me 3 variations of Email 1 for targeting CFOs at mid-market companies.
Which variation should I use when I have strong social proof numbers?

Part of Frontal — free, open GTM skills for your AI agent. Browse the library →

Files

1 file ship with this skill. They are installed beside the SKILL.md.

NOTICE1.4 KB
Email 1 variations
Imported from the GTM Skills library by Swan (https://www.gtmskills.com), skills/alex-vacca/email-1-variations-7
at https://github.com/swan-gtm/gtm-skills/commit/5d786aad0c7b2ca59b1abf1f601f9407ca261996. Written by Alex Vacca (https://linkedin.com/in/alex-vacca).
The skill is shared under the MIT License below; this notice must stay with any copy.

MIT License

Copyright (c) 2026 Swan

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.