sequence-best-practices

Included with Lifetime

$97 forever

Email sequence design and optimization best practices

Design

What this skill does

plugin: instantly
updated: 2026-01-20

# Sequence Best Practices

## Sequence Structure

### Standard 5-Step Sequence

| Step | Day | Purpose | Email Type |
|------|-----|---------|------------|
| 1 | 0 | Initial outreach | Problem + value prop |
| 2 | 3 | Social proof | Case study / results |
| 3 | 7 | Alternative angle | Different value prop |
| 4 | 10 | Soft breakup | "If not a fit..." |
| 5 | 14 | Breakup | Last attempt, value-add |

### Extended 7-Step Sequence

| Step | Day | Purpose | Email Type |
|------|-----|---------|------------|
| 1 | 0 | Initial outreach | Problem + value prop |
| 2 | 2 | Quick follow-up | Bump + new angle |
| 3 | 5 | Social proof | Case study |
| 4 | 8 | Value-add | Free resource |
| 5 | 12 | Alternative angle | Different ICP pain |
| 6 | 16 | Soft breakup | Check-in |
| 7 | 21 | Breakup | Final attempt |

## Timing Guidelines

### Optimal Delays

| Between Emails | Recommended | Reasoning |
|----------------|-------------|-----------|
| Email 1 -> 2 | 2-3 days | Stay top of mind |
| Email 2 -> 3 | 3-4 days | Let social proof sink in |
| Email 3 -> 4 | 3-4 days | Give time to consider |
| Email 4 -> 5 | 4-5 days | Breakup needs space |
| After breakup | 30+ days | Cool-off period |

### Send Time Optimization

```
Best Days: Tuesday, Wednesday, Thursday
Best Times:
  - 8-10am recipient local time (start of day)
  - 2-4pm recipient local time (post-lunch)

Worst Days: Monday morning, Friday afternoon
Worst Times: After 6pm, before 7am
```

## Email Copy Guidelines

### Length Guidelines

| Email Type | Word Count | Lines | Reason |
|------------|------------|-------|--------|
| Cold outreach | 50-100 | 5-8 | Scannable |
| Follow-up | 30-60 | 3-5 | Quick bump |
| Case study | 100-150 | 8-12 | Tell story |
| Breakup | 40-80 | 4-6 | Clear finale |

### Structure Template

```
[Personalized opening - 1 line]

[Problem statement or insight - 2-3 lines]

[Brief value proposition - 1-2 lines]

[CTA - 1 line]

[Signature]
```

### Subject Line Best Practices

| Do | Don't |
|----|-------|
| Keep 3-7 words | Write novel-length subjects |
| Use {{first_name}} or {{company}} | Over-personalize ("Saw you on LinkedIn...") |
| Create curiosity | Mislead with clickbait |
| Be specific when possible | Use generic templates |
| Test lowercase | Use ALL CAPS |

**Examples:**
- Good: "{{first_name}}, quick question"
- Good: "idea for {{company}}'s Q2"
- Bad: "RE: Our meeting" (fake reply)
- Bad: "FREE TRIAL INSIDE!!!" (spam trigger)

### CTA Best Practices

| CTA Type | Example | When to Use |
|----------|---------|-------------|
| Soft | "Thoughts?" | Early in sequence |
| Medium | "Worth a quick chat?" | Middle of sequence |
| Direct | "15 min this week?" | After engagement signals |
| Breakup | "Should I close the loop?" | Final email |

**One CTA Per Email:** Never give multiple options.

## Personalization Strategy

### Personalization Tokens

| Token | Example | Priority |
|-------|---------|----------|
| {{first_name}} | "Hey Sarah," | Required |
| {{company}} | "saw {{company}}'s recent..." | Recommended |
| {{title}} | "As a {{title}}, you..." | If relevant |
| {{industry}} | "In {{industry}}, we see..." | For segmented |

### Custom Personalization

| Level | Effort | Impact |
|-------|--------|--------|
| Basic | Low | {{first_name}}, {{company}} |
| Medium | Medium | + recent company news, role-specific |
| High | High | + mutual connections, specific insight |

**Rule:** Personalize opening line at minimum. Rest can be templated.

## Avoiding Spam Triggers

### Words to Avoid

```
FREE, GUARANTEE, WINNER, CASH, URGENT
Click here, Act now, Limited time, Don't miss
!!!!, ALL CAPS, $$$$
```

### Technical Best Practices

| Practice | Reason |
|----------|--------|
| No images in cold emails | Trigger spam filters |
| Max 1 link per email | Multiple links = spam |
| No HTML formatting | Plain text performs better |
| Short sentences | Looks more personal |
| No attachments | Major spam trigger |

## Sequence Psychology

### Email 1: The Opening

**Goal:** Establish relevance, create curiosity
**Approach:** Problem-focused, not product-focused
**Length:** 50-80 words

### Email 2: The Follow-Up

**Goal:** Add credibility via social proof
**Approach:** "Here's what happened when..."
**Length:** 60-100 words

### Email 3: The Pivot

**Goal:** Try different angle
**Approach:** Different pain point or benefit
**Length:** 50-80 words

### Email 4: The Soft Breakup

**Goal:** Create scarcity without desperation
**Approach:** "If this isn't a priority..."
**Length:** 40-60 words

### Email 5: The Breakup

**Goal:** Last attempt, leave door open
**Approach:** Value-add (resource) + clear close
**Length:** 50-80 words

Files: 1

Size: 4.7 KB

Complexity: 12/100

Category: Design

Source: https://github.com/madappgang/claude-code/tree/main/plugins/instantly/skills/sequence-best-practices

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts