Guide

Claude Projects for SMB Owners

Three ready-to-build Projects for a $5–50M services firm — proposals, onboarding, and monthly financial reviews. Full system prompts and file lists below.

Last updated: May 11, 2026 · ~12 min read

A Claude Project is a workspace inside claude.ai with two things attached: a long system prompt that tells Claude how to behave, and a set of reference files Claude reads at the start of every conversation. You build it once. Your team uses it forever — or until the workflow changes.

Most SMB owners don't need to build agents. They need to take the three or four recurring tasks that eat senior time — writing proposals, onboarding new clients, reviewing the monthly P&L — and turn each one into a workflow a junior on the team can run, with Claude doing 70–80% of the draft.

That's what Projects are for. Below are three you can build this week, each with the actual system prompt and the files we recommend uploading.

Claude Projects vs Custom GPTs

Both work. They're built differently. Pick by the shape of your workflow, not by which AI brand you prefer.

 Claude ProjectCustom GPT
Plan requiredClaude Pro (~$20/mo) or Claude Team (~$30/user/mo)ChatGPT Plus (~$20/mo) to use; Plus or Team to create
How files are readClaude reads the full file every conversation (~200K token context)Retrieval-style — the model pulls relevant chunks from uploaded files
Behavior on long reference docsCoherent across the entire doc; nothing is "missed"Can miss context if relevant chunks aren't retrieved
System prompt lengthLong (~32K tokens) — detailed instructions, anti-patterns, style rulesShorter (~8K tokens) for the "instructions" field
SharingPersonal on Pro; shared with your team on TeamPrivate, your workspace, or public to all ChatGPT users
Best forWorkflows where the model needs the whole reference doc every time (proposals, financial reviews, structured drafting)Workflows that pull narrow snippets, or use Custom Actions to hit an API

Three Projects to build this week

Each one targets a specific senior-time bottleneck. Copy the prompt, gather the files, ship in 30–60 minutes.

1

Proposal Drafter

Turn discovery notes into an 80%-there proposal draft in one prompt.

When to use it: Your firm wins work via written proposals or SOWs and your most senior person spends 4–6 hours per proposal. A junior could prep the first draft if they had your templates, past examples, and pricing in one place.

System prompt

You are the Proposal Drafter for [Firm Name], a $10M [services type] firm.

You draft client proposals using:
1. The discovery notes uploaded for THIS deal
2. Our standard proposal template (proposal-template.md)
3. Our service catalog with pricing (service-catalog.md)
4. Three past proposals as style reference

When asked to draft a proposal:
- Start by listing the 3 most important things you read in the discovery notes. Confirm with me before drafting.
- Use first-person plural ("our team", "we will") — never "I".
- Match the structure of the template exactly: Executive Summary → Scope → Approach → Timeline → Team → Investment → Next Steps.
- Cite specific lines from discovery in the Scope section — quote the client's own words for what they care about.
- Pricing: pull from service-catalog.md. Never invent numbers. If discovery doesn't make the price obvious, ask me what tier.
- Length: 1,200–1,800 words. The Executive Summary fits on one screen.
- Tone: confident, plain, no jargon. Read like a senior consultant talking to a CEO, not a marketing brochure.

What you must NOT do:
- Don't make up case studies or client names.
- Don't claim certifications, awards, or partnerships unless they're in service-catalog.md.
- Don't promise timelines or outcomes unless discovery gives you a date or metric to work from.

Output the proposal as a single markdown document I can paste into Google Docs.

Files to upload

  • proposal-template.md — your firm's standard structure
  • service-catalog.md — what you sell, with current pricing
  • 3 past won proposals (anonymized) as style reference
  • Per-deal: discovery call notes (uploaded fresh in each conversation)

What a $10M services firm gets out of it

Junior consultant runs discovery, drops notes into the Project, asks 'draft a proposal for [Client]'. Project produces an 80%-there draft. Senior reviews and edits for ~45 minutes instead of writing for 4 hours. Same proposal quality, ~75% senior time reclaimed.

2

Client Onboarding Coach

Run a tight 30-day onboarding for every new client without partner time.

When to use it: New clients sign and the first 30 days are ad-hoc. Partner handles kickoff, things slip, clients churn at six months. You have a real playbook somewhere but nobody follows it because it's 12 pages long.

System prompt

You are the Client Onboarding Coach for [Firm Name].

You help our team run a tight 30-day onboarding for every new client. You have:
- Our onboarding playbook (onboarding-playbook.md) — the 30-day sequence
- Our 12 most common kickoff questions (kickoff-questions.md)
- A template for the Week 1 client briefing doc (week-1-template.md)
- Templates for 30/60/90 check-in emails (check-ins/)

When a team member tells you a new client just signed:
1. Ask 4 questions: client name, primary contact, signed package/SOW summary, who's leading the engagement internally.
2. Output a day-by-day plan for the first 30 days, including: who-does-what, what document each step produces, and which template applies.
3. Draft the Week 1 briefing doc populated with the deal context.
4. Draft the welcome email from the engagement lead, the kickoff invite, and the Day 30 check-in.
5. Flag risks: anything from the SOW that's vague, dependent on the client's data, or relies on someone we haven't onboarded yet.

Style:
- Plain language. No "synergy", "leverage", "roadmap".
- Short paragraphs. Specific dates ("by Friday EOD") not vague phrases ("soon").
- All deliverables in markdown. No HTML, no fancy formatting.

What you must NOT do:
- Don't invent a contact's name, title, or email. Ask the team member.
- Don't promise meeting times — propose options.
- Don't auto-send anything. Output drafts the team reviews before sending.

Files to upload

  • onboarding-playbook.md — your 30-day onboarding sequence
  • kickoff-questions.md — the 12 most common kickoff questions
  • week-1-template.md — Week 1 client briefing template
  • check-ins/ — 30/60/90 check-in email templates

What a $10M services firm gets out of it

New client signs Monday. Account manager opens the Project and says 'we just signed [Client]'. By Tuesday EOD: full 30-day plan, populated briefing doc, drafted welcome email and kickoff invite, flagged risks. Engagement lead reviews and sends. What used to be 2–3 days of partner time becomes 90 minutes of review.

3

Monthly Financial Reviewer

Turn a bookkeeper export into a 1-page CFO review in 20 minutes.

When to use it: Your fractional or part-time CFO reviews the P&L monthly. Each review takes 2–3 hours of pulling reports, spotting anomalies, and drafting commentary. A Project can do the first 70% in 20 minutes.

System prompt

You are the Monthly Financial Reviewer for [Firm Name], a $10M services firm.

Every month our bookkeeper exports a P&L, balance sheet, A/R aging, and utilization report. I upload all four. You produce a 1-page CFO review.

Your reference files:
- chart-of-accounts.md — what every line item means in our books
- prior-12-months-baselines.csv — last year's monthly numbers as comparison
- review-template.md — the structure for the 1-page review
- known-anomalies.md — recurring things to ignore (e.g., bonus accrual in December)

When I upload the month's files:
1. Confirm: "Reviewing [Month] [Year]. P&L total revenue: $X. Compare to prior month $Y, prior year same month $Z. OK to proceed?"
2. Produce the 1-page review in this structure:
   - Headline number: revenue, gross margin %, utilization % — vs. prior month and prior year, with direction arrows.
   - What changed: 3-5 bullets of the biggest moves (>10% variance line items). Each bullet cites the GL line and the dollar amount.
   - Concerns: anomalies that don't have an obvious cause. Be specific — "March legal expense up 4x ($12K vs. $3K baseline) — no matching project; ask Tracy why."
   - Looks healthy: 2-3 things to acknowledge as on-track (only if true).
   - One ask: the single question I should bring to the partner meeting.

Style:
- Numbers, not adjectives. "Up 14% MoM" not "significantly higher."
- Cite the source. "Per P&L line 5210" or "per A/R aging."
- 1 page. ~400 words. If it doesn't fit, you're padding.

What you must NOT do:
- Don't invent numbers. If a line item is missing or unclear, flag it instead of guessing.
- Don't recommend hires, raises, or layoffs — that's the partner's call.
- Don't editorialize on strategy. Stick to what the numbers say.

Files to upload

  • chart-of-accounts.md — what every line item means in your books
  • prior-12-months-baselines.csv — last year's monthly numbers
  • review-template.md — the structure for the 1-page review
  • known-anomalies.md — recurring things to ignore (bonus accrual, etc.)
  • Per-month: P&L, balance sheet, A/R aging, utilization report (uploaded fresh each cycle)

What a $10M services firm gets out of it

Fractional CFO opens the Project on the 5th of every month, uploads four reports from the bookkeeper. Twenty minutes later, has a draft 1-page review with headline number, what changed, concerns, and one ask for the partner meeting. CFO edits for 30 minutes and sends. Total CFO time per month: ~50 minutes vs. the old 2–3 hours.

How to set up your first Project

Eight steps. Plan on 30–60 minutes once the reference files are ready.

  1. 1

    Pick the workflow

    Start with the workflow that eats the most senior time. Proposals, monthly financial reviews, and client onboarding are good defaults for a $5–50M services firm.

  2. 2

    Inventory the reference files

    List every document a senior person currently reads when they do this task — templates, past examples, pricing sheets, playbooks, chart of accounts. Those are your Project files.

  3. 3

    Clean and convert

    Reference files should be plain markdown or text. PDFs work but markdown is cleaner. Anonymize anything client-specific you're using as a style example.

  4. 4

    Write the system prompt

    Tell Claude: who it is, what files it has, what to do, what NOT to do, and what style/format to output. Use the three Projects on this page as a starting template.

  5. 5

    Create the Project in Claude

    In claude.ai, click your sidebar → New Project → name it → paste the system prompt → upload the reference files.

  6. 6

    Test with a real input

    Run yesterday's discovery notes, this month's bookkeeper export, or a recent new client through the Project. Compare the output to what your senior person would have written.

  7. 7

    Iterate the prompt

    Run 3–5 real inputs through it. Add specific anti-patterns to the 'what you must NOT do' section as you spot them. Two rounds of iteration usually gets a Project to 80% senior quality.

  8. 8

    Share with your team

    Upgrade to Claude Team if you haven't. Add the Project to a shared workspace so everyone on your team gets the same instructions and reference files.

What you need to actually build this

A Claude plan that supports Projects. Anthropic's pricing page has the current rates. Pro is one-person; Team is the right choice if you want partners or account managers to share the Project.

Your reference files, in markdown or plain text. The biggest gating step isn't Claude — it's having your templates, playbooks, and chart of accounts in a state you'd actually hand to a junior. If they don't exist cleanly anywhere today, building one Project forces you to create them. That work compounds.

One workflow at a time. Don't try to build all three at once. Pick the one with the biggest senior time drag. Ship it. Use it for two weeks. Iterate. Then start the next one.

Data hygiene. Anthropic doesn't train on Team and Enterprise data by default — but treat Project files like a Google Doc shared with a colleague. Don't upload PII, customer PHI, or NDA-covered content without checking the underlying contract.

Frequently asked questions

Claude Projects vs Custom GPTs — which should I use?

For SMB owners running internal workflows where the AI needs to read 100% of a reference doc every time (a template, a playbook, a chart of accounts), Claude Projects wins because the model reads the full context every conversation. For workflows that retrieve small snippets from a big knowledge base, Custom GPTs are fine. Most SMB use cases — drafting, reviewing, onboarding — fit Claude Projects better.

What Claude plan do I need to use Projects?

Claude Pro (around $20/month) lets one person use Projects. Claude Team (around $30/user/month, 5-user minimum) lets your team share a Project — same instructions, same files, everyone gets the same output quality. For a $10M services firm, Team is usually what you want.

Can my team share a Claude Project?

Only on the Team plan or above. On Pro, Projects are personal. If you want consistent outputs across multiple partners drafting proposals or running onboarding, you need Team.

How do I keep client data safe inside a Project?

Anthropic doesn't train on Claude Team and Enterprise data by default. Treat Project files like you'd treat a Google Doc — don't upload anything you wouldn't share with a colleague. Avoid PII, customer PHI, or NDA-covered material unless you've checked the underlying contract.

How long does it take to set up the first Project?

30–60 minutes for your first one once you have the reference files (templates, playbooks, chart of accounts) in a state you can upload. The hard part is curating the files, not configuring the Project.

How is this different from just pasting a prompt every time?

Three things: (1) the system prompt is reusable — every conversation starts with the same instructions; (2) the reference files are loaded once and available across every conversation; (3) on Team, your whole org gets the same setup.

What's the file size limit?

Per Anthropic's docs, each file is up to 30MB and total Project context is around 200K tokens (roughly 500 pages of text). That's plenty for templates, playbooks, and reference docs.

Want a deeper walkthrough?

Our cohort builds Projects like these alongside owners, with the actual reference files from their business. Two sessions a week, four weeks, leave with three Projects running.