[object Object]

A new SDR opens HubSpot and sees 312 templates and 89 snippets. Half are duplicates with one-word subject changes. The actual top performer is buried on page seven. That portal is one quarter past the point where templates and snippets help productivity and one quarter into the point where they actively cost it. The fix is curation, not more templates.

What each one is

Templates are full emails — subject, body, attachments — that a rep loads, edits, and sends. Snippets are reusable chunks: signatures, boilerplate paragraphs, common objection responses, calendar links. Templates fill the whole canvas; snippets get pasted into a section.

Template: "Discovery follow-up - manager persona"
  Subject: "Recap: how {{ company.name }} could move on {{ topic }}"
  Body:    Full email with personalization tokens

Snippet: "/sig"
  Body: Standard signature with name, title, calendar link

Type # in the email composer to insert a snippet inline.

Sharing scope and visibility

Private templates clutter individual lists; team templates serve a defined group; everyone-shared templates surface across the portal. Tag every template with audience and use case in the name:

SDR_outbound_persona-mgr_v3
AE_followup_post-demo_v2
CSM_renewal_30day_v1

Without naming discipline reps cannot find anything and recreate variants instead of reusing what exists.

Personalization tokens that survive

Tokens pull from contact, company, deal, and owner records. Each token needs a default value because broken tokens look worse than no personalization:

Hi {{ contact.firstname | default("there") }},
Thanks for the conversation about {{ deal.dealname | default("your project") }}.

Test every template against a contact missing each personalization field before publishing.

Performance reporting per template

Templates report send count and reply rate. Build a custom report ranking templates by reply rate over send volume so you separate “high reply rate, sent twice” from “high reply rate, sent 400 times”:

Object: Email
Group by: Template name
Metric: Reply rate, Send count
Filter: Sent in last 90 days, send count >= 25
Sort: Reply rate desc

The top three templates from this report are the ones to promote and study; the bottom 50 are candidates for retirement.

Snippet patterns that scale

Snippets shine for content that changes rarely but appears often:

#sig         - your signature
#calendar    - meeting link with current Q2 availability message
#pricing-overview - 2-paragraph plan summary
#security    - SOC2 compliance language
#refer       - referral program description

Avoid building snippets that overlap with templates. Keep snippets short and composable; if you find yourself stitching three snippets every time, make it a template.

Governance and pruning

Quarterly review:
  - Owner: RevOps designated curator
  - Action: archive templates with <10 sends in last 90 days
  - Action: archive templates with reply rate <50% of category median
  - Action: rename templates not following taxonomy
  - Action: consolidate near-duplicates

Restrict template-create permissions to a small group during the cleanup window. Open it back up once the library is healthy.

A/B testing what matters

Test subject lines, opening line, CTA copy. Design rarely moves reply rate at this stage of the funnel. Run tests until either statistical significance or 30 days, whichever comes first; promote the winner and archive the loser.

What to do this week

Pull a template performance report, tag the top three for promotion and the bottom 50 for archive, and assign a single curator before another rep adds template 313.

[object Object]
Share