Here is a scene I know far too well, because I lived it for about a year.

It is Monday morning. Coffee is hot, and you open your AI to get a head start. Then you type the same paragraph you typed last Monday. "I run a small business, my audience is X, my voice is warm and casual, please don't sound like a robot, here is my offer, here is my pricing..." Four hundred words of setup before you ask a single real question. Every single week.

That is not an AI problem. That is a setup problem, and it is the most common thing I fix for people. Once you stop starting over, the whole thing changes character. It stops feeling like a clever toy you keep re-explaining yourself to, and starts feeling like a coworker who was actually paying attention.

Quick definitions

  • Memory: a setting that lets Claude hold onto facts about you across separate conversations, so it stops asking what you do for a living.
  • Project: a saved workspace that holds the files and context for one client, offer, or job. Everything you chat about inside it already knows the background.
  • Skill: a saved set of instructions for one specific job, so that job comes out the same good way every time you ask.
  • Persistent instructions: standing rules that apply everywhere, like "never use exclamation points" or "always sign off as Jam."
  • Context: everything the AI knows in the moment. When you start a fresh chat with no setup, your context is empty and it shows.

Why Monday keeps happening

The reason the reset feels so normal is that most people learned AI through the chat box, and a chat box is designed to forget. Every new conversation is a blank room. You walk in, the lights come on, and nobody in there has met you.

That was fine when we were all just asking for a subject line. It stops being fine the second you start doing real work, because real work needs history. Your pricing, your customers, what you already tried, the way you sound, the thing you refuse to say in marketing copy. None of that fits in a one-off question, so you either re-type it forever or you accept generic output.

Most people quietly accept the generic output. Then they decide AI is overhyped. It is not overhyped. It is under-configured.

The six layers that make it stick

I think of this as a stack. You do not need all six on day one. Each one you add takes another chunk of Monday off your plate permanently.

1. Turn memory on and then actually feed it

Memory is the easiest win and the most skipped one. In Claude's settings there is a memory option, and turning it on lets the AI carry facts about you from one conversation to the next.

But here is the part people miss. Turning it on does not fill it. You have to tell it things worth remembering, out loud, on purpose. So spend fifteen minutes one time and say things like:

  • "Remember that I run a bookkeeping business for small trades companies in Denver."
  • "Remember that my writing voice is warm and plain, no jargon, no hype."
  • "Remember my main offer is a $500 monthly package and my busy season is January through April."
  • "Remember that I hate the word 'unlock' and never want it in my copy."

That is it. Next Monday, you skip the whole intro paragraph. It already knows.

One honest caution. Memory holds real details about your business, so be a little thoughtful about what goes in there. Business facts and preferences, yes. Client bank details, no. Same judgment you would use with a new assistant on their first week.

2. Give every recurring job its own project

A project is a folder with a brain. You create one, you drop in the relevant files, you write a short description of what this workspace is for, and every conversation you start inside it begins already briefed.

The mistake is making one giant project called "My Business." That is just the chat box with extra steps. Make them narrow instead:

  • One per active client, holding their notes, contracts, and brand details.
  • One per offer, holding the sales page, the pricing logic, the objections you hear.
  • One for content, holding your voice notes, best posts, and topic list.
  • One for operations, holding your processes, vendors, and standard replies.

Now when the Acme client emails with a weird question, you do not brief anybody. You open the Acme project and ask. The answer arrives already knowing what you agreed to in March.

3. Write the instructions once, at the top

Inside a project you can set standing instructions, and this is where most of the magic actually lives. This is not a prompt. It is a job description that never expires.

Good standing instructions cover four things: who I am, who I am talking to, how I sound, and what I never do. Something like this works for almost anyone:

"I run a small photography studio serving families and small brands. My readers are busy, non-technical, and skeptical of hype. Write in short warm sentences, first person, no jargon, no exclamation points. Always end with one clear next step. Never invent statistics or client names. If you need information I have not given you, ask me instead of guessing."

That last sentence is quietly the most valuable one on this page. It is the difference between an AI that confidently makes something up and one that stops and checks with you.

4. Turn your repeat jobs into skills

A skill is where this stops being convenient and starts being leverage. If you do a job more than twice, it should be a skill.

Think about what you redo constantly. The weekly newsletter. The client onboarding email. The proposal. The invoice. The social caption. Each has a right way you figured out through trial and error, and right now that right way lives in your head, which means you rebuild it from scratch every time.

A skill writes it down. It captures the structure, the tone, the required sections, the things to avoid, and the format of the finished thing. Then you just say "write this week's newsletter about the spring mini sessions" and out comes something already shaped correctly.

The first one takes an afternoon. Every one after that takes twenty minutes, because you are copying a pattern you already understand. And you build them by describing what you want in plain English, which is the whole point.

5. Keep one running file the AI can read

This is my favorite low-tech trick and it costs nothing.

Keep a single document called something like "Business Context." In it, write the boring durable facts. Your offers and prices. Your ideal customer in a paragraph. Your three content pillars. Your goals for the quarter. The things you are deliberately not doing this year. Drop that one file into every project, and update it once a month, on a Friday, in ten minutes.

Why bother when you already have memory? Because memory is automatic and a file is deliberate. The file is the version you control, the one you can read back, edit, and hand to a contractor. Memory is the assistant's own notes. You want both, and honestly the file is the one that saves you when you switch tools.

6. End every session by writing tomorrow's starting line

Here is the habit that ties it all together, and it takes ninety seconds.

Before you close the laptop, ask for a handoff. "Summarize what we decided today, what is still open, and what I should pick up next time." Then paste that into the project.

Now Monday does not start at zero. It starts at "here is exactly where you stopped and what you were about to do." That is how a real team works. Someone leaves notes.

Quick tip

Do not try to build all six layers this weekend. Do memory and one project for your single most repeated task. That combination alone kills most of the Monday reset, and you will feel it within a week. Add the rest when the next annoyance shows up.

What this actually feels like once it is running

Before, a Monday content session looked like this. Twenty minutes re-explaining the business. Ten minutes fixing the tone. Fifteen minutes cutting the words you would never say. Then maybe an hour of useful work, ending with a vague sense that you had done this exact wrestling match before.

After, it looks like this. Open the content project. Say "three posts this week, one on the pricing question people keep asking, one on the mini sessions, one story from Saturday's shoot." Read what comes back. Fix two lines. Done in twenty-five minutes, and it sounds like you because the setup already told it how you sound.

Same tool. Same person. The only difference is that the context stopped evaporating overnight.

And there is a compounding effect people do not expect. Once the AI reliably knows your business, you start asking better questions. You stop asking for captions and start asking "look at what I charged versus how long these jobs actually took, where am I losing money?" You only ask that when you trust it knows enough to answer.

The three mistakes I see most

Making one enormous project. If everything lives in one workspace, the context gets muddy and the answers get vague. Narrow beats big.

Writing instructions that are all vibes. "Be professional but friendly" tells it almost nothing. "Short sentences, first person, no exclamation points, one clear next step at the end" tells it everything. Be concrete enough that a new hire could follow it.

Setting it up and never revisiting it. If your prices went up in March and your context file says otherwise, you will get confidently wrong answers all year. Ten minutes a month keeps it honest.

Frequently asked questions

Do I need a paid plan to do any of this?

You can experiment with the free tier and get a feel for it, but projects and the more useful memory features generally live on the paid plans. Paid Claude plans start around $20 a month. Compared to what one wasted hour of your week is worth, it is not a close call.

Is memory the same thing as a project?

No, and mixing them up is common. Memory is a general layer that follows you everywhere, holding broad facts about you. A project is a bounded workspace for one topic, holding files and instructions specific to that job. Memory is who you are. A project is what you are working on. You want both.

What if I have already had a hundred messy conversations with no setup?

You are not behind, and you do not need to clean any of it up. Start fresh from today. Turn on memory, build one project, and let the old chats stay where they are. Nothing you have already done makes this harder.

Will my instructions make everything sound stiff and templated?

Only if you write stiff instructions. Good instructions do the opposite, because most of what makes AI writing feel robotic is the absence of direction. When you specify your actual voice, including the words you refuse to use, the output gets more human, not less. Give it your quirks on purpose.

How long does the initial setup take?

Realistically, about two hours to get memory, one solid context file, and two projects in place. Spread it over two sittings if that feels like a lot. Almost everyone I have walked through this tells me the same thing afterwards, which is that they wish they had done it months earlier.

Does this work if I switch between different AI tools?

The context file does, completely, which is why I keep pushing it. Memory, projects, and skills are features of a specific tool, so those stay put. But your written business context is yours, in plain text, and you can hand it to anything. That is the piece worth building first if you are still shopping around.

What is the very first thing I should do after reading this?

Open your AI, turn memory on, and tell it five true things about your business. Then start one project for whatever job you dread most on Mondays. That is the highest-return twenty minutes in this whole article.

You are allowed to stop repeating yourself

Most people never build any of this, not because it is hard, but because nobody told them it existed. They assumed the reset was just how AI works. So they keep paying a small tax every Monday, forever, and slowly conclude the tool is not that impressive.

You now know better. The setup is not the boring part before the real work. The setup is the work. Everything after it is just asking good questions to something that finally knows you.

If you want help building this out with people who are doing it alongside you, that is exactly what we do inside Club Jam on Skool. It is $47 a month with a 7-day free trial, and there are 220+ modules in there walking you through this stuff step by step, in plain English, with no assumption that you are technical. I have trained over 7,500 people this way, and our retention sits at 93%, which tells me the format works for regular humans with busy weeks.

Come build the setup once. Then let Monday be about the actual work for a change. 🧡