Unleash the Power of AI The Complete Startup Prompt Library

Copy. Customize. Accelerate your startup journey with expert-built prompts designed for real founders.

AI Prompts Image

Vibe Coding

+ Expand all
Key Assumptions Finder

Identify the critical underlying insights about your customers and how they use products.

<p>My product helps [target customer] [achieve purpose] using [unique feature or mechanism].</p> <p>Now I need to list the assumptions I’m making about how they use the product, what they expect, when they engage, and what behavior I’m counting on.</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| # | Assumption | Why It Matters |</p>
Simple Product Spec

Define your product's core features, functionality, and requirements in a clear, actionable way to be used as a prompt.

<p>I have an idea for a product and I want to turn it into a simple, clear product spec. Here&#39;s what I know so far:</p> <p>What it is or does:</p> <p>[briefly explain what your product is or helps with]</p> <p>Who it&#39;s for:</p> <p>[describe the people or businesses you&#39;re building it for]</p> <p>Why it matters:</p> <p>[what’s the main problem it solves or benefit it provides?]</p> <p>Important features (optional):</p> <p>[list a few things you think should be part of the product]</p> <p>Things I&#39;m not building (optional):</p> <p>[list anything you&#39;re intentionally leaving out or not focusing on for now]</p> <p>Take this and return a plain text product spec with the following sections:</p> <p>Product Name: [name it something simple for now]<br> One-Liner: [what it does, for whom, and why]<br> Target User: [who it&#39;s for]<br> Core Problem: [the main pain point it solves]</p> <p>Key Features:</p> <p>Feature 1<br> Feature 2<br> Feature 3</p> <p>User Flow:</p> <p>What happens first<br> What happens next<br> How the user completes their goal</p> <p>Out of Scope:</p> <p>Anything not being built for now</p>
Tooling Setup Checklist

List essential tools/software needed to build, launch, and operate your product effectively.

<p>ROLE<br> You are a startup operations expert with deep knowledge of the tools used to build, launch, and grow digital products.</p> <p>GOAL<br> List essential tools a team needs to build, launch, and operate the following product:<br> [Product description: what it does, who it’s for, and how it works]</p> <p>Include tools across categories like development, design, automation, analytics, customer support, and operations.</p> <p>OUTPUT<br> Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:<br> | Category | Tool | What It’s For |</p> <p>GUIDELINES<br> • Include 1 to 3 tools per category<br> • Prioritize proven, widely used tools<br> • Skip fluff and focus on tools that save time or help ship faster</p>
User Story Map

Visualize your user's journey and prioritize features by mapping their tasks, goals, and pain points throughout their experience with your product.

<p>I’m working on a product that helps<br> [target user]<br> [achieve goal or solve a problem]<br> using<br> [unique mechanism or key feature]</p> <p>I want to map out the main steps a user goes through, what they’re trying to achieve at each step, and what challenges they face — so I can decide what features to build first.</p> <p>OUTPUT<br> Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:<br> | Step | User Goal | Key Tasks | Pain Points | Potential Features |</p> <p>NOTES<br> • Include 5 to 7 steps in the journey<br> • Focus on high-level goals, not micro-actions<br> • Keep each entry short and clear</p>

Startup Ideation

+ Expand all
Unknowns Narratives

Uncover insights and assumptions that you make have missed out on.

<p>I’m building [product or solution] for [target audience] to help with [problem or goal] using [unique feature, mechanism, or approach].</p> <p>Using this information, dig deep into my idea and approach. Identify any hidden assumptions, unknowns, or uncertainties I might be overlooking. Focus on things that could affect product-market fit, user behavior, adoption, or business model. Return a short analysis in clear, thoughtful language that surfaces 5 to 7 key points I should think about.</p>
Problem Snapshot

Turn a fuzzy hunch into a crisp “who / struggle / why-now” statement.

<p>I’m building a product for [target audience] who struggle with [the main challenge or frustration].</p> <p>Using this information, rewrite it into a sharp who / struggle / why-now statement. Keep it short and clear so it highlights who the user is, what their struggle is, and why solving it now matters. Make sure the statement flows and reads well.</p>
Zero-to-One vs. One-to-N

State whether this is invention or scale play and how that changes your idea and assumptions.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, tell me whether this idea is more likely a zero-to-one play (invention, creating something new) or a one-to-n play (scaling or improving something proven). Explain why, and highlight how that framing changes my assumptions, risks, and approach to execution.</p>
Bad Ideas Blitz

Generate 20 intentionally “bad” ideas to surface surprising good ones

<p>My interest area is [industry, theme, or topic, for example AI tools, healthcare, travel, education, social media]</p> <p>Using this, generate 20 intentionally bad, silly, or impractical product or business ideas in this space. They should be exaggerated, funny, or clearly flawed but still loosely related to the industry or theme. The goal is to break patterns, surface overlooked angles, and spark creative thinking.</p> <p>Return the list as plain text with each idea numbered from 1 to 20.</p>
First Principles

Reduce the problem to fundamentals and rebuild solution logic without unwarranted assumptions.

<p>The problem I’m working on is<br> [state the problem in one or two sentences]</p> <p>Using this, break it down into first principles by</p> <p>Stripping away assumptions and restating the problem in its most basic terms<br> Identifying the fundamental truths or constraints that are undeniably valid<br> Rebuilding the logic step by step into a solution approach that is free from unproven assumptions<br> Highlighting how this new framing changes or challenges my original perspective</p> <p>Keep the explanation clear, logical, and structured so I can see both the raw fundamentals and the rebuilt solution logic.</p>
Before/After Story

Generate two short paragraphs: life before vs. after your product.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, write two short paragraphs</p> <p>Paragraph 1: Describe the life of the target audience before using the product. Highlight the struggles, inefficiencies, or frustrations they face.</p> <p>Paragraph 2: Describe their life after using the product. Show how their experience improves, what outcomes they achieve, and why it feels like a meaningful transformation.</p> <p>Keep it simple, relatable, and emotionally engaging.</p>
Unbundle/Bundle

Determine what you’re unbundling or rebundling and the user barriers you remove.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, tell me<br> • What existing solutions or workflows this product is unbundling (breaking apart)<br> • What it is rebundling (combining into one place or flow)<br> • The main barriers or frictions for users that this approach removes<br> • Why this framing matters for positioning and go-to-market</p> <p>Keep the output concise and clear so I can quickly see how my product fits into the unbundle vs rebundle story.</p>
Wedge Selection

Choose a narrow, high-pain beachhead; define use case and why users would choose your product.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, identify<br> • A narrow, high-pain beachhead use case where adoption is most likely to start<br> • Why this wedge is critical and how it builds credibility or traction<br> • The main reasons users in this wedge would choose my product first over alternatives<br> • How solving this wedge use case creates expansion opportunities into adjacent markets or features</p> <p>Keep the output focused, specific, and actionable so I can clearly see where to start and why it matters.</p>
PESTLE “Why Now”

Generate 1-3 Political, Economic, Social, Tech, Legal, Environmental shifts that enable your idea.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, generate 1 to 3 relevant shifts in each PESTLE category that support why now is the right time for this idea</p> <p>Political<br> Economic<br> Social<br> Technological<br> Legal<br> Environmental</p> <p>Keep each shift short, clear, and directly tied to how it enables or accelerates adoption of my product</p>

Customer Development

+ Expand all
Potential Customers

Identify and profile the specific individuals or organizations most likely to buy your product or service.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| # | Customer Segment | Description | Primary Needs | Where to Find Them |</p> <p>Guidelines<br> • Include 3 to 5 distinct segments<br> • Be specific. Avoid generic labels like &quot;everyone&quot;<br> • Think in terms of roles, behaviors, industries, or use cases<br> • In &quot;Where to Find Them&quot;, mention platforms, communities, or channels</p>
Customer Archetype

Create detailed profiles of your potential target customers based on your startup and market.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Based on this, return 2 to 3 detailed customer archetypes in a markdown table format with the following columns</p> <p>| Archetype Name | Description | Goals | Pain Points | Buying Triggers | Where to Reach Them |</p> <p>Guidelines<br> • Archetypes should represent distinct customer types or roles<br> • Focus on real-world behaviors and needs, not abstract personas<br> • Keep each field short but specific<br> • Use accessible language that a founder can act on</p>
Interview Plan & Script

Create structured questions and conversation flow for customer interviews to validate your assumptions and gather insights.

<p>What I’m working on:<br> [Describe your product or idea in one line]</p> <p>Who I want to talk to:<br> [Your ideal user or customer type]</p> <p>What I’m trying to learn:<br> [The assumptions, behaviors, or needs you want to validate]</p> <p>Now give me:<br> • A short intro to explain the purpose of the interview<br> • A couple of warm-up questions to get them comfortable<br> • 5 to 7 core questions that dig into their needs, habits, and pain points<br> • 1 or 2 wrap-up questions to close the conversation</p> <p>Keep it casual, open-ended, and focused on real stories</p>
Mapping Buyer Decisions

Analyze your target customer's complete decision-making process from problem awareness to purchase completion.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, describe the full decision-making journey a typical customer might go through. Start from the moment they become aware of the problem and walk through what they think, feel, and do at each stage leading up to the purchase. Include steps like recognizing the problem, researching options, comparing solutions, and making a decision.</p>
Research Goals Brief

Define the 3–5 questions you must answer about users, pains, and context each month.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, define 3 to 5 research questions I should aim to answer about my users, their pains, and the context in which they use or would use my product.</p> <p>Keep the questions specific, open-ended, and actionable so they can guide monthly customer interviews, surveys, or experiments. Return the output as a short list, not long paragraphs.</p>
Warm-Up Bank

A library of neutral openers and laddered probes for deeper insight during customer interviews.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, generate a list of neutral warm-up questions I can use to start customer interviews without bias. Then create a set of laddered probes that help me go deeper into user needs, pains, and behaviors.</p> <p>Organize the output into two sections</p> <p>Warm-Up Questions<br> 5 to 7 neutral openers that build rapport and get users talking about their context</p> <p>Laddered Probes<br> 5 to 7 progressively deeper questions that uncover motivations, struggles, and decision-making processes</p> <p>Keep all questions open-ended and simple enough to use in live interviews.</p>
Buying Committee Snapshot

Define roles (user, champion, budget holder, security, legal), decision rights, and possible timelines for potential B2B buyers.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Role | Responsibility in Buying Process | Decision Rights | Key Concerns | Likely Timeline Involvement |</p> <p>Guidelines<br> • Include common roles such as user, champion, budget holder, IT/security, legal, and procurement. Indicate who might be playing the role in each scenario. In case a role doesn&#39;t exists, specify that.<br> • Define what each role cares about most in the evaluation process<br> • Clarify who can influence vs. who can approve the purchase<br> • Suggest typical timelines for when each role enters the process</p>

Build Your Startup with AI in 2 Weeks

Join the 2-week bootcamp and learn to build, test, and validate your MVP using AI tools. No coding skills required.

Market Research

+ Expand all
Competitor List

Map direct and indirect competitors in your market, analyzing their strengths, weaknesses, and positioning.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Competitor | Type (Direct or Indirect) | Key Offering | Strengths | Weaknesses | How We’re Different |</p> <p>Guidelines<br> • Include 5 to 7 competitors<br> • Be specific and relevant to the space<br> • Focus on both product features and market positioning<br> • Type should reflect how closely they compete with what I’m building</p>
Market Definition & Boundaries

Define the exact category you’re in, close substitutes, and adjacent businesses you might collide with.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Category Type | Examples | Why It Matters for My Product |</p> <p>Fill the rows with<br> • Exact Market Category<br> • Close Substitutes<br> • Adjacent Businesses or Categories</p> <p>Guidelines<br> • Keep each entry short and easy to scan<br> • Show specific examples where possible<br> • Focus on how these categories affect positioning, differentiation, and potential collisions</p>
Demand Drivers

Identify forces (tech, regulation, behavior) that increase or decrease demand for your product in the future.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, write one short paragraph describing the major forces that could increase demand for my product over the next 3 to 5 years, focusing on technology, regulation, consumer behavior, or broader market shifts.</p> <p>Then write one short paragraph describing the major forces that could decrease demand, including risks, regulatory barriers, competitive dynamics, or behavioral shifts that might reduce adoption. Keep the analysis clear, balanced, and directly tied to my product’s context.</p>
Seasonality & Cycles

Identify calendar or economic cycles that affect demand for your product.

<p>I’m building a product that helps<br> [target audience and region]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, create a checklist of seasonality and cycle factors for me to consider. Organize them into these categories</p> <p>Calendar Cycles: holidays, cultural events, school terms, seasonal weather patterns</p> <p>Economic Cycles: recessions, booms, tax season, sector-specific shifts</p> <p>Behavioral Cycles: consumer habits, budget resets, annual planning, lifestyle trends</p> <p>For each category, list the 2 to 4 most relevant cycles and note whether they are likely to increase or decrease demand for my product. Keep entries short, clear, and actionable so I can use this as a planning checklist.</p>
Myth vs. Reality

Discover common myths about your category and contrast with proven insights.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Myth | Reality | Why This Matters for My Product |</p> <p>Guidelines<br> • Include 5 to 7 myths that are common in this category or market<br> • For each one, state the proven reality or insight that contradicts it<br> • Tie the reality back to why my product is relevant or differentiated<br> • Keep explanations short and punchy so they can be used in pitches, messaging, or content</p>
Trend Radar

List emerging tech/regulatory/social trends, theit likely impact, and early indicators to watch out for.

<p>I’m building a product that helps<br> [target audience and region/location]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Trend | Category (Tech, Regulatory, Social, etc) | Likely Impact | Early Indicators to Watch |</p> <p>Guidelines<br> • Include 5 to 10 trends that are relevant to the product and category<br> • Make sure the mix covers technology, regulatory, and social factors<br> • Explain the likely impact (positive or negative) in simple terms<br> • Give clear early signals or indicators that I should monitor to track the trend’s evolution</p>

Revenue & Business Models

+ Expand all
Pricing Design

Develop various pricing strategies, and structure based on your product and market dynamics.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return 3 to 4 possible pricing strategies I could consider.<br> For each one, include:</p> <p>Name of the strategy<br> How it works (brief explanation of the pricing structure)<br> Why it might work for my product and audience<br> A possible risk or tradeoff</p>
Pricing Experiments

Learn simple tests on price levels to improve revenue without hurting conversion.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, generate 3–5 pricing experiments I can run. Each experiment should include:<br> • Experiment Name<br> • Test Description (what to change and how)<br> • Hypothesis (what I expect to learn)<br> • Metric to Track (conversion, revenue, retention, etc)<br> • Risk Level (low, medium, high)</p> <p>Guidelines<br> • Focus on simple, quick-to-run experiments that don’t require major product changes<br> • Include at least one experiment testing higher pricing and one testing different packaging/bundling<br> • Make experiments specific enough that I can act on them right away</p>
Free vs. Trial

Decide between a freemium plan or a trial according to your business and market needs.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, provide a recommendation on whether a freemium plan or a free trial makes more sense for my business.</p> <p>Your response should include:<br> • A clear recommendation (freemium or trial)<br> • 2–3 reasons why this option fits my audience and business model<br> • Potential risks or downsides to consider<br> • An alternative scenario where the opposite model might work better</p> <p>Guidelines<br> • Consider product type (SaaS, marketplace, consumer app, etc.)<br> • Take into account buyer psychology (ease of adoption, trust-building, urgency)<br> • Frame the decision in terms of revenue growth, retention, and scalability</p>
Starter Plan

Define a low price plan that brings in users while nudge them towards higher tiers.

<p>I’m building a product for [target audience] that helps them [achieve outcome / solve problem] using [solution / approach].</p> <p>Based on this, imagine we are designing a Starter Plan. Your task is to create a simple entry-level pricing tier that feels irresistible to first-time users, while also leaving room for them to see value in upgrading later.</p> <p>In your response, do the following:<br> • Tell me what the Starter Plan would look like (pricing, features, positioning).<br> • Explain why this Starter Plan would appeal to new customers.<br> • Show how this plan naturally guides users toward a mid-tier or premium offering.<br> • Highlight the psychological triggers that make the Starter Plan feel safe, affordable, and easy to try.</p>
Localization

Suggest international price points that round cleanly, include a small FX buffer, and respect local willingness-to-pay.

<p>You are my startup’s international pricing strategist. My home market price is [currency and amount per user/usage] and my target regions are [target regions/countries]</p> <p>Your task is to:<br> Imagine you’re setting up the pricing page for each region tomorrow. For every country/region, tell me:</p> <p>The final localized price in local currency (rounded cleanly).</p> <p>Whether you raised, lowered, or kept the price level relative to my home market and why.<br> A one-line customer-facing justification I could use if asked.<br> Deliver the results as if you were handing me the draft of a real pricing page: clear, ready-to-use numbers and simple rationales.</p>
Simple Price Tests

Create an A/B test for pricing and define success metrics.

<p>I’m currently offering [product] to [target audience] at [current price]. I want to test an alternative price of [test price] to see if it increases or decreases overall performance.</p> <p>Using this information, design a simple A/B test that compares outcomes like conversion rate, revenue per customer, and customer retention (if relevant). Provide the exact experiment setup, what data I should track, the sample size or timeline needed, and how to interpret the results so I can make a confident decision about my pricing.</p>

Founder Market Fit

+ Expand all
Founder Market Fit

Analyze whether you have the right mix of background, skills, and personal connection to solve the problem your startup addresses.

<p>I’m building a startup that helps<br> [target audience]<br> [achieve what or solve what problem]<br> through<br> [product or approach].</p> <p>Here’s my background:<br> [relevant personal or professional experience]</p> <p>Here’s why I care about this problem:<br> [personal connection or motivation]</p> <p>Here are the skills or strengths I bring:<br> [relevant capabilities, knowledge, or insights]</p> <p>Here’s where I might need support:<br> [areas where I lack experience or skills]</p> <p>Now, evaluate my founder-market fit based on this input. Return:</p> <p>A short summary of why I may or may not be a good fit</p> <p>Any standout advantages I have</p> <p>Any notable gaps or risks</p> <p>A clear verdict: Strong Fit, Medium Fit, or Weak Fit — with 1 sentence explaining why</p>
Skill Stack Inventory

Catalog your top skills relevant to your market and where they map to today’s needs.

<p>I want to catalog my skills and see how they align with today’s market.</p> <p>Here are my inputs:<br> • Top skills: [list your hard and soft skills here]<br> • Target market/industry: [your target market or industry]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Skill | Description | Market Demand Today | Example Roles/Use Cases | Gaps or Next Steps |</p> <p>Guidelines<br> • In Description, briefly define what the skill means in practice.<br> • In Market Demand Today, label demand as High / Moderate / Low with a short reason.<br> • In Example Roles/Use Cases, connect the skill to current roles, industries, or startup applications.<br> • In Gaps or Next Steps, suggest how I can strengthen or complement the skill (training, adjacent skills, certifications).</p>
Risk Appetite & Runway

Determine risk level you’re willing to assume according to your runway and fallback income options.

<p>I want to understand my risk appetite based on my financial runway and fallback options.</p> <p>Inputs:<br> • Current monthly expenses: [amount]<br> • Current savings/runway: [amount and months]<br> • Fallback income options: [options such as freelancing, part-time work, family support, etc.]<br> • Risk tolerance: [low / medium / high, or leave blank to assess]</p> <p>Using this information, create a structured assessment with the following sections:</p> <p>Runway Analysis<br> How many months of runway I have<br> Burn rate vs. buffer</p> <p>Fallback Options<br> Practicality and reliability of each fallback source<br> How much they extend my runway</p> <p>Risk Appetite Level<br> Classification of my risk appetite (conservative, balanced, aggressive)<br> Explanation tied to my financial situation</p> <p>Recommendations<br> Strategic choices I can make (e.g., pursue high-risk startup full-time, balance with side income, conserve runway)<br> Key trade-offs to consider</p>
Bias & Blind Spot Checklist

Identify likely cognitive biases you have and checks to limit them.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return a plain text list of 5–7 likely cognitive biases and blind spots I may face as a founder. For each one, include:<br> • Name of the bias/blind spot<br> • How it might show up in my decision-making<br> • Why it matters (the risk or consequence)<br> • A practical check or safeguard to limit it</p> <p>Guidelines<br> • Make examples specific to early-stage founders (e.g., confirmation bias in customer interviews, optimism bias in runway planning)<br> • Keep safeguards simple and actionable (e.g., structured decision reviews, seek external feedback, run small tests before scaling)<br> • Focus on biases that could impact survival and growth in the earliest stages</p>
Ethical Alignment

Define values that matter in your chosen market and how align with your personal ethics.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>My personal ethics and values are:<br> [list 3–5 personal values or principles that matter to you as a founder]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Value in Market | Why It Matters | My Personal Alignment | Risks of Misalignment | How to Show Alignment |</p> <p>Guidelines<br> • Include 3–5 values relevant to this market<br> • Keep explanations short and clear<br> • Show how my personal values overlap with market expectations<br> • Suggest simple, visible ways to demonstrate alignment</p>

Build Your Startup with AI in 2 Weeks

Join the 2-week bootcamp and learn to build, test, and validate your MVP using AI tools. No coding skills required.

Pitching

+ Expand all
Elevator Pitch

Expand your one-sentence pitch by answering why now is the right time, why you're the right team to execute, and including a specific ask for investment, partnerships, or feedback.

<p>I’m working on [what your product or company does in one sentence]</p> <p>Using this, generate a complete elevator pitch that includes:</p> <p>What the company does, for whom, and the problem it solves<br> Why now is the right time for this product to exist<br> Why I’m the right person to build it<br> What I’m currently looking for (assume something realistic if not provided)</p> <p>Use the following structure, filling in any missing info with logical assumptions:</p> <p>My company, [name], is developing [offering] to help [audience] [solve a problem] with [unique approach].<br> The timing is right because [why now]. I’m the right person to build this because [why me].<br> I’m currently looking for [ask] to [what the ask will help you do].</p> <p>Keep it clear, conversational, and under 60 seconds.</p>
Pitch Deck Check

Check your pitch deck to ensure it covers essential information with clear visuals and persuasive messaging.

<p>I’ve attached a pitch deck. Review it and tell me if it clearly communicates the essentials of a strong startup pitch. Specifically, check if it covers the core elements like problem, solution, market, business model, traction, team, and the ask. Let me know what’s missing, what could be improved, and whether the visuals and messaging are clear and persuasive.</p>
Story Arc Builder

Structure your pitch narrative with clear problem setup, solution introduction, market opportunity, and compelling call-to-action that creates emotional engagement.

<p>Here’s what I know</p> <p>Problem<br> [what pain point or frustration are people facing]<br> Solution<br> [what your product or startup does to solve it]<br> Audience<br> [who this is for]</p> <p>Using this information, write a short pitch story in three to four sentences that introduces the problem, presents the solution, and explains why it matters to this audience. Make it clear, emotionally engaging, and easy to say out loud.</p>
Elephant Identifier

Anticipate obvious concerns, weaknesses, or questions that investors will raise about your startup based on your pitch deck.

<p>I’m building [what your startup does in one sentence]</p> <p>Based on this, act like an investor who just reviewed my pitch</p> <p>Tell me</p> <p>• What obvious questions or concerns immediately come to mind<br> • What might make you hesitate to invest<br> • What assumptions I may be making that need proof<br> • Any red flags in the business model, traction, team, or market<br> • One thing I should proactively address in my pitch to build more trust</p> <p>Be direct and critical as if you are evaluating whether or not to write a check</p>
Pitch Deck Content Auditor

Evaluate each slide's effectiveness in answering investor questions with clear data, compelling narrative, and clarity.

<p>I have a pitch deck for a startup that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, review the deck slide by slide and assess whether each slide<br> • Answers the core investor questions for that topic<br> • Uses clear, concise messaging<br> • Supports the narrative with relevant data or visuals<br> • Fits logically into the overall flow of the pitch</p> <p>Return feedback for each slide including<br> • What works well<br> • What is missing or unclear<br> • How to improve it to strengthen the pitch</p> <p>End with a summary of the deck’s overall strengths, weaknesses, and top three improvements that would make it more investor-ready.</p>
One Sentence Pitch

Create a one-sentence pitch using the Founder Institute format to clearly communicate your startup's core elements and grab listener attention quickly.

<p>Here’s what I have:<br> • Company Name: [name]<br> • What we’re building: [offering]<br> • Who it’s for: [audience]<br> • What problem it solves or goal it helps them reach: [problem or goal]<br> • What makes it different: [secret sauce]</p> <p>Return a single sentence pitch in this format:<br> My company, [Company Name], is developing [Defined Offering] to help [Defined Audience] [Solve Problem] with [Secret Sauce].</p>

Product Development

+ Expand all
Product Roadmap Builder

Sequence feature development priorities with timelines, resource requirements, and metrics aligned to your startup's goals.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]<br> Our main goals for the next 12 months are<br> [list top goals or priorities]</p> <p>Using this information, return a roadmap that includes</p> <p>| Feature or Initiative | Priority | Timeline | Resources Needed | Success Metric |</p> <p>Guidelines<br> • Sequence features logically based on impact and dependencies<br> • Assign realistic timelines<br> • Include both product and infrastructure work if relevant<br> • Tie each item to a measurable outcome linked to our goals</p>
Solution Goals Definer

Identify the most critical customer problems your product must solve to drive meaningful user adoption and growth.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Problem to Solve | Why It Matters | Impact if Solved | How to Measure Success |</p> <p>Guidelines<br> • List problems based on the needs of the target audience<br> • Focus on high-impact problems that directly influence adoption or retention<br> • Keep descriptions short, clear, and actionable<br> • Include measurable indicators for success where possible</p>
Product Experiments Designer

Standardize hypothesis, metric, sample needs, and kill rule for product tests.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, design 3–5 product experiments. Each experiment should be written in the format below:</p> <p>Experiment Name:<br> Give the test a short, descriptive title.</p> <p>Hypothesis:<br> State what I expect to learn or validate.</p> <p>Metric to Track:<br> Define the key outcome that will show if the hypothesis is correct.</p> <p>Sample Size / Timeline:<br> Estimate how many users or how long is needed to get a reliable result.</p> <p>Kill Rule:<br> Specify the clear criteria for stopping, pivoting, or scaling the experiment.</p> <p>Guidelines<br> • Keep each experiment simple and fast to execute<br> • Focus on measurable user behavior<br> • Make kill rules objective so decisions are clear</p>
Changelog Creator

Establish changelog format, and channels to build trust and momentum.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach].</p> <p>Using this information, describe the changelog format I should follow and how often to share updates. Explain what channels to use and how the changelog can build trust with users while also creating momentum and excitement around the product. Keep the response short, practical, and easy to apply.</p>
Feature Scorecard

Rank ideas by impact, confidence, and effort with a simple, repeatable rubric.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Feature Idea | Impact (1–5) | Confidence (1–5) | Effort (1–5) | Total Score |</p> <p>Guidelines<br> • Keep scoring simple (1 = low, 5 = high)<br> • Show how to calculate a total score (e.g., Impact × Confidence ÷ Effort)<br> • Include a short note on how to use the results to prioritize features</p>
Product Principles

Write 5–7 decision rules that guide tradeoffs and keep the product coherent and relevant.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach].</p> <p>Using this information, write 5–7 product principles I can use as decision rules. Each principle should guide tradeoffs, ensure consistency, and keep the product coherent and relevant as it grows. Keep them short, memorable, and practical enough that my team can apply them when making everyday choices.</p>

Build Your Startup with AI in 2 Weeks

Join the 2-week bootcamp and learn to build, test, and validate your MVP using AI tools. No coding skills required.

Co Founders & Teambuilding

+ Expand all
Role Prioritization Matrix

Identify the critical positions your startup needs to fill first based on business priorities, skill gaps, and growth requirements over the next 12 months.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]<br> Our main business priorities for the next 12 months are<br> [list top goals or priorities]<br> Current team and skills we already have<br> [list team members or core skills]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Role | Reason for Priority | Expected Impact | Timeframe to Hire | Urgency Level |</p> <p>Guidelines<br> • List 5 to 7 roles based on business priorities and skill gaps<br> • Explain why each role is important now<br> • Include realistic hiring timeframes<br> • Rank urgency as High, Medium, or Low</p>
Test Project Designer

Create specific assignments that allow candidates to demonstrate skills and fit before making hiring decisions.

<p>Role type<br> [job title or function, for example Product Designer, Backend Engineer, Growth Marketer]</p> <p>Key skills to test<br> [list the most important skills or capabilities for this role]</p> <p>Seniority level<br> [entry, mid, senior]</p> <p>Time commitment for the test project<br> [in hours or days]</p> <p>Additional context about the company or product<br> [brief description so the assignment feels realistic]</p> <p>Using this information, design a test project that<br> • Simulates a real problem the candidate would face in this role<br> • Clearly outlines the deliverables and success criteria<br> • Matches the time commitment specified</p>
Onboarding Checklist Creator

Design systematic processes that ensure new hire productivity while establishing clear expectations and performance standards.

<p>Role type<br> [job title or function, for example Customer Success Manager, Software Engineer, Marketing Lead]</p> <p>Seniority level<br> [entry, mid, senior]</p> <p>Key goals for the first 90 days<br> [list top priorities for the role]</p> <p>Company or team context<br> [brief description to help shape onboarding steps]</p> <p>Using this information, create a role-specific onboarding checklist that includes<br> • Pre-start preparations before day one<br> • Day one orientation steps<br> • First week activities and training<br> • First 30 days performance expectations<br> • 31 to 90 day goals and check-ins<br> • Leave room for customization where required</p>
Job Description Optimizer

Turn a basic organizational requirement into a concise, candidate-friendly JD that attracts the right people.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>I have a basic organizational requirement for a new role:<br> [insert rough requirement here]</p> <p>Using this information, create a candidate-friendly job description with the following sections:</p> <p>Role Summary<br> A short, clear overview of what the role is about.</p> <p>Key Responsibilities<br> 3–5 concise bullet points describing the main tasks.</p> <p>Must-Have Skills<br> The essential skills or experiences needed.</p> <p>Nice-to-Have Skills<br> Optional skills that would make a candidate stand out.</p> <p>Why Join Us<br> 1–2 sentences showing why this role is exciting and worth applying for.</p> <p>Guidelines<br> • Keep it concise and easy to scan<br> • Use approachable, non-corporate language<br> • Make it clear why the role matters in an early-stage startup</p>
Sourcing Strategy Map

List channels, communities, and messages to reach qualified candidates fast for each role.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>I need to hire for this role:<br> [insert role here]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Channel | Community / Platform | Message to Use | Why It Works |</p> <p>Guidelines<br> • Include 4–6 relevant sourcing channels<br> • Match messages to the role and the culture of the community<br> • Keep messages short, authentic, and founder-friendly<br> • Highlight why each channel is a good fit for reaching qualified candidates fast</p>
Referral Program Script

Create a simple referral ask with examples, rewards, and follow-up steps for your team.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach].</p> <p>Using this information, create a simple referral program script for my team. Include an easy referral ask, example messages they can use, possible rewards for successful referrals, and follow-up steps to thank people and keep momentum. Keep it short, natural, and founder-friendly.</p>
Compensation Bands Snapshot

Set transparent salary and equity ranges by level according to your startup's structure and market position.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. My startup is at [stage: pre-seed, seed, Series A, etc] and we are based in [geography].</p> <p>Using this information, create transparent compensation bands for my startup. Include salary and equity ranges by level (e.g., junior, mid, senior, leadership) that reflect both our stage and market position. Keep the ranges simple, realistic for an early-stage company, and easy to communicate to candidates.</p>
Interview Guide

Create a list of questions to interview potential candidates to assess their competency and team fit.

<p>I&#39;m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. I am preparing to hire for the role of [insert role here].</p> <p>Using this information, create a structured interview guide with a list of questions to assess both competency and team fit. Include a mix of technical/role-specific questions, behavioral questions, and culture-fit questions. Keep the list concise, practical, and tailored for an early-stage startup environment.</p>

Growth

+ Expand all
Growth Tactics Generator

Brainstorm and document specific strategies to increase acquisition through new channels, partnerships, or marketing approaches.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]<br> We have a current monthly marketing budget of [amount or leave blank]<br> Our current main acquisition channels are [list channels or leave blank]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Tactic | Channel or Approach | How It Works | Estimated Effort | Potential Impact |</p> <p>Guidelines<br> • Suggest 5 to 10 tactics that fit the target audience and budget<br> • Include a mix of low-cost, scalable, and experimental approaches<br> • Make each tactic specific enough to take action immediately<br> • Highlight at least one partnership or co-marketing idea</p>
Sales Target Tracker

Define aggressive revenue goals with specific metrics based on your vision, market and opportunity.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]<br> Our average sale value is [amount per deal or per customer]<br> Our sales cycle or purchase frequency is [number of days or months]<br> We have [number of sales reps or leave blank]<br> Our target time frame is [for example monthly, quarterly, yearly]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Time Period | Revenue Target | Number of Sales Needed | Leads or Prospects Required | Conversion Rate Assumed |</p> <p>Guidelines<br> • Make projections aggressive but achievable based on the inputs<br> • Adjust approach automatically depending on whether the product is B2B or B2C<br> • If data is missing, make reasonable assumptions and note them<br> • Include sales volume and lead requirements so goals are actionable, not just revenue numbers</p>
Growth Milestone Mapper

Set specific, time-bound growth targets with clear success criteria to maintain strategic focus and accountability for you and your team.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]<br> Our main growth goals for the next 12 months are<br> [list your top growth goals or priorities]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Milestone | Target Date | Success Criteria | Owner | Notes |</p> <p>Guidelines<br> • Include 5 to 8 milestones that are specific and measurable<br> • Ensure each milestone has a clear success metric and a deadline<br> • Assign an owner so accountability is built in<br> • Include notes with any dependencies or risks to track</p>
North Star Metric Picker

Choose a single metric that reflects your startup's value along with a clear definition.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]<br> We are currently at [stage: pre-seed, seed, Series A, etc]</p> <p>Using this information, suggest 2–3 possible North Star Metrics and return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Metric | Definition | Why It Matters | How It Drives Growth |</p> <p>Guidelines<br> • Pick only one final recommendation, but show alternatives for context<br> • Keep definitions clear and measurable<br> • Make sure the metric reflects core value delivered to users</p>
Growth Quick Wins

Identify low-effort, high-impact changes across product, pricing, or messaging to lift user activity immediately.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Quick Win | Category (Product / Pricing / Messaging) | Action | Expected Impact |</p> <p>Guidelines<br> • Include 5–7 quick wins that can be implemented fast<br> • Keep actions simple and concrete<br> • Focus on high-impact changes that drive immediate user activity</p>
Lead Magnet Ideas

Discover high intenet downloads or tools to engage potential users.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach].</p> <p>Using this information, suggest a set of lead magnet ideas I can create to attract potential users. Focus on high-intent formats like downloads, templates, or simple tools that are easy to produce but valuable enough for users to exchange their contact information. Explain why these lead magnets would engage my target audience and how they can be used to capture leads effectively. Keep the response short, specific, and founder-friendly.</p>
Partnership Shortlist

List high-fit partners, the value exchange, and potential co-marketing tests.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Partner Name | Why They’re a Fit | Value We Provide Them | Value They Provide Us | </p> <p>Guidelines<br> • Include 4–6 potential high-fit partners<br> • Keep the value exchange short and concrete<br> • Focus on partners that can deliver quick reach and credibility for an early-stage startup</p>

Product Market Fit

+ Expand all
Product-Market Fit Metrics

Learn about quantitative indicators that measure how well your product satisfies target customer needs and drives growth.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Metric | What It Measures | Why It Matters | How to Track It |</p> <p>Guidelines<br> • Include key metrics that directly indicate product-market fit<br> • Focus on actionable, measurable indicators rather than vanity metrics<br> • Where relevant, include benchmark ranges or targets for early-stage startups<br> • Keep explanations short and clear so they are easy to act on</p>
Defining KPIs

Identify and define the critical metrics that directly measure your startup's progress.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| KPI Name | What It Measures | Why It Matters | How to Track It |</p> <p>Guidelines<br> • Include 5 to 8 key performance indicators<br> • Focus on metrics that directly reflect progress or success<br> • Avoid vanity metrics and prioritize those I can take action on<br> • Use simple language and practical tracking methods</p>
North Star Metric

Choose one metric that best captures delivered value and list actions that drive it.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach].</p> <p>Using this information, pick one North Star Metric that best captures the value my product delivers. Define it clearly and list the main actions I can take to drive this metric. Keep the answer short and easy to apply.</p>
Habit Signals

Identify recurring user behaviors that indicate habit formation.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Habit Signal | Why It Matters | How to Track It |</p> <p>Guidelines<br> • Include 4–6 recurring behaviors that show habit formation<br> • Keep explanations short and concrete<br> • Focus on signals that are easy to measure in an early-stage product</p>
PMF Narrative

Write one paragraph explaining who loves you, why, and the proof points.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. We are currently at [stage: pre-seed, seed, Series A, etc]. Our most engaged users are [describe your strongest user/customer group]. The main proof points we have are [list metrics, testimonials, retention signals, or growth data].</p> <p>Using this information, write one clear paragraph that explains who loves my product, why they love it, and the evidence that shows product–market fit. Keep it concise, compelling, and easy to share with investors or the team.</p>

Build Your Startup with AI in 2 Weeks

Join the 2-week bootcamp and learn to build, test, and validate your MVP using AI tools. No coding skills required.

Funding

+ Expand all
Advisor Prep Script

Define the critical questions and information you'll present to advisors to maximize their input on funding, hiring, and growth plans.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Our upcoming advisor meeting will focus on<br> [funding, hiring, growth plans, or other topics]</p> <p>Using this information, prepare a script that includes</p> <p>A short opening briefing that quickly brings the advisor up to speed on recent progress and context</p> <p>Three to five critical questions I should ask to get actionable insights on my chosen focus areas</p> <p>Any key data points, metrics, or updates I should have ready to share in the meeting</p> <p>Suggested ways to frame each question so the advisor can give the most useful and strategic feedback</p> <p>Keep the script concise, clear, and designed to keep the meeting productive and outcome-driven.</p>
Capital Requirements Calculator

Map out your startup's complete financial needs over 24 months, including operational expenses, hiring costs, and growth investments required to reach key milestones.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. Our key milestones over the next 24 months are [list major goals or targets].</p> <p>Using this information, calculate my total capital requirements by estimating operational expenses, hiring costs, product development, and growth investments needed to reach these milestones. Provide a breakdown by category and timeframe, and highlight any areas where costs could vary significantly or where strategic trade-offs might be needed.</p>
Investor Research Matrix

Compile targeted investors who match your stage, sector, and geography with their investment criteria, and portfolio fit.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]<br> We are currently at [stage: pre-seed, seed, Series A, etc]<br> We are based in [geography or region]<br> Our sector is [industry or category]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Investor Name | Stage Focus | Sector Focus | Geography | Notable Portfolio Companies | Why They’re a Fit |</p> <p>Guidelines<br> • Include 8 to 12 investors that match stage, sector, and geography<br> • Pull from relevant VC firms, angels, or funds known for investing in similar companies<br> • Include a short reason for fit to help prioritize outreach<br> • Avoid listing generic or irrelevant investors</p>
Deal Room Checklist

Catalog all documents and materials investors will request during due diligence.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]<br> We are currently at [stage: pre-seed, seed, Series A, etc]</p> <p>Using this information, create a categorized inventory of deal room assets that covers<br> • Corporate and legal documents<br> • Financial statements and forecasts<br> • Team and HR documents<br> • Product and technology assets<br> • Market and customer data<br> • Fundraising and cap table records</p> <p>Include a short description for each asset explaining why it matters to investors and note if it is typically required, recommended, or optional.</p>
Fundraising Narrative

Articulate “why now, why us, why this market” to reduce perceived risk and unify your pitch narrartive across emails, meetings, and deck.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. We are currently at [stage: pre-seed, seed, Series A, etc] and based in [geography].</p> <p>Using this information, write a fundraising narrative that clearly answers “why now, why us, why this market.” The output should reduce perceived investor risk and unify my story across emails, meetings, and pitch decks. Keep it compelling but concise, making sure it feels founder-driven and authentic.</p>
Milestones to Next Round

Define the specific evidence (revenue, users, margins) needed to unlock the next round.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach].<br> We are currently at [stage: pre-seed, seed, Series A, etc].<br> Our current traction is [key metrics so far: revenue, users, engagement, margins, etc].<br> Our fundraising goal is [amount or round type].</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Milestone Area | Specific Target | Why It Matters to Investors | How to Measure Progress |</p> <p>Guidelines<br> • Include 4–6 milestone areas such as revenue, active users, retention, margins, team, or partnerships<br> • Make the targets realistic for my stage and fundraising goal<br> • Keep explanations short, concrete, and investor-focused</p>
Outreach Email Template

Lay out an email template and follow up sequence for cold outreach to potential investors.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. We are currently at [stage: pre-seed, seed, Series A, etc] with [traction details].</p> <p>Using this information, write a cold outreach sequence for potential investors in this format:</p> <p>Email 1: Subject + Body</p> <p>Subject: Short, compelling subject line that references traction or market opportunity</p> <p>Body: 2–3 sentences introducing what we do, why now is the right time, a proof point (traction, growth, or unique insight), and a clear ask for a short call</p> <p>Follow-Up 1 (Day 4–5)</p> <p>Subject: Simple reminder subject line</p> <p>Body: Polite nudge with one new proof point (metric, milestone, customer win), ending with the same ask</p> <p>Follow-Up 2 (Day 8–10)</p> <p>Subject: Final short reminder subject line</p> <p>Body: Very brief note reinforcing traction and timing, while leaving the door open to connect later if now isn’t the right time</p> <p>Guidelines<br> • Keep each message under 100 words<br> • Focus on traction and timing over vision-only pitches<br> • Make the ask consistent: a short intro call</p>
Financing Options

Discover venture debt/revenue-based options, and grants suited to your startup.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. We are currently at [stage: pre-seed, seed, Series A, etc] and based in [geography].</p> <p>Using this information, suggest financing options beyond traditional equity. Cover venture debt, revenue-based financing, and relevant grants that fit my stage and region. Explain which options are the best fit for my situation and why, along with the main risks or tradeoffs I should keep in mind. Keep the response concise and founder-friendly.</p>
Investment Readiness Check

Assess your startup's competitive position, financial health and scability to determine investor readiness.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach].<br> We are currently at [stage: pre-seed, seed, Series A, etc] with [key traction: revenue, users, or growth].</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Area | Strengths | Gaps | Why It Matters to Investors |</p> <p>Guidelines<br> • Cover competitive position, financial health, and scalability<br> • Keep each row short and specific<br> • Highlight what would increase investor confidence</p>

Leadership

+ Expand all
Leadership Principles

Define principles you’ll lead by based on your personal values and market.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. My personal values are [list 3–5 values that guide how you want to lead].</p> <p>Using this information, define 5–7 leadership principles I will lead by. Each principle should connect my values to how I’ll make decisions, build culture, and set the tone for the team. Keep the principles short, memorable, and practical so they can guide everyday actions as the company grows.</p>
Leadership Narrative

Write a short story of where you're going, why it matters, and what you expect from the team.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. My vision for the company is [brief description of long-term direction].</p> <p>Using this information, write a short leadership narrative that tells a story of where we’re going, why it matters, and what I expect from the team along the way. Keep it inspiring, clear, and practical. Make it something I can share to align and motivate the team.</p>
Decision Framework

Create a lightweight framework for important decisions and when to escalate.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach].<br> My startup is at [stage: pre-seed, seed, Series A, etc].</p> <p>Using this information, create a lightweight framework for making important decisions. Return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Decision Type | Who Decides | Criteria to Use | When to Escalate |</p> <p>Guidelines<br> • Include 4–6 common decision types for an early-stage startup (e.g., product, hiring, fundraising, partnerships)<br> • Keep criteria short and practical<br> • Make escalation rules clear (e.g., escalate if financial impact &gt;X, or if decision affects company direction)</p>
Meeting System

Define meeting system for your team with purpose, input, outcomes, and timebox.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach].</p> <p>Using this information, design a meeting system for my team. Return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Meeting Type | Purpose | Inputs | Desired Outcomes | Timebox |</p> <p>Guidelines<br> • Include 3–5 common meetings for early-stage teams (e.g., weekly sync, 1:1s, stand-ups, retros)<br> • Keep each row short and specific<br> • Emphasize outcomes and strict timeboxes to avoid wasted time</p>
One-on-One Guide

Outline a repeatable 1:1 agenda and expected outcomes.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. I want to run effective one-on-one meetings with my team.</p> <p>Using this information, outline a repeatable one-on-one format that keeps meetings consistent and valuable. Describe the key parts of the agenda, the flow of the conversation, and the outcomes I should expect. Keep it simple, founder-friendly, and easy to apply every week.</p>
All-Hands Agenda

Set a repeatable agenda and expected outcomes.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. I want to run effective all-hands meetings that keep the team aligned and motivated.</p> <p>Using this information, outline a repeatable all-hands agenda. Describe the key sections to include, how to structure the flow, and the outcomes I should expect. Keep it simple, engaging, and practical so the team walks away informed, inspired, and clear on priorities.</p>

Productivity

+ Expand all
Time Audit

Track how you spend the week and group time into deep work, shallow work, meetings, and life.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. My weekly schedule looks like this: [list typical hours or blocks of time]. My main priorities right now are [key goals or focus areas]. The team setup is [solo founder / small team / larger team].</p> <p>Using this information, review how I spent the past week and group my time into categories. Return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Category | Hours Spent | % of Total | Example Activities | Impact on Goals | Suggested Adjustment |</p> <p>Guidelines<br> • Use four main categories: Deep Work, Shallow Work, Meetings, and Life<br> • Highlight where time aligns with priorities vs. where it drifts<br> • Recommend 2–3 specific adjustments to move time toward higher-value work</p>
Single Source of Truth

Determine one system a single tools for tasks and notes based on your needs.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. My current workflow looks like [describe how you manage tasks, docs, and notes today]. My main needs are [collaboration, speed, simplicity, integrations, etc].</p> <p>Using this information, recommend one tool or system to serve as my single source of truth for tasks and notes. Explain why it fits my needs, how it can reduce duplication and confusion, and what benefits I should expect once it’s in place. Keep the response short, practical, and easy to act on.</p>
Automation Ideas

List small automations to free up time and energy for important tasks.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach].<br> My current workflow looks like [describe main tasks, recurring processes, or tools you use].</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Task / Process | Automation Idea | Tool or Method | Time/Energy Saved |</p> <p>Guidelines<br> • Include 5–7 lightweight automations that don’t require major setup<br> • Focus on repetitive tasks in communication, scheduling, data entry, or reporting<br> • Highlight easy-to-implement wins that free up focus for higher-value work</p>
Info Diet

Discover sources to follow for key market news and information.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. My focus area is [industry, category, or market].</p> <p>Using this information, suggest a set of high-quality sources I should follow to stay on top of market news and insights. Include newsletters, podcasts, and communities that are especially relevant. Explain why these sources are valuable and how often I should check them so I can stay informed without getting overwhelmed. Keep it concise, practical, and founder-friendly.</p>
Distraction Plan

List possible recurring distractions and a counter for each.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach].<br> My typical workday looks like [describe main environment, habits, or common interruptions].</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Distraction | Why It Happens | Counter Strategy |</p> <p>Guidelines<br> • Include 5–7 recurring distractions founders commonly face<br> • Keep counter strategies short, simple, and realistic<br> • Focus on practical ways to regain focus and protect time for important work</p>

Build Your Startup with AI in 2 Weeks

Join the 2-week bootcamp and learn to build, test, and validate your MVP using AI tools. No coding skills required.

Marketing

+ Expand all
Marketing Message Tester

Create three different value propositions for your startup to test them.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]</p> <p>Using this, return three different value proposition messages that each take a different angle. </p> <p>Each message should be one or two sentences long, clear enough for landing pages, cold emails, or ads. Keep the tone startup-friendly, flexible for testing</p>
Customer Acquisition Channel Mapper

Document viable marketing channels that align with your target customer behavior and budget.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach]<br> We have a monthly marketing budget of [budget amount] and are currently at [stage: pre-launch, MVP, early traction, etc]</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Channel | Why It Fits | Cost Level | Time to See Results | Notes or Tips |</p> <p>Guidelines<br> • Suggest 5 to 7 channels based on where my audience spends time and how they discover new products<br> • Mix short-term and long-term strategies<br> • Include both paid and organic options<br> • Keep recommendations lean and practical for early-stage execution</p>
Customer Journey Analyzer

Map the complete path from awareness to purchase decision, identifying friction points and optimization opportunities.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach].</p> <p>Using this information, describe the typical journey a customer would take from first discovering the problem to deciding to use this product. Walk through the key stages they go through, what motivates them, what questions they might ask, and how they evaluate options along the way. Then highlight any potential friction points or drop-offs, and suggest ways I can reduce hesitation and improve conversion.</p>
Brand Positioning Audit

Evaluate your current messaging, and market positioning to identify optimization opportunities.

<p>Here’s what I know about my brand<br> [briefly describe your product or service, target audience, and current messaging or tagline if you have one]</p> <p>Using this information, evaluate my current brand positioning.<br> Identify how clearly I communicate<br> • Who my product is for<br> • What problem it solves<br> • How it’s different from competitors<br> • Why someone should choose it now</p> <p>Highlight any gaps, weaknesses, or missed opportunities in messaging and positioning.<br> Suggest specific changes or refinements that could make the positioning stronger, more differentiated, and more memorable to my target audience.<br> Keep the recommendations clear and practical so they can be applied immediately.</p>
Positioning Statement

Define your who, the core problem, and your offering so every asset says the same thing.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. The core problem I’m addressing is [describe the main pain point].</p> <p>Using this information, write a clear positioning statement that defines who my product is for, the problem it solves, and the unique offering. Make it short, consistent, and practical so it can be repeated across all assets such as website, pitch deck, emails, and social.</p>
Hook Library

Create openers tailored to your product and audience to win the first 3 seconds.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. My key value proposition is [the main benefit or outcome]. The tone of my brand is [professional, playful, bold, etc]. The main channels I use are [email, social, landing pages, pitches].</p> <p>Using this information, create a set of hooks I can use to capture attention in the first three seconds. Include openers tailored to my product, audience, and brand tone that fit across the channels I use. Keep each hook short, specific, and designed to spark curiosity or highlight immediate value. Provide at least 5–7 examples I can rotate through.</p>
Content Calendar Outline

Plan weekly posts with goals, formats, and channels.

<p>I’m building a product that helps<br> [target audience]<br> [solve what problem or achieve what goal]<br> using<br> [product or approach].<br> My content goals are [brand awareness, lead generation, engagement, etc].<br> The main channels I use are [LinkedIn, Twitter, YouTube, newsletter, etc].</p> <p>Using this information, return the output as a normal Markdown table (no code blocks) with the following columns:</p> <p>| Day | Goal | Content Format | Channel | Example Topic |</p> <p>Guidelines<br> • Plan for one week of content with 5–7 posts<br> • Make sure each post has a clear goal and format (e.g., post, video, carousel, newsletter)<br> • Keep example topics specific to my product and audience<br> • Spread posts across the chosen channels for balance</p>
Social Content Flywheel

Turn a single YouTube transcript into a set of pieces ready to be posted on social media.

<p>I’m building a product that helps [target audience] [solve what problem or achieve what goal] using [product or approach]. My main social channels are [LinkedIn, Twitter, Instagram, TikTok, etc]. Here is the transcript I want to repurpose:</p> <p>[insert YouTube transcript here]</p> <p>Using this information, turn the single YouTube transcript into a set of ready-to-post pieces for social media. Break it into short posts, quotes, clips, and visuals tailored to each platform. Keep the content punchy, specific to the audience, and formatted for engagement. Provide at least 5 distinct content pieces I can immediately use across my channels.</p>

Frequently Asked Questions

The Prompt Library is designed for early-stage founders, solo builders, and aspiring entrepreneurs who want to optimize their workflows and accelerate how they learn.

You can use ChatGPT, Claude, or Gemini. The choice depends on your personal preference and each works well.

Start by adding your chosen prompt and replacing only the required inputs highlighted in green. You can then customize it further based on the output you want or ask follow up questions after the initial answer is generated.

In most cases yes. However, large language models can sometimes produce inaccurate information called hallucinations. Always fact check important outputs before using them.

You can join the Vibe Coding Bootcamp to learn how to build, test, and validate your first product using AI tools with no coding required. Apply here: https://fi.co/bootcamp/vibecoding

CTA BG

APPLY TO FI CORE

Join the world's largest pre-seed startup accelerator

The Founder Institute is the world’s most proven network to turn ideas into fundable startups, and startups into global businesses. Since 2009, our structured accelerator programs have helped over 8,100 entrepreneurs raise over 1.9BN in funding. Based in Silicon Valley and with chapters across 100 countries, our mission is to empower communities of talented and motivated people to build impactful technology companies worldwide.


Copyright © 2025, Founder Institute, Inc. All Rights Reserved