Stop Using Claude Like a Chatbot: Build a Work System Instead
Most people use AI one conversation at a time. They explain the context, set the format, finish the task, and a few days later do exactly the same again. For recurring work, that defeats the point.
Claude Projects fixes this. You set up the context and instructions once, then use separate conversations for each task.
Give each Project one job
A Project called "Work" is too broad. A Project called "Weekly Management Assistant" tells you, and Claude, exactly what belongs there.
Write its purpose in one sentence. For example: this Project helps me prepare for recurring management meetings, organise actions and turn rough notes into clear follow-up communication.
Write working instructions, not a magic prompt
Give Claude the instructions you would give a capable new colleague:
- Use clear British English.
- Keep routine answers concise.
- Separate facts from assumptions.
- Do not invent information when something is missing.
- When reviewing documents, identify risks, decisions, deadlines and actions.
Keep the knowledge base small and useful
Upload only what Claude needs for this job: a meeting template, an action-note structure, recurring terminology. More documents do not automatically mean better answers.
Confidential or restricted information stays confidential inside a Project too. Give AI what it needs to do the job, not everything you have.
Separate reusable context from individual tasks
The Project holds your standing instructions and reference material. Each conversation holds one task: preparing Monday's meeting, reviewing this week's notes, comparing two proposals.
Ask better questions than "summarise this"
Instead of "summarise this document", try: identify the main conclusion, the decisions required, the three biggest risks, anything unsupported, and the next actions.
Instead of "which proposal is better?", try: compare these on cost, difficulty, risk, time to value and unsupported assumptions, then tell me what information I still need.
The 5-part instruction structure
- Purpose. What is this Project for?
- Role. How should Claude help?
- Rules. What should it always do or avoid?
- Output. How should answers normally be structured?
- Uncertainty. What should happen when information is missing?
Start with one workflow
Pick one task you do every week. Build one Project for it, use it for a week, and refine the instructions where it misunderstands you. Then add the next one.
Watch the full walkthrough on YouTube.
Your next step
Have someone build an AI automation for my business?
If the same admin task eats hours every week, a small custom AI workflow can usually take most of it away. You describe the problem; a specialist team scopes and builds it.
See the fastest fixWant numbers for your own business? Try the admin time calculator or the AI readiness quiz.
More guides
- How to Hire a Freelancer on a Small Budget (and Get It Right First Time)Write a one-page brief, run a small paid trial and share access safely, so a freelancer can take admin off your plate without the risk.
- Use AI to Write Customer Emails in Your Own Voice: A 20-Minute SetupSet up ChatGPT or Claude once with your tone and templates, then draft quotes, follow-ups and replies in seconds, safely.
- Do Sole Traders Need a Business Bank Account?When a separate business account is required, when it is just a good idea, and what to compare before you open one.