The Six Layers of an AI Setup That Actually Works
Most people who say they "tried AI" never actually set it up. They opened ChatGPT, typed a few prompts, got answers that were fine but generic, and quietly decided the hype was overblown.
That's not AI failing. That's AI with no setup behind it, which is like judging a new hire by their first hour before you've told them anything about the business.
A real setup has six layers. Instructions, memory, connectors, skills, training, and a plan. Most people stop after layer zero, the blank chat box, and that's exactly why their AI feels mediocre. Here's what each layer does, in plain terms, and how to start on the one that matters most. None of this takes a developer.
TL;DR: A real AI setup has six layers: instructions (what you tell it), memory (what it learns), connectors (what it can see), skills (what it can repeat), training (whether your team uses it), and a plan (what order to build in). Most people stop at the blank chat box. Start with instructions this week; the rest stack on top.
Instructions: context you write on purpose. Start with one page on who you are and how you talk.
Memory: what it learns from working with you. Just use it, and correct it when it is wrong.
Connectors: live access to email, CRM, and files. Connect one app, read-only.
Skills: saved instructions you reuse. Save the thing you retype most.
Training: your team actually using it. Run one 30-minute working session.
Plan: what to automate, in what order. Name the workflow that costs the most time.
Layer 1: Instructions, so it knows who it’s working for
Instructions are what you tell the AI on purpose. Who you are, what your business does, how you want it to work. This is the layer you write. Memory, the next one, is the layer it learns on its own. Most real setups need instructions at three levels, and they stack on top of each other.
Org-level instructions: who the company is. This is the context that's true for everyone. The kind of company you are, your culture, who your clients are, what you sell, how you talk about it. Write it once and every conversation starts from it, so the AI never treats your roofing company like a software startup. This is exactly what we hand clients a fill-in template for in Cornerstone 3: The AI Setup Playbook.
Org-level instructions matter most when you set up a Teams AI system. That's a shared company account (Claude has a Team plan, and so do ChatGPT and Microsoft Copilot) where everyone works inside the same environment instead of each person on their own personal login. The company writes the org context once and the whole team inherits it. The side benefit is that your shared knowledge and approved tools live in one place, not scattered across a dozen private accounts.
Individual instructions: who you are. On top of the company layer, each person adds their own. Your role, what you're responsible for, how you like to communicate, the format you want things back in. Your CEO and your bookkeeper shouldn't get identical output, and this is the layer that makes sure they don't.
Project instructions: what this particular work is. The narrowest level. When you've got a specific, recurring body of work, a product launch, a major client, a hiring round, you can spin up a project with its own instructions: here's the goal, here's the background, here are the rules for this effort. Everything you do inside that project inherits that context, and when the work wraps, you archive it. It keeps one big initiative from bleeding into the context of everything else you do.
Layer 2: Memory, so you stop re-explaining your business
Memory is what the AI picks up about you and your business as you work, and holds onto, without being told again every time. If instructions are what you tell it on purpose, memory is what it learns on its own.
Out of the box, most AI chats forget everything the moment you close the tab. You re-explain who you are, what you sell, who your customers are, and how you like things done, over and over. It's exhausting, and it's the single biggest reason the output stays generic.
Turn memory on and that changes. Day one, it knows nothing. By day ninety, it knows your pricing, your top clients, the decisions you've made, your edge cases, and the shortcuts you prefer. The answers stop sounding like they're for "a small business" and start sounding like they're for yours. This is the layer that compounds: every week you use it, it gets a little more useful, like an employee who's been there long enough to know how things actually work.
You don't have to wait ninety days for that, though. Memory builds far faster when you feed it directly. Connect your live tools (that's the next layer) and load in a few knowledge files, your client list, your pricing, your process docs, last year's plan, and you've handed the AI your institutional knowledge on day one instead of making it pick the place up slowly. That's the difference between an assistant who absorbs your business over a quarter and one who walks in already briefed.
How to start: create one project or workspace for your business and drop in the basics. What you do, who you serve, how you talk, what you sell. Twenty minutes here changes every conversation after it.
Layer 3: Connectors, so it works from your real data
Connectors give the AI live access to the tools where your real information lives. Your email, your CRM, your accounting software, your calendar, your files.
Memory tells the AI about your business. Connectors let it see your business as it is right now. Without them, the AI is guessing from whatever you paste into the chat. With them, it can pull the actual invoice, the actual lead, the actual calendar, and answer from real data instead of a description of it.
This is the layer that turns AI from a clever writer into something that can actually do your work. It's also a whole topic on its own, which is why we wrote it up separately. If you want the walkthrough, start with Harnessing to 10x the Apps You Already Pay For.
How to start: connect one tool, read-only, the one you find yourself exporting reports from most. Ask it a question you usually answer by hand.
Layer 4: Skills, so you stop retyping the same instructions
Skills are reusable recipes. When you find a set of instructions that gets the result you want, you save it once and run it on command instead of rebuilding it from scratch every time.
Think about the things you explain to the AI repeatedly. How you want your weekly numbers summarized. The format your proposals follow. The way you screen an inbound lead. Right now you're probably re-typing those instructions every single time, and getting slightly different output because the wording drifts.
A skill fixes that. You teach the AI the task once, name it, and call it up whenever you need it. Same instructions, consistent result, no reinventing. The trick is to tell it what you want and what a good result looks like, not every keystroke to get there. Loose and clear holds up. Over-scripted breaks the moment something shifts.
How to start: pick the one thing you ask the AI to do most often and save it as a reusable skill. You've now got a process that runs the same way every time.
Layer 5: Training, because a setup nobody uses is worth nothing
Training is the human layer. The AI can be set up perfectly and still deliver zero return if your team doesn't actually use it.
This is the layer everyone skips, and it's the one that quietly kills most AI rollouts. One person gets excited, sets things up, and assumes everyone else will pick it up by osmosis. They won't. People default to the way they've always worked unless someone shows them a better one that's worth the switch.
You don't need a formal program. You need a few working sessions where people bring real tasks they hate and watch AI knock them out. Adoption follows usefulness. Show someone their own Tuesday-morning headache disappear and you won't have to sell them on it again.
How to start: pick the one task your team complains about most and run a 30-minute session solving it together, live.
Layer 6: A plan, so you get ROI instead of overwhelm
A plan is the order you do things in. What to set up first, second, and third, based on where the time and money are actually leaking.
Without one, people try to automate everything at once, get overwhelmed, and abandon the whole thing. The businesses that get real value are almost always the ones that started narrow. One role, one painful workflow, one clear win, then expand from there.
The sequence matters more than the speed. Get a visible result in the first couple of weeks and the rest of the rollout sells itself, because now everyone's seen what "good" looks like. Try to boil the ocean and you'll be back to the abandoned-tab stage by month two.
Figuring out that order is its own small piece of work, and it's worth doing on purpose. That's what an AI readiness assessment is for: a quick, honest look at how accessible your data is, which of your workflows are actually documented, and where your team's skills sit, so you can name the two or three places AI pays off first instead of guessing. You can run a rough version yourself, or have someone walk you through it.
How to start: name the one workflow that costs you the most time every week. That's where the plan begins. Everything else waits its turn.
What trips people up
Three patterns, and they're all about skipping layers.
Jumping straight to a plan with no memory or connectors underneath it. You can't automate work the AI can't see or remember. Build the foundation first, then sequence what to automate.
Treating it like a search engine. People type a question, get a so-so answer, and quit, never realizing the answer was so-so because the AI had no memory and no access. The setup is what makes the answers good.
Stuffing everything into memory on day one. More isn't better. A tight, high-signal set of business basics beats fifty documents the AI has to wade through. Keep it clean and add as you go.
Where to start this week
Do layer one, but don't stare at a blank doc trying to write your instructions from scratch. Flip it around and let the AI interview you. Paste this into Claude, ChatGPT, or Copilot to get going:
"I'm setting up an AI workspace for my business and I want you to help me build the instructions and knowledge it should run on. Interview me one question at a time. Start by asking for my website and anything else that explains what we do, then ask about my customers, my services, my goals for the year, how I want you to communicate, and whatever else you'd need to represent my business well. When we're done, write it up as a clean set of instructions I can save."
Feed it your website first, plus any marketing material that already describes what you do, a brochure, a capabilities deck, your about page. That alone gets you most of the way.
For extra credit, hand over whatever else captures how the company actually runs. Your strategic goals. The operating framework you use, if you run on Rockefeller Habits, EOS, or something similar. A breakdown of what each department does and who the key people are. Even job descriptions. The more of your real institutional knowledge the AI can see, the faster it stops sounding generic and starts sounding like it works there.
That's the foundation everything else stacks on. Once your instructions are in place, let memory build, add a connector, save a skill, and you're already past where most people who "tried AI" ever got.
Questions we hear about AI setup
Do I need a developer to set any of this up?
No. Every layer here happens inside the AI platform’s own settings: instructions are a settings page, connectors are a menu of toggles, and skills are saved text. If you can fill out a form, you can build all six layers.
How long does a real AI setup take?
The first layer takes an afternoon. A working six-layer setup for a small team usually lands in weeks, not quarters, and you feel the difference after the first week because the AI stops giving generic answers.
Which AI should I set up: Claude, ChatGPT, or Copilot?
The layers are the same on Claude, ChatGPT, Gemini, and Copilot. Pick the one that connects best to the tools you already pay for, then build the layers there. Switching later is easier than you’d think, because your instructions and skills are just text.This is part of the Practical AI Toolkit series. For the full company-wide setup framework, see Cornerstone 3: The AI Setup Playbook. Read next: Project Memory Done Right.