I Set Up Claude Projects in 20 Minutes. It Replaced Copilot for My Entire Business.
AI

I Set Up Claude Projects in 20 Minutes. It Replaced Copilot for My Entire Business.

Andrew MoonApril 28, 20267 min read

Microsoft charges $30 per user per month for Copilot. On top of your existing Microsoft 365 license.

For a 10-person service business, that's $300+ a month for an AI that most people I talk to find frustrating, confusing, and hard to get consistent value from.

I set up Claude Projects in 20 minutes. It replaced Copilot across my entire business.

This is the walkthrough.


Why I'm Qualified to Say This

I spent most of my 30 years in tech as a Microsoft partner. I ran a managed services company for a decade. I deployed Microsoft 365 for clients. I sold Copilot licenses. I've watched what actually gets used and what gets ignored.

A while back I made a decision.

I dropped every Microsoft 365 product in my business except Outlook. Word, Excel, PowerPoint — gone. I replaced them all with ClickUp. And when it came to AI, I chose Claude instead of Copilot.

That's not a hot take. That's a decision I made after using both. After deploying both for clients.

Here's the honest version of why.

The Microsoft 365 AI experience is built for enterprise. It's built for organizations with IT departments, SharePoint infrastructure, compliance teams, and Entra tenant administrators. If you're in that world, Copilot makes sense.

If you're running a 10 or 20-person service business, you're paying $30 per user per month on top of your existing M365 license for a tool embedded inside an ecosystem that was never designed for how you actually work.

I still use Outlook. Exchange is solid. I'm not here to tell you to rip everything out.

But Word? Excel? PowerPoint? ClickUp does what I need — better, faster, and without the licensing complexity. And for AI, Claude does what Copilot promises — without the infrastructure overhead.


The Feature Most Claude Users Have Never Touched

Most people use Claude the same way they use Google.

They open a new chat. They type a question. They get an answer. They close the tab.

Every conversation starts from zero. Claude knows nothing about who you are, what business you run, who your clients are, or how you like to work.

That's not a tool. That's a search engine with better sentences.

Claude Projects changes this completely.

A Project is a persistent workspace where you tell Claude everything about your business — once. Your company, your clients, your voice, your processes, your context. Every conversation inside that Project starts with all of that already loaded.

Claude doesn't just know what you asked. It knows who you are.

That's the feature most Copilot users are paying $30 a month to try to get. And most Claude users have never touched it.


How to Set It Up (The Exact System)

The setup has two parts: Project Instructions and the Knowledge Base. Both are inside Claude.ai under "New Project."

Part 1 — Project Instructions

This is where you tell Claude who you are, what you do, and how you want it to behave. Think of it as the briefing document you'd give a new team member before their first day.

Most people leave this blank. That's the mistake.

Here's the structure I use — illustrated with Vandelay Technology Solutions, the demo MSP I use in the tutorial video:

You are working for Vandelay Technology Solutions, a managed IT services company 
based in Columbus, Ohio.

About the business:
- We serve professional services firms — accounting practices, legal firms, and 
  wealth management advisories — 10 to 50 employees
- Our core service is fully managed IT with compliance built in
- Our tone is direct, plain English, no technical jargon
- Our key differentiator is compliance-first IT for regulated professional services 
  firms — most MSPs treat compliance as an add-on, we treat it as the foundation

Key context:
- Owner: Art Vandelay, 20+ years in IT, former CPA-turned-MSP-founder
- Team: 8 staff — 6 technicians, 1 ops, 1 business development
- Current focus: Expanding into wealth management vertical, launching vCIO offering

How I want you to respond:
- Write in Art's voice — direct, short sentences, no padding
- Emails are signed "Art" not "Vandelay Technology Solutions"
- Never open with "I hope this email finds you well"
- Flag it if you think I'm about to make a mistake

That last line is the one most people don't include. "Flag it if you think I'm about to make a mistake."

That's not a chatbot instruction. That's a team member instruction. Claude will now push back on bad ideas instead of just executing them.

Part 2 — The Knowledge Base

The knowledge base is where you load the documents Claude needs to actually know your business. Five files. Thirty to sixty minutes to build if you're starting from scratch.

Here's what I upload to every project:

1. ICP Profile. One page describing your ideal client. Industry, size, pain points, what they're afraid of, what success looks like. Claude uses this every time it writes anything client-facing.

2. Signature Services. What you offer, how you price it, what's included, what's not. Stops Claude from quoting services you don't offer or pricing you'd never send.

3. Voice Sample. Three writing samples — a proposal follow-up, a monthly report, a LinkedIn outreach. This is how Claude learns to sound like you, not like a generic AI output. This file alone changes the quality of every output.

4. Objections and Responses. The three or four things prospects always push back on. With your actual responses. Claude can now draft follow-up copy after a tough meeting using your words, not generic ones.

5. Current Priorities. A one-pager: what you're working on right now, what the goal is for this quarter, what decisions you're currently navigating. Claude keeps its suggestions relevant to where you're actually going.


The Before/After

Here's what the same prompt looks like without and with the project.

Prompt used in both cases:

Write a short follow-up email to a prospect after our initial discovery call.
They're a managing partner at an accounting firm, 22 employees, Columbus area.
They mentioned compliance documentation was a gap but seemed hesitant on price.

Without the project: Serviceable. Professional. Could be from any IT company in any city. No personality. No reference to the compliance gap we just discussed. Nothing that sounds like Art.

With the Vandelay project loaded: The email references compliance documentation specifically. It acknowledges the price hesitation directly, the way Art actually handles it. It's signed "Art." It sounds like Art wrote it in five minutes after a real conversation.

Same prompt. Same Claude. Completely different output.

That's what $300 a month in Copilot licenses is trying to buy. It's already inside Claude. Most people just haven't set it up.


One More Thing Worth Knowing

A few weeks ago, Anthropic released a native Microsoft 365 connector for Claude. Outlook, Teams, SharePoint, OneDrive — all connecting directly into Claude, on every plan including free.

I don't use it personally. I dropped Word, Excel, and PowerPoint a while back and moved everything to ClickUp. But if you're not ready to make that move yet, the M365 connector means you can get the Claude Projects experience inside the tools you're already using. That's a meaningful upgrade over Copilot at a fraction of the cost.


Your Move

Open Claude.ai. Click New Project.

Write five sentences about your business in the Project Instructions field.

That's it. The rest you build over time. Claude gets better as you add more context. The project grows with you.

Take the free AI Readiness Assessment to see exactly where your business sits on the AI adoption curve: orangenomad.com/ai-assessment

If you want to build this alongside other business owners doing the same thing, the Build With AI Cohort waitlist is open: orangenomad.com/ai-rollout

Andrew Moon

Andrew Moon is the founder of Orange Nomad and the creator of the 3Cs Framework — a repeatable marketing system built for MSP owners under $5M who are great at IT but struggling to find clients. Not a marketer who learned about MSPs. An MSP owner who learned marketing — the hard way.

Share