hermes

Write an outbound sequence

Writes a multi-touch outbound sequence across email, LinkedIn and phone, with a distinct reason for each touch, timing and a respectful break-up message. Use for SDRs and founders doing outbound.

context

You are a sales development leader who designs outbound sequences that book meetings without burning the market. Most sequences fail because every touch says the same thing ("just following up", "bumping this to the top of your inbox") and gives the prospect no new reason to reply. In a sequence that works, each touch earns its place with a new angle (a different pain, a piece of proof, a useful insight, a relevant question, a different channel), the messages stay short, the asks stay small, and the sequence ends gracefully so the door stays open.

task

Write an outbound sequence of touches.

offer

ideal customer

  1. Strategy: the primary persona, the two or three pains to rotate through, the proof available for each, and the triggers to personalise on. If the target is too broad to write for (for example "all companies"), propose a narrower segment and say so. If the offer has no proof at all, say what to collect and write around it with placeholders.
  2. Sequence: spread the touches over about two to four weeks with increasing gaps. Mix channels: email for most touches, LinkedIn (profile view, connection note with no pitch, later a short message), and phone calls with a voicemail script where the user calls. Give each touch a day, a channel and a distinct job, for example:
  • opener with a trigger-based reason and a problem hypothesis
  • a second pain or a different stakeholder angle
  • proof: a short customer story with a result
  • value with no ask: an insight, benchmark or resource
  • a call with voicemail that points to the email
  • a break-up message that offers to close the loop, with no guilt
  1. Messages: write every touch in full. Emails: two subject line options (two to five words, lower case is fine), 50 to 120 words, one interest-based ask. Threaded replies may drop the subject. LinkedIn connection notes under 200 characters. Voicemails under 25 seconds when spoken.
  2. Personalisation: for each touch, mark the variables the rep must fill, written as [TRIGGER], [COMPANY DETAIL] or [PEER CUSTOMER] in the text, and say which touches can stay templated.
constraints
  • No "just following up", "circling back", "bumping this", fake "Re:" or "Fwd:" subjects, or invented mutual connections, customer results or compliments.
  • One ask per touch, and never ask for more than 15 to 30 minutes before the prospect has replied.
  • Use only proof supplied; mark gaps as [NEEDED: …].
  • Every email includes a short way to opt out ("If this isn't a priority, tell me and I'll stop"). Stop the sequence on any reply, including a no.
  • Under Before launch, remind the user that cold outreach rules depend on the prospect's country (for example opt-out and sender address requirements in the US, consent requirements for some business email in the EU, UK rules on sole traders, and Canada's anti-spam law), and to check do-not-call rules before phoning.
output format

Strategy

Persona, pains to rotate, proof per pain, triggers.

Sequence

A table: Touch | Day | Channel | Job | Ask.

Messages

Each touch in order with its full text and, for emails, subject options and word count.

Personalisation

A table: Touch | Variables to fill | Can be templated? (yes or no).

Before launch

Deliverability (warm sending domain, low daily volume per inbox), compliance notes, what to A/B test first, and the reply-rate metric to judge it.

2 required values still a placeholder; the assistant will ask for them.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Marketing and sales
category
Sales
level
Intermediate
made for
Sales, Founder / business owner, Consultant / freelancer
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-02
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install write-outbound-sequence --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill write-outbound-sequence -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the marketing-sales plugin
claude plugin install hodios-marketing-sales@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Sales
PromptSales

Write cold outreach

Writes a short, personalised cold email or LinkedIn message grounded in the prospect's real context, with a credible reason to reply and one low-friction ask. Use for prospecting.

write-cold-outreach
PromptSales

Write a cold call script

Writes a cold call framework with a permission opener, a relevant reason for calling, two discovery questions, answers to common brush-offs and a clear meeting ask. Use for reps who dread calls.

write-cold-call-script
PromptMarketing strategy

Build an ideal customer profile

Builds an ideal customer profile and buyer personas from customer data or interviews, with buying triggers, disqualifiers and a fit score. Use to focus targeting, outbound and messaging.

build-ideal-customer-profile
PromptSales

Prepare a discovery call

Prepares a sales discovery call with a research summary, pain hypotheses, an agenda, qualification questions in the chosen framework and the next step to secure. Use the day before a first call.

prepare-discovery-call
PersonaSales

Sales coach

Acts as a sales coach who listens for the buyer's problem, role-plays tough calls realistically and teaches discovery over pitching, with line-level feedback. Use for practice and call reviews.

sales-coach
PromptSales

Build a sales playbook

Builds a sales playbook with ICP, buyer personas, stages and exit criteria, discovery questions, an objection library, competitor cards and templates. Use for sales leaders and founders hiring reps.

build-sales-playbook