Setting up your Claude Project as a solo founder

Everyone says to create a Claude Project. The advice is always the same: create a Project, add a system prompt with your context, upload relevant documents. Nobody shows you what this looks like for a solo founder building a B2B product.

This article fills that gap. Below is what to write and why, with explanations of what each section does and what happens if you skip it.

What a Project system prompt actually does

Before getting to the template: a Project system prompt is loaded into every conversation in that project, automatically. You do not have to repeat it. Claude starts every session already knowing what is in it.

The practical consequence: every piece of context you put in the system prompt is something you never have to explain again. Your company, your product, your customer, your current priorities — all of it. If you spend five minutes writing a good system prompt, you recover that time in the first week.

What to include

1. What you are building (one sentence)

Not a paragraph. One sentence that captures what the product does and who it is for.

"I am building a B2B SaaS tool that helps HR teams automate new hire onboarding — specifically the checklist and document collection process."

This determines what "good" looks like for every output Claude produces. Without it, Claude defaults to generic advice. With it, Claude knows whether to lean toward enterprise buyer language or SMB, whether to frame things around HR workflows or developer workflows, whether cost or compliance is likely to be the primary concern.

2. Where you are in the journey

"Pre-revenue, bootstrapped, no co-founder. Currently in active customer development — talking to HR managers at companies of 50–500 people."

This matters more than most founders realize. Claude's advice for a pre-revenue solo founder validating a market is different from advice for a funded startup hiring a sales team. Tell it where you are, so the advice is relevant to the actual stage you are in.

3. Your customer in one sentence

"My target customer is an HR Manager at a mid-size company (50–500 employees) who is managing new hire onboarding manually — spreadsheets, email chains, individual document requests."

This is your ICP (ideal customer profile) stated concisely. When you ask Claude to help you draft a cold email, write landing page copy, or prepare interview questions for customer discovery, this context determines whether the output is relevant or generic.

4. What you are working on right now

"Current focus: customer discovery. I am running 30-minute calls with HR managers and trying to understand whether the biggest pain is the tracking process, the compliance risk, or the new hire experience."

This changes every few weeks. Keep it updated. When you are actively working on customer discovery, Claude's suggestions for how to frame questions, analyze patterns, and synthesize what you are hearing will be much more targeted.

5. Your communication style

"I write in a plain, direct style. No corporate buzzwords, no padding. Short sentences. Conversational but professional."

Two sentences here eliminate the most common frustration with Claude-drafted content: the AI-smooth register that makes everything sound like it was written by a committee. Describe how you actually write, and Claude matches it.

The three things most founders skip

The stage. Without knowing whether you are pre-revenue, post-revenue, pre-product, or scaling, Claude defaults to generic startup advice that is often wrong for your specific moment. This is the single biggest impact addition.

The customer. Founders often write about their product but not their customer. Claude giving you advice about your product without knowing who you are selling to is like a copywriter writing without knowing the audience.

The current focus. The system prompt feels like something you set once and leave. But updating the "what I am working on right now" field every few weeks means Claude's input stays relevant to what you actually need this week, not what you needed three months ago.

Documents to upload

Beyond the system prompt, upload into the Project:

• Your current landing page copy — lets Claude match your voice and framing without being told
• Your customer discovery notes (anonymized) — lets Claude help you find patterns, synthesize themes, draft follow-up questions
• Any key email templates you have written — gives Claude a voice reference beyond what is in the system prompt

Do not over-upload. Three to five focused documents beats a Project stuffed with things Claude will rarely need. Quality over comprehensiveness.

The 15-minute setup

1. Open Claude, go to Projects, create a new project (name it "[Product] — Working Session" or similar)
2. In the project instructions, write the five sections above — 3–5 sentences total per section
3. Upload your landing page and any customer discovery notes you have
4. Start your next work session inside the project instead of in a regular conversation

The whole setup takes about 15 minutes. After that, every conversation in the project starts with Claude already knowing everything it needs to know about your product, your customer, and where you are.

---

For what a real working week with Claude looks like once the Project is set up, the founder workflow guide covers Monday through Friday. For the broader question of what to build with Claude vs. buy vs. prompt, this guide has the decision framework.

Further reading

• Collaborate with Claude on Projects — using Projects to organise founder workflows