FRDTLAB

FRDTLAB · Field Note · How it works

Marketing through the system, not on top of it.

By Amanda Friedt

If you run social, SEO, and paid for a business by yourself, you already know how to build a campaign structure. An AI operating layer is the same discipline pointed at your own work. Here is the whole thing in one picture and six stages, in words you already use.

The one idea. The model is not the system. It's the router. Everything that makes the output sound like you, use your data, and land where you actually publish lives in the layers around it. Most people set up the router and skip the layers, then wonder why every session starts from zero.

A request enters on the left and passes through six stages: brief, route, sources, work, publish, and remember. A shared drive runs as a bus beneath all six. Brief and sources read from it, publish and remember write to it, and the last stage feeds the first so the next request starts with everything learned. your ask 1 · Brief2 · Route3 · Sources 4 · Work5 · Publish6 · Remember known beforeyou type voice · ruleschecks analytics · adsCMS · files draft · analyzefan out · review site · schedulerreport · tasks decisionslessons · runs next request starts here, nothing re-explained One shared drive: the source of truth every tool reads and writes think: your product feed, but for how the business works reads the briefreads the data writes the deliverablewrites lessons Not on the bus: chat history, one tool's memory, your Downloads folder. Those are caches. The drive is the record. Six stages stacked top to bottom: brief, route, sources, work, publish, remember. A shared drive runs alongside all six. Brief and sources read from it; publish and remember write to it. A dashed loop carries the last stage back to the first. your ask ↓ One shared drive: the record 1 · Brief known before you type reads 2 · Route voice · rules · checks 3 · Sources analytics · ads · CMS reads 4 · Work draft · analyze · review 5 · Publish site · scheduler · report writes 6 · Remember decisions · lessons writes Dashed loop: the next request starts with everything learned.
Six stages, one bus. Solid arrows are one request. The dashed loop is why the second month is faster than the first.

The six stages, translated

You already do every one of these in PPC and SEO.

StageWhat it actually isYou already do this in PPC / SEOWhat breaks without it
1 · BriefStanding context that loads before you type: who the brand is, what's decided, what's in flight, where files live.Your account structure and naming convention. Nobody re-explains the account every morning; it's in the structure.Every session starts cold. You re-paste the brand guide. Output drifts.
2 · RouteRules that pick the voice, the guardrails, and the review steps for this kind of task. Encoded once, applied every time.Campaign settings and negative keyword lists. Match types. The stuff that stops the wrong thing from serving.Client tone leaks between brands. Health or legal claims slip through. You become the QA step.
3 · SourcesLive pipes into your real data: analytics, Search Console, ad platforms, the CMS, your own files. Read where they sit; don't copy.Conversion tracking and data feeds. Merchant Center reads your catalog; you don't retype products into ads.The model guesses. Numbers in reports can't be traced to a source.
4 · WorkThe actual task: draft, analyze, compare. Small jobs run inline; big ones fan out (read 40 pages in parallel) or run as a pipeline (draft, review, verify).Bulk edits and scripts. You don't hand-edit 400 ad groups; you run the sheet.Everything is one long chat. Nothing is repeatable.
5 · PublishOutput lands where it's used: the site, the scheduler, the report, the task board. The chat is the preview, not the destination.Push to live. A campaign in a spreadsheet earns nothing until it's in the account.Deliverables die in chat tabs. You copy and paste all day.
6 · RememberDecisions, learnings, and open loops get written down in the same turn, and scheduled runs keep working when you're not there.Change history, automated rules, scheduled reports. The account keeps running while you're in a meeting.The system never compounds. Month two is as slow as month one.

Why the drive is the bus

One copy. Many readers.

Every tool you use has its own memory: the chat app remembers your account, the desktop app remembers this machine, a session remembers itself until it closes. None of those can see each other. A shared drive is the one place all of them, plus your automation tool, plus a scheduled run at 7am, plus a human on your team, can read and write the same file.

You already trust this pattern. Your product feed is the single source of truth that Merchant Center, the ad account, and the site all read from. Nobody maintains three catalogs. The operating layer just applies that rule to how the business works: brand rules, decisions, briefs, deliverables. One copy, many readers.

If you're a one-person shop

Set up these three things first.

01 · Brief

A registry file

One document that lists every brand or client you touch: a short code, where its files live, what the current gate is, who owns it. Any tool that reads it starts informed.

02 · Route

A voice kernel per brand

Not a 40-page brand book. A one-page rule set: register, banned words, claims you can't make, the CTA pattern. It's what keeps a local clinic's copy from sounding like a parts retailer's.

03 · Naming

A naming rule

Files, tasks, and chats carry the brand code and the date in the name. Naming is routing. A file called "final-v3.docx" belongs to nobody; a file called ACME_Report_2026-09.docx files itself.

Do those three and the rest (data pipes, scheduled runs, task-board mirrors) has somewhere to attach. Skip them and you're building automation on sand.

What changes about your job

You hold judgment. The system holds state.

  • You stop being the memory. The registry and the drive hold state. You hold judgment.
  • You stop being the QA step. Guardrails are encoded in the route stage; the system checks health claims, banned words, and source citations before you see the draft.
  • You review at the gate, not the keyboard. Agents draft and stage; nothing client-facing ships until a human flips it. That single rule is what lets the rest run unattended.
  • Your reporting gets honest by default. Every number traces to a pipe. Gaps get flagged as "awaiting data" instead of being smoothed over.

Three things people get wrong.

  • "Better prompts." A prompt is one request. The layer is what makes the thousandth request as good as the first without re-explaining. Prompts are stage 4; most of the payoff is in stages 1, 2, and 6.
  • "One tool to rule them all." You'll use several. The question isn't which one; it's whether they all read the same drive. If they do, switching costs nothing.
  • "Automate first." Automation runs on top of structure. A scheduled run can only act on brands whose brief, voice, and home are filled in. Empty slot, skipped work.

Bottom line. You are not learning a new discipline. You are applying account structure, negatives, feeds, and change history to your own operation. The model does the typing. The layers do the remembering. That's marketing through the system.

Educational, not a tool recommendation. More operating models live in Frameworks.

From field note to build

Want the layer built with you?

The registry, the voice kernels, the pipes, and the gate, installed alongside your team.

Work with me