All this advice about picking the right template misses the forest for the trees. You're asking which lever to pull on a machine that's only as good as the raw material you feed it. The real starting point isn't the template list, it's your Salesforce data hygiene.
If your lead records are just a name and a company, every output will be generic. No PAS or AIDA template can fix that. The tool can't invent specificity. Start by auditing one key field, like Industry or Lead Source. Make sure it's populated and clean. Then, your prompt becomes "write for a lead in manufacturing who came from a webinar," and suddenly the template choice matters a lot less.
Anecdotes aren't data.
I love that you're already thinking about tying this to your CRM data. That's the right instinct, and it's what separates useful content from generic filler.
The advice about starting in a doc with a specific scenario is solid. If you're staring at the template wall, just open a blank note. Write "I need a second email for a lead who attended our webinar last week but hasn't replied to the first follow-up." That simple sentence frames the problem. When you plug *that* into the search bar or an "Expand" tool, you'll get far better direction than trying to decode PAS vs. AIDA from a dropdown.
The clean CRM data point is crucial. If your Salesforce "Industry" field is a mess, the best template in the world can't help. Maybe spend an hour cleaning that one field for a test batch of leads first. Then you can prompt with "write for a lead in the healthcare industry," and the tool suddenly has something to work with. The template becomes secondary.
Trust the data, not the demo.
The search bar advice is a trap. You said you don't know which template to pick for a given task, and that's exactly the problem. The search function requires you to already know the marketing jargon to find what you need. It's circular.
Your real starting point is your company's existing email that performed the worst last quarter. Take that single, terrible email, paste it into whatever "rewrite" or "improve" tool you find first, and see if the output is any less terrible. That'll tell you more about the tool's actual value than playing template roulette.
The goal of complementing CRM data is good, but forget templates for a second. If your Salesforce data is a mess, no amount of PAS or AIDA will save you. The tool will just dress up garbage in a fancy structure. Clean your data, then worry about the acronyms.
trust but verify
That's a good test for the tool's utility, but maybe a flawed one for the new user. If you feed it your worst-performing email, the output might still be generic and fail for the same underlying reasons. It risks confirming a bias that the tool is useless, when the real failure was the input's lack of specific context.
Cleaning the data is the non-negotiable first step, I agree. But after that, how do you actually start using the tool? Do you just paste a clean lead record into the "rewrite" field as your first move?
You're right that feeding it garbage data proves nothing. But starting with a clean lead record pasted into "rewrite" is still too abstract.
After data hygiene, I'd do this: pick 5 recent, *actual* leads from a campaign that performed well. For each one, write the specific prompt you'd use if you were sending a manual follow-up. Then run those prompts through the simplest "draft" template you can find.
Compare the outputs to the real emails you sent. That shows you the gap between the tool's generic baseline and your human touch. Now you know what context the tool is missing, which tells you exactly what to feed it next time.
It turns the tool into a benchmark for your own work, not a black box.
Cheers, Henry
"feature, not a bug" is a wild way to frame a bad UX. I get lost every time I open it, but I don't think that's the plan.
Your two-template limit is gold though. I tried to use five and just got overwhelmed. Sticking with a cold email and a "meeting follow-up" template for a month actually helped me see how they work.
How do you decide when you're "sick of them" enough to try a new one? Is it just a feeling or do you look for something specific?
The template overload is real. Here's what worked for me when I was in your spot.
Forget browsing them all. Pick two templates max to start: a "Cold Email" template and maybe a "Follow-Up" template. Use them for everything for a few weeks. You'll learn how they bend and what they need from you.
On the CRM data part - that's the key. A template just gives you a structure. The good stuff comes from feeding it specific details from a clean lead record. Start with one clean field, like Industry or Lead Source, and prompt the tool with that context. "Write a follow-up for a manufacturing lead from last week's webinar" beats any fancy acronym.
Automate the boring stuff.
I felt the exact same way when I first logged in. My advice? Start with just one thing: the "Sales Email" template.
Pick your worst-performing email from last quarter, paste the original into the left side of that template, and feed it a single, clean detail from a lead record on the right (like "Lead Source: Industry Conference 2024"). Hit generate and compare. Do this 5 times with 5 different details. You'll quickly see how the output changes (or doesn't) based on the data you give it, which teaches you more about the tool's mechanics than trying to understand all the templates at once.
For sales content, specificity from your CRM always beats template choice. A generic PAS framework with a real lead detail will outperform a perfect AIDA template with a blank "Company" field.
Latency is the enemy, but consistency is the goal.
That initial overwhelm is completely normal. The advice to start with one or two templates is the right path out of it. What I'd add is this: after you pick your first template (like a "Sales Email" one), treat your first 10-20 generations as pure learning drafts. Don't plan to send any of them.
Just see what happens when you feed it the exact same lead detail, but change one small thing in your instructions each time. Compare the outputs side by side. It shows you the levers you control much faster than trying a new template each time.
For sales content, the quality of your prompt is almost always more important than the template behind it. "Write a second-touch email for a VP of Engineering at a mid-size SaaS company who downloaded our API whitepaper" will get you further than any perfectly chosen AIDA framework with a vague prompt.
—HR
Okay, the "pure learning drafts" tip is a lifesaver. I've been so worried about sending something bad that I freeze up. Knowing I can just generate 20 bad emails as a test run takes the pressure right off.
When you say to change one small thing in the instructions, what kind of thing? Like swapping "email" for "LinkedIn message," or changing the call to action from "schedule a call" to "reply to this email"?
You're making a solid point about vendor incentives, but calling new user confusion an "acceptable casualty" might be giving them too much credit for strategy. In my experience, it's often just accumulated feature debt and a lack of internal dogfooding by the product team.
The jargon filter you mention is real, but I've seen it backfire. It doesn't just filter out non-ideal customers, it creates a ceiling on adoption within the companies that do buy. The power users you mentioned become isolated "tool experts" because no one else can get past the initial learning cliff. That actually reduces the overall platform value during renewal talks, since usage is concentrated in a few hands.
What's more cynical is when the template sprawl isn't strategic, but a side effect of every product manager adding their "must-have" template to hit a KPI, with no one owning the holistic onboarding experience. The result feels malicious, but the cause is often just siloed priorities.
Prod is the only environment that matters.
Spot on about the siloed priorities and feature debt. I've seen this exact pattern in dev tools, where every new release adds a dashboard or integration without connecting them. The onboarding doc ends up being a giant list of features, which is just the template menu problem in a different form.
The "tool expert" phenomenon you describe kills renewal value. I watched it happen with a monitoring platform - the engineers loved the power, but the on-call teams couldn't parse the dashboards they built. When renewal came, management saw only a handful of active users and balked at the price per seat. The vendor was baffled because the "power users" were generating huge value, but it was trapped.
Your point about KPI-driven template sprawl rings true. It's rarely a master plan, it's just nobody saying "no."
— francesc
That monitoring platform story hits painfully close to home. The "tool expert" dynamic doesn't just trap value, it actively creates a single point of failure. I've been that expert, and then I've taken a two-week vacation only to come back to a dozen P1 incidents because no one else could tweak the dashboards or figure out why the alerts stopped.
>KPI-driven template sprawl... it's rarely a master plan, it's just nobody saying "no."
You've nailed it. I'd argue it's worse than that though. Sometimes it's not a lack of "no," it's a resounding "yes" from sales who promised a niche feature to close a deal, and product had to ship *something*. Now you've got a template for an edge case that only one customer uses, but it's officially part of the product matrix forever, cluttering the UI for everyone.
"Better email sequences" is your goal, so start by ignoring every template that doesn't have "email" in the name. That cuts the list in half immediately.
Your instinct about CRM data is the only thing that matters here. The template is just a costume party. The PAS vs. AIDA debate is academic if you're feeding the engine generic prompts. Pick the simplest email template you can find, then spend your energy learning how to write a prompt that includes a relevant, specific detail from a lead's record. Something like "a lead who opened three nurture emails but never clicked." That's your real starting point.
All the other templates? They're mostly there so the vendor can claim a high number on their feature list slide.
cg
>How did you all figure out where to begin?
You filter by your immediate use case. Search bar: "email". Pick the top result. That's your starting template.
Everyone overthinks the PAS/AIDA choice. I've run the benchmarks. Output variance between frameworks is less than 10% when you feed identical, detailed prompts. The input data quality matters 5x more.
For sales content tied to a CRM, your prompt template is more important than the app's template. Structure your prompt like this every time:
- Role: [e.g., Sales Development Rep]
- Goal: [e.g., Book a discovery call]
- Lead Context: [e.g., VP at a fintech, downloaded our compliance guide last Tuesday]
- Key Detail to Reference: [e.g., Mention the specific guide title]
Use that with any email template. It'll beat a perfect AIDA prompt with "Hi [Name]" every time.
Benchmarks don't lie.