Business
245 prompts in this category · Page 21 of 21
Product Requirements Document (PRD) Writer
Turn a product idea into a complete PRD: problem, users, scope, user stories, acceptance criteria, metrics, and launch risks.
Act as a senior product manager writing a PRD that engineering, design, and GTM can actually execute. Be precise about what is in, what is out, and what is still unknown. Do not dress guesses up as facts. Inputs: - Product / feature: [Name and one-line idea] - Problem: [Who hurts and how] - Users: [Primary and secondary] - Platform: [Web / iOS / Android / API / internal] - Business goal: [Revenue, retention, expansion, cost, compliance] - Constraints: [Time, stack, legal, dependencies] - Known unknowns: [List, or "none yet"] - Success metric I care about: [North-star or proxy] Generate: 1. Summary: 8-12 sentences. What we are building, for whom, why now, and what "done" means for v1. Flag any Input that is still vague. 2. Problem and context: Current workaround. Cost of the workaround. Why existing tools or the current product fail. Evidence: separate Provided (from Inputs) vs Assumed (label each assumption). 3. Goals and non-goals: - Goals (3-6): Outcome-based, testable. - Non-goals for v1: Explicit cuts. Include at least two tempting features we will refuse. 4. Users and JTBD: Primary user, secondary user, anti-user (who this is not for). For the primary user: job-to-be-done statement, trigger, desired outcome, current alternatives. 5. Scope: In-scope list. Out-of-scope list. Open questions with an owner suggestion (PM / Eng / Design / Legal / GTM). 6. User stories (8-12): Format "As a [user], I want [action], so that [outcome]." Tag each P0 / P1 / P2. P0 must be a shippable vertical slice, not a layer of polish. Include 1-2 negative stories (what the system must not do). 7. Acceptance criteria for every P0 story: Given / When / Then. Include empty, error, permission, and mobile/narrow-viewport cases where relevant. No "should feel fast" without a number or a qualitative test method. 8. UX notes: Happy path in 6-10 steps. Empty states. Edge cases. Key copy (buttons, errors). What must be designed vs. what can ship with existing patterns. 9. Analytics and success metrics: Leading and lagging metrics. Event names (object_action). Guardrail metrics that would make us roll back. How we will decide to iterate vs. kill after launch. 10. Launch plan: Feature flag / staged rollout sketch. Internal dogfood. Beta criteria. Support and docs needed. GTM one-pager bullets (who we tell, what we claim, what we will not claim). 11. Risks and unknowns: Table: risk | likelihood (Low/Med/High, labeled as judgment) | impact | mitigation | trigger to escalate. Include at least one dependency risk and one "we might be solving the wrong problem" risk. Constraints: - No fake certainty. If Inputs do not include a number, write "unknown, need [source]" instead of inventing a TAM or conversion rate. - Do not invent APIs, vendors, or legal positions. - Stories must be independently testable. No "and also make it beautiful." - Write for a staff engineer who will challenge scope. Short sentences. Named sections. No vision-deck fluff.
SWOT Analysis Generator: Strategic Business Assessment Tool
Produce a thorough SWOT analysis for any business or project. Get actionable strategic insights across strengths, weaknesses, opportunities, and threats.
Act as a management consultant specializing in strategic analysis and competitive intelligence. Conduct a comprehensive SWOT analysis for [Company/Business/Project Name] operating in [Industry/Market]. Follow these steps: Strengths (Internal): Identify 5-7 internal advantages. Consider resources, capabilities, brand equity, team expertise, proprietary technology, and cost advantages. Weaknesses (Internal): Identify 5-7 internal limitations. Consider skill gaps, resource constraints, operational inefficiencies, and brand perception issues. Opportunities (External): Identify 5-7 external opportunities. Consider market trends, regulatory changes, technology shifts, partnership potential, and underserved segments. Threats (External): Identify 5-7 external risks. Consider competitor actions, economic downturns, supply chain risks, changing consumer preferences, and regulatory risks. Strategic Recommendations: Based on the SWOT, provide: 3 SO strategies (use Strengths to capture Opportunities) 3 WO strategies (address Weaknesses to capture Opportunities) 3 ST strategies (use Strengths to mitigate Threats) 3 WT strategies (minimize Weaknesses and avoid Threats) Priority Matrix: Rank the top 5 strategic actions by impact and feasibility. Constraints: Be specific to [Industry]. Avoid generic statements. Tone: Analytical, objective, and actionable. Format: Use a 2x2 SWOT grid followed by a detailed breakdown.
Complete Business Plan Generator: Investor-Ready Documents
Generate a professional, investor-ready business plan with financial projections, market analysis, and competitive positioning for any startup idea.
Act as a senior business strategy consultant with experience advising startups and preparing investor pitch materials. Generate a complete business plan for [Business Idea / Startup Name]. Follow this structure: Executive Summary: A 200-word overview covering the problem, solution, target market, and revenue model. Problem Statement: Define the specific pain point your business addresses. Use data or statistics where applicable. Solution: Describe the product/service and how it solves the problem. Target Market: Define the TAM, SAM, and SOM with estimated figures for [Industry]. Competitive Analysis: Identify 3-5 direct competitors. For each, list strengths, weaknesses, and your differentiation. Revenue Model: Outline pricing strategy, revenue streams, and projected monthly revenue for Year 1. Go-to-Market Strategy: Detail the first 90 days of customer acquisition. Financial Projections: Provide a simplified 3-year projection table (Revenue, COGS, Gross Margin, Operating Expenses, Net Profit). Team: Describe the key roles needed and their responsibilities. Ask: State the funding amount needed and how it will be allocated. Constraints: Use realistic, conservative financial estimates. Tone: Professional, data-driven, and concise. Avoid jargon unless standard in business planning.
B2B Cold Email Outreach Campaign Builder
Craft highly personalized and high-converting B2B cold email sequences. This prompt ensures your outreach avoids spam folders and drives replies.
Act as a top-producing B2B Sales Executive and lead generation expert. Design a 3-step cold email outreach sequence offering [Product/Service] to [Target Job Title] at [Target Industry/Company Type]. Follow these strict guidelines: Sequence Structure: Email 1 (The Hook & Value), Email 2 (The Gentle Nudge & Case Study), Email 3 (The Breakup/Final Offer). Personalization: Include clear placeholders like [Company Name], [Recent News/Achievement], and [Recipient First Name] for hyper-personalization. Brevity & Clarity: Keep each email under 120 words. Focus on the prospect's pain points, not your product's features. Call to Action (CTA): Use a low-friction CTA (e.g., asking for interest rather than a 30-minute call). E-E-A-T: Establish authority by seamlessly introducing a relevant one-sentence case study or metric. Tone: Professional, calm, and confident. Avoid aggressive sales language. Use active voice.
Startup Pitch Deck Architect
Builds a 10-slide outline for a startup pitch based on the problem-solution model.
Create a 10-slide pitch deck outline for a startup that [Brief Description of Business]. For each slide, provide a clear title and three bullet points detailing the key information to include. Follow the standard venture capital pitch structure.