Growth File · Operator Notes · SW-06
Operator edition
Melbourne, Australia
The Growth Files
Field note 04
Read · Test · Keep
Friday 20 November 2026AI setup for marketing work

Why AI gives poor results when it is not set up properly

One product update shows where the brief, current facts, writing preferences, decisions and steps fit, and what still needs a check.

Blue ballpoint drawing of a robot at a desk holding a pen over a blank page while a person slides a stack of folders across to it
A blank page, and the folders it needed first.Illustration: operator field notes

I used Claude Code to redesign a website and had to pretty much start again. What came back was the sort of generic redesign I call AI slop.

I'd given Claude Code the job with no skills set up. Skills are instructions an AI tool can use again. Back then I started each project from scratch, so the tool was learning the job from the beginning, with no record of how I worked and no steps to follow. Starting again on that site cost me a lot of time.

Now I keep my preferences, past work and decisions where later sessions can use them, and I set up folders so the tool has a place to start and steps to follow. About your job, the tool only knows what's in front of it. Leave a gap in that material and the draft can fill it with a guess that reads like a fact. In an email, that might be a single line saying a feature is available now when the release date is still open.

Getting the right material in front of it takes work. You have to write down the rules worth keeping, gather the current facts and read what comes back, then keep those notes current. If it's a one-off email you know how to write and check yourself, setting all that up may be more work than writing it by hand.

The example here uses five pieces of setup for one product update email. Start with the brief and the current product facts. For repeat work there's a place for writing preferences, a note for decisions that need to carry over, and steps for a job that has to happen in a certain order. Together they set out what the email is for, what the chat has to work with and what you'll check the draft against.

Why a draft can sound right and still miss the job

Say an email arrives with the subject The new location filter is here. When would you go looking for the filter? Even a short update has to answer questions about who's reading, what's worth telling them and whether there's anything for them to do. Ask the chat for an email without giving it those decisions and it can draft a different email from the one you meant to send.

Here's a made-up example. A business that sells a booking calendar wants to tell existing customers it's getting a filter that shows bookings for one location at a time. The release date is still open, so the business has agreed to describe what the filter does and leave timing out. Give the chat only the request Write a product update email and here's one possible opening.

Example of a draft that misses the job
Subject: The new location filter is here
We're thrilled to bring you a whole new way to manage bookings. The location filter is now available to all customers. Book a demo to see it in action.

The date was open. The email said now.

That's one reason to stop the email. A customer could open the calendar expecting to find the filter, though the release hasn't been confirmed. There's another decision in the last line. Book a demo makes sense in an email to someone still deciding whether to buy. Here it asks a customer who already uses the calendar to do something the business hasn't asked them to do. The writing looks like ordinary marketing copy.

A brief is a short note that says what this particular job needs. For the calendar email, a few lines are enough to say who it's for, what source to use and where the job ends.

Example Brief
Write a subject line and a short email for existing booking calendar customers. Explain that the location filter will show bookings for one location at a time. Use Product facts for claims about the calendar. Leave out anything the source doesn't confirm. This is an update for information. The reader has no action to take. Return a draft for review.

Start with Brief and Product facts. The first says what the email is for, and the second holds what you know about the product today. Use headings on one page if that's enough. The example Brief still leaves the tone open.

Save the preferences you keep explaining

We're thrilled puts the business's excitement in the first sentence. Where's the change the customer opened the email to find? That opening has a place in a launch announcement, but this is a routine update for people who already know the calendar. The chat had no writing preferences to go on, so it picked a style. I think leaving those preferences unsaved is a mistake. I keep mine with my marketing work.

If you cross out We're thrilled, tell the chat what should go there. The chat has only been asked for an update, so an opening like that fits the request it received. Sound more like me still leaves it to guess what you'd change. Put the actual change in the first sentence gives you a rule with an exact place to look.

Example Writing preferences
Audience. Write to existing customers. They already know what the calendar does.
Tone. Put the actual change in the first sentence. Use everyday words and short paragraphs.
Words. Use Australian spelling. Call it the booking calendar. Leave out phrases like we're thrilled and a whole new way.
Sample for style. The calendar now shows cancelled bookings in grey.
Use of the sample. Follow the way the first sentence gets to the point. Take the details for this email from Product facts.

The sample comes from an earlier update, and the grey bookings are there on purpose. The sentence shows how the business gets straight to the change, but it also contains a product detail the chat could reuse by mistake. Without a line telling it which document to use for which job, it can borrow the old detail as readily as the style. Take today's filter details from Product facts. Borrow the shape of the sentence and leave the grey bookings where they are.

For your own sample, pick a short bit of writing you own, are happy to share and would still send in the same circumstances. A well-written sales email is a poor sample for this kind of update. It spends words explaining things existing customers already know, and it has a different reason to ask for a reply. The closer the sample is to the job, the clearer the choice you're showing the tool.

If you keep having to move the main change up to the top, save that instruction with the recurring job and paste or attach the current preferences when you start the next draft. When one group needs background before the update makes sense, put the exception in the Brief for that group. Make that a standing rule and every regular customer gets background they don't need. The preference that carries over is to lead with the change. Which change goes in that first line depends on what you've decided for this email.

Give the next chat the decisions that still matter

An old release plan had 8 December 2026 pencilled in for the calendar filter. The date had to stay out of the email. A fresh chat given only that plan might use the date.

The business has decided to describe the filter and leave timing out until there's a confirmed date. That's a decision about this job, so having exactly the right Writing preferences doesn't settle it.

Example Decision note, 1 December 2026
Decided. Explain what the location filter does. Leave timing out of this email. Draft for existing customers.
Current source. Product facts, 1 December 2026, location filter entry.
Still open. The release date and who will get access first. Update Product facts when those details are confirmed, then update this note.

The Product facts page records what the business has confirmed, while the note tells you how to handle the open details in this draft.

Example Product facts, 1 December 2026
Location filter. The booking calendar will get a filter that shows bookings for one location at a time. Release date and first group of customers are unconfirmed.

Date the Decision note and name the version of Product facts that goes with it. The pencilled date belonged to the release plan. The latest note records what to do with timing in the email. If the business confirms a date later, update Product facts and record the new decision in Decision note. Keep the old note if you need the record, and mark it as replaced.

A filename tells you where to look. Paste the relevant text into the new chat or attach the actual file if your tool accepts it, using material you have permission to share. An old chat can still be in your history while the new one knows nothing about what you decided in it. For this email, check whether the fresh chat has both the current source and the instruction to leave timing out.

That's the handover done by hand. My own setup does it with memory systems. MBrain is a memory system I built for myself. It saves what comes into my computer, such as emails, messages and meeting notes. You can't download it, and a setup like mine takes technical work. If you want memory like this, I'd suggest installing GBrain, an open source project on GitHub.

OpenViking is an open source tool that organises information an AI assistant can refer back to. I use it to collect my AI chats and coding sessions from different tools in one place. It keeps the decisions I've made and the facts, including the ones that change. It sorts and summarises what I've worked on, so I can ask what happened on a project. When I start a new session, I don't have to brief the AI from scratch. You can install it from its GitHub page. GBrain and OpenViking overlap in places, but they work well together.

My working files and projects feed into my memory setup too. I keep my marketing work in one project with my preferences, the work I've done and the stats.

If I were setting up one thing first, I'd set up memory for the AI tools doing the work. I'd connect my chat and coding sessions and collect the work so it can build from one session to the next.

You don't need my setup for the calendar email. Ask the fresh chat what it understands about the timing before it drafts. If it says there's a confirmed date, look for that date in Product facts. The source settles what goes in the email, which is why it belongs before the first line of the draft.

Put the steps and references where AI can find them

Write a product email sounds like a step. Where in that step do you check whether the date is settled? Save an instruction like that as a skill and the tool can use it again. I call that generic version a flat skill. It's one instruction, and it has little to do with how you run the job. Even a page of good writing advice can leave the chat guessing if it drafts before it gets to the source.

I had no skills set up for that website redesign. Now, in my home project for code, the kind of work tells the tool which folder to start in. That folder holds the steps and reference files for the job, and some steps have reference files of their own. My memory systems can fill in gaps alongside those instructions. That's what I mean by a folder structured workflow. The steps give the work an order, and the references give each step the material it needs.

Start the calendar email with the location filter entry in Product facts and the instruction in the Decision note. That pair settles what belongs in the draft while the date is open. With a generic instruction to write, the chat might put a likely release into the subject before you've even looked at the product entry.

Here are the pages for the calendar update in an ordinary folder. Their names match the pages in the steps, so you know what to open at each point. If your chat only takes text, open the pages yourself and paste the relevant parts.

Example folder: Product update email
Email steps · the order and what counts as finished
Brief · the audience and the job for this update
Writing preferences · the rules and the style sample
Decision note · what has been decided and what's still open
Product facts · the current information about the filter

The Email steps page takes this job from the product entry to a checked, unsent draft in four steps.

  1. Find the facts. Use the Brief and Product facts to pick out the confirmed details about the filter that belong in the email.
  2. Settle timing before writing. Follow the Decision note and leave timing out. If the email needs a date, stop here until it's confirmed.
  3. Write the email. Use the settled facts, the Brief and Writing preferences for a subject and a short update for existing customers.
  4. Review and save. Put the draft beside Product facts and the Brief. Finish with a checked, unsent draft in your usual drafts folder.

During the facts step, leave date unconfirmed on its own line. In a draft, a phrase like is here can make the question look settled. When the decision is to leave timing out, the description of the filter is enough to finish this email.

Keep that order when the product changes. Replace Product facts for the next update and keep the step that tells you to settle the facts first. Leave the steps as headings beside the Brief if that's all the job needs. A folder helps when the material for a recurring job comes from several places and you need to know where the job starts and where the facts live. When you review the draft, go back to the product entry you started with.

Keep the final check in your hands

When I checked the ad videos by hand, I found text covering faces and title text that was too small. Both were simple fixes. I've used AI to write ad copy and create video assets, and I went through the work myself to check for mistakes and see how close it looked to the brand. I kept that way of working. The calendar email gets the same check.

Two ordinary words change what the draft says. Put the first draft beside Product facts and look at now and all in now available to all customers. The source leaves both timing and first access open. Take out now and there's still a claim about who gets the filter. Check the subject too. The new location filter is here makes a timing claim before the customer even opens the email.

Example of a checked draft
Subject: A new location filter for the booking calendar
The booking calendar is getting a filter that shows bookings for one location at a time.

Customers can tell what the filter will do from the new subject and body. The release date stays out, as the Brief asks. The old subject told them to expect the filter when they opened the calendar. Changing that claim matters more than polishing the words around it.

The first draft gives you a place to look for each problem. All customers points to an access claim, while book a demo points to a mismatch with the job in the Brief. A line that sounds like a launch might point to a missing preference or a sample written for the wrong purpose. Even with the right instruction and source, the chat can still misread a line. Correct the draft and look at the gap you actually found before you add another page to the setup.

If the chat points to a source, open it and check that the line supports what the draft says. The filter is planned gives you no basis to send The filter is here. The draft can look finished while that check is still yours to do. Once you've made it, you know which line to watch for the next time you draft an update.

Test your setup on one marketing job

If you do one thing today, open your last AI draft, pick one claim in it and check that claim against your source. For a fuller test, pick one marketing job you do regularly and write down one mistake you'd check for before the draft went out. For the calendar email, that mistake is saying the filter is already available. Your usual setup may already keep that claim out. See whether giving the chat the current source changes the draft or what you have to fix.

Use the same tool and brief in two fresh chats. If your tool has a memory setting, turn it off for both, or the second chat may already have what you gave the first. Prepare both requests before you start, using your usual setup for one and adding the current source to the other. Use only material you're allowed to share. If your usual setup already includes the current source, pick something else it's missing and test that. Save both first drafts before editing.

Write one line for each draft. Record whether it made the timing claim, what you had to fix and how long the whole job took, including setup and review. Edit both until you'd be happy to send either and leave them unsent, or note where you stopped.

One pair is a hint. If both make the claim, look at the instruction to leave open dates out. Drafts can vary with the same request, so try another comparable update before making a call. Swap which version you run first. Keep the change for this job if it repeatedly addresses the fault, the draft passes your checks and the whole job is worth the effort. If the fault keeps turning up or the work takes more effort than you want to put in, set the change aside for this job.

Go back to the line that made you stop. In the calendar email it was now available to all customers. Look at the facts the chat had, the decision it was given and where the line first appeared. If the source was missing, try giving it the source. If it was there, check how the line came to be in the draft and fix it. The job ends with the words your customer would actually read, checked against the source.

Privacy notice