HubSpot Sequences Designer
Hubspot sequences

Designs and optimizes HubSpot sequences: enrollment triggers, multi-channel steps, task creation, analytics, and A/B tests. Use when the user is building or fixing sequences in HubSpot Sales Hub.
---
name: hubspot-sequences
description: >-
Designs and optimizes HubSpot sequences: enrollment triggers, multi-channel
steps, task creation, analytics, and A/B tests. Use when the user is building
or fixing sequences in HubSpot Sales Hub. Triggers on: "HubSpot sequences",
"HubSpot automation", "HubSpot cadence", "sales hub sequences".
license: MIT
compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
metadata:
version: "1.0.0"
author: LeadMagic
category: tools
tags: [hubspot, sequences, sales-hub, crm, cadence]
frameworks:
- "HubSpot Knowledge Base — Sequences"
- "Google and Yahoo — Bulk sender requirements (2024)"
- "Outreach — Sales Engagement Cadence Design"Overview
Before delivering, verify: - [ ] All required sections are complete - [ ] Output matches the user's stated need - [ ] Named frameworks are cited for key recommendations - [ ] No vague claims — every recommendation has a specific action - [ ] Deliverable is ready for operational use, not just conceptual
Manual install (npx, ZIP)
npx skills add LeadMagic/gtm-skills --skill hubspot-sequences -g -a claude-codenpx degit LeadMagic/gtm-skills/skills/tools/hubspot-sequences#main ~/.claude/skills/hubspot-sequencesConnects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md6.6 KB
Read SKILL.md here
Show the full text145 lines
HubSpot Sequences
Overview
HubSpot Sequences power the SDR and AE outbound motion inside Sales Hub. Done right, they automate touches while maintaining personalization. Done wrong, they're spam cannons that burn your domain reputation.
Authoritative Foundations
- HubSpot Knowledge Base — Sequences — Configure enrollment, task steps, and automatic unenrollment on reply or meeting booked; sequences send from each rep's connected inbox.
- Google and Yahoo — Bulk sender requirements (2024) — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and respect per-inbox daily volume.
- Outreach — Sales Engagement Cadence Design — Sequence governance, task-based selling, and CRM-locked cadences.
When to Use
- "Set up HubSpot sequences"
- "Build HubSpot cadences"
- "Optimize HubSpot sequence performance"
- "HubSpot sequence A/B test"
Step-by-Step Process
Phase 1: Sequence Architecture
Design sequences by persona and trigger:
- Inbound follow-up: Auto-enroll on form fill, 3-touch, 7-day window
- Outbound cold: Manual enroll after list build, 6-touch, 21-day window
- Re-engagement: Enroll on CRM status change, 3-touch, 14-day window
- Event follow-up: Enroll on event attendance, 2-touch, 5-day window
Phase 2: Step Configuration
Per step: channel, timing, template, task creation rules.
- Email steps: plain text, from first name, no tracking pixel if cold
- Call steps: auto-create task with call notes template
- LinkedIn steps: manual task (HubSpot can't automate LinkedIn)
- Delay steps: minimum 2 business days between touches
Phase 3: Enrollment Rules
- Suppression: don't enroll if already in another sequence
- Unenrollment: auto-unenroll on reply, meeting booked, or bounce
- Queue limits: max 50 contacts per sender per sequence
- Business hours: only send Mon-Thu 6am-8pm prospect timezone
Phase 4: A/B Testing
Test one variable at a time with 2-week minimum run time:
- Subject lines (2-3 variants)
- Opening lines (different hooks)
- CTA phrasing (soft vs direct)
- Send time (morning vs afternoon)
Phase 5: Analytics
Track: enrollment rate, completion rate, reply rate, meeting rate. Kill sequences with <1% reply rate after 50+ enrollments.
Output Format
Sequence design document with: architecture map, step-by-step configuration, enrollment/unescape rules, A/B test plan, and analytics dashboard design.
Quality Check
Before delivering, verify:
- All required sections are complete
- Output matches the user's stated need
- Named frameworks are cited for key recommendations
- No vague claims — every recommendation has a specific action
- Deliverable is ready for operational use, not just conceptual
Common Pitfalls
- Skipping research. Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
- Generic output. "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
- Missing framework citations. Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.
Execution Artifacts
references/framework-notes.md— HubSpot workflow enrollment, rep-triggered rulestemplates/output-template.md— properties + workflow + sequence deliverablescripts/check-output.py— local checklist validator This skill includes lightweight artifacts the agent can load on demand:references/enrichment-enrollment-gate.md— lm_email_status workflow gatereferences/pat-spielmann-outbound-copy.md— verify-before-enroll (Pat Spielmann)references/gtm-table-blueprints.md— clay-toolkit property mapreferences/leadmagic-waterfall.md— loop list → workflow patternreferences/gtm-experts-outbound-index.md— expert router Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.
Implementation Depth
Use this section when the user asks for a finished asset, not a high-level explanation.
Diagnostic Questions
- What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
- Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
- What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
- What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
- What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
Framework Application
Map the recommendation explicitly to the named frameworks in this skill:
- HubSpot Sequences Best Practices: apply only the part that directly improves the requested deliverable.
- ColdIQ Multi-Channel Cadence: apply only the part that directly improves the requested deliverable.
- Outreach — Sales Engagement Cadence Design: apply only the part that directly improves the requested deliverable.
Deliverable Standard
A strong output from this skill includes:
- A crisp diagnosis of the current situation
- A recommended path with tradeoffs, not a generic list
- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
- A measurement plan with leading and lagging indicators
- Risks and edge cases called out before execution
Adaptation Rules
- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
Related Skills
- cold-email-strategy, cold-email-copywriting, sending-platforms, inbox-setup, email-deliverability
| 1 | |
| 2 | name hubspot-sequences |
| 3 | description >- |
| 4 | Designs and optimizes HubSpot sequences: enrollment triggers, multi-channel |
| 5 | steps, task creation, analytics, and A/B tests. Use when the user is building |
| 6 | or fixing sequences in HubSpot Sales Hub. Triggers on: "HubSpot sequences", |
| 7 | "HubSpot automation", "HubSpot cadence", "sales hub sequences". |
| 8 | license MIT |
| 9 | compatibility Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed |
| 10 | metadata |
| 11 | version "1.0.0" |
| 12 | author LeadMagic |
| 13 | category tools |
| 14 | tags [hubspot, sequences, sales-hub, crm, cadence] |
| 15 | frameworks |
| 16 | - "HubSpot Knowledge Base — Sequences" |
| 17 | - "Google and Yahoo — Bulk sender requirements (2024)" |
| 18 | - "Outreach — Sales Engagement Cadence Design" |
| 19 | |
| 20 | |
| 21 | # HubSpot Sequences |
| 22 | |
| 23 | ## Overview |
| 24 | HubSpot Sequences power the SDR and AE outbound motion inside Sales Hub. |
| 25 | Done right, they automate touches while maintaining personalization. Done wrong, |
| 26 | they're spam cannons that burn your domain reputation. |
| 27 | |
| 28 | ## Authoritative Foundations |
| 29 | **HubSpot Knowledge Base — Sequences** — Configure enrollment, task steps, and automatic unenrollment on reply or meeting booked; sequences send from each rep's connected inbox. |
| 30 | **Google and Yahoo — Bulk sender requirements (2024)** — Authenticate with SPF, DKIM, and DMARC, keep spam complaints below 0.3%, and respect per-inbox daily volume. |
| 31 | **Outreach — Sales Engagement Cadence Design** — Sequence governance, task-based selling, and CRM-locked cadences. |
| 32 | |
| 33 | ## When to Use |
| 34 | "Set up HubSpot sequences" |
| 35 | "Build HubSpot cadences" |
| 36 | "Optimize HubSpot sequence performance" |
| 37 | "HubSpot sequence A/B test" |
| 38 | |
| 39 | ## Step-by-Step Process |
| 40 | |
| 41 | ### Phase 1: Sequence Architecture |
| 42 | Design sequences by persona and trigger: |
| 43 | **Inbound follow-up:** Auto-enroll on form fill, 3-touch, 7-day window |
| 44 | **Outbound cold:** Manual enroll after list build, 6-touch, 21-day window |
| 45 | **Re-engagement:** Enroll on CRM status change, 3-touch, 14-day window |
| 46 | **Event follow-up:** Enroll on event attendance, 2-touch, 5-day window |
| 47 | |
| 48 | ### Phase 2: Step Configuration |
| 49 | Per step: channel, timing, template, task creation rules. |
| 50 | Email steps: plain text, from first name, no tracking pixel if cold |
| 51 | Call steps: auto-create task with call notes template |
| 52 | LinkedIn steps: manual task (HubSpot can't automate LinkedIn) |
| 53 | Delay steps: minimum 2 business days between touches |
| 54 | |
| 55 | ### Phase 3: Enrollment Rules |
| 56 | Suppression: don't enroll if already in another sequence |
| 57 | Unenrollment: auto-unenroll on reply, meeting booked, or bounce |
| 58 | Queue limits: max 50 contacts per sender per sequence |
| 59 | Business hours: only send Mon-Thu 6am-8pm prospect timezone |
| 60 | |
| 61 | ### Phase 4: A/B Testing |
| 62 | Test one variable at a time with 2-week minimum run time: |
| 63 | Subject lines (2-3 variants) |
| 64 | Opening lines (different hooks) |
| 65 | CTA phrasing (soft vs direct) |
| 66 | Send time (morning vs afternoon) |
| 67 | |
| 68 | ### Phase 5: Analytics |
| 69 | Track: enrollment rate, completion rate, reply rate, meeting rate. |
| 70 | Kill sequences with <1% reply rate after 50+ enrollments. |
| 71 | |
| 72 | ## Output Format |
| 73 | Sequence design document with: architecture map, step-by-step configuration, |
| 74 | enrollment/unescape rules, A/B test plan, and analytics dashboard design. |
| 75 | |
| 76 | |
| 77 | |
| 78 | ## Quality Check |
| 79 | |
| 80 | Before delivering, verify: |
| 81 | [ ] All required sections are complete |
| 82 | [ ] Output matches the user's stated need |
| 83 | [ ] Named frameworks are cited for key recommendations |
| 84 | [ ] No vague claims — every recommendation has a specific action |
| 85 | [ ] Deliverable is ready for operational use, not just conceptual |
| 86 | |
| 87 | ## Common Pitfalls |
| 88 | |
| 89 | **Skipping research.** Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables. |
| 90 | **Generic output.** "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner. |
| 91 | **Missing framework citations.** Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority. |
| 92 | |
| 93 | ## Execution Artifacts |
| 94 | |
| 95 | `references/framework-notes.md` — HubSpot workflow enrollment, rep-triggered rules |
| 96 | `templates/output-template.md` — properties + workflow + sequence deliverable |
| 97 | `scripts/check-output.py` — local checklist validator |
| 98 | This skill includes lightweight artifacts the agent can load on demand: |
| 99 | `references/enrichment-enrollment-gate.md` — lm_email_status workflow gate |
| 100 | `references/pat-spielmann-outbound-copy.md` — verify-before-enroll (Pat Spielmann) |
| 101 | `references/gtm-table-blueprints.md` — clay-toolkit property map |
| 102 | `references/leadmagic-waterfall.md` — loop list → workflow pattern |
| 103 | `references/gtm-experts-outbound-index.md` — expert router |
| 104 | Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice. |
| 105 | |
| 106 | ## Implementation Depth |
| 107 | |
| 108 | Use this section when the user asks for a finished asset, not a high-level explanation. |
| 109 | |
| 110 | ### Diagnostic Questions |
| 111 | |
| 112 | What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led? |
| 113 | Which ICP tier is the output for: small business, mid-market, enterprise, or mixed? |
| 114 | What proof is available today: customer stories, usage data, third-party validation, screenshots, or none? |
| 115 | What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow? |
| 116 | What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure? |
| 117 | |
| 118 | ### Framework Application |
| 119 | |
| 120 | Map the recommendation explicitly to the named frameworks in this skill: |
| 121 | |
| 122 | HubSpot Sequences Best Practices: apply only the part that directly improves the requested deliverable. |
| 123 | ColdIQ Multi-Channel Cadence: apply only the part that directly improves the requested deliverable. |
| 124 | Outreach — Sales Engagement Cadence Design: apply only the part that directly improves the requested deliverable. |
| 125 | |
| 126 | ### Deliverable Standard |
| 127 | |
| 128 | A strong output from this skill includes: |
| 129 | |
| 130 | A crisp diagnosis of the current situation |
| 131 | A recommended path with tradeoffs, not a generic list |
| 132 | A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan |
| 133 | A measurement plan with leading and lagging indicators |
| 134 | Risks and edge cases called out before execution |
| 135 | |
| 136 | ### Adaptation Rules |
| 137 | |
| 138 | For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity. |
| 139 | For mid-market: include workflow ownership, handoffs, integrations, and enablement assets. |
| 140 | For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements. |
| 141 | |
| 142 | |
| 143 | ## Related Skills |
| 144 | cold-email-strategy, cold-email-copywriting, sending-platforms, inbox-setup, email-deliverability |
| 145 |
Details
- License
- MIT
- Stars on the repo
- ★ 62
- Checked
- Source
- LeadMagic/gtm-skills ↗
- Creator
- LeadMagic · 129 listings
Similar skills
See all →
SkillBrowser Automation
SkillDeepeval LLM Assessment
SkillBrowser Automation Tool
SkillSkill to App Converter
SkillBrowser Test Automation
SkillTinyFish CLIMore from LeadMagic
SkillStrategic Account Marketing
SkillCluster Account Marketing
SkillProgrammatic Account Targeting
SkillAccount Strategy Designer
SkillTarget Account Selector