[Full Guide] How To Create A Master "Business Context" Folder To Arm Your AI With Everything It Needs To Help You Scale Your Business, Streamline Workflows, And Create Output You Can Trust
Spending an hour on this exercise is the highest leverage thing you can do for your business today
Welcome back to AI Operator: the weekly newsletter for integrating AI into every vertical of your internet business — one SOP, system, or honest reflection every week that you can steal, install, and run by the end of the week. Last week we added 102 subscribers, taking us to 288 total AI Operators. If someone forwarded this to you, subscribe here.
If you’re using AI as a business owner but you haven’t armed your LLM with 50+ pages of business context, you are playing on hard mode.
In fact, you might as well not use AI at all—because you’re probably spending more time filling in knowledge gaps or correcting incorrect output than if you just did things manually.
If that sounds familiar, then keep reading.
What I’m about to share is the single most impactful AI upgrade I’ve made in the last 6 months. And I want to help you make the same upgrade in the next hour.
Now, I could write you a 2,000-word intro story about how I came to this realization, but today I’m going to cut straight to the point.
My time spent using AI is up 100% in the last few months, but my output is up more than 500%.
I’m using AI more, and I’m getting way better with it.
And it’s not that I got better at prompting or that the models got better. Those helped, but the real needle-move was one “context architecture” change. I answered 150 questions to build a set of context documents that give the AI a deep understanding of my business. And as a result, every single output I get requires significantly less editing, correction, or additional input from me.
So today I’m going to walk you through each of those 8 documents, what they are, why you need them, and examples of what they look like.
And if you want the full system: fill-in-the blank templates, real examples from my business, and copy-paste prompts that interview you one question at a time to build each document, like this post and leave a comment (or reply) to this email with the word CONTEXT and I’ll send it over to you.
Now let’s dive into these 8 documents:
The Money Model Builder — what you sell, how it’s priced, the full money model
The Perfect Avatar Map — who you sell to, their pains, fears, beliefs, and objections
The Belief Ladder — the sequential chain of beliefs your prospect must adopt before they buy
The Acquisition Blueprint — how strangers become customers, funnel by funnel
The North Star Brief — your mission, vision, values, and operating principles
The Org Chart Builder — who does what, reporting to whom
The Tech Stack Inventory — every tool in your business and what it does
The “What Good Looks Like” Vault — real examples of your best content, copy, and voice
Create each of these, upload them to one Project in your LLM of choice, and watch what happens to your conversations & outputs.
💰Document 1: The Money Model Builder
What it is: A complete breakdown of what you sell, at what price points, in what order.
What’s inside: Your offer name, core promise, transformation, deliverable stack, pricing, and upsell/downsell/continuity paths
Why you need it: Without this, your AI is blind to what you sell. So every time you ask it to write something relevant to your offer, it lacks the context required to write anything specific. You can also make better strategic decisions around your offer & pricing by asking it to brainstorm ways to make it more efficient
🎯Document 2: The Perfect Avatar Map
What it is: A deep profile of the person you sell to—everything from demographics to the thoughts they have when they’re considering your offer
What’s inside: Their current circumstances, 5 tangible pains (and the emotional pain behind each one), 5 tangible desires (and how achieving them would feel), what they’ve already tried, 5 fears and limiting beliefs, the 5 necessary beliefs they need to adopt before they’ll buy, and the top 10 objections they have before purchasing — categorized by uncertainty, timing, spouse, and money.
Why you need it: This is the doc that makes your AI sound like it actually understands your customer. Ad copy hits different when the AI knows the exact words your buyers use, the exact objections they raise, and the exact beliefs holding them back
🪜Document 3: The Belief Ladder
What it is: The sequential chain of beliefs your prospect must adopt, in order, before they’ll buy your offer.
What’s inside: Your destination belief (the single conclusion your prospect must reach), your unique mechanism (the proprietary method that makes the destination belief true), and the belief ladder itself — 5-7 rungs, each building on the last, from their current faulty belief to the belief that makes buying the obvious next step. Plus an argument summary that walks the whole chain in one paragraph.
Why you need it: This is the doc that turns your AI from a random copy generator into a persuasion strategist. Without it, every ad, email, and sales script says different things. With it, every piece of content follows the same logical and emotional argument.
🧲 Document 4: The Acquisition Blueprint
What it is: A map of every channel you use to get customers and the step-by-step funnel that turns a stranger into a buyer.
What’s inside: All your acquisition channels (organic, paid, referrals, partnerships, SEO, community), then your core funnel mapped end to end — capture step, conversion step, and every bridge touchpoint in between (what happens, who does it, when).
Why you need it: When you ask AI to help with your marketing & sales, it needs to know how your funnel actually works. Otherwise it gives you advice for a funnel you don’t have. With this loaded, it can spot gaps in your bridge, write emails that fit your sequence, and suggest improvements to your actual system.
⭐️ Document 5: The North Star Brief (Mission/Vision/Values)
What it is: A one-page doc that captures what you’re building, why you’re building it, and the rules you operate by.
What’s inside: Your vision (the long-term destination), your mission (the daily work), 3-5 core values (with what each one looks like in action), and 5-12 operating principles (the “how” behind the values — your actual decision-making frameworks).
Why you need it: This is the doc that keeps the AI aligned with how you think. Without it, the AI defaults to generic business advice. With it, it makes recommendations that match your values and uses your language.
👥 Document 6: The Org Chart Builder
What it is: A full roster of who’s on your team, what they do, and who they report to.
What’s inside: Your department structure, then every person listed with their name, role, department, core responsibility, who they report to, and how long they’ve been with you. Plus a visual org chart the AI compiles for you.
Why you need it: This is the doc that makes delegation and planning actually useful. Instead of “communicate this to your marketing team,” the AI can say “have Colin update the master content table and loop in Vitor for the YouTube cut.” It knows your people by name.
🛠️ Document 7: The Tech Stack Inventory
What it is: A complete list of every tool your business runs on.
What’s inside: 40+ business functions (email hosting, CRM, payment processing, scheduling, design, automations, etc.) — for each one, which tool you use and what you use it for.
Why you need it: When the AI helps you build a workflow or write an SOP, it needs to know what tools you actually use. Without this, it suggests tools you don’t have or writes instructions for software you’ve never touched. With it, every system it builds plugs directly into your existing stack.
📝 Document 8: The “What Good Looks Like” Vault
What it is: A collection of real examples of your best content, copy, emails, sales materials, and brand voice
What’s inside: Best-performing short-form posts, long-form content, ad copy, landing page copy, emails, sales scripts, DM outreach, objection handling, client deliverables, testimonials — plus one example that perfectly nails your voice and one example of what your voice is NOT.
Why you need it: This is the doc that kills the “this sounds like a robot wrote it” problem. Without examples, the AI defaults to generic. With them, it has a concrete reference for what good looks like in YOUR world — your tone, your structure, your style. The floor on every piece of content goes up immediately.
How To Set This Up (LLM Project Architecture Best Practices)
Once you have your 8 context docs built, here’s exactly how to set up your project:
Step 1: Create one Project. Call it whatever you want — “Biz Operations,” “[Your Company] HQ,” whatever. This is home base.
Step 2: Load all 8 context docs as files in that Project. Every chat you start inside this project now inherits all of that context automatically.
Step 3: Create your persistent chats. These are ongoing conversations you come back to again and again:
One “CEO Strategy” chat — this is where you think through big decisions, bottleneck analysis, restructuring, prioritization. The AI has your full business context so it can actually be useful here.
One chat per department — Sales, Marketing, Product, Success, Ops, etc. Each one becomes a running thread where you make strategic decisions for that area of the business.
Step 4: Use tactical one-off chats for everything else. Need to write an email? Draft an SOP? Brainstorm ad copy? Open a new chat inside the same project. It still has all the context — you just don’t need to keep the thread going.
I use strategic chats for things I want to come back to over time. I use tactical chats for things I use then move on from. Either way, both inherit the full context from the project.
Bonus Context Documents To Add
The 8 docs above cover the foundation. But the more context you give, the better. Here are a few additional documents & tools you can add to give the LLM even more context.
Any spreadsheets or dashboards you reference regularly — download them and upload them to the project. Revenue trackers, ad dashboards, conversion trackers, etc. Eventually AI will be able to read these in real time, but for now, a snapshot gives them context on how things are currently going.
Bank account or financial statements — if you want the AI to help you analyze where your money is going, give it the data. Upload a recent month’s transactions or P&L.
Your current SOP library — if you have SOPs written for your team, drop them in. Now the AI can reference your actual processes instead of making up generic ones. We currently host everything in Notion so it can easily connect via MCP.
Meeting notes or strategy docs — anything that captures recent decisions, priorities, or context that wouldn’t be in the 8 core docs.
Connect Claude to Slack — this one allows you to scan Slack to get real time updates of what you’re building
Anything else you think would be relevant — the more context you give, the better your results.
IMPORTANT! Remember these are living documents
Don’t treat your context docs like a one-time project. They should be updated in real time as your business changes.
Hired someone new? Update the Team Structure doc.
Changed your pricing? Update the Money Model.
Launched a new funnel? Update the Acquisition Blueprint.
The more current your context is, the more useful every conversation becomes.
ALSO IMPORTANT! These prompts are not perfect
Once you start using the prompts to build out your context documents, remember that there may be some errors. I’ve built them to handle most scenarios and output things in a formulaic way, but don’t conclude “these are broken!” if the output is not 100% accurate on the first go.
Use these as a collaborative back & forth exercise to save your hours and hours of time in the future.
Want the Full Context Architecture Starter Kit? (For Free)
Now, if you want to set these up for yourself, I built something for you—for free.
For each of the 8 docs, you get:
A fill-in-the blank template if you want to do it manually
A real example from my business so you can see exactly what “done” looks like
A copy-paste prompt that interviews you one question at a time and compiles the finished doc for you
All you have to do to get it:
Subscribe to AI Operator
Like this post by clicking the heart at the bottom
Leave a comment below or reply to this email with the word CONTEXT, and I’ll send it over to you
Looking forward to seeing what you build ✊
Why should you do this in the first place?
Once you have all of these documents set up, here are a couple things that will happen.
Content sounds like you on the first draft. No more “this sounds like a robot.” It has your real voice and examples loaded.
Strategy conversations actually go somewhere. You can have a real back-and-forth about your business because it understands your model, your team, and your funnels.
Copy references your real offer. Not “unlock your potential” — real copy about real deliverables for real people at real price points.
SOPs reference your tools and your people. “Send this via Slack to Tristan” — not “communicate the update to the relevant stakeholder.”
Bottleneck analysis is actually useful. Feed it your metrics and it spots where you’re leaking because it knows the full system.
Delegation briefs are ready to hand off. It knows who owns what, so the specs it writes are actually assignable.
And tons more that I’m missing. In short, it turns AI into a Genius Consultant with a deep understanding of your business.
So if you’re looking to take your AI output to the next level…
All you have to do to get the Context Architecture Quickstart Kit:
Subscribe to AI Operator
Like this post by clicking the heart button below
Leave a comment below or reply to this email with the word CONTEXT, and I’ll send it over to you
Talk soon,
Dickie
P.S. — The frameworks in this newsletter are the same ones we teach live inside AI Writing Skool. If you’d rather build alongside a community and get your questions answered in real time, come join us here.




Built something like this over about 6 months of iteration rather than deliberately. Started with a single CLAUDE.md. Then added a memory file. Then separate files for secrets, contacts, project state. Ended up with a folder structure that the agent navigates by convention. The deliberate version you're describing here would have been faster.
One thing I'd flag though: the folder only works if the agent is told what it means. The 50-page context doesn't help if the instruction file doesn't tell the model where to look, when to look, and what to do with what it finds.
Context