Most people quit on AI after one bad answer. The ones who win treat it like a new hire they train over time. Here’s the 3-level setup and the prompts that make it get better every week.
MIT’s NANDA initiative found that about 95% of company AI pilots stall with little to no measurable impact on profit and loss. The cause wasn’t the models. MIT blamed a "learning gap": generic tools don’t learn or adapt to how a company actually works. (Fortune on the MIT report)
I see the same thing with people. They type a vague prompt, get a mediocre answer and quit, like firing a new hire an hour into their first day. The fix is to stop expecting an expert on day one and onboard it over a few weeks.
01
Run the onboarding interview
A new hire knows nothing about your business on day one. You train them on your goals, voice, systems and workflows, and a few weeks in they run real work without you. AI works the same way. Instead of a one-line prompt, let it interview you.
All that training has to live somewhere, or you start over every chat. Pick the level that fits where you are. You can climb later.
01
Level 1 is a Claude Project
In Claude, click Projects, then New project. Click Set project instructions and paste your Onboarding Brief. Then upload your files, like your brand guide, past work and SOPs. Every chat in that Project starts with all of it. Free accounts get up to five Projects. This is where almost everyone should start.
02
Level 2 is turning repeat work into Skills
Anything you do every week, turn into a Skill Claude runs the same way every time. Open a chat, describe the workflow and attach your templates or examples. Claude asks about your process, writes the skill file and packages it for you. Save it, then make sure it’s switched on in your skills list (under Customize, which is being renamed Plugins). Skills need Code execution and file creation (called Create and edit files in the newer layout) turned on under Settings, then Capabilities. (Anthropic’s walkthrough)
03
Level 3 is Claude Code and agents
When you want to go all in, move into Claude Code. Give it a folder with a CLAUDE.md file that holds your context, and it loads that file at the start of every session. Then build agents that run multi-step work for you. (How CLAUDE.md works)
01
Run the review at the end of every session
This is the habit that makes everything above compound. Most people get an okay answer, close the tab and start from scratch tomorrow. Instead, have the AI look at what you corrected and rewrite its own instructions. Then paste the new version into your project instructions.
Do this for a couple of weeks and your AI stops acting like a chatbot. It gets better every week because it’s writing its own training from your real feedback.
Don’t Boil The Ocean
Don’t try to train it on your whole business at once. Pick the one task you repeat most, get it running well, then add the next. One workflow at a time is how you end up on the right side of that 95%.