The 6 Documents Every Freelancer Should Have in Their AI Brain

If you've read The Co-Founder Setup, you've got the filing system. Identity, Vision, Business, Clients, the lot.

Which is when almost everybody hits the same wall: lovely folders. What on earth do I put in them?

So this is the answer. Six documents. Write these and your AI stops giving you generic advice, because for the first time it actually knows who it's talking to.

I'd write them in this order too, because each one makes the next easier.

---

1. Core Context - who you are

This is the foundation, and it's the one people write too briefly.

It isn't a CV. It's everything about you that would change how somebody advises you - your background, how you work, what you're brilliant at, what you avoid, and what you're currently trying to do.

Structure it like this:

• Who I am - name, where I'm based, what I do, in about three lines
• My background - the whole career. The corporate years, the side jobs, the things you think are irrelevant. They aren't. Context you leave out is context it can't use.
• How I work - your hours, your energy, how you like to be spoken to, how you make decisions
• What I'm genuinely good at - including the things that feel too obvious to write down
• What I'm not good at, and what I avoid
• What I'm working towards right now
• Things you should never assume about me - this one saves a surprising amount of correcting later

2. Business & Offers - what you actually sell

Your AI cannot help you price, pitch, propose or plan if it doesn't know what you sell and to whom.

Structure it like this:

• What the business is, in one paragraph a stranger would understand
• Who I serve - the real description. Their situation, what's going wrong for them, and the words they'd use to describe it themselves
• My offers - each one, with what's included and what it costs
• How each one is delivered - the process, the timeline, what you need from the client
• What I don't do - the enquiries you turn down and why
• Where the money currently comes from - roughly what percentage from retainers, projects, anything else

That last line matters more than it looks. It's what lets your AI say "you've got one client at 60% of your revenue, that's a risk" rather than generic business advice.

3. Brand Bible - how you sound

This is what stops everything coming back sounding like a LinkedIn post written by a committee.

Structure it like this:

• The one-line version of what I do - the sentence you'd say at a party
• My tone - describe it in plain words. Warm? Blunt? Funny? All three?
• Words and phrases I use - the ones that are properly yours
• Words and phrases I never use - and this is the most valuable section in the document. Every time you catch yourself thinking "I'd never say that", add it here.
• How I format things - do you use dashes or commas? Emojis or not? Short paragraphs?
• A good example and a bad example - one paragraph that sounds exactly like you, one that doesn't, with a line on why

The never-list grows over time and that's the point. Mine is long, and it's the reason nothing comes back sounding like a stranger wrote it.

4. Vision - where you're going

Without this, your AI optimises for today. Ask it about a client and it'll help you keep that client, even if that client is the reason you're stuck.

Structure it like this:

• Where the business is right now - revenue, clients, capacity, honestly
• Where I want it to be in twelve months
• The bigger picture - three to five years
• What I want life to look like - not just the business. Hours, travel, where you work from, what your week feels like.
• What I'm deliberately not building - the agency you don't want, the team you're not hiring
• This quarter's goals - the near-term version

That "not building" section does a lot of quiet work. It stops every conversation drifting towards scale-scale-scale when that was never the point.

5. Agent Instructions - who your AI is and the rules it follows

This is the one nobody has, and it's the one that changes the experience most.

Everything above tells your AI about you. This one tells it about itself - what it's for, how to behave, and the rules it doesn't get to break.

Structure it like this:

• Who you are - give it a role. Not "an assistant" - a chief of staff, a business partner, a co-founder. It changes how it responds.
• What you have access to - the vault, the calendar, the task manager, the inbox
• How to start - what it should read or check before answering anything
• How I want you to talk to me - direct, no flattery, challenge me when I'm wrong. Whatever you actually want.
• Rules you never break - numbered, specific, one behaviour each
• What to do when you're not sure - ask, don't guess. Say so, don't fill the gap.
• What you must never touch - the files, lists or systems that are off limits

Mine are written as numbered protocols and each one is a single specific behaviour. Things like: how to name a file. Never modify my task list unless I've asked. Log what we did at the end of a session. Check the source of truth before answering, and if you can't reach it, tell me rather than working from memory.

They read as strict, and that's deliberate. Rules like those are the difference between something helpful and something you have to check constantly.

One practical note: where this document lives depends on your setup. In Claude, it goes into your project's custom instructions or a CLAUDE.md in your folder. In other tools it's an agent file. Same content either way - it's the instructions that matter, not the filename.

6. Client Files - one per client

One document per client, and this is the one that pays for itself fastest.

Structure each one like this:

• Who they are - the business, what they sell, who they sell it to
• What I do for them - what's in scope, in detail
• What's explicitly out of scope - so scope creep gets caught early
• What they pay, and how - the number, the terms, when it's reviewed
• How they like to communicate - email or Slack, formal or casual, how fast they expect a reply
• Their preferences and quirks - the things you've learned that nobody wrote down
• What's live right now - current projects and where each one is up to
• Decisions we've made, and why - the most useful section six months later
• What I've learned the hard way - the mistakes, so nobody repeats them

Don't write these from scratch

You will not sit down and type six documents. Nobody does, which is why most people's AI brain is one hopeful file called "about me."

So talk instead.

Open a chat, tell Claude which document you're writing, and just ramble at it - voice notes are ideal here. Then:

I'm writing my [Core Context / Brand Bible / Vision] document for my AI knowledge
base.

Here's a brain dump: [talk. Don't structure it. Go off on tangents]

Turn this into a proper md document using this structure: [paste the structure
from above]

Where I've been vague or skipped something important, ask me about it rather than
filling the gap yourself.

Then tell me what's still missing.

"Ask me rather than filling the gap" is the line that matters. A knowledge base full of plausible invented detail about you is worse than no knowledge base at all, because you won't notice until it's confidently wrong in front of a client.

Then keep them alive

These documents rot. Your prices change, your offers change, your clients change, and a knowledge base describing your business in March is quietly making you worse in September.

So once a month, ask: what's changed that these documents don't know about?

That's it. Six documents, one conversation each, and your AI stops being a clever stranger and starts being something that actually knows your business.

Start with Core Context

Just that one. Talk for twenty minutes and let Claude structure it.

You'll notice the difference in the very next conversation you have - and that's usually enough to make you write the other five.

If you haven't built the filing system yet, do that first: The Co-Founder Setup.

And if you want the whole system - the setup, the delegation and the business model that sits on top of it - that's what I teach.

Watch the free training →