# Company CLAUDE.md Template

Agentic AI for Business Owners, Module 4
Bruno Ashford

This is a complete, fill-in company handbook for Claude Code. Claude reads a file named CLAUDE.md automatically at the start of every session started in that folder (or any folder below it).

## How to use this template

1. Copy everything below the line "START OF YOUR CLAUDE.md" into a new file called `CLAUDE.md` at the root of your Company folder.
2. Replace every item in [square brackets]. Delete any section that genuinely does not apply.
3. Keep the finished file under about 200 lines. Anthropic's documentation recommends this: longer files use more context and are followed less reliably.
4. Move long material (full price lists, detailed brand guides) into separate files and link them with an import line such as `@docs/pricing.md`. Imported files load together with CLAUDE.md, so import only what most tasks need. For documents Claude only needs sometimes, list the path in the folder map instead (in backticks, so it is not imported) and Claude will open it when relevant.
5. Restart Claude Code and run `/context` to confirm CLAUDE.md is listed under memory files.
6. Never put passwords, API keys, bank details or private client data in this file.

Tip: you can ask Claude to fill it in for you.

```
Create CLAUDE.md in this folder using materials/04-company-claude-md-template.md as the structure. Fill in what you can from the files here, leave [placeholders] where you need me, and ask me the missing questions five at a time.
```

---

START OF YOUR CLAUDE.md

```markdown
# [Company name] Handbook for Claude

You are working inside the files of [Company name]. Read this before every task. When anything here conflicts with a request, stop and ask me.

## 1. Who we are
- [Company name] is a [type of business] based in [city, country], serving clients in [area].
- Founded [year]. Team of [number]. Owner: [name, role].
- In one sentence: we help [who] to [result] by [how].
- What makes us different: [one or two concrete differences, not slogans].

## 2. What we sell
| Offer | Who it is for | Typical price | Notes |
|---|---|---|---|
| [Offer 1] | [client type] | [price or range] | [e.g. fixed fee, includes X] |
| [Offer 2] | [client type] | [price or range] | [notes] |
| [Offer 3] | [client type] | [price or range] | [notes] |

- Only quote prices from this table or from `finance/price-list.md`. If a price is not listed, say "price to be confirmed".
- We do NOT offer: [services people ask for that you do not provide].

## 3. Who we serve
- Ideal client: [industry, size, location, role of the buyer].
- Their top 3 problems: [problem 1], [problem 2], [problem 3].
- Why they choose us: [reason].
- Clients we avoid: [type] because [reason].
- Key accounts (use ID or short name only): [Client A], [Client B], [Client C]. Each has a brief in `clients/<name>/brief.md`. Read it before writing anything for that client.

## 4. Voice and tone
- Spelling: [US / UK] English. Currency: [USD / GBP]. Dates: [YYYY-MM-DD in files, "3 April 2026" in client text].
- We sound: [e.g. calm, direct, warm, expert]. Short sentences. Plain words.
- We always: [e.g. say "fixed fee", give a clear next step, sign off with first name].
- We never: [e.g. use jargon, use exclamation marks, say "cheap", use em dashes].
- Words we use: [list]. Words we avoid: [list].
- Example of our voice (a real sentence we are proud of):
  "[Paste one short real email opening or paragraph here.]"

## 5. Red lines (never break these)
- Never send emails, messages or posts. Draft only, because a human approves everything that leaves the company.
- Never edit, move or delete anything in `originals/`, because it is our source of truth.
- Never quote a price, discount or deadline that is not written in this handbook or the price list.
- Never put client names or personal data in file names, because file names get shared.
- Never invent numbers, facts, testimonials or references. If data is missing, say so.
- Never give [legal / medical / tax / financial] advice as final. Flag it for [role].
- [Add your own. One rule per line, with a short reason.]

## 6. Standards (how we always do things)
- New files: lowercase, hyphens, date first. Example: `2026-09-15-proposal-client-a.md`.
- Drafts go in `drafts/`. Finished reports go in `reports/`. Working copies of data go next to the original with `-clean` in the name.
- For any task that changes more than a few files, show me a plan first.
- When working with data: state which files and columns you used.
- [Add your own standards.]

## 7. Quality bar (check before handing anything to me)
- The main answer or recommendation comes first.
- Every number cites its source file.
- Assumptions are labelled as assumptions.
- It follows the voice rules in section 4.
- Length: emails under [120] words, summaries under one page unless I ask for more.
- If you are not confident, say so and say why.

## 8. Folder map
- `sales/`: pipeline exports, quotes, call lists. No contracts.
- `marketing/`: campaigns, content, brand assets.
- `finance/`: price list, invoices summaries, budgets. No bank logins.
- `operations/`: SOPs, suppliers, schedules.
- `clients/<name>/`: one folder per client with a `brief.md`.
- `templates/`: approved templates for proposals, emails and reports.
- `reports/`: finished outputs.
- `drafts/`: work in progress.
- `originals/`: read-only source files. Never edit.
- `archive/`: old material. Ignore unless I ask.

## 9. People and roles
- [Name]: [role]. Approves [what].
- [Name]: [role]. Owns [what].
- When a task needs sign-off, name the person who approves it.

## 10. Current priorities (update monthly)
- This quarter we are focused on: [priority 1], [priority 2], [priority 3].
- Not a priority right now: [thing to ignore].

## 11. Useful references
- Full price list: `finance/price-list.md`
- Brand guide: `marketing/brand-guide.md`
- [Import only what almost every task needs, for example:]
@templates/email-signature.md
```

END OF YOUR CLAUDE.md

---

## Worked example (filled in, shortened)

```markdown
# Hartley Roofing Handbook for Claude

You are working inside the files of Hartley Roofing. Read this before every task.

## 1. Who we are
- Residential roofing company in Leeds, UK, serving homes within 40 miles.
- Founded 2011. Team of 14. Owner: Dave Hartley, Managing Director.
- We help homeowners fix and replace roofs without stress by giving fixed quotes and a 10-year workmanship guarantee.

## 2. What we sell
| Offer | Who it is for | Typical price | Notes |
|---|---|---|---|
| Roof repair | Leaks, storm damage | GBP 250 to 1,500 | Free inspection |
| Full replacement | Roofs over 25 years old | GBP 7,000 to 14,000 | 10-year guarantee |
| Gutter package | Any homeowner | GBP 450 to 900 | Often bundled |

## 4. Voice and tone
- UK English, GBP, dates as "3 April 2026" in client text.
- Plain, reassuring, never pushy. Always mention the 10-year guarantee in quotes.
- Never say "cheap". Never use exclamation marks.

## 5. Red lines
- Never send anything. Draft only.
- Never promise a start date. Say "we will confirm dates after survey".
- Never quote outside the price ranges above.
- Never edit files in originals/.
```

---

## Testing your handbook

Run these three prompts in a fresh session. If an answer is weak, the handbook section behind it needs work.

1. "Without opening any other file, describe our ideal client, our main offer and how we sound."
2. "Draft a follow-up email to a homeowner who received a quote 10 days ago." (checks voice and red lines)
3. "Email the new price list to all clients now." (should be refused or turned into a draft)

## Keeping it alive

- When you correct Claude on something that should always apply, say: "Add this rule to CLAUDE.md."
- Review the file once a month. Delete anything outdated or contradictory.
- Use `/memory` to open and edit it from inside Claude Code.