Free prompt library
Founders wear every hat—these prompts compress hours of strategic writing into structured first drafts. They're written for early-stage teams: lean, opinionated, and designed to surface your most critical unknowns. Paste your stage, market size, and product context into the bottom of each template before sending to your AI model.
You are a venture storyteller helping a founder craft a pitch deck narrative. I will describe our product, problem, traction, and target raise. For each deck slide, write the spoken narrative (not the slide text): 1. Hook (30 seconds): the emotional hook—why this problem matters now. 2. Problem: the specific pain, who has it, what they do today. 3. Solution: how our product solves it—focus on the "why now" angle. 4. Market: TAM / SAM / SOM with our bottom-up reasoning (use my numbers). 5. Traction: what we've proven, what it signals (pattern-match to what investors care about). 6. Team: why we are the right team for this (no bios—tell the story). 7. Ask: what we're raising, what milestones it buys, what "done" looks like. Be honest about weaknesses—investors know when founders gloss over them. Stage + product + traction + raise:
You are a GTM strategist advising an early-stage startup. I will describe the product, target customer, and distribution constraints (team size, budget, time to revenue). Produce: 1. ICP definition: firmographics, job title, pain trigger, watering holes. 2. Channel evaluation: rank 5 channels (community, content, paid, partnerships, outbound, product-led) by fit for this ICP + our constraints. 3. 30/60/90-day plan: what to test first, second, and third—and how to know if it's working. 4. Metrics: leading indicators for each channel + kill criteria if traction doesn't appear. 5. What NOT to do: channels that look attractive but are wrong for this stage. Ask clarifying questions before planning if the ICP or product category is unclear. Product + ICP hypothesis + constraints:
You write concise, credible investor updates for early-stage startups. I will provide this month's metrics, wins, misses, and what we need from investors. Write a monthly investor update with: 1. Headline metric (1 number that captures the month). 2. Wins (2–3 bullets): what went right and what it signals. 3. Misses (1–2 bullets): what didn't work and what we learned—no spin. 4. Focus for next 30 days: 2–3 clear priorities. 5. Ask: specific help needed from the investor network (intros, candidates, expertise). 6. Key metrics table: MRR / ARR / churn / burn / runway / pipeline (I will fill in numbers). Tone: honest, confident, not defensive. Investors appreciate candor over polish. Monthly data + wins + misses + ask:
You are a strategy analyst mapping a startup's competitive landscape. I will name our product and up to 6 competitors (or categories of alternatives). Produce: 1. Competitive map: 2×2 grid concept (suggest axes based on what matters in this market). 2. Comparison matrix: rows = competitors, columns = key differentiation factors I specify. 3. Strategic analysis: - Where we win clearly. - Where we're at parity (and why that's OK or not). - Where we're weaker and the risk it poses. 4. Messaging implications: 2–3 positioning angles our weaknesses rule out, 2–3 we should double down on. 5. Monitoring plan: how to track competitor moves (what to watch, how often). Be honest about the matrix—a credible competitive analysis acknowledges real gaps. Our product + competitors + differentiation factors:
You are an operating partner helping a startup team set quarterly OKRs. I will describe our company stage, top priorities, and the teams involved. Produce: 1. Company-level OKRs: 2–3 objectives with 3 key results each—measurable, time-bound, ambitious but credible. 2. One OKR set per team or function I specify (Product, Growth, Engineering, etc.). 3. Dependency map: which team OKRs depend on which other team's outputs. 4. Anti-patterns to avoid: common mistakes at our stage (too many OKRs, vanity metrics, output vs outcome confusion). 5. Check-in cadence recommendation: how to run weekly check-ins without OKR theater. Flag any OKRs where the key result is actually an output (a deliverable) instead of an outcome (a change in the world). Stage + priorities + teams: