AI Email Automation Blueprint For E-Commerce
A beginner-to-expert course that builds your store's complete email programme with AI from your own data: consent and sending, six ...
Show more
Instructor
David Tainsh
Course details
Lectures
:
24
Level
:
Beginner
- Description
- Curriculum
- Reviews
Course · For e-commerce stores and drop shippers
Turn the customers you already paid for into repeat sales, with AI-built email.
Six automated flows that sell while you work, a campaign plan worth sending, and a scorecard that shows which emails make you money. All of it built with AI from your own store’s data, whether you ship from your own shelves or from a supplier.
- Six flows that sellWelcome, abandoned cart, post-purchase, VIP, win-back and re-permission, every email written and timed.
- Emails that landYour sending domain checked against Gmail’s rules, and a list you are allowed to email.
- Orders you can countA four-weekly scorecard of orders and profit by flow and campaign. Not open rates.
Who this is for
Online stores with a customer list that is not selling.
This assumes you have customers, or are about to. The question is whether they ever hear from you again after the first order, and whether what they hear makes them buy.
- 01Store owners who hold their own stock
A Shopify or WooCommerce store with hundreds or thousands of past customers, and an email platform sending one newsletter now and then.
- 02Drop shippers
No stock, a supplier’s delivery times and thin margins. Every email quotes your real delivery times and every offer is costed against your margin first.
- 03Stores about to launch
No customers yet. You build the whole programme on the example store that ships with the course, then switch it on for your first sign-ups.
- 04Anyone who tried AI for email and stopped
A few AI-written emails that sounded like everyone else’s. Here every email is written from your own customers, products and reviews.
- 05Freelancers and agencies
Building email for a client’s store. The finished programme is one file you can hand over, with every open decision listed.
You do not need Klaviyo, a copywriter, a designer or technical skills. You need a customer export, an email platform and Claude.
What you walk away with
A complete email programme, ready to set up.
Built from your own store’s data rather than from templates, and assembled into one programme you can build in any email platform.
- Abandoned cart emails that answer the question that stopped the sale
- A welcome series that turns new subscribers into first orders
- Post-purchase and reorder emails that bring the second order
- Win-back emails for customers who have gone quiet
- A consent register: who you may email and text, and why
- A sending domain set up to Gmail’s rules, so you reach the inbox
- A campaign calendar, with what one campaign is worth worked out first
- A scorecard of orders and profit by flow and by campaign
Plus 22 single-build prompts for anything else you need: a monthly newsletter, an onboarding flow, browse abandonment, back in stock, a launch, a sale or a gift season.
Why the list never sells
You paid to win every customer. Most never hear from you again.
Nothing breaks, so nothing gets fixed. The list sits there while you pay for the next customer. Four things keep a store’s email from selling.
- ×The flows were never built
Someone adds to cart and leaves. A first-time buyer gets an order confirmation and nothing else. The emails that sell at the moment a customer decides do not exist.
- ×Everyone gets the same email
Your best customers, your new ones and the ones who left a year ago all receive one newsletter, so it is written for none of them.
- ×The discount does the work
A code in the first cart email teaches customers to wait for one. On a thin margin, it costs more than the sale makes.
- ×Open rates hide the answer
Opens are inflated by mail apps that open every email. You cannot tell which emails produce orders, so you cannot tell what to send more of.
None of this needs more emails. It needs the right ones, sent to the right customers, at the moment they decide.
The trap
A template is not your email programme.
“Hey, you left something behind!” “Here’s 10% off your first order.” “We miss you!” Template emails are written for every store, which means they are true for none.
A template pack
- Delivery times that are not yours
- Invented reviews and generic claims
- A discount wherever there is a gap
- Sent to everyone on the list
- Judged on open rates
Your programme
- Your delivery times, quoted from your own policy
- Your customers’ real reviews, word for word
- Every offer costed against your margin first
- Sent to the customers you may email, by segment
- Judged on orders and profit
The through-line
AI writes the emails. The facts have to be yours.
Claude can segment, write, time and check. What it cannot do is know your delivery times, your margins or what your customers actually say, so every lesson gives it your files first.
- 1You set up one Claude Project
Six files about your store: profile, catalogue, customers, reviews, policies and brand voice, built from exports you already have.
- 2The prompts build from them
Every lesson reads those files and saves one more, so the welcome series knows your offer and the cart emails know your delivery times.
- 3Nothing is guessed
Where a file does not hold a fact, the prompt says “not known” rather than inventing one. No made-up reviews, no promised delivery speed you cannot meet.
One master prompt then assembles every file into your complete email programme, with every open decision listed once.
The framework
Six flows, each sent at the moment a customer decides.
Each one has one trigger, one audience and one job. One email a day per customer, across all six, so no one is buried.
- 1Welcome
Four emails in a new subscriber’s first week, delivering the offer they signed up for and turning them into a first order.
- 2Abandoned cart
Four emails over two days. Each answers the question that stopped the order, and no discount appears before the fourth.
- 3Post-purchase and reorder
How to use it, the one thing that goes with it, a reorder reminder timed to when it runs out, and a review request to every buyer.
- 4VIP
Recognition for your best customers that does not give your margin away.
- 5Win-back
Four emails for customers who have stopped buying, with a clear point at which you stop.
- 6Re-permission
One email that asks quiet subscribers whether to keep writing, so the rest of your emails keep reaching the inbox.
Cart and post-purchase emails quote your own delivery and returns policy, which is what makes them work for drop shipping as well as stock you hold.
What’s included
Every lesson comes with the prompts that build it.
The lessons are short. The work happens in the SOP and AI Prompts PDF — numbered steps, the full prompts in order, and what a good output looks like so you know when to run one again.
- SOPA step table in every pack
Numbered steps from your export to a saved file. Work down it and the lesson’s part of the programme is built.
- AI75 prompts, in plain English
Copy and paste into Claude. Square brackets mark the few things only you can supply.
- QAWhat good looks like
A concrete standard for every prompt, so you can tell a usable email from a plausible one.
- DEMOAn example store to practise on
A complete store with a catalogue, 600 customers, reviews and policies, so you can do every lesson before your own data is ready.
How the course runs
Four sections, each finished with a live build.
18 lessons and 6 live builds, about 2 hours 45 minutes of video. At the end of each section the prompts are run end to end on camera, so you see every file produced before you produce yours.
Set-up
Your Claude store Project
One lesson: the Project, its instructions and the six files about your store.
Section 1
Consent, sending and segments
Who you may email and text, your sending domain, the four customer segments and a list growth plan. Then a live build.
Section 2
The six email flows
The flow map, then welcome, abandoned cart, post-purchase and VIP, win-back and re-permission. Then a live build.
Section 3
Copy, design, campaigns and measurement
Copy from your customers’ words, a phone-ready template, a campaign calendar, subject lines and a scorecard. Then a live build.
Section 4
Assemble, maintain and build
The Master Email Engine, modular updates, and 22 single builds. Then three live builds, one for each lesson.
The live builds
Follow along step by step, and finish with the same result.
At the end of each section, every prompt is run start to finish on screen, in order. Pause, run the same step on your own store, and carry on. When the video ends, that part of your email programme is built.
Watch
Every step on screen
- Each prompt run in order, nothing skipped
- What to paste, and where
- What a good output looks like
Follow
Your store, alongside
- Pause after each step and run it yourself
- The same prompts, from your SOP PDF
- Each file saved before the next step reads it
Finish
The section, built
- Section 1: who you may email, inbox-ready sending
- Section 2: all six flows, written and timed
- Sections 3 and 4: campaigns, scorecard, full programme
Six live builds in all: one at the end of Sections 1, 2 and 3, and one for each lesson in Section 4.
Is it for you
Store owners who want email that sells, built on their own data.
A good fit
- You run, or are launching, a store or a drop shipping store
- You can export your customers and products as a CSV
- You use, or will use, an email platform that runs flows
- You want orders and profit, not open rates
- You will read what the AI writes before you send it
Not a fit
- You want templates to paste in unchanged
- You want a promised revenue figure
- You want to email people who never agreed to it
- You want a discount in every email
- You have no plan to use an email platform
What it costs
One payment, and the programme is yours.
$28.95
One payment. Lifetime access, including every update.
18 lessons · 6 live builds · 75 prompts · SOP and prompt PDFs · example store
30-day guarantee, no questions asked. Run the prompts. If you do not finish holding a complete email programme built from your own store’s data, ask for your money back.
Quick answers
The questions people ask before starting.
Does this work for drop shipping?
Yes. The emails quote your own delivery times and policies, product picks come from your catalogue whether or not you hold the stock, and every offer is costed against your margin.
Do I need Klaviyo?
No. Any email platform that runs automated flows and exports customers with their consent status will do: Klaviyo, Omnisend, Mailchimp, Shopify Email or another.
Will it work for my niche?
Yes, because nothing in it is a template. Every prompt reads your own catalogue, customers and policies. The example store sells coffee, and no lesson assumes what you sell.
Do I need copywriting or technical skills?
No. You need to export a customer list and follow numbered steps. Every lesson gives you the prompts in full, and Claude writes the emails from your files.
Which AI does it use?
Claude, with a Project holding your store’s files. The first lesson sets it up.
What if I have no customers yet?
Build the whole programme on the example store that ships with the course, then run it again on your own data when you have it.
How long is the course?
18 lessons and 6 live builds, about 2 hours 45 minutes of video in total. Lifetime access, including every update.
What exactly do I get?
18 video lessons, 6 live builds, an SOP and AI Prompts PDF for every lesson with 75 prompts in all, an example store to practise on, and a business invoice.
Sell again to the customers you already have.
Six automated flows, a campaign plan and a scorecard, built with AI from your own store’s data — for stores that hold stock and for drop shippers.
A Digital Plan · adigitalplan.com
Section 1 — Consent, Sending and Segments
-
2
1.1 — Who You May Email and Text: Consent and the Soft Opt-InThe two ways a UK or EU store may send marketing email, the six soft opt-in conditions, and how to read the consent columns in your customer export. You write a consent register giving every customer one email status and one SMS status, with the reason for each.
You finish with:
consent-register.md -
3
1.2 — How to Set Up Your Sending Domain in 5 Checks
SPF, DKIM, DMARC, one-click unsubscribe and complaint rate: what Gmail requires of senders, and how to confirm each one from a single test email. You record your setup and the exact number of spam complaints that puts your list at risk.
You finish with:
sender-setup.md -
4
1.3 — The 4 Customer Segments Every Flow Uses
VIP, Dormant, New and Active, the rule behind each, and the order they are applied in. You count your segments with code on a dated export, and see how many in each you may email and text.
You finish with:
segments.mdNorthmill is a UK shop, so the video and SOP show these figures in £. Your own will be in your currency.
-
5
1.4 — How to Grow Your List with Sign-Up Forms and Lead Magnets
The five kinds of sign-up offer, what each costs you per first order, where to place a form on each page type, and how to word it so every sign-up arrives with consent. You write a list plan for your store.
You finish with:
list-growth.mdNorthmill is a UK shop, so the video and SOP show these figures in £. Your own will be in your currency.
-
6
Live build: Section 1
Consent register, sending domain checks, segment counts and list plan, built in one conversation from the customer export and policies.
You finish with:
consent-register.md,sender-setup.md,segments.mdandlist-growth.mdNorthmill is a UK shop, so the video and SOPs show these figures in £. Your own will be in your currency.
Section 2 — The Six Email Flows
-
7
2.1 — The 6 Email Flows and What Triggers Each One
Welcome, abandoned cart, post-purchase, win-back, VIP and re-permission: the one trigger that starts each, who each can reach, and what happens when a customer qualifies for two on the same day. You map your six flows under a one-email-a-day limit.
You finish with:
flow-map.md -
8
2.2 — How to Write a Welcome Series
The four emails a new sign-up receives in their first week, the one job each does, and how to use real reviews in them. You write your welcome series, ending on a first order or after seven days.
You finish with:
welcome-series.mdNorthmill is a UK shop, so the video and SOP show these figures in £. Your own will be in your currency.
-
9
2.3 — How to Write Abandoned Cart Emails in 4 Steps
The four emails after an unfinished checkout, at 30 minutes, 3 hours, 24 hours and 48 hours, the question each one answers, and why no discount appears before the fourth. You write your cart flow with every policy line in your policy’s own words.
You finish with:
cart-recovery.mdNorthmill is a UK shop, so the video and SOP show these figures in £. Your own will be in your currency.
-
10
2.4 — How to Write Post-Purchase, Reorder and VIP Emails
The emails that follow an order: how to use it, one product that goes with it, a reorder reminder timed to how long it lasts, a review request to every buyer, and the VIP welcome. You write your post-purchase flow and VIP email.
You finish with:
post-purchase.md -
11
2.5 — How to Win Back Lapsed Customers and Re-Permission Your List
The four win-back emails for customers who have stopped buying, the one email that asks quiet subscribers whether to keep writing, and when to stop sending. You write both flows and the rule for suppressing addresses.
You finish with:
winback.md -
12
Live build: Section 2
All six flows written in one conversation, from the flow map through welcome, cart, post-purchase and VIP to win-back and re-permission.
You finish with:
flow-map.md,welcome-series.md,cart-recovery.md,post-purchase.mdandwinback.mdNorthmill is a UK shop, so the video and SOPs show these figures in £. Your own will be in your currency.
Section 3 — Copy, Design, Campaigns and Measurement
-
13
3.1 — How to Write Email Copy from Your Customers’ Own Words
The five parts of an email, five kinds of opening line taken from what customers say, and a source tag on every sentence. You write the copy rules every email in your programme is checked against.
You finish with:
copy-rules.md -
14
3.2 — How to Design an Email That Reads Well on a Phone
One template for every email, and the six checks it passes on a real phone, in dark mode and with images switched off. You check your template and record the results.
You finish with:
email-design.md -
15
3.3 — How to Plan Your Campaign Calendar and How Often to Send
What one campaign is worth to your store, the four kinds of campaign in a month, and how often to send to whom, based on who clicks. You plan four weeks of campaigns.
You finish with:
send-plan.mdNorthmill is a UK shop, so the video and SOP show these figures in £. Your own will be in your currency.
-
16
3.4 — How to Write Subject Lines, and When a Test Is Worth Running
How to write a subject line and preview from what is in the email, five kinds that come from your customers, and how to work out whether your list is big enough to test them. You set your subject line rules and start a log.
You finish with:
subject-lines.md -
17
3.5 — How to Measure Your Email with Counts, Not Rates
The six counts to record for every flow and campaign every four weeks, how your platform decides which orders count, and when to read the orders themselves. You fill your first scorecard.
You finish with:
email-scorecard.mdNorthmill is a UK shop, so the video and SOP show these figures in £. Your own will be in your currency.
-
18
Live build: Section 3
Copy rules, template checks, the campaign plan, subject lines and the scorecard, built in one conversation, with a test send on screen.
You finish with:
copy-rules.md,email-design.md,send-plan.md,subject-lines.mdandemail-scorecard.mdNorthmill is a UK shop, so the video and SOPs show these figures in £. Your own will be in your currency.
Section 4a — Assemble and Maintain Your Programme
-
19
4.1 — How to Assemble Your Email Programme with the Master Email Engine
One prompt reads the fourteen files this course produced, checks them against each other, and assembles your complete email programme, with every open decision listed once. You run the engine and close your first open item.
You finish with:
email-programme.md -
20
4.2 — How to Update One Flow with Modular Prompts
How to change one part of your programme, a decision, a policy or a flow, by finding every file it touches, re-running only those lessons, and recording the change. You make one change and log it.
You finish with:
change-log.mdNorthmill is a UK shop, so the video and SOP show these figures in £. Your own will be in your currency.
-
21
4.3 — How to Build One Email or Flow at a Time with 22 Build Prompts
How to build a single piece of your programme on its own from your Project’s files: a newsletter, an onboarding flow, a launch, a sale, a back-in-stock alert, a failed-payment email and sixteen more. Every build starts with a brief that checks its files and audience, and ends with a check that adds it to the programme and the change log. You also learn which builds are marketing and need consent, and which are service emails that may not promote. You build one piece and add it.
You finish with: one file per build, such as
newsletter.md, and an entry inchange-log.md
Section 4b — Live Build
-
22
Live build: Section 4, part 1
Lesson 4.1's prompts run live on the example store. The Master Email Engine reads all fourteen course files, checks them against each other and assembles the email programme, with every open decision listed once. The follow-up prompt then closes one open item through its source file, and the quarterly rebuild prompt is run on a fresh set of readings.
You finish with:
email-programme.mdNorthmill is a UK shop, so the video and SOP show these figures in £. Your own will be in your currency.
-
23
Live build: Section 4, part 2
Lesson 4.2's three modular prompts run live on one change: a decision on the welcome offer. Prompt 01 finds the source file and the one other file that reads it, the lesson prompts are re-run in lesson order with every line marked added, changed, removed or kept, and prompt 03 updates only the two programme sections affected and writes the change log entry.
You finish with: an updated
email-programme.mdand an entry inchange-log.mdNorthmill is a UK shop, so the video and SOP show these figures in £. Your own will be in your currency.
-
24
Live build: Section 4, part 3
Lesson 4.3's single builds run live: a monthly newsletter, an onboarding flow for new subscribers, a preference survey and one SMS message. Each one starts with the build brief and ends with the check that adds it to the programme and the change log. The SMS build stops at the brief, because too few customers have said yes to texts.
You finish with: one file per build, such as
newsletter.md, and an entry inchange-log.mdfor each
Stars 5
4
Stars 4
0
Stars 3
0
Stars 2
0
Stars 1
0