amalgama
internal · email drafts
AI Starter Map · sequence

Email sequence

10 drafts covering the full lifecycle of the 2-session series — invitation, welcome, pre/post each session, gap-week submission, post-series conversion and nurture.

index

10 emails · in send order

#EmailWhenPhase
01Invitation — coldDay −14 to −3Acquisition
02Invitation — warmDay −14 to −3Acquisition
03Welcome — registration confirmedImmediately on application approvalRegistration
04Pre-S1 reminder (T-3)Thursday before S1 MondayPre-event
05Post-S1 — recording + flow submission CTATuesday (T+1 after S1)Gap week
06Flow submission FUP (T+3)Thursday after S1Gap week
07Pre-S2 reminder (T-1)Sunday evening before S2Pre-event
08Post-S2 — thank-you + W-A applyTuesday (T+1 after S2)Post-series
09W-A nudge (wellness ops, T+7)Tuesday, 7 days after S2Post-series
10Non-wellness nurture (T+14)Tuesday, 14 days after S2Post-series
Acquisition

Outreach before launch — get applications in.

01

Invitation — cold

Acquisition
when
Day −14 to −3
audience
Cold list — Apollo, Tomspot Warm Prospects, LinkedIn
goal
Application to the series
channel
Email + LinkedIn DM variant
T
Tom Agrimbauto: applicant
tomas@amalgama.co
Most AI pilots in wellness ops die before production
~20 wellness operators, two Mondays, no upsell. Application only.
Variant: LinkedIn DM (shorter)
Sender notes (4)
  • Personalize the opening line if you know one specific friction at their company (1 sentence).
  • Don't add bullets beyond what's here — kills deliverability.
  • If sent via Apollo/SendGrid: avoid the word "free" in subject (spam filter). Alt subject: *AI prototype in 2 Mondays — no code*.
  • Track reply rate separately. Goal: 8–12% application rate from a clean list.
02

Invitation — warm

Acquisition
when
Day −14 to −3
audience
Warm network — past clients, partners, alumni, intros
goal
Application + share with their network
channel
Email 1:1 (manual or BCC small batch)
T
Tom Agrimbauto: applicant
tomas@amalgama.co
20 wellness operators · 2 Mondays · maybe a fit for you or someone you know
Closed cohort, application only. Wellness operators only.
Sender notes (4)
  • This is 1:1 — write the recipient's name and tweak the opening line per relationship.
  • If you have a specific person in mind for them to forward to, mention them by name.
  • Don't BCC more than 5–6 at a time, only people who would genuinely engage.
  • Track share variable in CRM ("warm-share-{{first_name}}") to see who actually forwards.
Registration

Triggered automatically on approved application.

03

Welcome — registration confirmed

Registration
when
Immediately on application approval
audience
Approved applicants
goal
Confirm + set expectations + deliver worksheet + plant attendance commitment
channel
Transactional email
T
Tom Agrimbauto: applicant
tomas@amalgama.co
You're in — AI Starter Map series
Two Mondays, your worksheet attached, and one rule.
Sender notes (4)
  • This is the only email where the "rule" appears in bold. Set expectations once, hard.
  • Worksheet downloadable without a second form gate.
  • Calendar invite should include Zoom/Demio link if provisioned. Otherwise follow up in #04.
  • Reply-to: Tom's actual inbox. Replies here are warm signals — capture them.
Pre-event

Days before each session — reduce no-show.

04

Pre-S1 reminder (T-3)

Pre-event
when
Thursday before S1 Monday
audience
All approved applicants
goal
Reduce no-show + ensure worksheet downloaded
channel
Email
T
Tom Agrimbauto: applicant
tomas@amalgama.co
Monday {{s1_time}} — your AI Starter Map seat
Three days out. Worksheet attached. One question for you.
Sender notes (3)
  • Resend the worksheet link — many will have forgotten where it is.
  • The one-question prompt warms them up + gives Tom sample frictions for S1.
  • Optional A/B: subject "Bring one answer Monday" — sometimes outperforms logistical subject.
07

Pre-S2 reminder (T-1)

Pre-event
when
Sunday evening before S2
audience
All approved applicants
goal
Reduce S2 drop-off + announce the chosen flow
channel
Email
T
Tom Agrimbauto: applicant
tomas@amalgama.co
Tomorrow {{s2_time}} — bring your laptop
Live build is on. Here's what we're building and what you need ready.
Sender notes (4)
  • Announcing chosen flow + author name: rewards submitter + shows cohort this is real.
  • If author wants anonymity, replace {{author_first_name}} with "someone from the group".
  • Zapier free tier mention reduces friction for followers.
  • 'Things will break' framing lowers Tom's pressure during live build + positions failure as method.
Gap week

Between S1 and S2 — flow submission, drop-off prevention.

05

Post-S1 — recording + flow submission CTA

Gap week
when
Tuesday (T+1 after S1)
audience
All S1 attendees (no-show variant included)
goal
Deliver recording + ask attendees to submit their flow for the live build in S2
channel
Email
T
Tom Agrimbauto: applicant
tomas@amalgama.co
S1 recording + your shot at the live build
Your flow could be the one we build live on Monday. Submit by Friday.
Variant: No-show variant (different subject + opening)
Subject override
S1 recording — and how to catch up before Monday
Sender notes (4)
  • Critical metric: % of S1 attendees who submit a flow. Target 25–35%. Below that → S2 live build is weak.
  • Tom reads every submission, picks by Saturday morning for Sunday dry-run.
  • If submissions vague, reply 1:1 for sharper trigger/output — doubles as warming.
  • DO NOT mention AI Blueprint W-A. Too early.
06

Flow submission FUP (T+3)

Gap week
when
Thursday after S1
audience
S1 attendees who have NOT submitted a flow yet
goal
Last call to submit a flow before Friday EOD
channel
Email
T
Tom Agrimbauto: applicant
tomas@amalgama.co
Tomorrow's deadline — one flow gets built live
Send yours by Friday EOD. Trigger / steps / output / metric.
Sender notes (3)
  • Brutally short. People who haven't submitted have a psychological friction, not technical.
  • Don't shame no-submitters. The 'free read' line is the hook.
  • Tom should actually deliver — spend 10–15 min Saturday morning replying to non-selected submissions.
Post-series

After S2 — conversion to AI Blueprint W-A + nurture.

08

Post-S2 — thank-you + W-A apply

Post-series
when
Tuesday (T+1 after S2)
audience
S2 attendees, segmented wellness vs non-wellness
goal
Deliver recording + W-A application for wellness, nurture for others
channel
Email
T
Tom Agrimbauto: applicant
tomas@amalgama.co
Recording + what's next
S2 is live. If your operation needs more than a Zap, here's the next conversation.
Variant: S2 no-show variant
Subject override
S2 recording (live build) + what's next
Sender notes (4)
  • Biggest decision: where in this email does the wellness CTA appear? Currently mid-page after value delivery.
  • {{author_first_name}} = the person whose flow was built live. Public credit moment.
  • Track: open → click W-A apply → application submitted → approved. Target 8–15% wellness-tagged conversion.
  • DO NOT mention $4,900 — that price is W-B.
09

W-A nudge (wellness ops, T+7)

Post-series
when
Tuesday, 7 days after S2
audience
Wellness-tagged S2 attendees who haven't applied to W-A
goal
Final honest push to W-A application
channel
Email
T
Tom Agrimbauto: applicant
tomas@amalgama.co
Did you ship the quick win?
Quick check-in. And one more question.
Sender notes (4)
  • Three-option diagnostic is the entire point. Replies tell you exactly where each prospect stuck.
  • Don't automate replies. Tom or trusted second eyes answers each personally within 48h.
  • Category-3 replies describing the flow = high-intent signal (stuck on execution = exactly what AI Blueprint solves).
  • ONE follow-up only. If no apply after #09, → nurture.
10

Non-wellness nurture (T+14)

Post-series
when
Tuesday, 14 days after S2
audience
Non-wellness S2 attendees (+ wellness low-intent fallback)
goal
Stay in funnel without burning the list. Surface resources. Open replies.
channel
Email
T
Tom Agrimbauto: applicant
tomas@amalgama.co
Three things that might be useful
Resources from the series, plus what we publish next.
Sender notes (5)
  • END of sequence for non-wellness. No further drips. Hard exit.
  • "Pattern most often" should be updated each cohort with real submission data.
  • The "reply" CTA is the only line driving reply rate. Track replies.
  • Last note intentionally separate (P.S.-like). Lower stakes, polite unsubscribe.
  • DO NOT include W-A apply link. Pushing again destroys trust.
variables key

Variables to fill before sending

{{first_name}}recipient first name
{{s1_date}}Monday of session 1 (e.g. "Monday, June 8")
{{s1_time}}session 1 time + TZ (e.g. "12:00 PM ET")
{{s2_date}}Monday of session 2 (S1 + 7 days)
{{s2_time}}session 2 time + TZ
{{apply_url}}landing apply form URL
{{worksheet_url}}Friction Map worksheet PDF link
{{calendar_invite}}.ics or platform join link
{{recording_s1_url}}S1 recording link (post-S1 only)
{{recording_s2_url}}S2 recording link (post-S2 only)
{{wa_apply_url}}AI Blueprint Webinar A application URL
{{author_first_name}}first name of attendee whose flow was selected
{{flow_one_liner}}short description of the selected flow
{{unsubscribe_url}}unsubscribe link (final email only)
voice

Voice rules