# CLAUDE.md Before/After Examples

> From NerdSmith Founder Track -- Module 0, Lesson 4: CLAUDE.md Setup
> See the difference a good CLAUDE.md makes on actual Claude outputs.

---

## Example 1: Product Spec Request

### WITHOUT CLAUDE.md

**You type:**
```
Help me write a product spec for a new feature.
```

**Claude responds:**
```
I'd be happy to help! To write a useful product spec, I'll need some information:

1. What product are you building?
2. What's the feature?
3. Who is the target user?
4. What problem does it solve?
5. What's your technical stack?
6. What's the timeline?
7. Any specific format requirements?

Could you provide these details?
```

**Result:** 7 questions. You're annoyed. You answer them. Claude writes a spec that's too technical because it assumed you're a developer.

---

### WITH CLAUDE.md

**Your CLAUDE.md says:**
```markdown
# Project: TeamFlow MVP

## What This Project Is
B2B SaaS tool for remote teams (10-50 people). Team collaboration platform.
Stage: Pre-launch MVP.

## My Role
- Founder & Product Lead
- NOT a developer (no code, no jargon)

## Style Preferences
- Keep specs under 2 pages
- Plain English, benefit-focused
- Format: Problem / Solution / Features / Metrics
```

**You type:**
```
Write a product spec for our "Task Automation" feature -- it lets users create
if-this-then-that workflows to automate repetitive team coordination.
```

**Claude responds:**
```
## Problem Statement

Remote teams waste 5-10 hours per week on repetitive coordination: manually
notifying teammates when tasks are done, updating multiple tools, chasing approvals.
Team leads want to focus on strategy, not busywork.

## Proposed Solution

Task Automation lets users create simple rules: "When [trigger], then [action]."
No coding required. Set up in under 2 minutes.

## Key Features
- Trigger-action builder (drag and drop)
- Pre-built templates (task done → notify, overdue → escalate)
- Slack and email integration

## Success Metrics
- 50% reduction in manual notifications within 30 days
- 80% of active teams create at least 1 automation
- Net Promoter Score increase of 10+ points
```

**Result:** Immediate, formatted, non-technical spec. No clarifying questions. Exactly 2 pages. Because Claude already knew your context.

---

## Example 2: Marketing Copy

### WITHOUT CLAUDE.md

**You type:**
```
Write landing page copy for my product.
```

**Claude responds:**
A 600-word generic landing page with buzzwords like "leverage," "revolutionize," and "cutting-edge solution." Includes technical features ("RESTful API," "microservices architecture") because Claude didn't know you're non-technical.

---

### WITH CLAUDE.md

**Your CLAUDE.md includes:**
```markdown
## Style Preferences
- Tone: Professional but approachable (like Slack, not like SAP)
- No buzzwords: never use "leverage", "synergy", "revolutionary"
- Benefit-focused, not feature-focused
```

**You type:**
```
Write landing page hero copy. Goal: get email signups for our beta.
```

**Claude responds:**
```
Headline: Stop Managing Tools. Start Managing Teams.

Subheadline: TeamFlow automates the busywork so your remote team
can focus on what actually matters. Join 200+ teams in the beta.

CTA: Get Early Access (free)
```

**Result:** On-brand, benefit-driven, no buzzwords. Claude knew the tone, the audience, and the constraints without being told.

---

## Example 3: Customer Research

### WITHOUT CLAUDE.md

**You type:**
```
Read the interview files and find patterns.
```

**Claude responds:**
```
I found 15 files in various folders. Which ones are interview transcripts?
Also, what patterns are you looking for? Pain points? Feature requests?
Satisfaction levels? Demographics?
```

**Result:** Claude doesn't know where interviews live or what "patterns" means to you.

---

### WITH CLAUDE.md

**Your CLAUDE.md includes:**
```markdown
## File Structure
- `research/interviews/` -- Customer interview transcripts

## Common Workflows
### Customer Insight Synthesis
1. Read transcripts in research/interviews/
2. Identify top 5 pain points ranked by frequency
3. Include direct quotes as evidence
4. Save to analysis/customer-insights-[date].md
```

**You type:**
```
Run the customer insight synthesis workflow on this month's interviews.
```

**Claude responds:**
```
Reading 8 transcripts from research/interviews/...

## Pain Point 1: Context Switching Between Tools
- Mentioned by: 7/8 interviewees
- Quote: "I have 6 browser tabs open just to manage my team." -- Interview #3
- Why current solutions fail: Integrations exist but require technical setup

[... continues for all 5 pain points ...]

Saved to: analysis/customer-insights-2026-02.md
```

**Result:** Claude knew exactly where to find files, what to look for, how to format the output, and where to save it. You said one sentence.

---

## Example 4: Iterating on Output

### WITHOUT CLAUDE.md

**Turn 1:** "Write a product spec" -- Claude asks 5 questions
**Turn 2:** You answer the questions -- Claude writes a 4-page technical spec
**Turn 3:** "Make it shorter" -- Claude cuts to 3 pages, still technical
**Turn 4:** "No code or technical stuff" -- Claude rewrites, 2 pages
**Turn 5:** "Add success metrics" -- Claude adds metrics

**Total: 5 turns to get a usable spec.**

### WITH CLAUDE.md

**Turn 1:** "Write a product spec for the Task Automation feature" -- Claude delivers a 2-page, non-technical spec with metrics
**Turn 2:** "Add user stories" -- Claude adds them

**Total: 2 turns.**

---

## The Math: Time Saved Per Session

| Action | Without CLAUDE.md | With CLAUDE.md |
|--------|-------------------|----------------|
| Explain your role | 2 min (every session) | 0 min |
| Explain your product | 2 min (every session) | 0 min |
| Specify tone preferences | 1 min | 0 min |
| Answer clarifying questions | 3-5 min | 0-1 min |
| Re-request in correct format | 2-3 min | 0 min |
| **Total overhead per session** | **10-13 min** | **0-1 min** |

Over 20 sessions per month: **200-260 minutes saved = 3.5-4.5 hours/month.**

That's not just time. It's cognitive load. Every minute spent re-explaining context is a minute not spent thinking about your product.

---

## What Makes the Difference

| CLAUDE.md Element | What It Prevents |
|-------------------|-----------------|
| "Non-technical founder" | Claude suggesting code, using jargon |
| "Keep under 2 pages" | Claude writing 5-page essays |
| "Save to analysis/" | "Where should I save this?" questions |
| "Benefit-focused, not feature-focused" | Technical feature lists instead of user value |
| "No buzzwords" | "Leverage our revolutionary paradigm-shifting solution" |
| File structure section | "Which folder has the interviews?" questions |
| Common workflows | Multi-step processes completed in 1 prompt |

---

## Your Next Step

Write your CLAUDE.md. Use the Complete Template or Industry Templates Pack from this module's downloads. Test it. Update it. Save hours.

---

*NerdSmith Founder Track -- Module 0: Claude Code Bootcamp*
*Download: CLAUDE.md Before/After Examples*