Module 7: Portfolio and Proof
Clients and employers can't watch you work, so they judge the evidence you put in front of them. With no client list yet, you build that evidence deliberately: a complete spec program for a sample brand, teardowns that show how you think in public, and a case-study habit that turns every piece of work — spec or paid — into proof.
A spec program: full flows and campaigns for a sample brand
A spec program is a complete piece of work you build on your own initiative for a sample brand, to show a stranger exactly what hiring you produces. It exists because of how this trade hires: a brand owner or an agency lead will believe one finished welcome flow over any amount of "I'm passionate about email." Your spec program is the thing you'll attach to pitches and applications for the next year, so build it like a deliverable, not a school project.
The program has two halves. First, the flows from Module 3, written in full: a welcome flow (every email, not just the first), browse and cart abandonment, post-purchase, and a winback — each shown twice, as a simple map with triggers and timing, and as the finished emails themselves. Second, three campaigns: one promotional, one content newsletter, one built for a launch or a season. Write the actual copy and lay out the design. A reviewer should be able to judge your copy, your structure, and your judgment in about ten minutes.
Choose the sample brand with intent. Pick a business type in the niche you leaned toward in Module 0 — a mid-size skincare brand, a coffee subscription, a local services company with an online booking flow — realistic in size and price, not a giant everyone knows. Invent a plausible brand or work from a real business's public emails, but keep the audience, products, and price points believable, because reviewers can smell a fantasy brief. Every decision in the program should trace back to that brand's reality.
And label it. Every document, every page: "Spec / concept work — built to demonstrate approach, not for a client." That label is not a weakness; it's what makes the rest believable. The same rule runs through this whole module: never present spec work as client work, never attach results you didn't produce, never imply a brand endorsed you when they didn't. The checklist below is your build order — when every box is ticked, you have a portfolio.
A prospect looks at your spec program and asks, "So which of these brands actually hired you?" What's the right answer?
Teardowns as public proof
A teardown is a public breakdown of a real email: what it's trying to do, what's working, what you'd change and why. Published on your LinkedIn, a simple portfolio page, or a small newsletter of your own, teardowns do something a portfolio alone can't — they show your judgment in motion, in public, on a schedule. A brand owner who has read three of your teardowns already knows how you'll look at their program before you ever pitch them.
Work from emails that land in your own inbox as a subscriber; that's a fair and endless supply. Structure each teardown the same way: the email's job in one line, the subject line and preview text, the structure and the single call to action (or the lack of one — Module 5), then two things done well and two changes you'd make, each tied to a reason from this course. "The cart email arrives six hours after abandonment; the product is a $24 consumable people buy on impulse — I'd test it at one hour" is a professional observation. "The design feels dated" is not.
Keep it clean. Critique the work, never mock the brand — the people who run that program may be your next employer, and the industry is smaller than it looks. Remove anything personal that arrives in an email (names, order details) before you screenshot it. And never, under any circumstances, tear down a client's emails or share anything from an account you were given access to. Your teardowns run on public, received-as-a-subscriber material only.
Do one a week. It's a small cadence with a compounding effect: twelve teardowns is a body of work, a search trail for your name, and — quietly — the best interview preparation there is, because you've been practicing the exact skill interviews test. The worksheet below turns one teardown into the other proof format this module builds: a case study, ready for when the work is yours.
Your turn: Build a case study from your spec program or a teardown. Write the Problem (what the brand's email was doing — or failing to do — when you looked), the Choices (the flows, campaigns, or changes you built or would make, and why), and the Result. For paid work, use real numbers (revenue, revenue per recipient, list health). For spec work, write the outcome you'd expect and the exact metrics you'd watch to prove it — and label that section "projected."
Saved.
You have two teardown drafts. Draft A lists six design nitpicks about a brand's welcome email. Draft B points out the brand has no post-purchase flow at all, and walks through the revenue logic of adding one. Which do you publish?
The case-study habit: problem, choices, result
A portfolio shows what you can make. A case study shows what your work did — and it's the format every serious client and hiring manager scans for. Three blocks, in this order, every time: Problem (where the program stood, with numbers), Choices (what you built or changed, and why those things first), Result (what the numbers did afterward). One page. No adjectives doing the work that numbers should do.
The habit that makes case studies possible starts before the work does: capture the baseline. Before you change anything on any program — a client's, or your own spec brand's inbox research — record the starting state: which flows exist, what each earns per recipient, list size and health, campaign rhythm. Screenshots and a dated note are enough. Without a baseline, every result is a claim; with one, it's arithmetic. Professionals take the "before" picture automatically, the way builders photograph a wall before they open it.
Honesty rules, same as the rest of this module. Small real numbers beat big vague ones — a welcome flow going from $0.11 to $0.19 per recipient is a result a good reviewer respects, because they know exactly what it takes. If the work was spec, the result section says what you'd expect and what you'd measure, labeled projected, the way the worksheet in the last lesson had you write it. Never round a projection into a fact. Your credibility compounds slower than your claims do, and it's worth more.
Build the file as you go: one case study from your spec program now, then one from your first trial or client engagement, then one per quarter after that. They feed everything downstream — proposals in Module 8 quote them, applications in Module 10 lead with them, and rate raises get easier to justify when the results are already written down. The marketer who can say, in numbers, what their last three projects did is playing a different game from the one still saying "I'm passionate about email."
Two case studies land in front of a brand owner. A: "I transformed the email program and significantly boosted engagement across all flows." B: "Problem: no welcome flow, cart emails at 24 hours. Choices: built a 3-email welcome flow, moved cart send to 1 hour, added post-purchase. Result in 60 days: welcome flow $0.21 per recipient, email at 31% of store revenue." Who gets the call?
What you can now do
- Build a spec program like a deliverable, not a school project: the full flow stack written in finished copy and layout, three completed campaigns, every piece labeled spec — the asset you attach to pitches and applications all year.
- Publish teardowns of real emails from your own inbox — the email's job, what's working, what you'd change and why — so brand owners can watch your judgment in public before you ever pitch them.
- Keep the case-study habit with the baseline captured before you change anything: the problem with numbers, your choices and why those first, and the result — one page, no adjectives doing the work numbers should do.