You open Claude, paste in your context, explain what you’re working on, and get to work. Tomorrow you open it again and do the same thing. And the day after that. That’s not delegating. That’s training a new hire every single day.
Chat is fine for a quick answer. But the admin work that actually eats your week:
- managing client deliverables
- writing proposals
- building a workshop
you need systems for that. And that’s basically what Claude Projects are. They’re systems containers that have context and memory so they can pick up where you left off.
In this post, I’ll show you the setup that powers all of this, and three specific admin handoffs you can start using today. All in the browser. No Cowork, no new tool to learn.
Why chatting keeps costing you time
When you start a fresh chat, Claude walks in knowing very little about you, your clients, or what you’re trying to get done. So you write a giant prompt explaining the whole situation, you re-upload the same three files you uploaded yesterday, and then you get to work.
It’s the intern’s first day, every day. And it’s exactly why so many business owners think AI is more work than it’s worth.
Projects fix that. Because you codify the instructions (similar to an SOP). And it remembers what you worked on yesterday (similar to a real person). So you get to a working draft faster than starting from a prompt in the chat. Projects are the first step in being able to hand off real work to AI.
The setup that powers every handoff
Every project, no matter what you’re using it for, comes down to two things: instructions and files.
Instructions are the standing context for the engagement. Here’s a template I created that you can use every time.
Context is where you upload detailed files related to what you’re working on. For a client project I’d upload four: a CLIENT_CONTEXT file with stakeholders, decision-makers, products and competitors; a BRAND_GUIDELINES file; a WORK_HISTORY file you update after each milestone; and the PROPOSAL so Claude knows the scope. Save them as markdown ( the .md format strips the formatting, which is cheaper for you and easier for Claude to read). One warning : files you attach here do not auto-update. When something changes, you have to reattach it.
Handoff #1: Build a client brain
Create one project per client. Projects can’t share information with each other, which is the point. You want each client’s information siloed.
Once Claude knows the client, the handoffs stack up fast:
- Drop in a meeting transcript and ask it to pull action items, assign owners, and draft the follow-up emails. No more copy-pasting between your notetaker, your to-do list, and your inbox.
- Send it out for competitive research and have it come back as a memo you can share or use to shape your own recommendations.
- Use it to speed up client reporting, which is where most of us leave money on the table. I under-reported the value I delivered as a strategy consultant for years. Claude, sitting on your emails, notes, and deliverables, builds a far richer picture of what you actually did.
One more that people miss: ask Claude to review the project history and write a playbook. I did exactly this after building a few client priority plans – instead of reinventing the steps each time, I had a repeatable process. A playbook also makes a strong leave-behind when you roll off an engagement. It reminds the client what you did together and keeps you top of mind for referrals. If you’re using projects it’s a few prompts away instead of a week of digging through old docs.
Handoff #2: Turn it into a proposal writer
Set up a separate project for proposals. Here the instructions are mostly about you:
- your specialty and title
- the exact steps Claude should take when you hand it a brief
- the structure you want the proposal to follow
- your formatting rules.
For files, upload three to five past winning proposals so Claude can see what good looks like, plus your service and pricing catalog.
Then the flow runs like this: research the stakeholders and get a report back, then use that report to draft the proposal. Proposals aren’t a 10/80/10 job – they’re closer to 20/70/10, because you have to feed Claude the client’s website, your discovery-call notes, anything that points its thinking in the right direction. From the same project you can reformat the winning draft into a pitch deck, write the email that carries it, and draft the contract or MOU. When the proposal lands, move those conversations into the client project so Claude keeps the backstory.
Handoff #3: Set up a workshop wizard
Projects aren’t just for ongoing work. They’re just as useful for a one-time build like a workshop. Create a new project for each one.
Start with instructions: your role, the audience (Claude does noticeably better when it knows who it’s talking to), the goal, and the output you want. Say you’re running a 90-minute hands-on session for your local Chamber of Commerce, teaching small business owners to cut admin work with Claude, and you want an outline, talking points, Google Slides, and a PDF workbook.
For files, treat the upload space as a brain dump. Research reports, past workshop decks and workbooks, a link to a relevant video, screenshots, stray notes are all helpful here.
Then hand it off. Ask Claude to:
- organize the notes into an outline
- draft talking points
- generate text and images for the deck,
- draft the workbook. And connect to Canva or Gamma if you want Claude to build the finished collateral.
When to build a project instead of just chatting
You don’t need a project for everything. Build one when you keep re-explaining the same work every day, when Claude loses the thread because there are too many moving parts like multiple clients or multiple deliverables, or when it helps to keep the files, notes, and drafts together, like the workshop planner.
Market research, content systems, data analysis are all strong candidates for their own projects as well.
My recco is to start with building client projects because they’ll help keep you organized and on task.
A few times here I mentioned making projects even more powerful with Claude connectors. That’s a whole capability on its own – connecting Claude to the apps you already use – and it’s the next thing worth learning once your projects are running.
