Field Notes

Vol. 04 · 2026The campaign annual of Jordan Green

Field Notes−2+1−1

Five campaigns from a year of growth marketing and AI operations — printed, proofed, and marked up in red pencil. The pretty pages are the creative work. The red marks are the machinery that made it perform.

Printed campaign proof sheets fanned across a white studio desk with a red editing pencil resting on top
Plate № 1Proofs, first pass

Letter from the editor

Marketing has two portfolios. You usually only get shown one.

There's the case-study version — the campaign at its best angle, the up-and-to-the-right chart, the tasteful mockup. And there's the version that actually happened: the segmentation query, the prompt with twelve graded examples stapled to it, the kill rule that quietly saved the budget. Most portfolios print the first and bury the second. This annual prints both, on the same page.

I'm Jordan Green. For nine years I've run growth for DTC and B2B companies — first as the person writing the emails, then as the person building the systems that decide which emails get written. These days I sit deliberately on the seam: half creative direction, half operations engineering. I write subject lines and I write SQL, and I think refusing to choose is the whole job now.

What follows are five campaigns from the last year. Read them clean and they're a creative portfolio. Flip on “Show the machinery” and an editor's red pencil marks up every page with the stack, the queries, the experiment design, and the honest caveats. The annotations aren't decoration — they're the technical résumé.

Everything here is real work, real numbers, measured the boring way: holdouts, pre-registered rules, one source of truth. Where a number deserves an asterisk, the red pencil gives it one.

— Jordan
Editor, sole staff writer, and the person on call when the pipeline breaks

DTC skincare · Lifecycle email

The second order is the business

A skincare brand with beautiful acquisition and a leaky bucket: 71% of customers never came back. We rebuilt the entire lifecycle program — nine flows, a real segmentation model, and a sunset policy with teeth.

+38%Repeat purchase rate
41%Email revenue from flows, up from 18%
9Flows rebuilt from scratch

The old program was one welcome email and a weekly blast to everyone. The new one treats the file like a garden: every subscriber sits in an RFM segment recomputed nightly, and every flow — welcome, replenishment, post-purchase education, winback — speaks to where that person actually is, not where the calendar is.

The unglamorous hero was the replenishment flow. Skincare runs out on a schedule; we computed each SKU's median days-to-depletion from order history and timed the nudge to land a few days before the jar does. It reads like thoughtfulness. It's arithmetic.

And we shrank the list on purpose. A 120-day sunset policy moved disengaged profiles through a three-touch winback and then suppressed them. The file got 22% smaller, deliverability recovered, and — the circled number above — repeat purchase rate rose 38%. Smaller, warmer, richer.

A hand marks up a printed email flow proof with a red pencil
Fig. 1 — flow logic, proofed on paper before it touched Klaviyo

B2B fintech · AI operations

Nobody reads 4,200 leads a month

Sales was cherry-picking by company name and ignoring the rest. We built an AI scoring pipeline — n8n orchestration, Claude as the grader — that reads every single lead, scores it against a rubric, and routes it with its reasoning attached.

4,200Leads scored monthly
+22%More SQLs, same traffic
90 secForm-fill to routed lead, was next-day
Form / webhookEnrichment Claude · rubricScore → CRM route every source, one doorfirmographic + intent graded 0–100rationale attached n8n · 14 nodes · retries + dead-letter queue temp 0 · 9-criteria rubric · 12 graded examples in-prompt ≥70 → AE · 40–69 → nurture · <40 → archive
Fig. 2 — the pipeline, as printed schematic

The rubric is the product. Nine weighted criteria — firmographic fit, use-case language, buying-stage signals — written with the sales team in a two-hour argument that was worth more than any model tuning. Claude applies it identically to lead number one and lead number four thousand, at two in the morning, without getting bored.

Trust was the real deliverable. Reps don't follow a number; they follow a number with a paragraph of reasoning they can check. Within a quarter, "the score" went from a marketing curiosity to how the pipeline meeting starts — and SQL volume rose 22% with zero new traffic.

B2B SaaS · Content engine

Ninety posts a quarter, zero slop

A content operation that publishes like a newsroom: AI drafts from data-driven briefs, human editors own every word that ships, and the publish button never belongs to a machine.

90Posts per quarter
3.1×Organic traffic in three quarters
2Human editors. Non-negotiable.

Briefs come from clustering, not vibes. We pull every query the site already ranks 5–25 for, cluster them by intent, and let the gaps write the editorial calendar. Each brief carries the target cluster, the angle, the internal links to earn, and the one question the post must answer better than anyone.

Then the assembly line with a human at every gate: AI produces a structured first draft from the brief; an editor reworks it — cuts the hedging, adds the opinion, checks every claim; a subject-matter reviewer signs off. Average human time per post is 24 minutes, which is the entire economics of the engine.

Three quarters in, organic sessions were up 3.1× and — the number I watch harder — signups attributed to content up 2.4×. Slop compounds in the wrong direction; edited work compounds in the right one.

Over-the-shoulder view of printed content-cluster charts being pinned to a white wall board above a studio desk
Fig. 3 — the quarter's clusters, on the wall where the whole team argues with them

Consumer subscription · Paid social

214 variants walk into an auction

Creative testing that behaves like an experiment instead of a mood board: a hook × format × proof matrix, pre-registered kill rules, and a naming convention strict enough to be a database.

214Ad variants in 12 weeks
−27%Blended CAC
6Concepts that earned scale

Fig. 4 — one testing wave, 40 of 214 variants. Red strikes = killed by rule, blue = scaled.

H1F1
H1F2
H1F3
H2F1
H2F2
H2F3
H3F1
H3F2
H3F3
H4F1
H4F2
H4F3
H5F1
H5F2
H5F3
H6F1
H6F2
H6F3
H7F1
H7F2
H7F3
H8F1
H8F2
H8F3
H9F1
H9F2
H9F3
HAF1
HAF2
HAF3
HBF1
HBF2
HBF3
HCF1
HCF2
HCF3
HDF1
HDF2
HDF3
HEF1

The matrix does the creative directing: twelve hooks — price anchor, social proof, founder story, contrarian claim — crossed with formats and proof devices. Every variant exists to answer a question, and the question is in its name. H07-F2-P3_v1 isn't a filename. It's a row in a results table.

Kill rules were written down before launch, so no one's favorite ad got mercy: dead at 2,000 impressions if CPA ran past 2× target, no exceptions, no "let's give it the weekend." Losers died in days, the six winning concepts took the budget, and blended CAC fell 27% over the quarter.

Marketplace · Marketing ops

One number everyone believes

Six channels, five dashboards, three versions of "what's our CAC?" in every meeting. We built the warehouse and the attribution model that ended the argument — one source of truth the CFO and the media buyer both sign.

6Channels, one model
1Source of truth
6h → 20mWeekly reporting, now mostly automated
$96$72$48 FebAprJunAug last-click modeled when the two lines disagree, we say so out loud
Fig. 5 — blended CAC, eight months, both honesties shown

The plumbing is deliberately boring: managed connectors land every channel's spend and every product event in the warehouse; a versioned, tested transform layer turns it into marts anyone can query; the dashboard on top is thin because the truth lives below it.

Attribution is where ops work becomes trust work. We run a position-based model as the baseline and a Markov removal-effect model as its skeptic; when they agree, decisions are easy, and when they diverge the divergence itself is reported. No single number pretends to be more certain than it is — which, it turns out, is exactly why people finally believe it.

Colophon

Set in type & SQL

Every annual ends with a colophon — the page that admits how the thing was made. This is mine: the standing toolkit behind the five campaigns, grouped the way it actually gets used.

Data & warehouse

  • BigQuery home of truth
  • dbt transforms, tested
  • Fivetran ingestion
  • Hex analysis & dashboards

AI & automation

  • Claude API scoring, drafting
  • n8n orchestration
  • Embeddings query clustering
  • Evals before anything ships

Channels & CRM

  • Klaviyo lifecycle email
  • HubSpot CRM & routing
  • Meta / Google paid, on a leash
  • Customer.io product messaging

Craft

  • Figma creative & specs
  • SQL the second language
  • Search Console raw organic signal
  • A red pencil quality control

This annual is hand-set in Fraunces (display, optical sizes 9–144) and Archivo (text), with annotations in Caveat — built as a single HTML page, no framework, no tracking. psst — press G to see the baseline grid it's set on.

Notes from the field

Jordan is the only marketer I've worked with who can argue with the data engineer and the designer in the same meeting — and be right in both rooms.

VP of Growth · DTC skincare brand, № 01

The scoring pipeline paid for itself inside a month. For the first time, sales actually trusts a number marketing produced.

Head of Sales · B2B fintech, № 02

Half agency brain, half ops brain. We hired Jordan and quietly stopped needing three vendors.

Founder · Consumer subscription, № 04

Correspondence

Put your campaign in the next annual.

I take two engagements per quarter — growth programs that need the creative and the machinery built by the same person. If that sounds like your next twelve months, write to me.