Claude Projects: Build a 24/7 AI Client Portal in 1 Hour

Who This Is For

This guide is for freelancers, consultants, and small agency owners who are still answering the same client emails on repeat — "What's the status?", "How do I send you files?", "When will this be done?" If you're spending 2-3 hours a week on client communication that follows the same script every single time, this is exactly what you need.

You don't need to know how to code, and you don't need to have used Claude before. If you've got clients, a basic understanding of what your work involves, and 60 minutes to spare, you can build something that runs for you around the clock.

What You'll Be Able to Do After This Guide

• Set up a Claude Project that automatically handles your top 10-15 client FAQs — cutting your inbox response time from hours to zero
• Create a fully structured client onboarding flow that walks new clients through your process, pricing, and next steps without a single email from you
• Build a living knowledge base inside Claude that updates as your business changes — so your AI portal never goes stale

What Claude Projects Actually Are (And Why They're Different From a Normal Chat)

Most people use Claude like a search engine — they type a question, get an answer, close the tab. Claude Projects are completely different. They let you create a persistent AI workspace with a custom System Prompt, uploaded documents, and a memory of everything you've told it — so every conversation Claude has starts from the same informed baseline.

Think of it like hiring a team member and spending one hour briefing them on everything about your business. Except that team member never forgets, never sleeps, and can talk to 10 clients at the same time.

Here's the core mechanic: when you create a Project, you write a System Prompt that tells Claude exactly who it is, what it knows, and how it should behave. You also upload supporting documents — your onboarding guide, your FAQ sheet, your pricing doc, your contract terms. Claude reads all of it and uses it as its reference for every single conversation inside that Project.

The result? A client asks "What do I need to send you to get started?" and Claude doesn't guess — it pulls from your actual onboarding doc and replies in your voice, with your exact process. That's the shift from generic AI to a real business tool.

Building Your System Prompt: The Foundation Everything Else Rests On

Your System Prompt is the most important thing you'll write in this whole setup. Get it right and your portal feels like you. Get it wrong and it sounds like a confused chatbot. Here's how to build it in four steps.

Step 1: Define the role. Tell Claude exactly what job it's doing. Don't be vague. Instead of "You are a helpful assistant," write something like: "You are the client-facing assistant for [Your Name/Studio Name], a freelance brand designer. Your job is to help new and existing clients understand the design process, answer questions about project timelines, collect onboarding information, and direct clients to the right next step."

Step 2: Set the tone and rules. Tell Claude how to speak. Write: "Match the tone of a professional but warm creative studio. Use plain language. Never use jargon. If a client asks something you're not sure about, say: 'Great question — let me flag that for [Your Name] to confirm. In the meantime, here's what I know…'" This prevents Claude from making up answers when it hits the edge of its knowledge.

Step 3: Give it your key facts. Drop in your working hours, turnaround times, revision policy, payment terms, and anything clients always ask about. Write it conversationally — "We typically turn around initial concepts within 5 business days of receiving all onboarding materials. Revisions are included up to 2 rounds."

Step 4: Define what it should always do at the end of each reply. A simple instruction like "End every response by asking if the client has any other questions or by directing them to the next clear action" makes the whole experience feel guided instead of abrupt.

Uploading Documents That Turn Claude Into a Full Client Portal

Once your System Prompt is live, you add documents to the Project — this is where the real power kicks in. Claude reads these files and treats them as its knowledge base for every conversation.

The three documents to upload first:

1. Your Onboarding Guide — A simple 1-2 page doc (PDF or plain text works great) that walks a new client through exactly what happens after they book you. Include: what you need from them, how to send it, what the first week looks like, and when they'll hear from you. If you don't have one yet, open a Google Doc right now and write it in 20 minutes — it doesn't need to be fancy.
2. Your FAQ Document — Write out the 10-15 questions you get most often and your exact answers. Questions like: "Do you do rush jobs? What if I need more revisions? How do I pay? What file formats do you deliver?" Claude will pull directly from this document when clients ask — which means your answers are always consistent and always sound like you.
3. Your Project Status Template or Service Menu — Upload a breakdown of your services, what's included in each package, and what the typical timeline looks like. When a client asks "I need a logo, what does that involve?", Claude walks them through it using your actual process.

After uploading, test the portal yourself. Ask it the questions your clients ask most. If Claude gives a weird or off-brand answer, the fix is almost always in your document — either something wasn't there, or it was written ambiguously. Tighten the document and re-upload.

Making Your Portal Feel Alive: The Technique Most Guides Don't Cover

Here's what separates a good Claude Project from a great one: dynamic escalation logic. Most people set up their Project and leave Claude to figure out when it's out of its depth. The problem is, Claude will try to answer even when it shouldn't — and a confident wrong answer to a client is worse than saying nothing.

You fix this by building explicit escalation rules into your System Prompt. Something like: "If a client asks about a specific project update, a custom quote, a complaint, or anything involving money or contracts, do not attempt to answer. Instead, say: 'This one's better handled directly by [Your Name]. I've noted your question — expect a reply within [X hours]. In the meantime, is there anything else I can help clarify?'" This keeps Claude in its lane and keeps you in control of the sensitive stuff.

The second advanced move is intake collection. Your portal can double as an onboarding form. Write a sequence into your System Prompt like: "When a new client introduces themselves or says they're interested in working together, ask them the following questions one at a time: 1) What type of project are you looking for help with? 2) What's your approximate timeline? 3) Do you have a budget range in mind? After collecting all three, summarize their answers and tell them what their next step is." Now your portal is pre-qualifying leads and collecting info before you've even opened your laptop.

Finally, version your Project when your business changes. Every time you update your rates, add a service, or change your process, update the documents in the Project and note the date in your System Prompt header. A quick comment like "# Last updated: [date]" at the top keeps you from accidentally leaving old information running.

Common Mistakes (and How to Fix Them)

• Mistake: Writing a System Prompt that's only 2-3 sentences long → Fix: Your System Prompt should be at least 200-400 words. The more context Claude has about your business, your voice, and your rules, the more accurate and on-brand every answer becomes.
• Mistake: Uploading documents with vague or inconsistent language (like a Google Doc full of half-finished notes) → Fix: Before uploading, clean every document into clear, declarative statements. Claude reads your documents literally — if your FAQ says "we usually get back to people pretty quickly," Claude can't give a client a real answer. "We respond to all enquiries within 24 business hours" gives Claude something concrete to work with.
• Mistake: Setting up the Project and never testing it as a client would → Fix: Spend 15 minutes roleplaying as a brand new client. Ask confusing questions. Ask edge-case questions. Every time Claude stumbles, that's a gap in your documents or System Prompt — fix it before your real clients find it.

Your Next Steps

1. Right now (next 5 minutes): Open Claude, click "Projects," and create a new Project. Give it a name like "[Your Name] Client Portal." Write your first System Prompt draft — even an imperfect one. The act of starting is what matters.
2. This week: Write and upload your three core documents — Onboarding Guide, FAQ Sheet, and Service Menu. Then spend 30 minutes testing the portal yourself. Share the link with one trusted client or colleague and ask them to try breaking it.
3. In 30 days: Track how many client emails you didn't have to write because your portal handled them. Most freelancers who do this report saving 3-5 hours a week by the end of the first month. Use that time to take on one more client — or just close your laptop earlier.