Email Swipe File

5-Part Nurture Email Swipe File — AI Opportunity Audit

Audience: Scorecard takers (lead magnet) in the 40–79 “prime buyer” band, who have NOT yet booked an audit.

Send engine: Resend (via n8n HTTP Request node, or Resend’s native n8n node). All emails are copy-paste ready as Resend API JSON payloads.

Merge tokens (replace at send time from Supabase contacts + scorecard_results):

{{first_name}} — contacts.first_name
{{score}} — scorecard_results.overall_score
{{band}} — scorecard_results.band
{{binding_constraint_1}} — scorecard_results.binding_constraint_1
{{ref_code}} — referrals.ref_code (their own, if they’ve converted; else the referrer’s)
{{calcom_url}} — $env.CALCOM_URL
{{sales_url}} — $env.SITE_URL + “/audit”
{{portal_graphic}} — Placid share graphic URL (generated on scorecard completion)

Send timing & cadence:

Email	Trigger	Delay	Goal
1	Scorecard complete	Immediate	Deliver score + offer audit
2	Email 1 sent	+2 days	Show what an audit actually looks like
3	Email 2 sent	+3 days	Scarcity — limited slots
4	Email 3 sent	+5 days	The #1 mistake costing them AI ROI
5	Email 4 sent	+4 days	Final nudge + bonus

Exit rules (suppress if): contact.status IN (‘won’,‘active’,‘delivered’) OR engagement exists for contact_id. Check via a Supabase lookup node at the top of each send.

From address: Dwad <dwad@dwadlane.com> (set MAIL_FROM env var). Use a verified Resend sending domain for dwadlane.com.

Resend API — Base Payload Template

Every email below uses this skeleton. Only subject, html, text, and send_at change.

POST https://api.resend.com/emails
Headers:
  Authorization: Bearer {{$env.RESEND_API_KEY}}
  Content-Type: application/json

{
  "from": "Dwad <{{MAIL_FROM}}>",
  "to": ["{{contact_email}}"],
  "subject": "...",
  "html": "...",
  "text": "...",
  "tags": ["nurture"],
  "headers": { "X-Entity-Ref-ID": "{{contact_id}}" }
}

For scheduled sends, add "send_at": "2026-07-06T09:00:00+08:00" (ISO 8601, Manila time). Resend also supports a scheduled_at field — check current Resend docs for the exact field name on your version.

Log every send to email_log (contact_id, email_type, resend_message_id, subject, sent_at).

EMAIL 1 — The Score + The Offer (Immediate)

Subject: Your AI Readiness Score: {{score}}/100

Preheader: You’re in the “{{band}}” band — here’s what that means (and the one thing to fix first).

Plain text:

Hi {{first_name}},

You just completed the AI Readiness Scorecard. Here's your result:

  Score: {{score}}/100
  Band: {{band}}
  Your binding constraint: {{binding_constraint_1}}

What "binding constraint" means: this is the one dimension that's capping
everything else. Fix this first and every other AI investment compounds.

Most businesses in your band are losing 15–25 hours per week to work that
AI could handle — but only after that constraint is cleared.

I run a fixed-scope AI Opportunity Audit that pinpoints exactly which
15–20 automations are worth building, ranked by impact × effort, with a
defensible ROI projection. You walk away with a 30/60/90 roadmap a
competent operator can start Monday.

Three tiers, $1.5K–$5K. Delivery in 7 business days.

See the details and book here: {{sales_url}}

— Dwad

HTML:

<div style="font-family: -apple-system, sans-serif; max-width: 560px; margin: 0 auto; color: #1a1a1a;">
  <p>Hi {{first_name}},</p>
  <p>You just completed the AI Readiness Scorecard. Here's your result:</p>
  <table style="border-collapse: collapse; margin: 16px 0;">
    <tr><td style="padding: 6px 12px; background: #f4f4f5; font-weight: 600;">Score</td><td style="padding: 6px 12px;">{{score}}/100</td></tr>
    <tr><td style="padding: 6px 12px; background: #f4f4f5; font-weight: 600;">Band</td><td style="padding: 6px 12px;">{{band}}</td></tr>
    <tr><td style="padding: 6px 12px; background: #f4f4f5; font-weight: 600;">Binding constraint</td><td style="padding: 6px 12px;">{{binding_constraint_1}}</td></tr>
  </table>
  <p><strong>What "binding constraint" means:</strong> this is the one dimension capping everything else. Fix it first and every other AI investment compounds.</p>
  <p>Most businesses in your band lose <strong>15–25 hours per week</strong> to work AI could handle — but only after that constraint is cleared.</p>
  <p>I run a fixed-scope <strong>AI Opportunity Audit</strong> that pinpoints exactly which 15–20 automations are worth building, ranked by impact × effort, with a defensible ROI projection. You get a 30/60/90 roadmap you can start Monday.</p>
  <p>Three tiers: $1.5K / $3K / $5K. Delivered in 7 business days.</p>
  <p><a href="{{sales_url}}" style="display: inline-block; padding: 12px 24px; background: #111; color: #fff; text-decoration: none; border-radius: 6px;">See the audit & book →</a></p>
  <p>— Dwad</p>
</div>

EMAIL 2 — What an Audit Actually Looks Like (+2 days)

Subject: What you actually get when you buy an AI audit

Preheader: Not a 40-page PDF that gathers dust. Here’s the real deliverable.

Plain text:

Hi {{first_name}},

A lot of "AI audits" are a generic 40-page PDF that tells you to "adopt AI."
Worthless. Here's what mine actually delivers:

1. A 7-dimension maturity score, with a binding-constraint analysis
   (the 2 dimensions capping your ROI — fix these first).

2. An opportunity matrix: 15–20 automations ranked by impact × effort,
   each with estimated hours saved, annual $ savings (with the math shown),
   and time-to-value.

3. A 30/60/90 roadmap: what to build in days 1–30 (foundations),
   31–60 (quick wins), 61–90 (scale). Specific enough to start Monday.

4. A defensible ROI projection: "Estimated 24-month net savings: $X
   (YYY% ROI on a $3,000 audit)." Conservative, rounded down, math shown.

5. A 5–8 min Loom walkthrough of the whole thing — in plain English.

6. A live client portal (radar chart, opportunity heatmap, roadmap tiles)
   you can share with your team or board.

Total hands-on time from you: ~90 minutes across intake + interviews.
I do the rest.

Book here: {{calcom_url}}

— Dwad

HTML:

<div style="font-family: -apple-system, sans-serif; max-width: 560px; margin: 0 auto; color: #1a1a1a;">
  <p>Hi {{first_name}},</p>
  <p>A lot of "AI audits" are a generic 40-page PDF that tells you to "adopt AI." Worthless. Here's what mine actually delivers:</p>
  <ol>
    <li><strong>7-dimension maturity score</strong> with binding-constraint analysis — the 2 dimensions capping your ROI.</li>
    <li><strong>Opportunity matrix:</strong> 15–20 automations ranked by impact × effort, each with hours saved, annual $ savings (math shown), and time-to-value.</li>
    <li><strong>30/60/90 roadmap:</strong> days 1–30 (foundations), 31–60 (quick wins), 61–90 (scale). Specific enough to start Monday.</li>
    <li><strong>Defensible ROI projection:</strong> "Estimated 24-month net savings: $X (YYY% ROI on a $3,000 audit)." Conservative, rounded down.</li>
    <li><strong>5–8 min Loom walkthrough</strong> of the whole thing — in plain English.</li>
    <li><strong>Live client portal</strong> (radar chart, opportunity heatmap, roadmap tiles) you can share with your team or board.</li>
  </ol>
  <p>Total hands-on time from you: ~90 minutes across intake + interviews. I do the rest.</p>
  <p><a href="{{calcom_url}}" style="display: inline-block; padding: 12px 24px; background: #111; color: #fff; text-decoration: none; border-radius: 6px;">Book your audit →</a></p>
  <p>— Dwad</p>
</div>

EMAIL 3 — Scarcity (+3 days)

Subject: 4 audit slots left this month

Preheader: I cap at 8 audits/month so delivery stays sharp. 4 are gone.

Plain text:

Hi {{first_name}},

Quick one. I cap AI Opportunity Audits at 8 per month — beyond that,
delivery quality drops and the Loom walkthroughs get rushed.

{{month_name}} has 4 slots left.

If you're in, grab one before they go: {{calcom_url}}

If you're not sure which tier fits, reply with your team size and your
biggest time-sink and I'll point you to the right one.

— Dwad

HTML:

<div style="font-family: -apple-system, sans-serif; max-width: 560px; margin: 0 auto; color: #1a1a1a;">
  <p>Hi {{first_name}},</p>
  <p>Quick one. I cap AI Opportunity Audits at <strong>8 per month</strong> — beyond that, delivery quality drops and the Loom walkthroughs get rushed.</p>
  <p>{{month_name}} has <strong>4 slots left</strong>.</p>
  <p><a href="{{calcom_url}}" style="display: inline-block; padding: 12px 24px; background: #111; color: #fff; text-decoration: none; border-radius: 6px;">Grab a slot →</a></p>
  <p>Not sure which tier fits? Reply with your team size and biggest time-sink and I'll point you to the right one.</p>
  <p>— Dwad</p>
</div>

EMAIL 4 — The #1 Mistake (+5 days)

Subject: The AI mistake that’s costing you {{binding_constraint_1}}

Preheader: Most businesses buy tools before fixing this. Here’s the fix.

Plain text:

Hi {{first_name}},

The #1 mistake I see in your band ("{{band}}"):

Businesses buy AI tools before fixing their binding constraint.

Your binding constraint is {{binding_constraint_1}}. That means no matter
how many tools you stack on top, the ROI stays capped — because the
foundation underneath is the bottleneck.

It's like buying a Ferrari and putting it on a dirt road.

The fix is unglamorous but pays for itself in 60 days:
1. Name the constraint (the scorecard already did this for you).
2. Sequence ONE fix into week 1 of a roadmap.
3. Then layer the automations that were blocked by it.

That's exactly what the audit produces: the constraint named, the fix
sequenced, and the 15–20 automations ranked behind it.

Book here: {{calcom_url}}

— Dwad

HTML:

<div style="font-family: -apple-system, sans-serif; max-width: 560px; margin: 0 auto; color: #1a1a1a;">
  <p>Hi {{first_name}},</p>
  <p>The #1 mistake I see in your band ("{{band}}"):</p>
  <p><strong>Businesses buy AI tools before fixing their binding constraint.</strong></p>
  <p>Your binding constraint is <strong>{{binding_constraint_1}}</strong>. No matter how many tools you stack, the ROI stays capped — the foundation is the bottleneck. It's like buying a Ferrari and putting it on a dirt road.</p>
  <p>The fix is unglamorous but pays for itself in 60 days:</p>
  <ol>
    <li>Name the constraint (the scorecard already did this).</li>
    <li>Sequence ONE fix into week 1 of a roadmap.</li>
    <li>Layer the automations that were blocked by it.</li>
  </ol>
  <p>That's exactly what the audit produces: the constraint named, the fix sequenced, and 15–20 automations ranked behind it.</p>
  <p><a href="{{calcom_url}}" style="display: inline-block; padding: 12px 24px; background: #111; color: #fff; text-decoration: none; border-radius: 6px;">Book the audit →</a></p>
  <p>— Dwad</p>
</div>

EMAIL 5 — Final Nudge + Bonus (+4 days)

Subject: Last one from me — + a free audit if you refer

Preheader: Closing this nurture. One bonus if you act this week.

Plain text:

Hi {{first_name}},

This is the last email in this sequence — I don't want to fill your
inbox. But before I go, two things:

1. If you book an audit this week, I'll add a free "competitor AI
   teardown" — I audit how 2 of your competitors are using AI and where
   they're exposed. Normally $500. On the house.

2. Whether or not you buy, you can earn 15% of any audit fee for every
   business you refer. Your link: {{site_url}}/?ref={{ref_code}}

If the audit isn't right for you right now, no worries — the scorecard
insights are yours to keep.

Reply "audit" if you want a slot, or ignore this and I won't bother
you again.

— Dwad

HTML:

<div style="font-family: -apple-system, sans-serif; max-width: 560px; margin: 0 auto; color: #1a1a1a;">
  <p>Hi {{first_name}},</p>
  <p>This is the last email in this sequence — I don't want to fill your inbox. But before I go, two things:</p>
  <p><strong>1. Bonus if you book this week:</strong> I'll add a free <em>competitor AI teardown</em> — I audit how 2 of your competitors use AI and where they're exposed. Normally $500.</p>
  <p><strong>2. Refer & earn:</strong> whether or not you buy, earn 15% of any audit fee for every business you refer. Your link: <a href="{{site_url}}/?ref={{ref_code}}">{{site_url}}/?ref={{ref_code}}</a></p>
  <p>If the audit isn't right for you right now, no worries — the scorecard insights are yours to keep.</p>
  <p><a href="{{calcom_url}}" style="display: inline-block; padding: 12px 24px; background: #111; color: #fff; text-decoration: none; border-radius: 6px;">Reply "audit" or book here →</a></p>
  <p>— Dwad</p>
</div>

n8n WIRING (how to send these)

For each email, create a Resend HTTP Request node (or use the Resend node) with:

Supabase lookup node (top of branch) — SELECT * FROM contacts c JOIN scorecard_results s ON s.contact_id=c.id WHERE c.id = ? to populate merge tokens. Also check exit-rule suppression.
Set node — build the merge-token map (first_name, score, band, binding_constraint_1, ref_code).
Resend send node — paste the HTML/text from the relevant email above with {{token}} placeholders (n8n resolves them).
Supabase insert node — log to email_log.

For the delay between emails, use n8n Wait nodes (Schedule after interval) OR Resend’s scheduled send. Wait nodes are more visible/debuggable.

OPTIONAL: Make it a sequence in Resend Audiences

If you move off n8n-triggered sends and into Resend Audiences:

Create an Audience “AI Audit Nurture.”
Add a contact on scorecard completion (tag: scorecard_complete).
Build the 5 emails as a Resend Sequence with the delays above.
n8n then only needs to: upsert contact to Resend Audience + tag on scorecard completion. Resend handles the cadence.

This is the lighter-touch path once you’ve validated conversion.