Course 3 · Beginner $29 New in v2

Owned Audience and the Newsletter as Product

This is the course that answers the governing question directly. Search sends strangers once. A brief someone chose to receive brings the same person back fifty times a year — and it is the only distribution no platform can revoke.

  • 6 lessons
  • 6 labs
  • 6 artifacts
  • 1 scenario assessment
  • ≈5 hours
  • Prereq: Course 2
Your progress · 0/6 lessons0%

Overview

v1 treated email as a conversion tactic bolted onto a content site. v2 inverts it: the recurring dated brief is the product, and the site is the marketing that acquires readers for it. That inversion changes what you publish, what you measure and what a sponsor is buying.

Each Phase 1 site ships one weekly brief — the Weekly Cash Flow Brief, the Weekly Stack Brief and the Weekly SMB Security Brief. All three serve the same buyer, the small-business operator, which is why one research routine can feed three products.

LessonLabArtifact
3.1 List as productWrite the promise and return triggerBrief product definition
3.2 Recurring brief designDraft three complete issuesIssue template & calendar
3.3 Subscriber economicsModel cost per subscriber and paybackSubscriber economics sheet
3.4 AcquisitionBuild two magnets from displaced topicsAcquisition map
3.5 Deliverability & consentAuthenticate a domain, write consent flowDeliverability & consent record
3.6 SegmentationDefine segments and a sponsor one-pagerSegment map & sponsor kit

3.1 What is the owned-audience inversion?

What is it?

Treating the recurring email brief as the primary product with its own promise, format and retention metrics, and treating the website as the acquisition channel that feeds it — rather than the reverse.

Why it matters

Every other channel is rented. Rankings move, feeds re-weight, assistants summarise you without a link. A subscriber who opted in is the only audience relationship that survives all three. It is also the only asset that makes the governing question answerable with something other than "we rank well".

How to do it

  1. Write a one-sentence promise: who it is for, what arrives, how often, and what the reader can do afterwards that they could not before.
  2. Define the return trigger — the specific recurring thing that makes opening it non-optional. "Interesting links" is not a trigger. "The three rate changes that hit your payroll this week" is.
  3. Set a cadence you can hold for 52 weeks at your worst week, not your best. Weekly beats daily that dies in month two.
  4. Decide what the site now exists to do: acquire subscribers, and host the tools and data the brief references.
  5. Write the falsifiable version: "if the engaged ratio is below X at week 12, the promise is wrong." Carry it into the risk register.
Weak versus strong return triggers
Weak promiseStrong promise (return trigger)
"SMB finance news and tips""Every Tuesday: the rate, fee and lending changes that affect a 5–50 person business, and what to do this week"
"AI tool roundup""Every Thursday: what changed in the SMB software stack — pricing moves, deprecations, one tested workflow"
"Cybersecurity awareness""Every Monday: exploited vulnerabilities in tools SMBs actually run, with the patch status of each"

Tools needed

Your niche scorecard and audience value profiles from Course 2, plus the unit economics tool for the cadence cost.

Lab 3.1

Write the product definition for all three Phase 1 briefs: promise, return trigger, cadence, format, week-12 falsification threshold. Show each to one person from the audience and record whether they could restate the promise back to you.

Artifact

Brief product definition x3
  Promise (1 sentence) | Return trigger | Cadence | Sections
  Week-12 falsification threshold | Audience restatement test result

Common mistakes

  • Launching a newsletter that summarises your own blog posts. There is no reason to subscribe to something the site already gives away in full.
  • Choosing daily because it sounds committed, then missing week three.
  • A promise that is a topic ("finance") rather than a job ("know what changed and what to do about it").

Pro astuces

  • The best return triggers are dated and perishable. Anything an assistant can answer from static knowledge is a bad trigger; anything that changed this week is a good one.
  • If you cannot name the trigger, you do not have a product — and you should not build the signup form.
Not saved yet
Artifact: Brief product definition

3.2 How do you design a recurring dated brief?

What is it?

A fixed issue skeleton — the same sections in the same order every week — so production is fast, quality is consistent and readers know where to look.

Why it matters

Recurring dated assets are 20% of the v2 content ratio and carry a disproportionate share of retention. A fixed skeleton turns a creative act into an operational one, which is the only way a solo publisher holds a 52-week cadence across three sites.

How to do it

  1. Design five to seven fixed sections. Every section must have a named source routine — where the input comes from, every week, without inspiration.
  2. Time-box production. If an issue takes more than three hours, cut a section, not the cadence.
  3. Put one original element in every issue: your own count, test or table. That is what an assistant cannot regurgitate.
  4. Link out to the site's tools and data assets from inside the brief — the brief drives usage, usage drives ad revenue and sponsor value.
  5. Archive every issue as a permanent page. Archives are acquisition surfaces and dated proof of consistency.
Weekly SMB Security Brief — fixed skeleton
1. The one thing        (60 words: what to do this week)
2. Exploited this week  (source: vendor advisories, fixed list)
3. Patch status table   (ORIGINAL — your own tracking)
4. Tool/pricing changes (source: vendor changelogs)
5. Reader question      (source: inbox)
6. One number           (ORIGINAL — your dataset)
Production budget: 3 hours. Sections may be cut; the Monday send may not.

Image placeholder — issue skeleton diagram

Generation prompt: "Clean editorial diagram of a weekly email newsletter skeleton, six stacked labelled sections in a vertical column, two sections highlighted as 'original data', minimal flat design, muted teal and slate palette, generous white space, no text smaller than 12pt, 16:9."

Prefer a real screenshot? Steps to produce it
  1. Open your email tool's template editor and build the six-section skeleton with placeholder copy.
  2. Set the browser to 1440px wide at 100% zoom.
  3. Capture the full template at 2× device pixel ratio.
  4. Redact subscriber counts and client names before publishing, and note the capture date in the caption — Rule 1 applies to screenshots too.
A fixed skeleton is what makes 52 weeks survivable.

Tools needed

Any email platform, a shared source-routine document, and the content brief builder.

Lab 3.2

Draft three complete issues of one brief — not outlines, finished issues. Time yourself on the third. If it took more than three hours, cut a section and redraft.

Artifact

Issue template + 3 finished issues + 12-week editorial calendar
Each section annotated with its weekly source routine and time budget

Common mistakes

  • Redesigning the format every issue, destroying both speed and reader habit.
  • Sections with no source routine — they become the reason an issue slips.
  • No original element, making the brief a link roundup an assistant replicates instantly.

Pro astuces

  • Write issues one to three before you open a signup form. If you cannot produce three, you cannot produce fifty-two.
  • The "one number" section, tracked weekly, becomes your original dataset by month six — raw material for Course 10's digital PR.

Knowledge check (3 questions)

1. Why must every section have a source routine?

Because cadence fails at the section that requires inspiration. A named weekly input turns production into a repeatable operation rather than a creative gamble.

2. What do you cut when an issue overruns?

A section — never the send. Missing the date breaks the habit the whole product depends on; a shorter issue does not.

3. Why archive issues on the site?

Archives are acquisition surfaces, dated evidence of consistency for sponsors, and over time they accumulate into the original dataset behind your PR campaigns.

Self-score: Not scored yet
Not saved yet
Artifact: Issue template & calendar

3.3 What are subscriber unit economics?

What is it?

The cost to acquire one subscriber, the revenue that subscriber generates across advertising, affiliate and sponsorship, and the months until acquisition cost is repaid.

Why it matters

Course 0 modelled the site. This models the product. Without it, "grow the list" is a vanity goal — 20,000 unengaged subscribers can be worth less than 2,000 engaged ones while costing more to send to.

How to do it

  1. Count acquisition cost honestly: your hours at a real rate, plus magnet production, plus platform fees.
  2. Estimate revenue per engaged subscriber per month from three sources separately — never blend them, because Course 11's concentration limits apply per source.
  3. Define engaged before measuring it: opened at least one of the last four issues is a defensible line.
  4. Compute payback in months and compare against the 12-month cost model from Course 0.
  5. Model churn and list-cleaning cost. Sending to dead addresses damages deliverability and costs money.
Subscriber economics — structure (fill with YOUR figures)
  Acquisition cost per sub = (hours x rate + magnet cost + fees) / net new subs
  Monthly revenue per engaged sub = ad share + affiliate share + sponsor share
  Payback months = acquisition cost / monthly revenue per engaged sub
  Engaged ratio  = engaged subs / total subs      (define your own floor)
  Kill signal    = payback months > runway months remaining
No benchmark numbers are supplied here — deliberately

Any RPM, open-rate or CPM figure we printed would be a third-party claim subject to Rule 1's 90-day expiry, and it would be wrong for your niche anyway. Measure your own for eight weeks, then log each figure in the claim register with a source, an owner and an expiry date.

Tools needed

Unit economics tool, revenue & RPM calculator, your platform's engagement export.

Lab 3.3

Model subscriber economics for one brief across pessimistic, expected and optimistic scenarios. Identify the single input that most changes payback, then write down how you would measure it within 30 days.

Artifact

Subscriber economics sheet: 3 scenarios, sensitivity ranking, 30-day measurement plan

Common mistakes

  • Valuing your own hours at zero, which makes every channel look profitable and hides the real constraint.
  • Blending revenue sources into one number, concealing a concentration breach.
  • Measuring list size instead of engaged list size.

Pro astuces

  • Sponsorship is priced off engaged subscribers and audience quality, not raw count. Optimising for the raw number can actively lower revenue.
  • Run the sensitivity analysis before the growth push. Usually one input dominates, and it is rarely the one you were about to optimise.
Not saved yet
Artifact: Subscriber economics sheet

3.4 How do you acquire subscribers without paid spend?

What is it?

Converting the traffic and relationships you already have — including traffic to topics being displaced — into opt-ins, using assets valuable enough to justify an email address.

Why it matters

Course 2 produced a "displaced but valuable" list: topics with real commercial audiences whose answers assistants now give away. Those topics are poor articles and excellent lead magnets. This is where that list pays off.

How to do it

  1. Pick two displaced topics with high audience value and build each into a downloadable or interactive asset — a calculator, checklist, template or tracked dataset.
  2. Place the offer where intent is highest: inside the relevant tool, at the end of money pages, and in the brief's archive.
  3. Make the exchange explicit and honest: what arrives, how often, how to leave. Never obscure the unsubscribe.
  4. Use partnerships from Course 10 — co-produced data, cross-recommendations, community answers — rather than buying attention.
  5. Track conversion per placement, not per site. One placement usually produces most of the signups.
Displaced topics converted into lead magnets
Displaced topicPoor asStrong as
"What is a cash flow forecast?"1,500-word explainer13-week cash flow template with your worked example
"MFA vs 2FA"Definition postSMB rollout checklist with per-tool configuration notes
"SaaS pricing tiers explained"Generic guideTracked price-change dataset for 40 SMB tools

Tools needed

Your Course 2 displaced-topic list, the site's tool pages, and an email platform with per-form tracking.

Lab 3.4

Build two lead magnets from displaced topics and place each in three locations. After 14 days, rank placements by conversion and remove the worst performer entirely rather than trying to fix it.

Artifact

Acquisition map: 2 magnets x 3 placements, 14-day conversion by placement, one removal decision

Common mistakes

  • A generic "subscribe to our newsletter" box, which converts poorly because it promises nothing specific.
  • Gating something the reader can get free elsewhere in ten seconds.
  • Interstitials that damage Core Web Vitals and irritate the exact reader you want (see Course 5).

Pro astuces

  • The highest-converting placement is almost always inside a tool the reader is actively using, at the moment they have a result worth keeping.
  • Offer the archive itself as the magnet: "the last twelve issues, and the next one Tuesday" is concrete and honest.
Not saved yet
Artifact: Acquisition map

3.5 What are deliverability and consent hygiene?

What is it?

The technical and legal practices that get mail into inboxes and keep the list lawful: domain authentication, honest consent capture, easy unsubscribe, list hygiene and record-keeping.

Why it matters

A list you cannot deliver to is not an asset, and a list gathered without proper consent is a liability. Both failures are silent until they are catastrophic — and both sit in the risk register under platform and legal categories.

How to do it

  1. Authenticate your sending domain (SPF, DKIM, DMARC) before the first send and verify with your platform's diagnostics.
  2. Send from a subdomain dedicated to the brief so reputation damage is contained.
  3. Capture consent explicitly: unticked box, plain description of what you send, timestamp and source recorded per subscriber.
  4. Put one-click unsubscribe in every issue and honour it immediately. Never make removal a support ticket.
  5. Clean the list on a fixed schedule — sunset unengaged addresses rather than paying to email them.
  6. Take the jurisdiction question to counsel. Consent, records and disclosure requirements differ by market.
This is not legal advice

Email marketing law varies by jurisdiction and changes. Log every specific requirement you rely on in the counsel question sheet rather than acting on a summary from a course, an article or an assistant. Sponsored or affiliate content in a brief also brings the FTC endorsement and review guidance into scope — disclosure must be clear and conspicuous inside the email itself, not only on the website.

Tools needed

DNS access, your platform's authentication checker, an inbox-placement test, and the risk register.

Lab 3.5

Authenticate one sending subdomain end to end and document the records you created. Then write your consent flow as a numbered sequence and identify the exact point at which the reader is told the cadence.

Artifact

Deliverability & consent record
  Authentication records created (SPF/DKIM/DMARC) + verification date
  Consent flow (numbered) + where cadence is disclosed
  Sunset policy (trigger + frequency)
  Counsel questions raised (list)

Common mistakes

  • Sending from the root domain, so a deliverability problem contaminates all your mail.
  • Pre-ticked consent boxes, or bundling newsletter consent into an unrelated action.
  • Keeping unengaged subscribers for years because the total looks better.
  • Disclosing a sponsorship only in the website footer while the paid mention sits in the email.

Pro astuces

  • Record the acquisition source on every subscriber record. When a deliverability problem appears, source is usually the fastest explanation.
  • Run an inbox-placement test before any send larger than your usual volume — growth spikes are when reputation problems surface.
Not saved yet
Artifact: Deliverability & consent record

3.6 How do segmentation and sponsor readiness work?

What is it?

Dividing the list by attributes a sponsor would pay differently for, and packaging the evidence of audience quality into something a buyer can evaluate without trusting your adjectives.

Why it matters

Sponsorship is the revenue source least exposed to algorithm change, and it is priced on audience definition, not size. It is also capped at 25% from any single sponsor by the v2 concentration limits, so you need several — which means the kit has to be reusable.

How to do it

  1. Segment on attributes that change buying behaviour: company size, role, tool stack, stage. Collect them progressively, never in one hostile signup form.
  2. Measure engagement per segment. A small segment with high engagement is the sellable one.
  3. Build a sponsor one-pager: who the audience is, how they were acquired, engagement evidence, what a placement looks like, what you will not do.
  4. State your disclosure policy in the kit. Sponsors who object to clear labelling are a risk you decline early.
  5. Track sponsor share of revenue against the 25% ceiling from month one, not after you breach it.
Sponsor one-pager — required sections
1. Audience definition (role, company size, market) and how it was verified
2. Acquisition sources and consent basis
3. Engagement evidence (your measured figures, dated)
4. Placement formats, positions, production requirements
5. Editorial firewall: what sponsors cannot influence
6. Disclosure standard, quoted verbatim as readers see it
7. Concentration policy: no single sponsor above 25% of revenue

Tools needed

Email platform segmentation, the revenue calculator, and your advertiser disclosure page.

Lab 3.6

Define three segments with the evidence you would use to prove each, then write the sponsor one-pager. Have someone outside the project read it and tell you what the audience is — if they cannot, the definition is not specific enough.

Artifact

Segment map (3 segments, evidence per segment) + sponsor one-pager v1

Common mistakes

  • Segmenting on data you never collected, producing segments you cannot target.
  • Selling a placement you have not defined, then negotiating editorial control after the money arrives.
  • Letting one sponsor grow past a quarter of revenue because the relationship is easy.

Pro astuces

  • Publish the disclosure standard publicly before you have a single sponsor. It shortens the conversation and filters out the buyers who would have become a problem.
  • The strongest line in a sponsor kit is usually the one describing what you refuse to do.
Not saved yet
Artifact: Segment map & sponsor kit

Scenario assessment: the big list that is worth nothing

A publisher has 24,000 subscribers on the SMB finance site, acquired mostly through a free template shared widely in general small-business groups. The engaged ratio has fallen every month for five months. A sponsor offers a rate based on total list size, which would be 40% of next quarter's revenue. The platform bill scales with total subscribers, and the sunset policy has never been run.

Decide first, then open (5 questions)

1. Should the sponsorship be accepted as offered?

No, on two grounds. It would be 40% of revenue, breaching the 25% single-sponsor concentration limit; and it is priced on a number that misrepresents what the sponsor will actually reach. Selling on total size while engagement collapses ends the relationship and the reputation.

2. What is the root cause of the decline?

Acquisition–audience mismatch. The magnet was shared to a general small-business population, not the defined buyer, so most subscribers never had the recurring need the return trigger addresses. The list grew; the audience did not.

3. What is the first operational move?

Run the sunset policy and re-permission the list. This cuts platform cost, restores deliverability, and produces the honest engaged-subscriber figure any sponsor conversation must be based on.

4. How should the sponsorship be restructured?

Priced on the engaged segment, capped below 25% of revenue, with audience definition and engagement figures stated and dated in the kit. A smaller defensible deal now, plus a second sponsor sought to spread concentration.

5. What goes in the risk register?

Two entries. Revenue concentration: leading indicator "any single sponsor above 20% of trailing quarter revenue", trigger "pause new placements and open two replacement conversations". Audience quality: leading indicator "engaged ratio falling two consecutive months", trigger "freeze acquisition and re-test the return trigger".

Self-score: Not scored yet

Final project: one brief, three issues, one economic model

Ship a real product definition, prove you can produce it, then prove it can pay for itself.

Deliverable
1. Product definition for all 3 Phase 1 briefs (promise, trigger, cadence, falsification threshold)
2. Fixed issue skeleton with a named source routine per section
3. Three finished issues of one brief, the third one timed
4. Subscriber economics sheet: 3 scenarios + sensitivity ranking + 30-day measurement plan
5. Acquisition map: 2 lead magnets from displaced topics x 3 placements
6. Deliverability & consent record with counsel questions logged
7. Segment map and sponsor one-pager v1

Pass standard: someone in the target audience reads the promise and restates it correctly, and your economics sheet shows the one input that decides whether the product survives.

Course 3 checklist

0 complete

AI-agent prompt for Course 3

Owned-audience product strategist
Act as a newsletter product strategist for an independent publisher whose search traffic is being displaced by AI answers.

I will paste: my niche, my audience value profile, my displaced-topic list, and my weekly production budget in hours.

Do this:
1. Propose three candidate promises for a recurring dated brief. For each, state the return trigger and explain why an AI assistant cannot satisfy it from static knowledge.
2. Recommend one promise and justify the choice against the others.
3. Design a fixed issue skeleton of 5-7 sections. For every section name the specific weekly source routine and estimate production time. The total must fit my stated budget.
4. Identify which sections are ORIGINAL (my own count, test or dataset) and flag any skeleton where fewer than one section is original.
5. Convert my three highest-value displaced topics into lead magnets, and specify three placements each, ranked by expected intent.
6. Build the subscriber unit economics model as a formula sheet with named inputs. Do NOT invent benchmark values.
7. Draft a sponsor one-pager outline including the disclosure standard and a 25% single-sponsor concentration cap.

Rules:
- Do not state open rates, RPMs, CPMs or deliverability thresholds as facts. Output every such figure as a claim row: claim, why it matters, primary source needed, owner, 90-day expiry.
- Do not give legal advice on consent or email marketing law. Output those as counsel questions with the jurisdiction left for me to fill in.
- Prefer perishable, dated content over evergreen explainers in every recommendation.
- If my production budget cannot sustain the cadence, say so explicitly and propose a smaller cadence rather than a smaller quality bar.
Output as tables.

Primary sources

Verify every platform-specific requirement against the provider's own current documentation. Under Rule 1, any claim taken from these sources expires 90 days after the date you recorded it.