AGENT ACTIVE · COMPOUNDING SINCE AUG 2024 · 1,247 LESSONS
A lone Australian eucalyptus tree silhouetted against a vast sky transitioning from warm sunset orange to deep indigo and stars
▸ About · One operator · Since Aug 2024

I built a marketing studio that runs from a terminal.

One human, one model. Twenty months of compounding. No plugins, no SaaS sprawl, no agency overhead — just a system that gets sharper every day.

Get on the stackRead the story
20mo
Shipping AI-native since Aug 2024
1,247+
Lessons compounded across every project
0SaaS
Built every layer in-house
A bright wildflower blooming in a sun-bleached drying field
▸ The thesis

Marketing, built like software.
Versioned. Observable. Owned.

▸ Why this practice exists

I spent seven years inside marketing agencies that worked the way agencies have always worked: standups, slides, status reports, six people in a meeting because nobody trusted one person to ship. The work got done. It also got slower, blander, and more expensive every year.

Then Anthropic shipped Claude 3.5 Sonnet, and the math broke.

In August 2024 I built and shipped a production marketing system end-to-end on AI for the first time. Schema, routes, ads pipeline, conversion tracking, deploy — all of it. Twenty months later I haven't built anything any other way.

What I have now is a stack I built specifically for marketing work. Not Claude. Not Cursor. A studio. My own agent harness. My own skill library — 47 codified workflows for everything from Google Ads bulk-edits to GA4 conversion debugging. My own memory system — 1,247 lessons compounded across every project, persistent across every session.

It's all native. All in the terminal. No plugins, no SaaS sprawl, no UI layer between me and the model. You will not find another marketing operator with this stack — because there isn't one to download. It was built lesson-by-lesson, ship-by-ship, since August 2024.

Every lesson I learn becomes a skill the next session inherits. The system gets sharper every day I work in it.

▸ The 20-month changelog

This is not a roadmap.
This is a changelog.

AUG 2024
First AI-built site shipped to prod
End-to-end on Claude 3.5 Sonnet. Schema, routes, ads pipeline, conversion tracking, deploy. The traditional stack got deprecated that week.
OCT 2024
Built my own agent harness
No plugins, no SaaS UI. Terminal-native from day one. The whole studio runs from a shell, which means every workflow can be scripted, observed, and version-controlled.
JAN 2025
Shipped the memory system
Persistent across sessions, cross-project, full-text searchable. Every lesson I learn — a corrected bug, a validated approach, a client preference — becomes a record the next session inherits.
MAR 2025
Shipped the skill library
47 codified workflows so far. Auto-discovered. Self-improving. When a process matures, it becomes a skill any future agent can call — Google Ads bulk-edits, GA4 conversion debugging, deploy verification, session reviews.
ONGOING
Day-zero upgrades on every Claude release
Claude 4.5 → 4.6 → 4.7. My entire system upgrades the same day a new model ships. Across every client. No vendor roadmap to wait on. No agency pricing meeting six months from now.
An empty dirt road curving forward toward distant blue mountains at golden hour

Get on the stack now,
or wait 18 months for it to trickle down.

▸ The stack

What's actually running.

jordan@studio:~ ▸ tree -L 1 ~/studio
~/studio
├── agents/ 38 active · 12 marketing-specific
├── skills/ 47 codified workflows · auto-discovered
├── memory/ 1,247 lessons · persistent · cross-session
├── hooks/ 23 PreToolUse safety gates
├── clients/ 7 live · own repos · own accounts
├── playbooks/ Google Ads · GA4 · SEO · CRO · email
├── tools/ cli · review · deploy · monitor
└── ship.log currently writing your studio
$ claude --version
claude-opus-4-7 [1M context]
↳ upgraded day of release
▸ How it compounds

Every project teaches the stack. A bug I fix today becomes a hook that prevents it everywhere. A workflow I write twice becomes a skill any agent can call.

▸ Why upgrades arrive day-zero

When Anthropic ships a new model, my entire system upgrades the same day — across every client. No vendor roadmap. No agency pricing meeting six months from now.

▸ Why that matters for you

The agency you use is waiting for SaaS vendors to surface AI through buttons. I'm shipping those features now, on your account, the week they exist. That's the entire proposition.

A lone eucalyptus tree standing tall in a wide wheat field at sunrise

Stood alone.
Grew anyway.

▸ Principles

How the work gets done.

P/01SHIP
Smaller, more often, end-to-end.
A working v1 beats a perfect plan. The smallest useful thing goes to prod, we watch what happens, we iterate. Most weeks ship 3–5 times. None of them are slide decks.
P/02OWN IT
Built on your stack, in your accounts.
Code lives in your repo. Ads in your Google Ads. Analytics in your GA4. When the engagement ends — and one day it will — nothing leaves with us. The whole system is yours.
P/03MEASURE
Tracking gets installed in week one.
GA4, server-side conversions, call tracking, lead-to-revenue attribution — wired before the first campaign turns on. We don't optimise what we can't see.
P/04COMPOUND
Every lesson goes back into the stack.
A bug I hit becomes a hook. A workflow I write twice becomes a skill. A page that converts becomes a pattern. Your engagement adds to the system — and so does every other client's.
P/05SAY NO
Wrong-fit work makes everyone miserable.
If your business is too early, too cold, or too at-odds with what this stack does well, I'll say so on the first call. The 20-minute 'no' is cheaper than the 3-month 'we should have said no.'
▸ The guarantee

If I don't deliver measurable results inside 90 days,

I'll keep working until I do.

No excuses · No extra charges · Your success is the deliverable
▸ Open for 2 new clients in May

Get onto
the stack.

A 30-minute call. No slides, no SDR. Just whether the fit is real.

Book the callLinkedIn
info@jordanjamesmedia.com · 0475 897 737 · Sydney