Claude Prompt Library

Launch and Scale Your Startup with Claude AI

35 copy-paste prompts

35 strategic Claude prompts for idea validation, pitch decks, fundraising prep, go-to-market plans, financial modeling, and team building — built for Claude's structured analysis.

Idea Validation

5 prompts

Startup Idea Stress Test

1/35

<context> Startup idea: [DESCRIBE IN 2-3 SENTENCES] Target customer: [WHO HAS THIS PROBLEM] How they solve the problem today: [CURRENT ALTERNATIVES] Your unfair advantage: [WHY YOU SPECIFICALLY] Stage: [IDEA / BUILDING / LAUNCHED] </context> <task> Stress test this startup idea: 1. Problem validation: is this a real problem or a solution looking for a problem? Score the pain (1-10) 2. Market size: TAM, SAM, SOM — rough estimates with reasoning 3. Competition landscape: direct competitors, indirect competitors, and the "do nothing" competitor 4. Timing: why now? What has changed that makes this possible or necessary today 5. Business model viability: how this makes money and whether unit economics can work 6. 10 reasons this could fail: be brutally honest 7. 10 reasons this could succeed: be genuinely optimistic 8. The "mom test" questions: 5 questions to ask potential customers that reveal truth (not validation) 9. MVP definition: the smallest thing to build that tests the core assumption 10. Go/no-go verdict: honest assessment with specific conditions for proceeding I want harsh truth, not encouraging lies. Save me months by being honest now. </task>

Stress-tests a startup idea with market sizing, competitive analysis, failure modes, and a brutally honest go/no-go verdict.

💡

Pro tip: The most valuable output is the "10 reasons this could fail" list. If you can solve for the top 3 failure modes, the idea has legs. If the failures are structural, pivot before investing more time.

Customer Discovery Interview Guide

2/35

<context> Product idea: [DESCRIBE] Target customer: [WHO] Assumptions about the customer: [LIST WHAT YOU BELIEVE IS TRUE] Stage: [PRE-MVP / POST-MVP / POST-LAUNCH] </context> <task> Create a customer discovery interview guide: 1. Interview objective: what specific assumptions are we testing (not "do people like our idea") 2. Screening criteria: how to find the RIGHT people to interview (not just anyone) 3. Interview questions (20 questions organized by topic): - Current behavior: how they solve the problem today (5 questions) - Pain points: what frustrates them about current solutions (5 questions) - Willingness to pay: how much they spend now and what they would pay (5 questions) - Feature exploration: what matters vs what is nice-to-have (5 questions) 4. Questions to NEVER ask: common mistakes that produce misleading validation 5. Observation guide: what to watch for beyond their words (hesitation, enthusiasm, body language) 6. Analysis framework: how to synthesize 10-15 interviews into actionable insights 7. Decision criteria: what responses mean "proceed" vs "pivot" vs "kill" Customer discovery is not about asking if they would use your product. It is about understanding their problem deeply enough to build the right solution. </task>

Creates a structured customer discovery interview guide with screening, 20 questions, analysis framework, and decision criteria.

💡

Pro tip: Never ask "would you use this?" or "would you pay for this?" People say yes to be polite. Instead ask about their current behavior and spending. Past behavior predicts future behavior; hypothetical answers do not.

Competitive Moat Analyzer

3/35

<context> Your startup: [DESCRIBE] Direct competitors: [LIST WITH BRIEF DESCRIPTIONS] Indirect competitors: [LIST] Your current advantages: [WHAT YOU THINK MAKES YOU DIFFERENT] </context> <task> Analyze competitive moats: 1. Current moat assessment: do you actually have a moat or just a head start? 2. Moat types analysis for your business: - Network effects: does the product get more valuable with more users? - Switching costs: how hard is it for customers to leave? - Data advantage: do you accumulate data that improves the product? - Brand/trust: do you have brand equity competitors cannot replicate? - Cost advantages: can you operate cheaper than competitors? - Regulatory/legal: any licensing, patents, or regulatory barriers? 3. Competitor moat assessment: what moats do THEY have? 4. Moat building plan: which moat types are realistic for your business and how to build them 5. Time to moat: how long until your advantages become defensible (not just better features) 6. Vulnerability analysis: where are you most attackable right now? 7. Moat deepening: for each existing advantage, how to make it stronger over time Features are not moats. Anyone can copy features. Moats are structural advantages that get stronger over time. </task>

Analyzes current and potential competitive moats with building plans, vulnerability assessment, and deepening strategies.

💡

Pro tip: If your only advantage is "better product," you do not have a moat. A well-funded competitor can match features in months. Focus on advantages that COMPOUND over time: data, network effects, switching costs.

Market Sizing Calculator

4/35

<context> Product: [DESCRIBE] Target customer: [WHO] Pricing: [PRICE POINT OR RANGE] Geography: [WHERE — US, global, specific regions] Distribution: [ONLINE / OFFLINE / BOTH] </context> <task> Calculate market size using both top-down and bottom-up approaches: Top-down: 1. TAM (Total Addressable Market): the entire market if you had 100% market share 2. SAM (Serviceable Addressable Market): the segment you can actually reach 3. SOM (Serviceable Obtainable Market): realistic market share in the next 3-5 years 4. Show the math and assumptions for each level Bottom-up: 5. Number of potential customers × average revenue per customer × purchase frequency 6. Customer acquisition assumptions: channels, conversion rates, growth rate 7. 3-year revenue projection based on bottom-up model Reality check: 8. Comparable companies: what revenue did similar startups achieve at 3 and 5 years? 9. Market growth rate: is this market expanding, stable, or contracting? 10. The investor test: is this market big enough to build a venture-scale business? Investors care about market size. Customers care about problem-solution fit. Both matter. </task>

Calculates market size using top-down and bottom-up methods with reality checks against comparable companies.

💡

Pro tip: Bottom-up market sizing is more credible than top-down in investor conversations. Saying "there are 50,000 dentists who each spend $2,000/year on this" is more believable than "the dental software market is $3 billion."

MVP Scoping Workshop

5/35

<context> Product vision: [DESCRIBE THE FULL PRODUCT YOU IMAGINE] Core value proposition: [THE ONE THING CUSTOMERS NEED MOST] Target user: [WHO WILL USE THE MVP] Technical resources: [WHAT YOU CAN BUILD — team skills, budget, timeline] Validation goal: [WHAT ASSUMPTION THE MVP NEEDS TO TEST] </context> <task> Scope the minimum viable product: 1. Feature decomposition: list every feature in your full vision 2. MoSCoW prioritization: Must have / Should have / Could have / Will not have 3. Core loop: what is the essential user action that delivers value? (The MVP is this loop and nothing else) 4. Feature elimination: for each "must have," ask: "Can I test my core assumption without this?" If yes, cut it 5. The "wizard of Oz" test: which features can be done manually before building (fake the backend) 6. MVP specification: the final feature list with basic technical requirements 7. Build timeline: realistic estimate for each feature and total development time 8. Success criteria: specific metrics that determine if the MVP validated or invalidated the hypothesis 9. What happens after MVP: if validated, the next 3 features to add; if invalidated, how to pivot The MVP is not a crappy version of the full product. It is the smallest experiment that tests your biggest assumption. </task>

Scopes an MVP through feature elimination, core loop identification, and clear success criteria.

💡

Pro tip: If your MVP takes more than 6 weeks to build, it is not minimum enough. The goal is learning speed, not product completeness. Build less, learn faster.

XML tags are just the start. Learn the full Claude workflow.

A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.

Start 14-Day Free Trial

Fundraising

5 prompts

Pitch Deck Builder

6/35

<context> Company: [NAME] Stage: [PRE-SEED / SEED / SERIES A] Asking: [HOW MUCH AND WHAT FOR] Traction: [REVENUE, USERS, GROWTH RATE — whatever you have] Team: [FOUNDERS AND KEY HIRES WITH BACKGROUNDS] Previous funding: [ANY] </context> <task> Build a pitch deck outline (10-12 slides): 1. Cover: company name, one-line description, logo 2. Problem: the pain point in specific, relatable terms (not abstract) 3. Solution: what you built and how it solves the problem (demo screenshot/mockup direction) 4. Market: TAM/SAM/SOM with credible sourcing 5. Business model: how you make money, pricing, unit economics 6. Traction: the slide investors actually care about — metrics, growth rate, milestones 7. Competition: positioning map showing why you win (not a feature checklist) 8. Team: why this team is uniquely qualified to solve this problem 9. Go-to-market: how you acquire customers and what the CAC/LTV looks like 10. Financials: 3-year projection, key assumptions, burn rate 11. The ask: how much, what it funds, what milestones it reaches 12. Vision: where this goes in 5-10 years (end on the big dream) For each slide: the key message (one sentence), supporting data points, and what NOT to include. </task>

Creates a 12-slide pitch deck outline with key messages, data points, and common pitfalls for each slide.

💡

Pro tip: The traction slide is the most important. Everything else is a story — traction is proof. Put your best metric on this slide and make it impossible to miss.

Investor Q&A Prep

7/35

<context> Company: [NAME AND DESCRIPTION] Stage: [STAGE] Metrics: [KEY NUMBERS] Weaknesses: [HONEST ASSESSMENT OF WHAT INVESTORS WILL QUESTION] Competition: [MAIN COMPETITORS] Burn rate: [MONTHLY BURN] </context> <task> Prepare for investor Q&A: 1. Generate the 30 most common investor questions for my stage, organized by category: - Market and opportunity (6 questions) - Product and technology (6 questions) - Business model and unit economics (6 questions) - Team and execution (6 questions) - Competition and differentiation (3 questions) - Fundraise specifics (3 questions) 2. For each question: a concise, confident answer (under 60 seconds spoken) 3. The 5 hardest questions specific to MY company's weaknesses — with honest, non-defensive answers 4. Bridge techniques: how to redirect from weak areas to strong areas without being evasive 5. Questions to ask investors: 5 questions that show sophistication and help me evaluate them 6. Red flag responses: answers that make investors lose interest (so I can avoid them) The Q&A often matters more than the pitch. Investors invest in founders who think clearly under pressure. </task>

Prepares 30 investor questions with answers, hard-question strategies, and bridge techniques for weak areas.

💡

Pro tip: Practice the 5 hardest questions until you can answer them without flinching. Investors watch your reaction to hard questions as much as they listen to the answer. Confidence without defensiveness is the goal.

Financial Model Framework

8/35

<context> Business model: [SAAS / MARKETPLACE / ECOMMERCE / AD-SUPPORTED / OTHER] Current revenue: [AMOUNT OR PRE-REVENUE] Pricing: [MODEL AND AMOUNTS] Current customers: [NUMBER] Growth rate: [MONTHLY/ANNUAL] Main cost categories: [LIST] Burn rate: [MONTHLY] </context> <task> Build a financial model framework: 1. Revenue model: detailed assumptions for each revenue stream - New customer acquisition rate (monthly) - Churn rate (monthly) - Average revenue per customer - Expansion revenue from existing customers 2. Cost model: - COGS / cost of revenue - Customer acquisition cost (CAC) by channel - Team costs (current and planned hires) - Infrastructure and tools - G&A overhead 3. Unit economics: - CAC, LTV, LTV/CAC ratio, payback period - Gross margin, contribution margin 4. 3-year monthly projection: revenue, costs, cash flow, headcount 5. Key assumptions: list every assumption and flag which ones investors will challenge 6. Sensitivity analysis: how results change if growth is 50% slower or CAC is 50% higher 7. Fundraise runway: at current burn, how long does the money last Provide the framework structure and formulas. I will plug in my actual numbers. </task>

Creates a financial model framework with revenue, cost, and unit economics models plus sensitivity analysis.

💡

Pro tip: Investors expect your model to be wrong. What they are evaluating is whether you understand the key drivers and assumptions. A simple model with clear assumptions beats a complex model with hidden ones.

Fundraising Strategy Planner

9/35

<context> Company: [DESCRIBE] Stage: [PRE-SEED / SEED / SERIES A] Amount needed: [HOW MUCH] Timeline: [WHEN YOU NEED THE MONEY] Current investors: [ANY EXISTING] Location: [WHERE YOU ARE BASED] Network: [YOUR INVESTOR CONNECTIONS — strong / weak / none] </context> <task> Create a fundraising strategy: 1. Readiness assessment: are you ready to raise? Check: traction, team, market, timing 2. Investor targeting: profile of ideal investor (stage focus, sector, check size, value-add) 3. Pipeline building: how to identify and reach 50-100 potential investors 4. Warm intro strategy: how to get introductions (the only reliable way to get meetings) 5. Outreach sequence: cold email template, follow-up cadence, LinkedIn approach 6. Meeting preparation: what to prepare for the first call, partner meeting, and diligence 7. Timeline and process: how long fundraising takes at each stage and how to manage the process 8. BATNA: what to do if fundraising takes longer than expected (bridge, revenue, reduce burn) 9. Term sheet evaluation: key terms to negotiate and terms to accept 10. Closing: how to create urgency without desperation Fundraising is a sales process. Treat it like one: pipeline, qualification, conversion, close. </task>

Plans a complete fundraising process from readiness assessment to term sheet evaluation with pipeline and timing strategies.

💡

Pro tip: Do not start fundraising until you can tell a compelling story supported by data. Fundraising while unprepared burns your one chance with each investor. You do not get a second first impression.

Valuation Preparation

10/35

<context> Company: [NAME] Stage: [STAGE] Revenue: [ANNUAL OR MRR] Growth rate: [PERCENTAGE] Comparable companies: [IF KNOWN] Previous valuation: [IF ANY] Amount raising: [TARGET] </context> <task> Prepare for valuation discussions: 1. Valuation methods appropriate for my stage: - Pre-revenue: comparable deals, team quality, market size - Early revenue: revenue multiples, growth rate premium - Growth stage: ARR multiples, growth-adjusted comparables 2. Comparable analysis: similar companies at similar stages and their valuations 3. Revenue multiple range: what multiple my growth rate and market justify 4. Dilution math: how much of the company I am giving up at different valuations 5. Negotiation range: my target valuation, walk-away floor, and ideal outcome 6. Investor perspective: what valuation makes the math work for THEIR return expectations 7. Pre-money vs post-money: clear explanation and implications 8. Anti-dilution and other terms that affect effective valuation Valuation is not about what your company is worth today. It is about what both sides believe it will be worth in 5-10 years. </task>

Prepares for valuation negotiations with comparable analysis, dilution math, and negotiation range planning.

💡

Pro tip: Optimize for the right investor at a fair valuation over the highest valuation from the wrong investor. A strategic investor who opens doors is worth more than an extra million in valuation from a passive check-writer.

Go-to-Market

5 prompts

Go-to-Market Strategy

11/35

<context> Product: [DESCRIBE] Target customer: [DESCRIBE IN DETAIL] Pricing: [MODEL AND PRICE] Current traction: [DESCRIBE] Budget for GTM: [AMOUNT] Team: [WHO IS AVAILABLE FOR GTM] Timeline: [WHEN TO LAUNCH OR SCALE] </context> <task> Design a go-to-market strategy: 1. ICP (Ideal Customer Profile): ultra-specific description of the first 100 customers 2. Acquisition channels ranked by: - Expected CAC for each channel - Time to results (immediate vs slow-build) - Scalability ceiling 3. Channel-market fit: which channels reach my specific ICP most efficiently 4. Launch plan: - Pre-launch: building audience, waitlist, beta testers - Launch week: specific daily actions - Post-launch: first 30 days of customer acquisition 5. Sales vs self-serve: which model fits my product and price point 6. Pricing strategy: launch pricing, early adopter offers, pricing psychology 7. Retention from day 1: what happens after signup to ensure customers stay 8. Metrics dashboard: 5 numbers to track daily during launch 9. 90-day GTM calendar: week-by-week activities and milestones The best go-to-market strategy is one that gets you to 100 paying customers as fast as possible. </task>

Creates a complete go-to-market strategy with ICP, channel ranking, launch plan, and 90-day execution calendar.

💡

Pro tip: Focus on one acquisition channel until it works. The startup that masters one channel beats the startup that dabbles in five. Find the channel that delivers your ICP at an acceptable CAC, then optimize relentlessly.

Pricing Strategy Builder

12/35

<context> Product: [DESCRIBE] Target customer: [DESCRIBE] Competitor pricing: [LIST COMPETITORS AND THEIR PRICES] Value delivered: [WHAT CUSTOMER GAINS — TIME SAVED, REVENUE GAINED, COST REDUCED] Current pricing: [IF ANY] Business model: [SAAS / USAGE / ONE-TIME / FREEMIUM] </context> <task> Build a pricing strategy: 1. Value quantification: calculate the actual dollar value your product creates for customers 2. Pricing model comparison: subscription vs usage vs one-time vs hybrid — best for your product 3. Price anchoring: what price anchors exist (competitor pricing, alternative costs, value delivered) 4. Tier structure: 2-4 tiers with features, limits, and target customer for each 5. Free tier decision: freemium vs free trial vs no free — analysis for your situation 6. Pricing psychology: specific tactics (charm pricing, annual discount, enterprise "contact us") 7. Launch pricing: should you launch low and raise, or start at target price? 8. Price sensitivity estimation: how sensitive is your market to price changes 9. Revenue modeling: projected revenue at different price points and conversion rates 10. Price change communication: how to raise prices later without losing customers Pricing is the most important lever in your business. A 10% price increase goes straight to the bottom line. </task>

Develops a pricing strategy with value quantification, tier structure, freemium analysis, and price change planning.

💡

Pro tip: Most startups underprice. If no one complains about your price, you are too cheap. Aim for 10-20% of customers pushing back — that means 80-90% see the value, which is exactly right.

Content Marketing Playbook

13/35

<context> Startup: [DESCRIBE] Target audience: [DESCRIBE] Buyer journey: [HOW DO CUSTOMERS FIND AND EVALUATE SOLUTIONS] Content resources: [WHO WILL CREATE CONTENT AND HOW MUCH TIME] Current content: [WHAT EXISTS] Goal: [SEO TRAFFIC / THOUGHT LEADERSHIP / LEAD GEN / COMMUNITY] </context> <task> Create a content marketing playbook: 1. Content-market fit: what content does my audience actually consume and where? 2. Keyword strategy: 20 keywords prioritized by search volume, competition, and buyer intent 3. Content pillars: 4-5 topic clusters that establish expertise and drive organic traffic 4. Content calendar: 12 weeks of specific content pieces with titles, formats, and keywords 5. Distribution plan: where and how to promote each piece beyond "post and pray" 6. Funnel mapping: which content serves awareness, consideration, and decision stages 7. Lead capture: how to convert readers into leads (without annoying gated content for everything) 8. Repurposing system: how to turn one piece of content into 5-10 pieces across channels 9. Measurement: which metrics to track at each funnel stage 10. Scaling: how the content engine grows as the team grows Content marketing compounds. Month 1 feels like nothing. Month 12 is an unstoppable organic traffic engine. </task>

Creates a content marketing playbook with keyword strategy, 12-week calendar, distribution plan, and lead capture system.

💡

Pro tip: Do not create content about your product. Create content about your customer's problem. The person searching "how to reduce churn" is your customer. The person searching "[your product name]" already knows about you.

Partnership Strategy

14/35

<context> Startup: [DESCRIBE] Target customer overlap: [COMPANIES/PRODUCTS WITH THE SAME CUSTOMER] Current distribution channels: [DESCRIBE] Partnership experience: [NONE / SOME / EXPERIENCED] What you can offer partners: [VALUE YOU BRING] </context> <task> Design a partnership strategy: 1. Partner identification: 3 categories of potential partners: - Complementary products (non-competing, same customer) - Channel partners (distribution access you lack) - Technology partners (integrations that add value) 2. For each category, list 5-10 specific companies 3. Value proposition for partners: what is in it for THEM (not just you) 4. Partnership models: referral, co-marketing, integration, reseller, white-label — which fits 5. Outreach strategy: how to get initial meetings with partnership teams 6. Partnership proposal template: structure for a compelling partnership pitch 7. Success metrics: how both sides measure whether the partnership works 8. Partnership management: how to maintain and grow relationships over time 9. Warning signs: when a partnership is not working and how to exit gracefully Partnership is the startup cheat code for distribution — but only if you lead with their value, not yours. </task>

Develops a partnership strategy with partner identification, value propositions, and partnership proposal templates.

💡

Pro tip: The best partnerships are ones where both sides get customer access they could not get alone. If the value flows only one direction, it is not a partnership — it is a vendor relationship.

Customer Onboarding Designer

15/35

<context> Product: [DESCRIBE] User type: [TECHNICAL / NON-TECHNICAL / MIXED] Current onboarding: [DESCRIBE OR "none"] Time-to-value: [HOW LONG UNTIL USER GETS VALUE] Churn: [WHEN DO USERS TYPICALLY LEAVE] Setup complexity: [SIMPLE / MODERATE / COMPLEX] </context> <task> Design a customer onboarding experience: 1. Aha moment identification: what specific action = the user "gets it"? 2. Time-to-aha: how quickly can we get a new user to that moment? 3. Onboarding flow: - First 5 minutes: immediate win or setup progress - First day: core value experienced - First week: habit formed - First month: fully activated 4. Guided vs self-serve: for each user type, the right level of hand-holding 5. Email sequence: 5-7 onboarding emails timed to user behavior triggers 6. In-app guidance: tooltips, checklists, and empty states that educate without annoying 7. Success metrics: activation rate, time-to-value, onboarding completion rate 8. Failure recovery: what to do when a user stalls during onboarding 9. Onboarding for different personas: how the flow adapts for different user types Onboarding is the highest-leverage work in any startup. A user who does not activate never becomes a customer. </task>

Designs a customer onboarding flow from first minute to first month with aha moment identification and failure recovery.

💡

Pro tip: Track where users drop off during onboarding. The biggest drop-off point is your biggest opportunity. Fix that one step and activation rate jumps more than improving anything else.

Operations & Scaling

5 prompts

Hiring Plan Builder

16/35

<context> Company stage: [PRE-SEED / SEED / SERIES A / GROWTH] Current team: [NUMBER AND ROLES] Burn rate: [MONTHLY] Funding: [RUNWAY IN MONTHS] Biggest bottleneck: [WHAT ROLE WOULD HELP MOST] Growth plans: [WHAT YOU NEED TO ACCOMPLISH IN 12 MONTHS] </context> <task> Build a hiring plan: 1. Role prioritization: rank the next 5 hires by impact on the business 2. For each role: - Why this role now (not later) - Job description framework (responsibilities, requirements, nice-to-haves) - Compensation range for the stage and market - Full-time vs contractor vs fractional assessment - Hiring timeline: how long each role typically takes to fill 3. Budget impact: monthly burn increase with each hire and remaining runway 4. Build vs buy: which functions to hire for vs outsource vs automate 5. Culture preservation: how to maintain culture through rapid hiring 6. Hiring process: a lightweight but effective interview process for a startup (not enterprise bureaucracy) 7. Founder role evolution: what the founder should stop doing as each hire comes on Every hire should either increase revenue or enable the team to move faster. If neither, wait. </task>

Creates a prioritized hiring plan with role analysis, budget impact, and founder role evolution.

💡

Pro tip: Hire for the problem you have today, not the problem you might have in 6 months. Early-stage startups that hire ahead of need burn cash on roles that may not be needed if the plan changes.

Startup Metrics Dashboard

17/35

<context> Business model: [SAAS / MARKETPLACE / ECOMMERCE / OTHER] Stage: [PRE-REVENUE / EARLY REVENUE / GROWTH] Current metrics tracked: [LIST OR "none systematic"] Tools used: [ANALYTICS, CRM, BILLING, etc.] Reporting audience: [FOUNDERS ONLY / TEAM / INVESTORS] </context> <task> Design a startup metrics dashboard: 1. North Star Metric: the ONE number that best captures value delivery 2. Tier 1 (Check daily — 5 metrics): - Revenue/signups, activation rate, key engagement metric, and 2 others specific to my model 3. Tier 2 (Check weekly — 8-10 metrics): - CAC, LTV, churn, conversion rates, support volume, NPS 4. Tier 3 (Check monthly — 5-8 metrics): - Burn rate, runway, hiring plan, market share indicators 5. For each metric: - How to calculate it - What "good" looks like at my stage - What triggers action (threshold or trend) 6. Investor update template: how to present these metrics in monthly investor updates 7. Anti-metrics: numbers that look impressive but do not matter (vanity metrics to ignore) You cannot improve what you do not measure. But measuring everything is as useless as measuring nothing. </task>

Builds a tiered metrics dashboard with daily, weekly, and monthly metrics, benchmarks, and an investor reporting template.

💡

Pro tip: One metric matters most at each stage. Pre-product-market-fit: retention. Post-PMF: growth rate. Post-scale: unit economics. Focus on the metric that matches your stage.

Startup Operations Playbook

18/35

<context> Team size: [NUMBER] Remote/hybrid/office: [SETUP] Current tools: [LIST] Biggest operational pain: [WHAT IS INEFFICIENT] Stage: [DESCRIBE] </context> <task> Create a startup operations playbook: 1. Communication system: - When to use Slack vs email vs meeting vs doc - Meeting cadence: which recurring meetings and who attends - Decision documentation: how decisions get recorded and shared 2. Project management: - Sprint/cycle structure for the team - Task management approach (simple — not enterprise project management) - Weekly rhythm: planning, standup, retro schedule 3. Documentation: - What to document vs what to discuss (not everything needs a doc) - Where docs live (single source of truth) - Decision log template 4. Tool stack: essential tools for a team of my size (minimize tool count) 5. Onboarding: how a new hire gets up to speed in their first week 6. Spending and approvals: a lightweight process that prevents waste without bureaucracy 7. OKR/goal cascade: how company goals translate to team and individual goals Operations should feel invisible when working. If people are fighting with process, there is too much of it. </task>

Creates a lightweight operations playbook covering communication, projects, documentation, and tools for startup pace.

💡

Pro tip: Start with the minimum viable process. A startup with 5 people does not need a 50-page operations manual. Start with 3 rules: how we communicate, how we decide, how we track progress. Add more only when something breaks.

Scaling Readiness Assessment

19/35

<context> Current MRR/ARR: [AMOUNT] Growth rate: [PERCENTAGE] Team size: [NUMBER] Product-market fit signals: [DESCRIBE] Biggest constraint to growth: [WHAT LIMITS YOU] Funding: [CURRENT RUNWAY] </context> <task> Assess scaling readiness: 1. Product-market fit validation: do you actually have PMF or just early traction? - Retention curves: are they flattening (good) or declining to zero (bad)? - Organic growth: are customers coming without paid acquisition? - NPS/satisfaction: would customers be disappointed if the product disappeared? 2. Unit economics check: can you acquire a customer profitably? 3. Operational readiness: what breaks when you 10x customers? - Product/infrastructure: can it handle 10x load? - Team: which roles are bottlenecked? - Support: can you maintain quality at scale? - Processes: what is manual that needs automation? 4. Financial readiness: do you have the capital to fund growth? 5. Market timing: is now the right time to accelerate? 6. Scale plan: a phased approach to scaling (do not try to do everything at once) 7. Warning signs: indicators that you are scaling too fast Scaling before product-market fit is the most expensive mistake a startup can make. </task>

Evaluates product-market fit, unit economics, and operational readiness before committing to scaling.

💡

Pro tip: The test for product-market fit is simple: are customers pulling the product from you faster than you can push it to them? If you are still pushing, focus on product, not growth.

Pivot Decision Framework

20/35

<context> Current product: [DESCRIBE] Original thesis: [WHAT YOU BELIEVED ABOUT THE MARKET] Current reality: [WHAT ACTUALLY HAPPENED] Traction: [DESCRIBE — whatever you have or do not have] Burn rate and runway: [MONTHS LEFT] Team morale: [DESCRIBE] New direction considered: [DESCRIBE THE PIVOT, IF ANY] </context> <task> Evaluate whether to pivot: 1. Honest assessment: why is the current approach not working? (Product? Market? Execution? Timing?) 2. The "one more month" trap: am I persevering or just avoiding a hard decision? 3. Data review: what does the data actually say vs what am I hoping it says? 4. Pivot signals: which of these apply? - Customers use the product differently than intended (partial pivot opportunity) - One feature gets all the love (focus pivot) - Wrong customer segment but right product (market pivot) - Right problem but wrong solution (solution pivot) 5. Pivot options: 3-5 possible pivots with assessment of each 6. Kill criteria: at what point would I shut down entirely? 7. Team and investor communication: how to communicate the pivot decision 8. Execution plan: the first 30 days of the new direction The best pivots preserve some of what you have learned and built. A total restart is not a pivot — it is a new company. </task>

Evaluates a potential pivot with data review, pivot type identification, and communication planning.

💡

Pro tip: Most successful startups pivoted at least once. The pivot is not a failure — it is an application of what you learned. The only failure is running out of money before finding what works.

Team & Culture

5 prompts

Co-Founder Alignment Session

21/35

<context> Co-founders: [NAMES AND BACKGROUNDS] Relationship: [HOW YOU KNOW EACH OTHER] Business stage: [IDEA / BUILDING / LAUNCHED] Current disagreements: [IF ANY] Equity split: [DECIDED / NOT YET] </context> <task> Facilitate a co-founder alignment session: 1. Vision alignment: do you agree on what this company looks like in 5 years? 2. Role clarity: who owns what? Create a RACI matrix for key decisions 3. Decision-making framework: how to make decisions when you disagree (majority, domain owner, etc.) 4. Equity conversation framework: factors to consider (time commitment, cash, skills, risk) 5. Vesting: standard 4-year vesting with 1-year cliff — explanation and customization 6. Exit scenarios: what happens if one person wants to leave? 7. Conflict resolution: a specific process for resolving disagreements before they become resentment 8. Working style: schedules, communication preferences, work-life boundaries 9. Financial alignment: salary expectations, side projects, personal financial runway 10. The conversation you are avoiding: identify the uncomfortable topic you have not discussed yet and discuss it Co-founder breakups kill more startups than competition does. Have these conversations now. </task>

Structures a co-founder alignment session covering vision, roles, equity, decision-making, and the conversations most founders avoid.

💡

Pro tip: Have this conversation within the first month of working together. The longer you wait, the harder it gets. Disagreements that are easy to resolve in month 1 become company-destroying in month 12.

Company Culture Definer

22/35

<context> Company: [NAME] Team size: [NUMBER] Stage: [EARLY / GROWTH / ESTABLISHED] Values you care about: [LIST] Behaviors you want to see: [DESCRIBE] Behaviors you want to prevent: [DESCRIBE] Culture problems: [ANY CURRENT ISSUES] </context> <task> Define your company culture intentionally: 1. Core values: 4-5 values that genuinely guide decisions (not generic "integrity" and "innovation") 2. For each value: - What it means in practice (specific behaviors, not abstract concepts) - A decision example: when this value was tested, what the right choice looks like - The uncomfortable tradeoff: what you sacrifice to honor this value 3. Culture operating principles: 5-7 "rules of the road" (e.g., "default to transparency" or "disagree and commit") 4. Hiring for culture: interview questions that reveal alignment with your values 5. Anti-values: what your culture explicitly rejects (e.g., "we value speed over perfection") 6. Culture rituals: 3-5 recurring practices that reinforce the culture 7. Culture challenges: how culture gets tested as you scale and how to protect it Culture is not what you write on the wall. It is what happens when the boss is not in the room. </task>

Defines company culture with actionable values, hiring criteria, operating principles, and scaling protections.

💡

Pro tip: Test your values with this question: "If following this value cost us money or slowed us down, would we still do it?" If the answer is no, it is not really a value — it is a nice-to-have.

Remote Team Playbook

23/35

<context> Team size: [NUMBER] Locations: [TIME ZONES AND COUNTRIES] Remote experience: [NEW TO REMOTE / EXPERIENCED] Biggest remote challenges: [DESCRIBE] Tools currently used: [LIST] </context> <task> Create a remote team playbook: 1. Communication norms: - Async-first principle: what should be async (most things) vs sync (few things) - Response time expectations by channel (Slack: 4 hours, Email: 24 hours, etc.) - Overlap hours: when everyone must be available 2. Meeting cadence: the minimum effective meetings (not "let's add a meeting for everything") 3. Documentation culture: how to make information accessible to all time zones 4. Social connection: how to build relationships when you cannot grab lunch together 5. Performance management: how to evaluate output when you cannot see input 6. Onboarding remotely: how new hires integrate when there is no office to walk around 7. Tool stack: the essential tools and how to use each one (prevent tool sprawl) 8. Time zone equity: how to prevent one time zone from becoming "headquarters" 9. Mental health: remote-specific burnout prevention (boundaries, isolation, Zoom fatigue) Remote work is not office work done from home. It is a fundamentally different operating model. </task>

Creates a remote team playbook with async-first communication, meeting cadence, and time zone equity policies.

💡

Pro tip: The biggest remote work mistake is trying to replicate the office online. Fewer meetings, more async documentation, and intentional social connection produce better results than 8 hours of Zoom calls.

Advisory Board Builder

24/35

<context> Startup: [DESCRIBE] Stage: [STAGE] Biggest knowledge gaps: [WHAT EXPERTISE YOU LACK] Biggest relationship gaps: [WHAT CONNECTIONS YOU NEED] Current advisors: [IF ANY] Equity budget for advisors: [PERCENTAGE] </context> <task> Build an advisory board strategy: 1. Advisor needs assessment: 3-5 specific gaps that advisors could fill (not generic "industry expertise") 2. Ideal advisor profiles: for each gap, describe the perfect advisor 3. Advisory structure: formal board vs informal advisors vs both 4. Compensation: standard advisor equity (0.25-1% with vesting), meeting cadence expectations 5. Finding advisors: where to look and how to approach them 6. Pitch to advisors: why they should invest their time in your startup 7. Advisor agreement template: key terms to include 8. Getting value: how to structure advisor interactions for maximum impact (not just quarterly calls) 9. Evaluation: how to know if an advisor is delivering value or just collecting equity 10. Graduating advisors: how to gracefully end relationships that are no longer valuable One great advisor who opens three doors is worth more than five prestigious names on a website. </task>

Designs an advisory board strategy with needs assessment, finding and pitching advisors, and value extraction methods.

💡

Pro tip: The best advisors are not the most famous people — they are the ones who will actually pick up the phone when you need help. Prioritize engagement over prestige.

First 10 Customers Strategy

25/35

<context> Product: [DESCRIBE] Target customer: [DESCRIBE] Current state: [PRE-LAUNCH / JUST LAUNCHED / HAVE SOME BETA USERS] What you have tried: [DESCRIBE ACQUISITION ATTEMPTS] Price point: [AMOUNT] Your personal network: [DESCRIBE — industry connections, community, social following] </context> <task> Create a strategy to get the first 10 paying customers: 1. Why the first 10 matter: these are your learning customers, not just revenue 2. Warm outreach plan: 20 specific people in my network to contact first (by category) 3. Outreach message templates: personalized, not spammy, focused on their problem 4. Community infiltration: 5 online communities where my target customers gather 5. Content-led approach: 3 pieces of content that demonstrate expertise and attract the right people 6. Founder-led sales: how to personally sell the first 10 (no automation, no funnels — just conversations) 7. Concierge onboarding: how to white-glove serve each of the first 10 (and learn from every one) 8. Feedback extraction: specific questions to ask first customers that improve the product 9. Reference building: how to turn each of the first 10 into a case study or referral source 10. When the first 10 strategy stops working: how to transition to scalable acquisition Your first 10 customers teach you more than the next 1,000. Treat each one as a masterclass. </task>

Plans the acquisition of the first 10 paying customers through warm outreach, community, and founder-led sales.

💡

Pro tip: Do things that do not scale. Personally email every prospect, personally onboard every customer, personally call every churned user. The unscalable effort of the first 10 customers builds the foundation for the next 10,000.

Frequently Asked Questions

Claude provides structured analysis, frameworks, and strategic thinking that rival entry-level consulting. However, it cannot replace the pattern recognition, personal network, and emotional support of an experienced startup mentor. Use Claude for the analytical heavy lifting — financial models, market sizing, competitive analysis — and a human mentor for judgment calls, introductions, and the "I have seen this before" perspective.
Claude uses publicly available data and reasonable assumptions, but its market sizing should be treated as informed estimates, not research-grade numbers. For investor presentations, validate key assumptions with primary research, industry reports, and comparable company data. Claude is excellent at structuring the analysis and identifying assumptions — you should verify the inputs.
Yes, and Claude is particularly strong at this because investor emails require conciseness, clarity, and strategic framing — all Claude strengths. However, authenticity matters in investor communication. Use Claude to structure and refine your message, but make sure the final voice sounds like you, not like AI. Investors invest in founders, and founders need to sound human.
Claude can help with technical architecture decisions, technology stack evaluation, and build-vs-buy analysis. For deep technical implementation questions, it is best as a thinking partner — helping you weigh tradeoffs and consider options. For cutting-edge or highly specific technical decisions, supplement Claude with domain experts who have recent hands-on experience.
Use Claude for pre-meeting preparation (analysis, frameworks, options), post-meeting documentation (action items, decision records), and async problem-solving (strategy questions that do not need a meeting). Share Claude outputs as starting points for team discussion, not final decisions. The team adds context, judgment, and commitment that AI analysis alone cannot provide.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

14-day free trial. Cancel anytime.