# Before/After Prompt Gallery > From NerdSmith Founder Track -- Module 0, Lesson 3: Prompting Fundamentals > See the difference between vague and specific prompts. Learn from 8 real examples. --- ## How to Read This Guide Each example shows: - **BEFORE:** The vague prompt (and what goes wrong) - **AFTER:** The improved prompt (and why it works) - **Why it's better:** The specific fix that made the difference --- ## Example 1: Product Spec ### BEFORE (Vague) ``` Help me write a product spec for a new feature. ``` **What Claude does:** Asks 4-5 clarifying questions. You've wasted a turn. ### AFTER (Specific) ``` I'm a non-technical founder building a B2B team collaboration tool for remote teams (10-50 people). We're pre-launch. Write a product spec for our "Task Automation" feature. It lets users create simple "if-this-then-that" rules (e.g., "When task is Done, notify team in Slack"). Constraints: - Under 2 pages, plain English, no dev jargon - Focus on user benefits, not technical implementation Format: Problem Statement / Solution / Key Features / User Stories / Success Metrics ``` **What Claude does:** Delivers a complete, formatted spec immediately. **Why it's better:** Claude knows who you are, what the feature does, who it's for, and how to format the output. No guessing needed. --- ## Example 2: Customer Research ### BEFORE ``` Analyze these customer interviews. ``` **What Claude does:** "What are you looking for? How many interviews? What format?" ### AFTER ``` I have 10 interview transcripts in research/interviews/ from remote team leads (10-50 person companies). Goal: understand their biggest pain points with current collaboration tools. Analyze all 10 and identify: 1. Top 5 pain points (ranked by how many interviewees mentioned each) 2. Direct quotes supporting each finding 3. What solutions they've tried and why those failed Format each pain point as: Name / Mentioned by X/10 / Quote / Why current solutions fail ``` **Why it's better:** Claude knows what to look for (pain points, not features), how to rank them (by frequency), and what evidence to include (quotes). --- ## Example 3: Landing Page Copy ### BEFORE ``` Write landing page copy for my product. ``` **What Claude does:** Writes generic marketing fluff with no specificity. ### AFTER ``` Product: TeamFlow (B2B SaaS, team collaboration + task automation) Target: Non-technical team leads at remote companies (10-50 people) Goal: Get email signups for beta (launching March 2026) Write landing page copy: hero section + 3 benefit sections + CTA. Constraints: - Headline: 6-8 words, benefit-driven (not feature-driven) - Tone: Professional but approachable (like Slack's website, not like SAP) - Total: ~200 words - No buzzwords Example of the tone I want: "Stop Managing Tools. Start Managing Teams." ``` **Why it's better:** The example at the end shows Claude exactly what "good" sounds like. Claude mimics the tone, length, and structure. --- ## Example 4: Email Sequence ### BEFORE ``` Write some emails for my product. ``` **What Claude does:** Writes 1 generic promotional email with no strategy. ### AFTER ``` Product: TeamFlow (B2B collaboration tool) Trigger: User just signed up for free trial Goal: Get them to invite their team within 7 days (activation metric) Write a 4-email onboarding sequence, spaced 2 days apart. Constraints: - Subject lines under 50 characters - Body: 100-150 words each - Each email has exactly ONE call-to-action - Conversational tone (like writing to a colleague, not a press release) - Email 1: Welcome + quick win (2-min setup) - Email 2: Show value (what they're missing without team) - Email 3: Social proof (what other teams achieved) - Email 4: Urgency (trial expires in 3 days) ``` **Why it's better:** Each email has a specific job. Claude knows the sequence strategy, not just "write emails." --- ## Example 5: Competitive Analysis ### BEFORE ``` Tell me about my competitors. ``` **What Claude does:** "Who are your competitors? What industry? What specifically do you want to know?" ### AFTER ``` I'm building a team collaboration tool for remote teams (10-50 people). Research these 4 competitors and create a comparison: 1. Slack 2. Asana 3. Monday.com 4. Notion Focus on: how they position themselves, pricing tiers, what's missing for small remote teams specifically. Format as a comparison table (Feature / Slack / Asana / Monday / Notion / Us) plus a "Gaps We Can Exploit" section. Mark anything you're uncertain about with [UNVERIFIED]. ``` **Why it's better:** Named competitors, specific angle (small remote teams), requested format, and built-in honesty mechanism ([UNVERIFIED]). --- ## Example 6: Meeting Prep ### BEFORE ``` Help me prepare for a meeting. ``` ### AFTER ``` I have a 30-minute meeting tomorrow with a potential enterprise customer (500-person company, VP of Operations). They're evaluating our tool against Asana and Monday.com. They care most about: ease of onboarding (their team isn't technical) and integration with Slack. Help me prepare: 1. Three opening questions to understand their specific needs 2. Two-sentence pitch positioning us against Asana/Monday for non-technical teams 3. Three objection responses (price, "we already use X", "can we get a pilot first?") 4. One compelling customer story format (situation / problem / solution / result) Keep each answer concise -- I need to memorize these, not read a script. ``` **Why it's better:** Specific meeting context, specific competitor threats, specific objections to handle. Claude prepares you for the actual conversation. --- ## Example 7: Social Media Posts ### BEFORE ``` Write social media posts. ``` ### AFTER ``` Brand: TeamFlow (B2B collaboration tool) Platform: LinkedIn Audience: Team leads and ops managers at remote companies Voice: Helpful, no-fluff, data-informed, slightly opinionated Write 5 LinkedIn posts for next week: - 2 educational (teach something about remote team management) - 1 product-related (subtle, not salesy) - 1 engagement post (question that starts discussion) - 1 behind-the-scenes (building in public) Constraints: - 100-200 words each - No hashtag spam (max 2 per post) - End educational posts with a takeaway, not a pitch - The engagement post should be a genuine question, not "agree or disagree?" ``` **Why it's better:** Specific platform, specific content mix, specific voice guidelines. No generic "Check out our product!" posts. --- ## Example 8: Investor Update ### BEFORE ``` Write an investor update. ``` ### AFTER ``` Company: TeamFlow, seed-stage B2B SaaS Period: January 2026 Audience: 5 angel investors who invested $200K total Write a monthly investor update. Key data: - MRR: $4,200 (up from $3,100) - Active users: 145 (up from 98) - Churn: 8% (down from 12%) - Runway: 9 months Win: Landed first 50+ person team (Acme Corp) Challenge: Onboarding still takes 2 weeks (target: 3 days) Ask: Need intro to head of engineering at mid-size companies (50-200 employees) Constraints: - Under 400 words (investors skim) - Lead with metrics, not narrative - Be honest about the onboarding challenge - End with ONE specific ask ``` **Why it's better:** Real numbers, real challenges, real ask. Claude writes an update grounded in facts, not platitudes. --- ## The Pattern Every "After" prompt follows the same formula: | Element | What It Does | Example | |---------|-------------|---------| | **CONTEXT** | Tells Claude who you are and what you're building | "I'm a founder building a B2B tool for remote teams" | | **TASK** | Specific verb + specific deliverable | "Write a 4-email onboarding sequence" | | **CONSTRAINTS** | Rules, limits, tone, audience | "Under 200 words, no jargon, conversational" | | **FORMAT** | Exact structure for the output | "Table with columns: Feature / Comp 1 / Comp 2 / Us" | | **EXAMPLE** (bonus) | Shows what "good" looks like | "Tone like: Stop Managing Tools. Start Managing Teams." | When your outputs are disappointing, check which element is missing. That's usually the fix. --- *NerdSmith Founder Track -- Module 0: Claude Code Bootcamp* *Download: Before/After Prompt Gallery*