Stop Writing Bad AI Prompts

I want to build [business idea]. Act as a skeptical but fair venture advisor. Evaluate: 1) Market size — is this a big enough opportunity? 2) Customer pain — is this a painkiller or a vitamin? Rate 1-10. 3) Competitive landscape — who else does this? What's my moat? 4) Revenue model — how does this make money? Is it scalable? 5) Risks — top 3 things that could kill this. 6) Unit economics — rough CAC vs LTV analysis. 7) Go-to-market — first 100 customers: how? 8) Honest verdict: pursue, pivot, or pass? Don't sugarcoat. I want the truth, not encouragement.

Create a pitch deck outline for [startup/product]. Stage: [pre-seed/seed/Series A]. Include slide-by-slide content for: 1) Title slide (name, tagline, one visual concept), 2) Problem (make investors feel the pain), 3) Solution (demo/screenshot description), 4) Market size (TAM/SAM/SOM with sources to find real numbers), 5) Business model (revenue streams, pricing), 6) Traction (what to show even if early — waitlist, LOIs, pilots), 7) Competition (positioning matrix, not "we have no competitors"), 8) Team (what to highlight, what to add), 9) Financials (3-year projection framework), 10) Ask (amount, use of funds, milestones). Keep it to 12 slides max. Flag any red flags an investor would notice.

Build a financial model framework for [business type]. Revenue: [describe revenue streams]. Provide: 1) Revenue projection model (bottom-up, with assumptions listed and adjustable), 2) Cost structure breakdown (fixed vs variable, COGS vs operating), 3) Monthly cash flow projection template for months 1-18, 4) Break-even analysis, 5) Key metrics to track (CAC, LTV, churn, MRR, burn rate — whichever are relevant), 6) Scenario analysis: optimistic, base case, pessimistic. Show the formulas/logic, not just numbers. Make it so I can plug in my own assumptions. Flag the assumptions that matter most.

Write a detailed SOP for [process/task] at [company type]. Include: 1) Purpose — why this process exists (one sentence), 2) Scope — who uses this and when, 3) Prerequisites — what you need before starting, 4) Step-by-step instructions (numbered, each step is one action, include screenshots/example placeholders), 5) Decision points — "if X, do Y; if Z, do W", 6) Quality check — how to verify you did it right, 7) Common mistakes and how to avoid them, 8) Escalation — when and how to ask for help, 9) Version history table. Write it so a new hire on day 1 could follow it without asking questions.

Write a partnership pitch email to [target company/person]. My company: [brief description]. What I'm proposing: [partnership idea]. What's in it for them: [their benefit]. Structure: 1) Subject line (3 options — no "Partnership Opportunity" clichés), 2) First line that shows I've done my homework about them, 3) The pitch: one paragraph, clear and specific, 4) Social proof / credibility (one line), 5) Low-friction next step (not "Let's hop on a 30-min call"), 6) PS line with an extra hook. Total: under 150 words. Tone: peer-to-peer, not supplicant-to-gatekeeper.

Help me price [product/service]. Context: Target customer: [who]. Competitors charge: [range]. My costs: [if known]. Value delivered: [describe outcome for customer]. Analyze: 1) Cost-plus pricing (what's my floor?), 2) Competitor-based (where should I position?), 3) Value-based (what's this worth to them?), 4) Tiered pricing structure (3 tiers: what goes in each?), 5) Freemium considerations (should I have a free tier? what goes in it?), 6) Annual vs monthly discount strategy, 7) Launch pricing vs long-term pricing. Recommend a specific price with justification. Include psychological pricing tactics that apply.

Write a job description for [role] at [company description]. Include: 1) A hook opening (why someone should care about this role — not "We're looking for a rockstar"), 2) What you'll do: 5-7 responsibilities (outcome-focused, not task lists), 3) What you bring: separate "must-haves" (5 max) from "nice-to-haves" (3 max), 4) What we offer: compensation philosophy + benefits + culture elements, 5) About us: 2-3 sentences that show personality, not corporate speak. Remove any gendered language. Include salary range: [range]. Remote policy: [remote/hybrid/onsite]. Avoid: "fast-paced environment," "wear many hats," "competitive salary" without numbers.

Review this contract/agreement as a business advisor (not legal counsel). Flag: 1) Clauses that are unusually unfavorable to me, 2) Vague language that could be interpreted against me, 3) Missing protections I should ask for, 4) Non-standard terms compared to typical [type] agreements, 5) Termination clause analysis — how hard is it to exit? 6) Liability and indemnification concerns, 7) IP ownership clarity. For each flag: quote the concerning text, explain why it matters in plain English, and suggest alternative language. End with: "Ask a lawyer about: [specific items]." Contract: [paste contract text]

I have a meeting about [topic] with [who]. Duration: [X] minutes. Goal: [what I need from this meeting]. Create: 1) Pre-meeting: agenda with time allocations (always include 5 min buffer), key questions to answer, any prep work needed. 2) During meeting: talking points for each agenda item, questions to ask, decisions that need to be made. 3) Post-meeting template: action items (who, what, by when), decisions made, parking lot items, next meeting date. Make the agenda tight — no meeting should have "Any Other Business" as an agenda item.

Perform a comprehensive SWOT analysis for [business/product] in the [industry] market. For each quadrant, provide 5-7 specific, actionable items (not generic things like "strong team" — be specific about WHY). Then: 1) Cross-reference: How can Strengths address Threats? How can Opportunities cover Weaknesses? 2) Competitive positioning map — where do I sit vs [3 competitors] on axes of [price vs quality] and [feature-rich vs simple]? 3) Strategic priorities: top 3 things to do in the next 90 days based on this analysis. Base this on real market dynamics, not MBA textbook generics.

Write a consultative sales call script for selling [product/service] to [buyer persona]. Duration: 30 minutes. Structure: 1) Opening (build rapport without being fake — 2 min), 2) Discovery questions (10 questions that uncover pain, budget, timeline, decision process — don't ask them all, flow naturally), 3) Transition to pitch (bridge from their problem to your solution), 4) Presentation (focus on 3 benefits most relevant to their stated pain), 5) Objection handling (prep responses for: "too expensive," "need to think about it," "we're using [competitor]," "not the right time"), 6) Close (assume the sale, propose next step). Include talk tracks — actual words to say, not bullet points.

Write OKRs for [team/company] for [quarter/year]. Context: company stage is [startup/growth/enterprise], main priorities are [list 2-3]. Create 3-4 Objectives that are: inspiring but achievable, qualitative (not metrics). Under each, 3-4 Key Results that are: specific, measurable, time-bound, and a stretch (70% confidence of achieving). Include: 1) One "health metric" KR per objective (something that ensures you don't sacrifice quality for speed), 2) Suggested initiatives/projects that would drive each KR, 3) Anti-goals: what we're explicitly NOT doing this quarter. Avoid vanity metrics. Each KR should have a clear owner.

Design a customer survey to understand [what you want to learn] for [product/company]. Rules: 1) Max 10 questions (completion rate drops after that), 2) Start with easy/engaging questions, sensitive/hard ones later, 3) Mix: 3 multiple choice, 2 rating scale, 2 open-ended, 2 Yes/No, 1 NPS question. 4) No leading questions, 5) No double-barreled questions (asking two things at once), 6) Include a "What's the #1 thing we could improve?" open-ended question. Provide: the survey questions, logic/skip patterns if applicable, an intro message, and how to analyze each question type. Platform suggestion for implementation.

I'm negotiating [what: salary, contract, deal, price] with [who]. My position: [what I want]. Their likely position: [what they probably want]. My BATNA (best alternative): [what I'll do if this fails]. Help me prepare: 1) My ideal, target, and walk-away numbers, 2) 5 arguments in my favor (ranked by strength), 3) Their likely counter-arguments and my responses, 4) 3 creative options for mutual gain (expanding the pie), 5) Anchoring strategy — should I go first or let them? 6) Concession plan — what I can give up that costs me little but has value to them, 7) Opening statement (first 30 seconds), 8) Power phrases to use and phrases to avoid.

Write a PRD for [feature/product]. Include: 1) Problem statement (who has this problem, how painful is it, evidence), 2) Proposed solution (high-level, with user flow description), 3) User stories (format: "As a [user], I want [action], so that [benefit]" — 8-12 stories), 4) Requirements: must-have vs nice-to-have (MoSCoW), 5) Success metrics (how we know this worked — pick 2-3 measurable KPIs), 6) Non-functional requirements (performance, security, accessibility), 7) Open questions (things we still need to figure out), 8) Out of scope (explicitly what this is NOT). Keep it to 2 pages. No fluff — engineers will read this.

Build a detailed customer persona for [product/service]. Based on: [any data or assumptions you have]. Include: 1) Demographics (age, income, job, location — be specific, not ranges), 2) Psychographics (values, fears, aspirations), 3) A day in their life (morning to night — where does our product fit?), 4) Their current solution to the problem we solve (and why it's inadequate), 5) Buying behavior (where they research, who influences them, objections), 6) Direct quotes they'd say (5 — make them realistic), 7) How to reach them (channels, communities, keywords they search), 8) What would make them switch to us vs stay with the status quo.

Create a 90-day launch plan for [product/service]. Budget: [amount]. Team: [size and skills]. Current status: [where things stand]. Break into 3 phases: Phase 1 (Days 1-30): Foundation — what to build, set up, and prepare. Phase 2 (Days 31-60): Pre-launch — audience building, beta testing, content creation. Phase 3 (Days 61-90): Launch — the actual launch sequence, day by day for launch week. For each phase: key milestones, tasks (with owners), tools needed, budget allocation, and risk mitigation. Include a launch day checklist. What does success look like at day 90? Define specific metrics.