Made by@gtmengineerSequence writer
@gtmengineer/sequence-writer
Write multi-step outbound sequences (email, LinkedIn, call) built on a real reason to reach out, with personalization slots instead of fake personalization. A built-in linter blocks spam phrases, fake Re: subjects, invented familiarity, unsourced stats, broken slots, too many links, and rushed cadence before anything is loaded into a sending tool.
- Activity
- New: be the first to try it
- Installs
- 0 installs
- Likes
- 0 likes
- Clones
- 0 clones
- 1{
- 2 "name": "RevOps leaders at companies that just opened a second sales team",
- 3 "persona": "Head of Revenue Operations, 200 to 2,000 employees",
- 4 "signal": "Hiring a second sales leader or a new regional sales team in the last 60 days",
- 5 "slots": [
- 6 "first_name",
- 7 "company",
- 8 "trigger",
- 9 "observation",
- 10 "peer_company",
- 11 "sender_name"
- 12 ],
- 13 "steps": [
- 14 {
- 15 "day": 1,
- 16 "channel": "email",
- 17 "subject": "{{company}}'s new sales team",
- 18 "body": "Hi {{first_name}},\n\nSaw {{trigger}}. When a second team spins up, the forecast usually splits into two spreadsheets within a quarter.\n\n{{observation}}\n\nWe help RevOps teams keep one forecast and one set of routing rules as teams multiply. {{peer_company}} used it to get their Monday forecast call back to 30 minutes.\n\nWorth comparing notes on how you plan to handle it?\n\n{{sender_name}}",
- 19 "sources": [
- 20 "Customer story approved by the customer, on file"
- 21 ]
- 22 },
- 23 {
- 24 "day": 4,
- 25 "channel": "linkedin",
- 26 "body": "Hi {{first_name}}, I work with RevOps leads at companies adding sales teams. Would be glad to connect."
- 27 },
- 28 {
- 29 "day": 7,
- 30 "channel": "email",
- 31 "in_thread": true,
- 32 "body": "Hi {{first_name}},\n\nOne more thought: the first thing that usually breaks is lead routing, because new territories get bolted onto old rules. Is that on your list this quarter, or already handled?\n\n{{sender_name}}"
- 33 },
- 34 {
- 35 "day": 12,
- 36 "channel": "email",
- 37 "subject": "routing rules for two teams",
- 38 "body": "Hi {{first_name}},\n\nWhen {{peer_company}} split routing across two teams, a one-page checklist saved them a week of rework. Want me to send it over?\n\nIf this is not your area, tell me who owns it and I will stop here.\n\n{{sender_name}}"
- 39 }
- 40 ]
- 41}