Revenue Enablement report
Email Sequence Generator: your result
This answer uses a made up example company. Change the details above and press Run to see your own result.
Email Sequence Generator
For SDRs and demand generation teams. The decision: what do we send, and when, to open a conversation?
Give it the sequence type, the buyer you are writing to and your solution, and get a series of emails with the day to send each one, plus tips for the sequence.
This sample is a made up example, built from the inputs behind Fill in an example. It shows part of one section of the answer.
Add the recipient's name after "Hello" if you have it; the emails do not guess it.
What was not given, and what each input would change:
specific pain point: it would change email 1 from a question about the topic to the problem in your words, and give email 3 a second angle.key value prop: it would change the emails from saying what the product is to saying what you aim for.social proof (a result, a customer quote or an award you may name): it would change emails 2, 3 and 5 from questions to quoted evidence; without it no email quotes a result or a customer.call to action: it would change the ask from a short call to your own wording.Suggested timings, lengths and counts: adjust them to your own.
See the full example answer or run it with your own details.
Revenue Enablement report
This answer uses a made up example company. Change the details above and press Run to see your own result.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
What next? Work with Shashwat Try another tool See all 85 tools and skills
Generated on 2 November 2026 from this branch, with the inputs behind Fill in an example. Your own inputs give a different result.
Revenue Enablement report
Subject: A question on our
Body:
Hello,
I am writing to people in third-party logistics about our. Who else feels this problem, and who would decide on a change?
A question to start with for teams in third-party logistics: Which part of the day goes wrong most often, and what does it cost?
I would welcome a short call next week.
Regards,
(Add your name and role before sending.)
Subject: One question on our
Body:
Hello,
The question that usually decides whether a change like this matters to heads of last-mile operations is this: What happens when plans change after work has started?
I would welcome a short call in the next two weeks.
Regards,
(Add your name and role before sending.)
Subject: Our on the ground
Body:
Hello,
A question from the same place: What have you tried so far on it, and what stopped it from working?
I would welcome a short call later this month.
Regards,
(Add your name and role before sending.)
Subject: Who looks after our in third-party logistics?
Body:
Hello,
I have written a few times about our and have not heard back, so I will ask plainly: is this yours, or does it sit with someone else?
If the problem is real but the timing is wrong, tell me which quarter suits you and I will come back then.
Regards,
(Add your name and role before sending.)
Subject: Questions on our in third-party logistics
Body:
Hello,
This is my last note. Here are the questions to ask before changing how you handle our in third-party logistics, useful even if we never speak:
1.
If you want to talk any of it through, reply and I will make the time for a short call.
Regards,
(Add your name and role before sending.)
Add the recipient's name after "Hello" if you have it; the emails do not guess it.
What was not given, and what each input would change:
specific pain point: it would change email 1 from a question about the topic to the problem in your words, and give email 3 a second angle.key value prop: it would change the emails from saying what the product is to saying what you aim for.social proof (a result, a customer quote or an award you may name): it would change emails 2, 3 and 5 from questions to quoted evidence; without it no email quotes a result or a customer.call to action: it would change the ask from a short call to your own wording.sender context (your name and role): add your name and role before sending.Suggested timings, lengths and counts: adjust them to your own.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
The generator writes a dated multi-email sequence (such as 5 emails across Day 1, Day 3, Day 7, Day 12, and Day 17 for Cold outreach) tailored to your Sequence type, Target persona, Target industry, Your solution, and Tone. Because it never invents recipient names, sender titles, or customer proof, it leaves (Add your name and role before sending.), tells you under Before you send to add the recipient's name after "Hello", and uses discovery questions instead of customer stats in Emails 2, 3, and 5 whenever Social proof is left blank. Also check the subject lines if you typed "our product" as your solution name, since the subject line trims the word "product" ("A question on our"), so always enter your real product or category name.
Come back whenever you launch outbound to a new buyer persona or industry, add a new verified customer proof point, or need a sequence for a different stage (Proposal follow-up, Nurture, Event follow-up, or Referral request). The tool applies the same fixed rules every time. It does not call an AI model, and this site does not keep what you enter.
Add Revenue Enablement once (see Use it in Claude, ChatGPT or Gemini), then ask in plain words. Here is a prompt built from the tested example:
My role is not stated. Ask me for my role first. Use Revenue Enablement's Email Sequence Generator tool. sequence type: Cold outreach; target persona: heads of last-mile operations; target industry: third-party logistics; your solution: our product; tone: Professional. If this tool is unavailable, ask me to open its web page; do not invent its output. In Gemini CLI or Antigravity, use the Helix GTM Suite skills package for related guidance, without claiming to run this connector.
You do not need to sign in. A web browser is enough, and the answer comes back in a second or two.
It applies fixed rules in the Revenue Enablement code to the inputs above and returns text. It does not call an AI model, does not look anything up, and does not store what you type. The web form and the AI assistant connector run the same tool code, so the same input gives the same answer in both.
MCP tool name: email_sequence_generator. REST: POST https://revenue-enablement.gtmhelix.com/api/tools/email_sequence_generator with this JSON body (see How it works):
{
"input": {
"sequence_type": "cold_outreach",
"target_persona": "heads of last-mile operations",
"target_industry": "third-party logistics",
"your_solution": "our product",
"tone": "professional"
}
}
Run a Helix tool in your browser, then take the result to ChatGPT, Claude or Gemini. Connectors work with supported plans in Claude, ChatGPT, Cursor, VS Code and Windsurf. The Helix GTM Suite skills package supports Claude Code, Gemini CLI, Antigravity, Cursor and VS Code, and is available through skills.sh. Each plugin has its own installation steps, below or on its own page.
Connector setup guides · Skills package setup guide · Find the skills on skills.sh