# The Founder's AI Toolkit **100+ tested prompts for running your business with AI — written for solo founders, by a solo founder.** Version 1.2 — 2026-08-12 --- ## Welcome You run the whole company. Marketing, sales, operations, finance, product — it's all you. AI won't replace you, but it will absolutely multiply you: it can be your first-draft copywriter, your analyst, your critic, your researcher, and your never-tired brainstorming partner. This toolkit is a working collection of 100+ prompts, organized into the five areas where a solo founder actually spends their time: 1. **Marketing** — positioning, content, campaigns, and channels 2. **Sales** — outreach, calls, proposals, and closing 3. **Operations** — systems, hiring, delegation, and decision-making 4. **Finance** — numbers, planning, pricing, and fundraising 5. **Product** — discovery, prioritization, building, and learning Every prompt in this pack is ready to paste. Every one has placeholders in **[SQUARE BRACKETS]** for you to fill in, and a line on when to use it. There is nothing here that requires you to be "good at prompts." There is everything here that requires you to be good at your business — the AI does the drafting, and you make the calls. --- ## Version & updates **Version 1.2 — 2026-08-12** Adds the skills layer: the same 105 prompts repackaged as six installable skills (marketing, sales, operations, finance, product, plus a founder-routine skill from the playbook) for Claude Code, claude.ai, and OpenAI-compatible tools. The skills ship as a separate ZIP from your download page; the prompts in this file are unchanged. Skills are optional — the prompts always work as plain text. A one-page install guide (INSTALL.md) is inside the ZIP. **Version 1.1 — 2026-08-02** This update deduplicates the overlapping invoice and launch-announcement prompts, adds a finance reconciliation angle and a public, cold-audience announcement angle, adds two worked examples, and adds a clickable prompt index. Purchasers get free updates. The download page always serves the latest version of this file, so return to your download link whenever you want to check for an update. ## Prompt index Jump to any prompt below. ### Marketing - [Sharpen your one-line positioning](#m1-sharpen-your-one-line-positioning) - [Define your ideal customer (ICP) in one page](#m2-define-your-ideal-customer-icp-in-one-page) - [Write a homepage hero section](#m3-write-a-homepage-hero-section) - [Draft a "this is who it's for / not for" section](#m4-draft-a-this-is-who-its-for-not-for-section) - [Generate 20 hook options for one piece of content](#m5-generate-20-hook-options-for-one-piece-of-content) - [Turn one piece of content into a week of content](#m6-turn-one-piece-of-content-into-a-week-of-content) - [Write a 5-email welcome sequence](#m7-write-a-5-email-welcome-sequence) - [Write a product launch email to your existing list](#m8-write-a-product-launch-email-to-your-existing-list) - [Draft a 30-day organic content calendar](#m9-draft-a-30-day-organic-content-calendar) - [Turn customer conversations into a case study draft](#m10-turn-customer-conversations-into-a-case-study-draft) - [Analyze a competitor's messaging and find the gap](#m11-analyze-a-competitors-messaging-and-find-the-gap) - [Write an SEO-optimized blog post from a brief](#m12-write-an-seo-optimized-blog-post-from-a-brief) - [Create a keyword and topic list from one seed topic](#m13-create-a-keyword-and-topic-list-from-one-seed-topic) - [Draft a paid ad with 5 variations](#m14-draft-a-paid-ad-with-5-variations) - [Draft a referral ask your customers won't cringe at](#m15-draft-a-referral-ask-your-customers-wont-cringe-at) - [Draft a press release or launch announcement](#m16-draft-a-press-release-or-launch-announcement) - [Draft a landing page section for social proof (real only)](#m17-draft-a-landing-page-section-for-social-proof-real-only) - [Write a "from zero" channel experiment plan](#m18-write-a-from-zero-channel-experiment-plan) - [Draft a response to negative feedback or a bad review](#m19-draft-a-response-to-negative-feedback-or-a-bad-review) - [Write a content brief for a guest post or collab](#m20-write-a-content-brief-for-a-guest-post-or-collab) - [Audit a piece of my own marketing and fix it](#m21-audit-a-piece-of-my-own-marketing-and-fix-it) ### Sales - [Write a first-touch outreach email that doesn't sound like spam](#s1-write-a-first-touch-outreach-email-that-doesnt-sound-like-spam) - [Write a 4-email follow-up sequence for one prospect](#s2-write-a-4-email-follow-up-sequence-for-one-prospect) - [Prepare for a discovery call in 10 minutes](#s3-prepare-for-a-discovery-call-in-10-minutes) - [Draft a discovery call agenda and question list](#s4-draft-a-discovery-call-agenda-and-question-list) - [Draft a demo script that focuses on their problem](#s5-draft-a-demo-script-that-focuses-on-their-problem) - [Role-play a sales call with me (objections edition)](#s6-role-play-a-sales-call-with-me-objections-edition) - [Prepare for the "it's too expensive" objection](#s7-prepare-for-the-its-too-expensive-objection) - [Draft a proposal that sells the outcome, not the features](#s8-draft-a-proposal-that-sells-the-outcome-not-the-features) - [Draft the follow-up after sending a proposal](#s9-draft-the-follow-up-after-sending-a-proposal) - [Write a "no, thanks" response that keeps the door open](#s10-write-a-no-thanks-response-that-keeps-the-door-open) - [Draft a LinkedIn profile that sells without being salesy](#s11-draft-a-linkedin-profile-that-sells-without-being-salesy) - [Draft a sales page from your product's facts](#s12-draft-a-sales-page-from-your-products-facts) - [Draft a testimonial request that gets real, usable quotes](#s13-draft-a-testimonial-request-that-gets-real-usable-quotes) - [Draft an upsell or expansion message to an existing customer](#s14-draft-an-upsell-or-expansion-message-to-an-existing-customer) - [Draft a partnership or joint-venture outreach](#s15-draft-a-partnership-or-joint-venture-outreach) - [Analyze my pipeline and tell me where it's stuck](#s16-analyze-my-pipeline-and-tell-me-where-its-stuck) - [Run a lost-deal autopsy](#s17-run-a-lost-deal-autopsy) - [Draft a "checking in" email that adds value (not noise)](#s18-draft-a-checking-in-email-that-adds-value-not-noise) - [Escalate a late invoice while preserving the relationship](#s19-escalate-a-late-invoice-while-preserving-the-relationship) - [Write a "thank you" that deepens the relationship](#s20-write-a-thank-you-that-deepens-the-relationship) - [Build my weekly sales routine](#s21-build-my-weekly-sales-routine) ### Operations - [Turn one task into a step-by-step SOP](#o1-turn-one-task-into-a-step-by-step-sop) - [Draft a job description that attracts the right person](#o2-draft-a-job-description-that-attracts-the-right-person) - [Draft interview questions that reveal how someone actually works](#o3-draft-interview-questions-that-reveal-how-someone-actually-works) - [Write a decision memo for a choice you're stuck on](#o4-write-a-decision-memo-for-a-choice-youre-stuck-on) - [Draft a meeting agenda that earns the meeting](#o5-draft-a-meeting-agenda-that-earns-the-meeting) - [Draft a delegation brief — hand something off properly](#o6-draft-a-delegation-brief-hand-something-off-properly) - [Draft a hiring offer and rejection that keep your reputation](#o7-draft-a-hiring-offer-and-rejection-that-keep-your-reputation) - [Draft a customer support response (from your real policies)](#o8-draft-a-customer-support-response-from-your-real-policies) - [Draft a refund or complaint response that protects the business](#o9-draft-a-refund-or-complaint-response-that-protects-the-business) - [Turn my scattered notes into a weekly review](#o10-turn-my-scattered-notes-into-a-weekly-review) - [Run an email triage and draft quick replies](#o11-run-an-email-triage-and-draft-quick-replies) - [Draft my daily standup plan](#o12-draft-my-daily-standup-plan) - [Draft a vendor or tool comparison for a buying decision](#o13-draft-a-vendor-or-tool-comparison-for-a-buying-decision) - [Draft a project plan from a one-paragraph goal](#o14-draft-a-project-plan-from-a-one-paragraph-goal) - [Draft a customer onboarding message sequence](#o15-draft-a-customer-onboarding-message-sequence) - [Draft the "house rules" for working with me](#o16-draft-the-house-rules-for-working-with-me) - [Draft a risk register for my business](#o17-draft-a-risk-register-for-my-business) - [Define my KPI dashboard from scratch](#o18-define-my-kpi-dashboard-from-scratch) - [Draft an offboarding or "end of engagement" checklist](#o19-draft-an-offboarding-or-end-of-engagement-checklist) - [Draft a knowledge-base article from a support conversation](#o20-draft-a-knowledge-base-article-from-a-support-conversation) - [Draft a crisis communication plan (worst-case, in advance)](#o21-draft-a-crisis-communication-plan-worst-case-in-advance) ### Finance - [Explain my monthly numbers like I'm smart (because I am)](#f1-explain-my-monthly-numbers-like-im-smart-because-i-am) - [Build a simple cash-flow forecast](#f2-build-a-simple-cash-flow-forecast) - [Analyze my pricing against the market](#f3-analyze-my-pricing-against-the-market) - [Work out my break-even numbers](#f4-work-out-my-break-even-numbers) - [Draft a simple budget for the next quarter](#f5-draft-a-simple-budget-for-the-next-quarter) - [Reconcile overdue invoices across clients](#f6-reconcile-overdue-invoices-across-clients) - [Review my expenses and find the waste](#f7-review-my-expenses-and-find-the-waste) - [Draft a tax-prep checklist (and a 30-day plan)](#f8-draft-a-tax-prep-checklist-and-a-30-day-plan) - [Draft the numbers section for a pitch deck or investor update](#f9-draft-the-numbers-section-for-a-pitch-deck-or-investor-update) - [Draft an investor update (the honest version)](#f10-draft-an-investor-update-the-honest-version) - [Stress-test my financial model's assumptions](#f11-stress-test-my-financial-models-assumptions) - [Draft a payment-terms negotiation for a big client](#f12-draft-a-payment-terms-negotiation-for-a-big-client) - [Explain the difference between profit and cash — with my numbers](#f13-explain-the-difference-between-profit-and-cash-with-my-numbers) - [Draft my pricing page copy (honest, clear, no tricks)](#f14-draft-my-pricing-page-copy-honest-clear-no-tricks) - [Draft a simple monthly finance review ritual](#f15-draft-a-simple-monthly-finance-review-ritual) - [Draft the financial questions to ask before raising prices](#f16-draft-the-financial-questions-to-ask-before-raising-prices) - [Draft a "can I afford this?" analysis for one purchase](#f17-draft-a-can-i-afford-this-analysis-for-one-purchase) - [Draft my annual plan numbers](#f18-draft-my-annual-plan-numbers) - [Draft a salary/draw decision for myself](#f19-draft-a-salarydraw-decision-for-myself) - [Draft a "why I'm cheaper than I should be" check](#f20-draft-a-why-im-cheaper-than-i-should-be-check) - [Draft a simple monthly "money dashboard" template](#f21-draft-a-simple-monthly-money-dashboard-template) ### Product - [Draft a customer problem interview script](#p1-draft-a-customer-problem-interview-script) - [Draft a short survey for existing customers or users](#p2-draft-a-short-survey-for-existing-customers-or-users) - [Turn interview notes into findings and decisions](#p3-turn-interview-notes-into-findings-and-decisions) - [Score my feature backlog with RICE](#p4-score-my-feature-backlog-with-rice) - [Draft a one-page PRD (product requirements doc)](#p5-draft-a-one-page-prd-product-requirements-doc) - [Turn a PRD into user stories and acceptance criteria](#p6-turn-a-prd-into-user-stories-and-acceptance-criteria) - [Define my MVP scope by cutting, not adding](#p7-define-my-mvp-scope-by-cutting-not-adding) - [Draft a competitive analysis from real research](#p8-draft-a-competitive-analysis-from-real-research) - [Draft a usability test script for my own product](#p9-draft-a-usability-test-script-for-my-own-product) - [Triage customer feedback into decisions](#p10-triage-customer-feedback-into-decisions) - [Draft a changelog or release note](#p11-draft-a-changelog-or-release-note) - [Draft onboarding copy for my product](#p12-draft-onboarding-copy-for-my-product) - [Draft a bug report triage and communication](#p13-draft-a-bug-report-triage-and-communication) - [Run a metrics review and pick one experiment](#p14-run-a-metrics-review-and-pick-one-experiment) - [Design a pricing experiment (features and tiers)](#p15-design-a-pricing-experiment-features-and-tiers) - [Draft a "kill the feature" review](#p16-draft-a-kill-the-feature-review) - [Draft a user story for a piece of feedback](#p17-draft-a-user-story-for-a-piece-of-feedback) - [Announce a product publicly to a cold audience](#p18-announce-a-product-publicly-to-a-cold-audience) - [Draft my retrospective (I shipped something — what now?)](#p19-draft-my-retrospective-i-shipped-something-what-now) - [Draft my "roadmap for one" — next 90 days of product work](#p20-draft-my-roadmap-for-one-next-90-days-of-product-work) - [Draft a customer-development question bank](#p21-draft-a-customer-development-question-bank) ## Part 1: The Playbook ### How this pack works The pack is simple to use: 1. **Open the section you need.** Marketing, Sales, Operations, Finance, Product. 2. **Find the prompt that matches the job.** Each one is titled with the job it does. 3. **Copy it, fill in the [BRACKETS], paste it into your AI tool.** (ChatGPT, Claude, Gemini, or any capable model — these prompts work with all of them.) 4. **Review, edit, and decide.** The AI drafts; you are the editor-in-chief. Never ship anything you haven't read and made your own. A few ground rules that make the whole pack work better: - **Fill in every bracket.** A prompt with empty placeholders is a guess. A prompt with real details — your product, your customer, your numbers — is a draft you can actually use. The 30 seconds you spend filling in brackets saves you 30 minutes of editing vague output. - **Replace the examples with yours.** Many prompts include an example or a "bad/good" pair. Swap in your own real material. The model follows the shape of what you give it. - **Iterate, don't regenerate.** The first answer is rarely the best answer. Say "Make it more specific," "Shorter," "More concrete, less fluffy," "Give me three alternative openings." Treat the output as a draft, not a verdict. - **Ask it to critique itself.** Many of the prompts below build this in ("find the weakest part and rewrite it"). Use that. The best results come from a second pass. - **Verify before you trust.** AI can produce confident, wrong numbers, invented quotes, and outdated facts. Anything factual — prices, dates, legal claims, statistics — check it yourself before it goes out. This is non-negotiable in anything a customer or the tax authority sees. ### Why these prompts are shaped the way they are Every prompt in this pack follows the same skeleton, and once you see it, you can write your own prompts forever: 1. **Role** — who the AI should be: "You are a direct-response copywriter with 15 years of experience in B2B SaaS." A role gives the model a voice and a set of instincts. 2. **Context** — what the model needs to know: who your customer is, what you sell, where this piece of work sits. Context is the single biggest lever on output quality. Garbage context, garbage output. 3. **Task** — the specific job, stated as a verb: "Write," "Analyze," "Draft," "Critique," "Summarize." 4. **Format** — what the deliverable should look like: "three options, each under 150 words, with a headline, body, and CTA." 5. **Constraints** — what to avoid or guarantee: "no hype, no exclamation marks, plain language, max 200 words, must mention the free trial." That's it. Role, context, task, format, constraints. If a prompt isn't working, you're usually missing one of the five — most often context. ### Getting good results: the five habits **Habit 1: Give context before you ask.** "Write a launch email" gets you a template. "Write a launch email to my existing subscriber list of 400 people who signed up for my free template but haven't bought anything in six months" gets you something you can edit and send. Context is everything. If you only change one habit, change this one. **Habit 2: Iterate in small steps.** Don't ask for a complete overhaul. Ask for one change at a time: "Tighter," "More concrete," "Less salesy," "Rewrite the second paragraph," "Give me a version from the customer's perspective." Small, specific edits keep the parts that work and fix the parts that don't. **Habit 3: Show, don't tell.** If you have an example of what you want — a competitor's ad you like, a past email that performed well — paste it in: "Write in this style" beats "write in a friendly style" every time. **Habit 4: Use the model as a critic.** Before you send anything important, run it through a critique pass: "Here's my draft. Identify the three weakest points and rewrite them." This doubles the quality of everything with one extra paste. **Habit 5: Ask for the question, not just the answer.** When you're unsure what you need, ask the AI to interview you: "Ask me the five questions you need answered to write this well." Answering questions is easier than writing from a blank page. ### A note on honesty This toolkit is built for building a real business, not for faking one. Use AI to write drafts, analyze numbers, and generate ideas — use your judgment to decide what's true and what ships. Don't ask AI to invent testimonials, fabricate case studies, or manufacture urgency. It will happily do it, and it will bite you. Real stories from real customers are more valuable anyway — there's a prompt in the Marketing section for getting them out of people honestly. ### The solo founder's weekly AI routine Consistency beats intensity. Here's a routine that takes about an hour a day, using this pack: **Every morning (15 minutes) — triage and prep.** - Open your inbox and to-do list. Pick the three things that actually move the business today. - Use the *Email Triage* prompt (Operations) to draft a fast response to anything that's a simple answer. - Use the *Daily Standup Planner* (Operations) to write out your three priorities for the day with the output saved to your notes app. **Monday (30-60 minutes) — the week's plan.** - Use the *Weekly Planning* prompt (Operations) to turn your goals into a concrete week: what will be finished by Friday, in what order, with what blocked off. - Use the *Content Calendar* prompt (Marketing) to batch a week of content in one sitting. One session of focused generating, then a few minutes a day of editing. **Tuesday & Thursday (30 minutes) — deep work with AI.** - Pick one big task and do it with the AI: a landing page draft, a customer interview script, a pricing analysis, a feature spec. - Rule: one task, one section of the pack, start to finish. **Wednesday (30-60 minutes) — sales time.** - Use the *Outreach Sequence* prompt (Sales) to write a week's worth of outreach in one go. - Use the *Follow-Up Sequence* prompt (Sales) to keep your pipeline moving. - Send at least five messages. Volume + consistency beats a single perfect email. **Friday (45-60 minutes) — review and learn.** - Use the *Weekly Review* prompt (Operations) to look at what happened: what shipped, what didn't, what the numbers say. - Use the *Metrics Review* prompt (Product or Finance) to look at one core number and decide one experiment for next week. - Use the *Lost Deal Autopsy* prompt (Sales) if something fell out of the pipeline — learn from it while it's fresh. **Sunday evening (15 minutes, optional but powerful) — set up Monday.** - Use the *Idea Board Review* prompt (Product) to clear your head of the five ideas buzzing around and decide which one Monday attacks. That's about five focused hours a week, and it covers every area of the business at least once. You don't have to do it all every week — but the weeks you do it, you'll get more done than the weeks you wing it. That's the whole point. --- ## Two worked examples — see the prompts in action. These are illustrative scenarios, not customer success stories. The numbers and businesses are fictional but intentionally plausible. ### Marketing example: M8, a warm-list launch email **Scenario and prompt filled in:** > You are an email copywriter. Write a launch email to my existing list. > > My product: **A $29 Notion template called Solo Cash Week, which helps freelancers review invoices, upcoming bills, and cash on hand in 20 minutes.** > What it does for the reader: **Turns a scattered weekly money check into one repeatable page.** > Why I built it: **I kept postponing my own cash review until Sunday night and wanted a smaller ritual.** > Launch offer: **No discount; the first 25 buyers can reply with one improvement request.** > My list: **312 subscribers who downloaded my free freelance proposal checklist; most know me for practical systems, but few know my finance templates.** > The ask: **Buy the template or reply with questions.** > > Write one email: subject line under 8 words, preview text, body under 250 words. Structure: the problem I kept seeing → what I built → who it's for and who it's not → what it costs → the honest reason I built it → the ask. Tone: like you're writing to one smart friend. No exclamation marks, no “don't miss out.” **Sample strong output (before → after):** - **Before:** “New template for freelancers.” - **After:** **Subject: A 20-minute money check for freelancers** I built this because I was treating my cash position like a problem for Future Me. Solo Cash Week is one Notion page for checking invoices due, bills coming up, and the cash actually available — without building a spreadsheet. It’s $29, and it’s for freelancers who want a weekly ritual, not a finance system. There’s no discount or countdown. If you’re one of the first 25 buyers, reply with the one thing you’d change and I’ll use that feedback for the next version. If your weekly money check is currently three tabs and a vague feeling, you can see it here: [LINK]. Questions are welcome. ### Finance example: F6, reconciling overdue invoices **Scenario and prompt filled in:** > You are a small-business finance operations analyst. Help me reconcile and track overdue invoices across clients so my books stay accurate while I chase payment. > > My open invoices: **Northstar Studio — INV-104 — $1,200 — issued Jun 3 — due Jul 3 — 30 days overdue — emailed Jul 10 — promised Jul 26; Cedar & Co — INV-109 — $650 — issued Jul 1 — due Jul 15 — 18 days overdue — no contact; Lakeview Labs — INV-111 — $2,400 — issued Jul 18 — due Aug 1 — current — no contact.** > My accounting labels: **Open, overdue, paid, partial, disputed.** > Payment terms: **Net 30; no late fee unless separately agreed in writing.** > Cash target this month: **$1,500.** **Sample strong output (before → after):** - **Before:** “Email everyone who owes me money.” - **After:** **Priority 1 — Northstar Studio, $1,200, 30 days overdue:** reconcile whether the Jul 26 promise was recorded as a payment or remains open; send a short confirmation today. **Priority 2 — Cedar & Co, $650, 18 days overdue:** send the invoice and request a payment date. Lakeview is current and needs no chase. Total open: $4,250; total overdue: $1,850; amount needed to reach the $1,500 target: $1,500 (assuming no pending credits or partial payments). **Northstar message:** “Hi [NAME] — checking on INV-104 for $1,200, which was due July 3. You mentioned July 26 as the payment date; I don’t see the payment marked in our records yet. Could you confirm whether it has been sent, or share the revised date? I’ve attached the invoice again. Thanks, [NAME].” Now the prompts. Five sections, 20+ each. Steal them, adapt them, make them yours. ## Part 2: Marketing Marketing for a solo founder is mostly this: knowing exactly who you serve, saying something useful to them repeatedly, and never lying. These prompts cover positioning, content, campaigns, and channels — the stuff that gets strangers to become customers. ### M1. Sharpen your one-line positioning **When to use:** When you're about to write anything — landing page, bio, pitch — and you need the core sentence right. You are a positioning strategist who has worked with early-stage companies. I run a business and I need a sharp one-line positioning statement. Here's what I do: [DESCRIBE WHAT YOU SELL IN ONE SENTENCE]. Who it's for: [DESCRIBE YOUR TARGET CUSTOMER]. The problem they have without it: [DESCRIBE THE PROBLEM]. What makes us different from alternatives: [LIST YOUR KEY DIFFERENCES FROM COMPETITORS OR DIY OPTIONS]. Current one-liner I'm not happy with: "[PASTE CURRENT MESSAGING]". Write 5 one-line positioning options. Rules: plain words a busy person understands in 5 seconds; no jargon, no hype words, no exclamation marks; each under 25 words; each must mention the customer, the outcome, and why it's different. Then pick the strongest and tell me in one sentence why it wins. ### M2. Define your ideal customer (ICP) in one page **When to use:** Before any marketing or sales work. If you skip this, every other prompt in this pack works worse. You are a market researcher. Based on the details below, build me a one-page profile of my ideal customer. What I sell: [DESCRIBE YOUR PRODUCT]. Who currently buys or uses it: [WHAT YOU KNOW ABOUT CURRENT CUSTOMERS]. Why they buy (as far as you know): [REASONS CUSTOMERS GIVE]. Price point: [PRICE]. Where I think they hang out: [CHANNELS]. Produce the profile in this exact structure: 1. Demographics: job title, company size, industry, location, income range (mark anything you're guessing). 2. Psychographics: goals, fears, frustrations, identity. 3. The trigger: the event or moment that makes them look for a solution like mine. 4. The buying journey: where they'd first hear about me, what they'd search, what would make them trust me. 5. Top 3 objections to buying. Mark every assumption as [ASSUMPTION] so I know what to verify with real customers. ### M3. Write a homepage hero section **When to use:** When your landing page needs a headline, subhead, and CTA that actually sell. You are a conversion copywriter. I need a hero section for my landing page. Product: [DESCRIBE YOUR PRODUCT]. Ideal customer: [ONE-LINE ICP FROM YOUR PROFILE]. Key outcome they want: [THE RESULT CUSTOMERS GET]. Key objection or doubt: [THE MAIN REASON PEOPLE HESITATE]. Primary action I want them to take: [CTA, E.G. START FREE TRIAL / BUY NOW]. Write three hero options. Each includes: headline (under 12 words), subheadline (1-2 sentences that explains what it is and who it's for), and a primary CTA button label (under 4 words). Constraints: plain, specific, zero hype words ("revolutionary," "game-changing," "unlock"), no exclamation marks. After the three options, critique your own best one and rewrite it once with the critique applied. ### M4. Draft a "this is who it's for / not for" section **When to use:** When you want to pre-qualify visitors so only the right people buy — this honesty converts better than trying to please everyone. You are a direct-response copywriter. Write a "This is for you if… / This is NOT for you if…" section for my product page. Product: [DESCRIBE YOUR PRODUCT]. Ideal customer: [DESCRIBE WHO IT'S FOR]. Outcome: [WHAT THEY GET]. Who it's NOT for: [BE HONEST — E.G. PEOPLE WHO WANT A FULL AGENCY, PEOPLE NOT WILLING TO PUT IN ANY TIME]. Write it as two bulleted lists, 5-7 bullets each, using the exact language my customers would use about themselves (plain, first-person-ish). The "not for" list must be genuine — turning away the wrong buyer is a feature. Keep the whole thing under 200 words. ### M5. Generate 20 hook options for one piece of content **When to use:** Before you post anything. The first line decides whether anyone reads the rest. You are a hook specialist who writes openings that stop the scroll. Here's the content I'm about to publish: Topic: [TOPIC]. Audience: [WHO IT'S FOR]. The single most useful thing in it: [THE KEY INSIGHT OR RESULT]. Format: [LINKEDIN POST / TWEET / EMAIL / VIDEO SCRIPT / NEWSLETTER]. Write 20 different opening hooks. Spread them across these styles: a surprising fact, a blunt statement, a question, a contrarian take, a mini-story, a "nobody talks about this" angle, a mistake I made, a before/after, a number-led claim, and a direct address. Rules: no clickbait that the content doesn't deliver, no all-caps, no "you won't believe." Each hook under 20 words. Then tell me which 3 you'd test first and why. ### M6. Turn one piece of content into a week of content **When to use:** When you have one good idea or piece of content and want to stretch it across channels without burning out. You are a content strategist. Help me repurpose one piece of content into a full week of posts. Original content: [PASTE YOUR CONTENT OR DESCRIBE IT]. Where I post: [LIST YOUR CHANNELS, E.G. LINKEDIN, X, EMAIL NEWSLETTER, YOUTUBE]. My audience: [WHO THEY ARE]. My voice: [ONE SENTENCE DESCRIBING YOUR TONE]. Create a 7-day repurposing plan: for each day, give me the channel, the angle (same idea, different framing — e.g. the story version, the list version, the contrarian version, the Q&A version), and a first-line hook. Also tell me which one asset from the week should be the "pillar" piece I put real effort into. Keep each day's brief under 80 words. ### M7. Write a 5-email welcome sequence **When to use:** When someone subscribes to your email list and you want to turn them into a customer without being pushy. You are an email marketer who writes honest, useful sequences. Write a 5-email welcome sequence for new subscribers. What I sell: [DESCRIBE YOUR PRODUCT AND PRICE]. What they signed up for: [THE LEAD MAGNET OR REASON THEY SUBSCRIBED]. My audience: [WHO THEY ARE]. The single biggest value I can give them for free: [YOUR BEST FREE ADVICE]. The main thing I want them to do by email 5: [E.G. BOOK A CALL / BUY THE PRODUCT]. Format: 5 emails, each with subject line, preview text, and body under 200 words. Structure: Email 1 — deliver the lead magnet and set expectations; Email 2 — useful content, no pitch; Email 3 — the story of why I started this; Email 4 — a second useful piece of content that shows off what I do; Email 5 — the offer, framed around the problem, not the product. Rules: no fake urgency, no "last chance," plain voice. ### M8. Write a product launch email to your existing list **When to use:** The day before or the day of launch, to the people who already know you. You are an email copywriter. Write a launch email to my existing list. My product: [DESCRIBE IT, INCLUDING PRICE]. What it does for the reader: [THE OUTCOME]. Why I built it: [ONE SENTENCE — THE HONEST REASON]. Launch offer: [ANY GENUINE LAUNCH OFFER, OR NONE]. My list: [HOW MANY SUBSCRIBERS, AND WHAT THEY KNOW ME FOR]. The ask: [BUY NOW / JOIN THE WAITLIST / REPLY WITH QUESTIONS]. Write one email: subject line (under 8 words), preview text, body under 250 words. Structure: the problem I kept seeing → what I built → who it's for and who it's not → what it costs → the honest reason I built it → the ask. Tone: like you're writing to one smart friend. No exclamation marks, no "don't miss out." ### M9. Draft a 30-day organic content calendar **When to use:** Monthly planning, so you're never staring at a blank page at 8 a.m. You are a content planner. Build me a 30-day organic content calendar. What I sell: [DESCRIBE YOUR PRODUCT]. My audience: [WHO THEY ARE]. Where I post: [CHANNELS]. Themes I want to cover (pick or add): [THEMES, E.G. HOW-TO, CASE STUDY, OPINION, BEHIND-THE-SCENES, MISTAKES, TOOLS]. My goal this month: [E.G. 10 NEW EMAIL SUBSCRIBERS / 5 INBOUND LEADS / LAUNCH AWARENESS]. Posts I already have or must do: [ANY COMMITTED POSTS]. Produce a table: Date | Channel | Theme | Topic idea | Format | CTA. 20 posts minimum, leaving the rest of the days for engagement and rest. Every topic must be something I can genuinely speak to. Mark each topic with the angle in one line. Keep it realistic — I'm a solo founder, not a content team. ### M10. Turn customer conversations into a case study draft **When to use:** After a customer tells you something good. Never fabricate these — this prompt extracts what really happened. You are a case study writer. I'm going to paste real notes from a customer conversation. Turn them into a case study draft, and tell me what's missing. Notes from my conversation: [PASTE YOUR RAW NOTES — WHAT THEY SAID, THE PROBLEM, THE RESULT, QUOTES IN THEIR WORDS]. My product: [WHAT YOU SELL]. Format needed: problem → solution → result, with a short pull quote. Draft it as: headline (under 10 words), 3-5 sentence summary, then the story in 300-400 words using their words where possible. After drafting: list the facts I should confirm with the customer before publishing, and list 3 specific questions I should ask them to strengthen the story. Do not invent quotes, numbers, or results — flag anything missing as [NEEDS CONFIRMATION]. ### M11. Analyze a competitor's messaging and find the gap **When to use:** Before positioning, launching, or writing sales pages — see where the market is crowded and where it's open. You are a competitive strategist. Here are my competitor's public marketing materials. Competitor materials: [PASTE THEIR HOMEPAGE COPY, ADS, OR KEY MESSAGING]. Who they target: [WHAT YOU KNOW OR INFER]. What I do differently: [YOUR DIFFERENCES]. Do four things: 1. Summarize their positioning in 3 sentences: who they target, what problem they claim to solve, how they differentiate. 2. List their top 3 messaging themes and the emotional appeals they use. 3. Identify gaps: promises they make but don't seem to back up, audiences they ignore, angles they avoid. 4. Recommend the positioning angle I could own that they're leaving open — but only if it's honest and defensible for my product. Mark any inference as [INFERENCE] so I can verify it. ### M12. Write an SEO-optimized blog post from a brief **When to use:** When you have a topic your customers search for and you want a draft to edit. You are an SEO content writer. Write a blog post from my brief. Topic: [TOPIC]. Primary keyword: [KEYWORD]. Who it's for: [AUDIENCE]. What I actually know about this topic (facts, experience, opinions): [YOUR REAL KNOWLEDGE — THIS IS THE PART THAT MAKES IT NON-GENERIC]. What I want the reader to do at the end: [CTA]. Word count: [TARGET]. Structure: a title with the keyword and a curiosity hook; intro under 100 words that states the problem; body organized in clear subheadings; a conclusion that leads to the CTA. Rules: no AI-sounding filler phrases, no "in today's fast-paced world," write like a practitioner who has done this. After the draft, give me a 3-bullet summary of what makes this post non-generic, and flag any factual claim I should verify. ### M13. Create a keyword and topic list from one seed topic **When to use:** When you're building a content pipeline and don't know what your customers actually search. You are an SEO researcher. Build me a keyword and topic map from one seed topic. My business: [WHAT YOU SELL]. Seed topic: [ONE TOPIC, E.G. "INVOICING FOR FREELANCERS"]. Audience: [WHO THEY ARE]. Produce: 1. 15 long-tail keyword ideas (3+ words) with the search intent for each: informational, commercial, or transactional. 2. 10 content titles that target those keywords, each with the format (how-to, list, comparison, case study, tool roundup). 3. The 3 "money" topics most likely to attract buyers, not just readers. Keep titles concrete and useful, not clickbait. Flag any keyword where I'd be competing with giants as [COMPETITIVE] so I know to target the long-tail version instead. ### M14. Draft a paid ad with 5 variations **When to use:** When you're testing paid traffic and need a batch of honest, compliant ad variants. You are a direct-response advertiser. Write ad variations for my product. Product: [DESCRIBE]. Audience: [TARGETING — WHO THEY ARE, THEIR INTERESTS]. Main benefit: [THE OUTCOME]. Main objection: [WHY PEOPLE DON'T BUY]. Platform: [GOOGLE SEARCH / META / LINKEDIN / TIKTOK]. Budget reality: [SMALL — SAY SO IF TRUE]. Write 5 ad variations: one problem-focused, one solution-focused, one social-proof-focused (use only real proof I have: [PASTE REAL SOCIAL PROOF, OR WRITE "NONE"]), one question-led, one straight-talking plain version. Each: headline, 1-2 sentence body, CTA. Rules: no superlatives I can't support, no "limited time" unless I'm actually running a limited offer, no earnings promises. After the 5, tell me which 2 to test first and what metric tells me the winner. ### M15. Draft a referral ask your customers won't cringe at **When to use:** After a customer has a win, to ask for referrals the honest way. You are a customer-success writer. Draft a referral request I can send to a happy customer. What they bought: [PRODUCT]. The win they got: [WHAT SUCCEEDED FOR THEM]. Our relationship: [HOW LONG THEY'VE BEEN A CUSTOMER, HOW WE MET]. What I'd like: [THE ASK — E.G. INTRO TO 3 PEOPLE / SHARE ON SOCIAL / A REVIEW]. Write a short message (under 150 words) that: acknowledges their win first, asks for help in a way that respects their time, makes the referral easy (give them a one-line description of who I'm ideal for), and explicitly gives them an out ("totally fine if not"). Also give me a one-line version I can use in person or at the end of a call. Tone: grateful, zero guilt-trip. ### M16. Draft a press release or launch announcement **When to use:** When something is genuinely newsworthy — a launch, a milestone, a funding round. Not for routine updates. You are a PR writer. Draft a press release for my announcement. The news: [WHAT'S HAPPENING — LAUNCH / MILESTONE / FUNDING]. My company and what it does: [ONE SENTENCE]. Why it matters (the honest version): [THE REAL SIGNIFICANCE]. A quotable line from me: [YOUR VIEW IN ONE SENTENCE]. Target outlet: [WHERE YOU'D HOPE IT RUNS]. Format: headline (under 15 words), dateline, lead paragraph answering who/what/when/where/why, one supporting paragraph with the detail, my quote, a boilerplate "About" paragraph, and contact info. Rules: journalistic, factual, no marketing adjectives. After the draft, list the 3 facts a journalist would most want verified, and 3 outlets that would plausibly care about this — be realistic. ### M17. Draft a landing page section for social proof (real only) **When to use:** When you have genuine proof — quotes, numbers, logos — and want it presented honestly and persuasively. You are a conversion copywriter. Draft the social-proof section of my landing page using only real proof I give you. Real proof I have: [PASTE REAL QUOTES, NUMBERS, OR CUSTOMER NAMES — OR WRITE "NONE YET"]. Product: [WHAT YOU SELL]. Audience: [WHO THEY ARE]. What I'm trying to prove: [E.G. THAT IT WORKS / THAT IT'S FOR PEOPLE LIKE THEM / THAT I'M LEGIT]. Write the section: a heading (under 8 words), then the proof arranged in the most credible order (specific numbers first, named sources before anonymous, quotes with context). If I said "none yet," instead write an honest placeholder that doesn't fake proof — e.g. a "built in public" framing or a guarantee — and tell me 3 ways to earn real proof in the next 30 days. Rules: never invent quotes or numbers. ### M18. Write a "from zero" channel experiment plan **When to use:** When you have no traffic and need to pick where to spend your limited time. You are a growth strategist for early-stage products. I need a channel experiment plan. My product: [DESCRIBE]. Ideal customer: [WHO THEY ARE]. Where they already hang out (my best guess): [CHANNELS]. My constraints: [HOURS PER WEEK, BUDGET, SKILLS]. What I've tried before: [CHANNELS AND RESULTS, OR "NOTHING"]. Give me: 1. A ranked list of 5 channels I could realistically win on, given my constraints — ranked by (probability of finding customers) x (my ability to compete), not by hype. 2. For the top 2: a 2-week experiment design — exactly what I'll post/do, how often, and the one metric that tells me if it's working. 3. The kill criteria: the number below which I stop and move to the next channel. Be blunt about channels that will waste my time at my current stage. ### M19. Draft a response to negative feedback or a bad review **When to use:** When someone criticizes you publicly — respond fast, publicly, and graciously. You are a crisis-communication writer. Draft a public response to negative feedback. The feedback: [PASTE THE REVIEW OR COMMENT, VERBATIM]. Where it appeared: [PLATFORM]. What happened, from my side: [THE FACTS AS YOU KNOW THEM]. What I've done or will do about it: [YOUR REAL PLAN]. What I must not say: [ANYTHING YOU KNOW TO AVOID, OR "NOTHING"]. Write a public reply under 150 words that: thanks them for the feedback, acknowledges the specific problem without defensiveness, states the facts if the feedback is inaccurate (without attacking the person), and describes the concrete step I'm taking. Then give me a private follow-up message offering to make it right. Rules: never argue with the reviewer, never promise anything I won't deliver. ### M20. Write a content brief for a guest post or collab **When to use:** When you're pitching or writing for someone else's audience and need a tight, respectful brief. You are a content editor. Help me pitch a guest post or collaboration. My expertise: [WHAT YOU KNOW DEEPLY]. Their audience: [THE PUBLICATION OR PARTNER AND WHO READS IT]. The post I want to write: [TOPIC IDEA]. What's in it for them: [HONEST VALUE — E.G. A DIFFERENT PERSPECTIVE, REAL EXPERIENCE]. Produce: 1) a pitch email under 120 words with subject line; 2) a 3-point outline of the post; 3) the specific promise to the reader in one sentence; 4) two alternative topic ideas that fit their audience better than my original, if mine is weak. Rules: no generic "I'd love to contribute to your great publication" flattery — lead with the value and be specific. ### M21. Audit a piece of my own marketing and fix it **When to use:** Before publishing anything important — a second pair of eyes that never gets tired. You are a ruthless marketing editor. Audit my draft and improve it. My draft: [PASTE YOUR DRAFT — LANDING PAGE, EMAIL, POST, AD]. Who it's for: [AUDIENCE]. What it must accomplish: [THE ONE GOAL]. My voice: [YOUR TONE IN A FEW WORDS]. Do this in order: 1) Tell me what's working — 3 specific things, honestly. 2) Tell me what's weak — the vague parts, the places a skeptical reader would bounce, anything that reads like generic AI or corporate filler. 3) Rewrite the weak parts in place, keeping my voice, tightening every sentence. 4) Give me the finished version with a one-line summary of the biggest change. Be direct — don't soften criticism. ## Part 3: Sales Solo founders sell with email, calls, and follow-through. These prompts cover the whole arc: finding the right person, getting their attention, running a good conversation, handling objections, and closing without being pushy. ### S1. Write a first-touch outreach email that doesn't sound like spam **When to use:** Cold outreach to a real, researched prospect. One email, not a blast. You are a sales writer whose emails get replies. Write a first outreach email. Who I'm contacting: [NAME, ROLE, COMPANY — AND ONE REAL, SPECIFIC THING YOU KNOW ABOUT THEM]. What I do: [YOUR BUSINESS IN ONE SENTENCE]. Why I'm contacting them specifically: [THE REAL REASON — A PROBLEM THEY MIGHT HAVE, SOMETHING THEY PUBLISHED, A CHANGE AT THEIR COMPANY]. What I want: [E.G. A 15-MIN CALL / A REPLY / NOTHING BUT A THOUGHT]. Warmth of connection: [ANY MUTUAL CONNECTION OR PRIOR INTERACTION — OR "NONE"]. Write the email: subject line under 6 words, body under 120 words. Structure: the specific thing I noticed about them → why it made me think of my product → what I'm offering → a low-pressure ask with an easy out. Rules: no "I hope this email finds you well," no "I wanted to reach out," no fake flattery, no attachment, one ask only. ### S2. Write a 4-email follow-up sequence for one prospect **When to use:** After the first email goes unanswered. Most sales happen in the follow-up. You are a sales persistence strategist. Write a follow-up sequence for a prospect who hasn't replied. Original email I sent: [PASTE IT]. Prospect: [WHO THEY ARE]. What I know they're busy with: [CONTEXT]. What I'm selling and why it's relevant to them: [THE RELEVANCE]. Stopping point: [HOW MANY TOUCHES BEFORE I STOP]. Write 4 follow-up emails: #1 (2 days later) — a short value-add (an insight, resource, or question relevant to them, no pitch); #2 (5 days later) — a different angle on the problem, with a tiny story or example; #3 (10 days later) — a blunt, respectful "is this worth your time?" with an explicit out; #4 (2 weeks later) — the graceful close that leaves the door open. Each under 80 words, each with subject line. Rules: no guilt-tripping, no passive-aggression, no "just circling back." ### S3. Prepare for a discovery call in 10 minutes **When to use:** Right before any sales call. Turn a prospect's public footprint into a prep sheet. You are a sales enablement coach. Prepare me for a call with a prospect. Prospect: [NAME, ROLE, COMPANY]. What I found about them: [PASTE THEIR LINKEDIN, WEBSITE, OR ANY PUBLIC INFO]. What I sell: [YOUR PRODUCT]. What I'd love to happen on the call: [OUTCOME — E.G. QUALIFY THEM, GET A SECOND MEETING, PITCH]. Produce: 1) 3 likely reasons they agreed to this call (based on their role and context). 2) 5 smart opening questions, ordered from easy/safe to sharp — questions that get them talking about their work, not small talk. 3) The 3 most likely objections and a one-line response to each. 4) A 2-line summary of what I should listen for that would make this a yes. 5) One question I should NOT ask (something that would reveal I didn't prepare). ### S4. Draft a discovery call agenda and question list **When to use:** When you run the call and want to stay in control without interrogating. You are a sales trainer. Build me a discovery call agenda and question set. My product: [DESCRIBE]. Who I'm talking to: [ROLE AND COMPANY TYPE]. What I need to learn to know if I can help: [THE KEY FACTS, E.G. BUDGET, TIMELINE, CURRENT PROCESS, PAIN]. Call length: [E.G. 30 MINUTES]. Build the agenda in 5 blocks with time allocations: 1) Warm-up and context (5 min) — questions that establish who they are and what their world looks like. 2) Current situation (10 min) — how they do this today, what's working, what's not. 3) Pain and impact (7 min) — questions that quantify the problem and its cost. 4) Fit and next steps (5 min) — budget, timeline, who else decides. 5) Close (3 min) — a natural summary and a clear next step. Write the questions in plain conversational language, 3-4 per block, and tell me the one question per block I should not skip. ### S5. Draft a demo script that focuses on their problem **When to use:** When you're showing your product to a qualified prospect. You are a demo scriptwriter for technical products. Write a demo script. My product: [DESCRIBE — WHAT IT DOES, HOW IT WORKS]. The prospect: [WHO THEY ARE, THEIR ROLE]. The problem we're solving for them: [THE SPECIFIC PAIN FROM THE DISCOVERY CALL]. Their likely familiarity with products like mine: [NOVICE / FAMILIAR / EXPERT]. Demo length: [E.G. 20 MINUTES]. Write the script with: 1) A 60-second opener that re-states their problem in their words (not my product's features) and sets the demo's promise. 2) The demo flow: 3-4 stops, each stop = the feature, the problem it solves, and one "would this work for you?" checkpoint question. 3) A close that proposes the specific next step. 4) A 30-second "if we only have 5 minutes" version. Rules: features only appear as answers to problems; no jargon unless they used it first. ### S6. Role-play a sales call with me (objections edition) **When to use:** Before a real call, to practice. This one is interactive — answer the AI like you would a prospect. You are a skeptical but fair buyer. We're going to role-play a sales call. My product: [DESCRIBE]. You are playing: [THE PROSPECT'S ROLE, E.G. A HEAD OF MARKETING AT A 20-PERSON AGENCY]. Your situation: [THE PAIN YOU'RE PLAYING — BE REALISTIC AND SOMEWHAT HARD TO CONVINCE]. Your budget: [TIGHT / REASONABLE / UNKNOWN]. Rules: respond to my pitch like a real busy buyer — short answers, questions back, and the objections people actually have (price, time to implement, "I can do this myself," "why you," "we tried this before"). After each of my messages, respond as the buyer, then give me a one-line note on how I handled it and one alternative response I could have used. Don't let me win easily — make me work for it. ### S7. Prepare for the "it's too expensive" objection **When to use:** Before a pricing conversation, and every time price comes up on a call. You are a value-selling coach. Help me handle the price objection. My price: [PRICE AND WHAT IT COVERS]. Their alternative: [WHAT THEY'D DO INSTEAD — INHOUSE, CHEAPER TOOL, NOTHING]. The value my product delivers: [CONCRETE OUTCOMES — TIME SAVED, MONEY MADE, RISK REMOVED]. Who they are: [ROLE AND SITUATION]. What I will NOT do: [E.G. DISCOUNT IMMEDIATELY, BADMOUTH COMPETITORS]. Produce: 1) The three reasons "too expensive" usually means something else (no budget, no urgency, no perceived value) and one diagnostic question to find out which it is. 2) A 3-step response script: validate → reframe around cost of doing nothing → anchor to their numbers. 3) Two honest alternatives I can offer if price is genuinely the blocker (e.g. smaller scope, annual payment, referral discount) — but only ones I'm actually willing to do. ### S8. Draft a proposal that sells the outcome, not the features **When to use:** When you've had a good call and need to turn it into a proposal. You are a proposal writer. Turn my notes into a proposal. My product/service: [DESCRIBE]. The prospect: [NAME, COMPANY, ROLE]. Their problem (from our call): [THE PAIN THEY CONFIRMED]. What I'm proposing: [SCOPE, DELIVERABLES, PRICE, TIMELINE]. What they said they care most about: [THEIR PRIORITIES]. Write the proposal structure: 1) A 3-sentence opening that re-states their problem in their words and the outcome they want. 2) "What I propose" — the scope, written as outcomes ("you'll have X by Y date"), not just deliverables. 3) What it costs and what's included, plainly. 4) Why me — 3 honest reasons, including relevant experience. 5) Next steps and validity. Keep it under one page where possible. Rules: no filler sections, no "we are excited to," no promises I can't keep. End with a one-line summary I can put in the email when I send it. ### S9. Draft the follow-up after sending a proposal **When to use:** After the proposal is sent. The silent period decides the deal. You are a sales follow-up specialist. Write my proposal follow-up. The prospect: [WHO]. What I sent: [PROPOSAL SUMMARY, PRICE]. When I sent it: [DATE]. Their likely hesitation: [YOUR BEST GUESS — OR "UNKNOWN"]. The deadline that actually exists: [ANY REAL TIMELINE, OR "NONE"]. Write: 1) A follow-up email for day 3 after sending — short, assumes the proposal was received, offers to walk through it, no pressure. 2) A follow-up for day 7 — a genuinely useful addition (a relevant example, answer to a likely question, a small concession if appropriate). 3) A follow-up for day 14 — the honest "should I close this file?" email with an easy out, and a plan for what I do if they say yes vs. no vs. nothing. No fake deadlines. ### S10. Write a "no, thanks" response that keeps the door open **When to use:** When a prospect declines. How you handle the no decides whether they come back. You are a relationship-sales writer. Draft my response to a prospect who said no. Their message: [PASTE THEIR DECLINE, VERBATIM]. Why they said no (if they said): [REASON — OR "UNKNOWN"]. What I'd genuinely want from them: [E.G. KEEP IN TOUCH / INTRO TO SOMEONE ELSE / FEEDBACK]. Write a short reply (under 100 words) that: thanks them for telling me directly (people rarely do), doesn't argue or re-pitch, leaves a specific, low-effort opening for the future, and — if appropriate — asks one honest question: what changed, or who else might benefit. Give me two versions: one for when they gave a reason, one for when they didn't. ### S11. Draft a LinkedIn profile that sells without being salesy **When to use:** When your LinkedIn is part of how people find and vet you. You are a personal-brand writer for founders. Rewrite my LinkedIn profile. My current headline: [PASTE IT]. What I do: [YOUR BUSINESS IN PLAIN WORDS]. Who I help: [TARGET CUSTOMER]. The result they get: [OUTCOME]. Proof I have: [REAL RESULTS, NUMBERS, OR CREDIBILITY — OR "STILL BUILDING"]. Voice: [YOUR TONE]. Produce: 1) A headline under 10 words that says who I help and the outcome (not just a job title). 2) An About section under 250 words: opening line that hooks, what I do, who it's for, how I'm different, a soft CTA — written in first person, no third-person corporate bio, no buzzwords like "passionate" or "results-driven." 3) 3 bullet points for a "What I'm working on" post that shows the work honestly. Rules: every claim must be true and specific. ### S12. Draft a sales page from your product's facts **When to use:** When the landing page needs to do the selling for you. You are a direct-response copywriter. Write a sales page. Product: [DESCRIBE]. Price: [PRICE AND WHAT'S INCLUDED]. Customer: [WHO IT'S FOR]. The problem: [THE PAIN — AS THEY FEEL IT]. The outcome: [WHAT THEY GET]. Objections: [WHY PEOPLE DON'T BUY — BE HONEST]. Real proof: [REAL TESTIMONIALS/NUMBERS, OR "NONE"]. Structure: headline (under 12 words) → subhead → the problem in their words (2-3 sentences) → the consequence of not fixing it → what I'm offering and how it works (plain steps) → what's inside (bullet list, specific) → price and what's included → why trust me (real proof or honest alternative) → the ask → a simple guarantee if I offer one. Rules: no hype words, no fake urgency, every claim traceable to a fact I gave you. If I gave no proof, don't invent any — write the honest section and tell me what to earn. ### S13. Draft a testimonial request that gets real, usable quotes **When to use:** After a customer's win. Ask for testimonials the way people actually respond to. You are a customer-advocacy writer. Draft a testimonial request. The customer: [WHO THEY ARE]. What they achieved with my product: [THE CONCRETE WIN]. Where the testimonial will be used: [WEBSITE / SOCIAL / CASE STUDY]. Write a short email (under 150 words) that: reminds them of the specific win (name it — people need the prompt), asks for a testimonial, makes it easy by offering 3 fill-in-the-blank prompts (e.g. "Before this, I was struggling with…", "What changed was…", "The best part is…"), and offers to draft it for them to approve. Also give me 3 specific questions I could ask them on a quick call instead, that reliably produce quotable lines. ### S14. Draft an upsell or expansion message to an existing customer **When to use:** When a customer is getting value and could use more — ask honestly, serve first. You are a customer-success writer. Draft an upsell message to an existing customer. The customer: [WHO THEY ARE, HOW LONG THEY'VE BEEN WITH ME]. What they use now: [CURRENT PLAN/PRODUCT]. The value they're getting (real evidence): [USAGE, RESULTS, THEIR WORDS]. The offer: [THE NEXT STEP — HIGHER TIER / ADD-ON / MORE SEATS]. Why it genuinely fits them: [THE HONEST REASON THIS HELPS THEM]. Write the message (under 180 words): lead with the value they're already getting (specific), surface the new thing as a natural next step, make the case in terms of their outcomes, and include a low-pressure next action. Rules: no "upgrade now and save," no manufactured deadlines. If I don't have a genuinely honest reason this fits them, say so instead of writing. ### S15. Draft a partnership or joint-venture outreach **When to use:** When you want to reach someone whose audience overlaps yours, in a way that offers value first. You are a partnership-negotiation writer. Draft outreach to a potential partner. The potential partner: [NAME, WHAT THEY DO, THEIR AUDIENCE]. Why we fit: [THE HONEST OVERLAP — SAME AUDIENCE, COMPLEMENTARY OFFERINGS, SHARED VALUES]. What I can offer them: [REAL VALUE — AUDIENCE ACCESS, A PRODUCT FOR THEIR AUDIENCE, CONTENT, A SPLIT]. What I'd want in return: [YOUR ASK]. Write a first email (under 150 words) with subject line that: opens with something specific about their work (not flattery), states the overlap and why their audience would genuinely benefit, proposes one concrete, low-effort first step (e.g. a 15-minute call, a cross-promo swap, a guest piece), and leaves the ball in their court. Then list 3 alternative offers I could make if my first one doesn't land. ### S16. Analyze my pipeline and tell me where it's stuck **When to use:** Weekly. Feed your deals in and find the bottleneck. You are a sales analyst. Analyze my pipeline. My deals (one line each): [LIST — PROSPECT, STAGE, AGE, VALUE, NEXT ACTION, LAST TOUCH]. My close rate historically: [IF YOU KNOW IT]. My goal: [REVENUE TARGET AND TIMEFRAME]. Do: 1) Tell me the 3 deals most likely to close this week and why. 2) Identify the stage where deals get stuck — point to the evidence. 3) Flag any deal that's a time-waster (age + no next step) and recommend what to do with it (revive, downgrade, or kill). 4) Give me a prioritized action list for today: the 5 things that most move the pipeline. Be blunt — I need decisions, not encouragement. ### S17. Run a lost-deal autopsy **When to use:** When a deal dies. Learn from it while it's fresh, then let it go. You are a sales coach who does post-mortems. Help me understand a lost deal. The deal: [PROSPECT, WHAT THEY WANTED, VALUE]. What happened (timeline): [KEY EVENTS — FIRST TOUCH TO LOSS]. Why they said no (if they said): [THE REASON]. What I did well: [YOUR READ]. What I'd do differently: [YOUR READ]. Any red flags I missed: [HONEST ASSESSMENT]. Produce: 1) The 3 most likely real reasons this deal died (people rarely give the real reason). 2) What I should have done differently at each stage — concrete, not vague. 3) The one systemic lesson: is this a one-off or a pattern I need to fix in my process, offer, or targeting? 4) A 2-sentence note to file so future me doesn't repeat it. No self-flagellation — this is about the pattern, not the person. ### S18. Draft a "checking in" email that adds value (not noise) **When to use:** When you want to stay top-of-mind with prospects or past customers without being annoying. You are a relationship-marketing writer. Draft a check-in email. Who it's to: [PROSPECT OR PAST CUSTOMER, THEIR SITUATION]. What I know about their world: [SOMETHING REAL — A CHANGE, A PROJECT, A SEASON]. What genuinely useful thing I can share: [A RESOURCE, INSIGHT, OR OFFER — MUST BE REAL]. What I want from this email: [E.G. NOTHING / A REPLY / A CALL]. Write the email (under 100 words): a specific nod to their situation, one genuinely useful thing, and one light ask or none at all. Rules: if I can't think of a genuinely useful thing to share, the email shouldn't be sent — tell me that honestly. No "just wanted to touch base" as the whole email. ### S19. Escalate a late invoice while preserving the relationship **When to use:** When an invoice is late. Get paid, stay friends. You are a relationship-preserving collections writer. Draft a late-payment escalation that protects the relationship without hiding the seriousness. The customer: [WHO, AND YOUR RELATIONSHIP]. The invoice: [AMOUNT, DATE DUE, DAYS OVERDUE]. What I've sent already: [PRIOR REMINDERS — OR "NONE"]. The stakes: [HOW MUCH THIS MATTERS TO ME — BE HONEST]. My actual contract terms and consequences: [TERMS — DO NOT INVENT ANY]. Write a 3-step escalation: 1) Day 1-3 — warm reminder with invoice and payment link. 2) Day 7 — firmer note that offers a practical way to resolve a blocker and asks for a payment date. 3) Day 14 — direct note with a hard deadline and only the consequence I am actually entitled and willing to apply. For each, include a subject line, message under 80 words, and tone label. Add a short branch for what to send if they promised to pay but broke that promise. Rules: preserve dignity, never shame or threaten, never imply a consequence not in my terms, and always leave a clear path to pay. ### S20. Write a "thank you" that deepens the relationship **When to use:** After a purchase, a referral, a call, or any moment worth marking. You are a relationship writer. Draft a thank-you message. Who it's to: [CUSTOMER / REFERRER / PARTNER]. What happened: [THE MOMENT — THEY BOUGHT, REFERRED, SHOWED UP]. What I actually appreciate: [THE SPECIFIC, HONEST REASON]. What I'd love to happen next: [ONE SOFT NEXT STEP, OR NONE]. Write it: under 100 words, specific about what they did and why it matters to me, no transactional "your business is important to us," one sincere detail only a real founder would notice. Give me a short version for a handwritten note or DM too. ### S21. Build my weekly sales routine **When to use:** When sales feel chaotic and you need a repeatable week. You are a sales productivity coach for solo founders. Build me a weekly sales routine. My situation: [HOW MANY PROSPECTS, CALLS, AND OPEN DEALS I HAVE]. My constraints: [HOURS PER WEEK FOR SALES, WHEN I WORK BEST]. What's working: [WHAT'S BEEN WORKING IN SALES]. What's not: [WHERE I DROP THE BALL]. Build a routine that fits my constraints: which hours of which days go to outreach vs. calls vs. follow-ups vs. admin; what gets done in each block; how I keep the pipeline fed without burning out; and one simple metric to track weekly (e.g. conversations had, proposals sent, follow-ups completed). Keep it realistic for a solo founder — I can't do 5 hours of outreach a day. Also tell me the one habit that would most improve my sales results. ## Part 4: Operations Operations is where solo founders drown — email, decisions, hiring, process. These prompts turn AI into your chief of staff: building systems, drafting decisions, and getting the admin out of your head. ### O1. Turn one task into a step-by-step SOP **When to use:** When you do something twice and don't want to think about it a third time. You are an operations consultant. Turn a task into a standard operating procedure (SOP). The task: [DESCRIBE THE TASK — E.G. ONBOARDING A NEW CLIENT, FILING A MONTHLY REPORT, SHIPPING AN ORDER]. Who will follow the SOP: [YOURSELF IN A HURRY / A HIRED ASSISTANT / A CONTRACTOR]. Tools involved: [THE TOOLS USED]. What "done" looks like: [THE FINISHED RESULT]. Common mistakes: [MISTAKES YOU'VE MADE OR SEEN]. Write the SOP: objective (2 lines), what you need before starting (checklist), the steps (numbered, each with the tool and the exact action, including the small details like naming conventions and where files go), what to check before calling it done, and a "what could go wrong" section with the fix for each. Format it so a smart person who has never done it could follow it. ### O2. Draft a job description that attracts the right person **When to use:** Before you hire anyone — contractor, part-timer, or first employee. You are a hiring writer for small teams. Write a job description. The role: [TITLE AND WHAT THEY'D ACTUALLY DO]. Hours and arrangement: [FULL-TIME / PART-TIME / CONTRACT, REMOTE / ONSITE]. What I actually need them to own: [THE 3-5 REAL RESPONSIBILITIES]. Who I'm looking for: [EXPERIENCE LEVEL AND KEY QUALITIES — HONEST ABOUT WHAT'S ESSENTIAL VS NICE]. What I can offer: [PAY RANGE, FLEXIBILITY, WHAT IT'S LIKE TO WORK WITH ME]. Company context: [ONE SENTENCE ABOUT YOUR BUSINESS]. Write it: a 3-sentence intro that sells the reality (not hype), responsibilities as 4-6 concrete bullets, requirements split into "must have" (short) and "nice to have" (short), what I offer, and an application instruction that filters for attention to detail (e.g. "reply with one line about why this role fits you"). Rules: no "rockstar," "ninja," or "we're looking for someone passionate" — specific beats enthusiastic. ### O3. Draft interview questions that reveal how someone actually works **When to use:** When you're about to interview and need questions that predict performance, not charm. You are an interviewing expert for early-stage companies. Write my interview question set. The role: [TITLE AND CORE RESPONSIBILITIES]. What success in this role looks like in 3 months: [THE OUTCOMES]. What would make them fail: [YOUR FEAR — E.G. NEEDS HAND-HOLDING, CAN'T PRIORITIZE, POOR WRITING]. Stage of company: [E.G. SOLO FOUNDER, FIRST HIRE]. Write 8 questions organized in 4 blocks: 1) Past behavior (2 questions) — ask for specific past situations with follow-ups that test for real detail vs. rehearsed answers. 2) Skills (2 questions) — a small practical task they can talk through, not a trick. 3) Self-awareness (2 questions) — what they're bad at, how they handle feedback. 4) Motivation (2 questions) — why this role, what would make them leave. For each question, add the follow-up that separates a real answer from a good story, and tell me the one red flag to listen for. ### O4. Write a decision memo for a choice you're stuck on **When to use:** Any significant decision — pricing change, new hire, platform switch, kill a project. You are a decision analyst. Help me think through a decision properly. The decision: [WHAT YOU'RE DECIDING]. The options: [LIST THE REAL OPTIONS — INCLUDE "DO NOTHING"]. What I care about (in order): [CRITERIA — E.G. TIME, MONEY, RISK, CONTROL, STRESS]. What I know: [FACTS AND CONSTRAINTS]. What I don't know: [THE UNKNOWNS]. My gut feeling: [YOUR INITIAL LEAN — BE HONEST]. Produce a one-page decision memo: 1) Restate the decision in one sentence. 2) Each option scored against my criteria with the reasoning (mark your scores as estimates). 3) The key uncertainty for each option — what would need to be true for it to work. 4) The best option and why, plus the worst-case scenario for it and whether I could survive it. 5) One test I could run in the next week that would de-risk the choice. End with the decision you'd make in my shoes and the assumption you made to get there. ### O5. Draft a meeting agenda that earns the meeting **When to use:** Any meeting you schedule — 10 minutes of prep saves 60 minutes of drift. You are a meeting-effectiveness coach. Build an agenda for my meeting. The meeting: [WHAT IT'S ABOUT, WITH WHOM]. The outcome I need by the end: [THE DECISION, ALIGNMENT, OR PLAN]. How long it should be: [DURATION]. What attendees care about: [THEIR STAKES — OR "UNKNOWN"]. Build the agenda: the one-sentence purpose at top; 3-5 items in priority order, each with the time, the goal (inform / discuss / decide), and the specific question or prompt that starts it; the decision or outcome required; and what happens after (owner + date). Rules: if the outcome can be handled in an email, say so and give me the email draft instead of the agenda. ### O6. Draft a delegation brief — hand something off properly **When to use:** When you give a task to anyone — assistant, contractor, future-you. You are a delegation coach. Write a delegation brief. The task: [WHAT NEEDS DOING]. Why it matters: [THE CONTEXT — WHY THIS TASK EXISTS]. What done looks like: [THE CONCRETE RESULT, INCLUDE QUALITY BAR]. Deadline and checkpoints: [WHEN AND HOW OFTEN TO CHECK IN]. What they have: [ACCESS, TOOLS, BUDGET, PRIOR WORK]. What they can decide themselves vs. what needs you: [DECISION BOUNDARIES]. Write the brief as a short document: context (3 sentences max), the task (one paragraph), done means (checklist of 3-6 concrete criteria), boundaries (what they decide vs. escalate), timeline with checkpoints, and what to do if stuck. Then write the 3-sentence version I'd send in Slack. Rules: clarity over politeness — vague briefs are how tasks come back wrong. ### O7. Draft a hiring offer and rejection that keep your reputation **When to use:** The moments people remember: when you say yes, and when you say no. You are a hiring-communication writer. Draft my candidate messages. The candidate: [NAME, ROLE THEY APPLIED FOR]. The news: [OFFER / REJECTION AFTER INTERVIEW / REJECTION WITHOUT INTERVIEW]. The offer (if applicable): [SALARY, START DATE, KEY TERMS]. The reason (if rejection): [THE HONEST REASON — OR "NO SPECIFIC REASON"]. What I liked about them: [A REAL, SPECIFIC COMPLIMENT]. Write: for an offer — warm but professional, the specifics, the next step, a deadline that's real. For a rejection after interview — specific thanks, one honest piece of feedback they can use (if I have one), no false "we'll keep your resume on file" unless I mean it, and an open door if genuine. For a silent rejection — short, respectful, and honest about not moving forward. Each under 150 words. Tone: like a human, because I am one. ### O8. Draft a customer support response (from your real policies) **When to use:** Any support email. Fast, on-brand, and honest about what you can do. You are a customer-support writer. Draft a response to a customer. The customer's message: [PASTE IT VERBATIM]. My product and what they bought: [CONTEXT]. My actual policy on this: [WHAT YOU CAN DO — REFUND, REPLACE, EXPLAIN, ESCALATE]. My tone: [YOUR VOICE — E.G. DIRECT, WARM, NO-BS]. What I cannot do: [BE HONEST — OR "NOTHING"]. Write the reply (under 150 words): acknowledge their specific situation first (name the details), tell them what I can do in plain words, handle the emotional register (apologize where I'm actually at fault, don't grovel where I'm not), and end with one clear next step. If their request goes beyond policy, offer the closest honest alternative. Then give me a one-line version for a quick reply. ### O9. Draft a refund or complaint response that protects the business **When to use:** When a customer is unhappy and asking for money back or making a complaint. You are a fair-resolution writer. Draft my response to a complaint or refund request. The customer: [WHO, AND WHAT THEY BOUGHT, HOW LONG AGO]. Their complaint: [PASTE IT VERBATIM]. What happened from my side: [THE FACTS]. My refund policy: [WHAT IT SAYS]. What I'm willing to do: [YOUR REAL OPTIONS — REFUND, PARTIAL, REPLACE, EXCEPTION]. Write a response that: takes the complaint seriously without admitting fault I'm not sure of, separates facts from feelings respectfully, states what I'll do (specifically and plainly), and sets the boundary if the request exceeds policy — kindly but firmly. Give me two versions: one for when I'm willing to make an exception, one for when I hold the line. Rules: no "unfortunately" groveling, no legalese, no fake empathy. ### O10. Turn my scattered notes into a weekly review **When to use:** Friday. Feed your week's notes in and get clarity on what actually happened. You are a founder coach. Help me run a weekly review from my notes. My notes from this week: [PASTE YOUR NOTES — DONE LISTS, EMAILS, IDEAS, WINS, FAILURES, SCATTERED THOUGHTS]. My goals for the month: [WHAT YOU'RE AIMING AT]. Numbers I track: [ANY METRICS — REVENUE, USERS, CUSTOMERS, OR "NONE YET"]. Produce a one-page review: 1) What actually got done this week (sorted by importance, not recency). 2) What I said I'd do but didn't — and the honest reason for each. 3) The one win that mattered most and why. 4) The one thing that wasted the most time. 5) What the numbers say (or what I should start measuring). 6) Three priorities for next week, each with a "done by Friday" definition. Be honest with me — call out where I'm fooling myself. ### O11. Run an email triage and draft quick replies **When to use:** Every morning or when the inbox feels like a second job. You are my operations assistant. Triage my inbox. My emails (paste the important ones, each labeled): [EMAIL 1: SUBJECT/SENDER/BODY — EMAIL 2: …]. What I do: [YOUR BUSINESS]. My priorities this week: [YOUR TOP GOALS]. Which emails need a human reply from me specifically: [YOUR RULE, E.G. ANYTHING ABOUT MONEY OR LEGAL]. For each email, classify: [DO NOW — matters, quick], [SCHEDULE — matters, slow], [DELEGATE/DRAFT — I draft it, you review], [IGNORE — doesn't matter]. For the "draft" ones, write a reply I can review and send in under 2 minutes, in my voice ([DESCRIBE YOUR VOICE]). For the "ignore" ones, tell me why it's safe to skip. End with a 3-line summary of what needs my actual attention today. ### O12. Draft my daily standup plan **When to use:** Every morning. Turn yesterday's chaos into today's plan. You are a productivity coach. Help me plan my day. Yesterday's reality: [WHAT YOU ACTUALLY DID AND WHERE YOU LEFT THINGS]. Today's commitments: [CALLS, MEETINGS, DEADLINES]. My energy patterns: [WHEN YOU'RE SHARPEST — E.G. MORNING DEEP WORK, AFTERNOON SHALLOW]. My goals this week: [WHAT MUST HAPPEN BY FRIDAY]. What I'm avoiding: [BE HONEST — THE TASK YOU KEEP PUTTING OFF]. Produce: 1) The three tasks that actually matter today, in order, each with a "done means" definition and a time block on my calendar. 2) One small task to do when energy is low. 3) One sentence on the task I'm avoiding and the smallest possible first step I can take on it today. 4) What I will say no to today. Keep it under half a page — the plan should be executable, not inspiring. ### O13. Draft a vendor or tool comparison for a buying decision **When to use:** Before you pay for any software or service. Compare properly, once. You are a procurement analyst. Help me compare options for a purchase. What I need the tool/service to do: [THE JOB, NOT THE TOOL — WHAT PROBLEM IT SOLVES]. My constraints: [BUDGET, TIME, INTEGRATION NEEDS, SKILL LEVEL]. Options I'm considering: [LIST THE OPTIONS — OR "RECOMMEND 3"]. What I already know: [NOTES, PRICING, OPINIONS]. What I'm not willing to give up: [DEALBREAKERS]. Produce a comparison table: each option against the criteria that matter (price, the core job, ease of use, integration, support, hidden costs). Then a recommendation with the honest trade-off — what I give up by choosing it. Then the 3 questions I should ask each vendor before buying (including one about the annual price increase). Rules: no "best tool" language — it's about fit, and tell me if "do nothing" is a real option. ### O14. Draft a project plan from a one-paragraph goal **When to use:** Any project bigger than a day — launch, redesign, migration, campaign. You are a project manager for a one-person company. Turn my goal into a plan. The goal: [WHAT YOU WANT DONE, AND BY WHEN]. Why it matters: [THE BUSINESS REASON]. What I have: [RESOURCES, TOOLS, HELP, BUDGET]. What I don't know yet: [THE UNKNOWNS]. My constraints: [OTHER COMMITMENTS, SEASON, ENERGY]. Produce: 1) The outcome defined in one sentence ("done means…"). 2) The work broken into phases with 3-5 tasks each, ordered, each with a realistic time estimate — total must fit my actual week. 3) The dependencies and the one thing that will block me if I don't do it first. 4) What I can cut if time runs out (scope, not quality). 5) Checkpoints: the 3 dates when I check if I'm on track and what tells me I'm not. Keep it to one page. ### O15. Draft a customer onboarding message sequence **When to use:** After someone buys. Get them to the "aha" moment fast — that's what stops refunds. You are a customer-onboarding specialist. Write my onboarding sequence. My product: [WHAT THEY BOUGHT AND WHAT IT DOES]. The "aha" moment: [THE FIRST WIN A NEW CUSTOMER SHOULD GET — AND WHEN]. Typical struggle for new users: [WHERE PEOPLE GET STUCK]. My voice: [YOUR TONE]. Write a 4-message onboarding sequence (email or in-app): Message 1 (immediately) — confirm the purchase, set expectations, give the single most important first step. Message 2 (day 1) — get them to the aha moment with a 2-minute guide, remove the biggest friction. Message 3 (day 3) — the next valuable thing, plus where to get help. Message 4 (day 7) — check in, ask how it's going, offer support. Each under 150 words, each with a subject line, each with one clear action. Rules: no feature dumps — one action per message. ### O16. Draft the "house rules" for working with me **When to use:** When you hire help — contractors, assistants, or partners — and want to avoid the classic miscommunications. You are an operations writer. Draft my working-agreement document. Who it's for: [CONTRACTOR / ASSISTANT / CO-FOUNDER]. What we're working on together: [THE SCOPE]. My communication style: [E.G. SHORT EMAILS, NO MEETINGS UNLESS NEEDED, FAST REPLIES DURING WORK HOURS]. My boundaries: [HOURS, RESPONSE TIMES, WHAT I DON'T WANT TO BE ASKED]. What they can expect from me: [WHAT YOU COMMIT TO]. Write a friendly but clear document (under 400 words) covering: how we communicate (channels, response times, meeting policy), how work gets assigned and what "done" means, how feedback happens (fast, specific, no drama), what I decide vs. what they decide, and the honesty rule (surface problems early, no silent struggles). Title it something human like "How we work together." This document saves hours of friction. ### O17. Draft a risk register for my business **When to use:** Once a quarter. Five minutes of gloom now saves five weeks of panic later. You are a risk-management consultant for small businesses. Build my risk register. My business: [WHAT YOU DO, HOW YOU MAKE MONEY, WHO DEPENDS ON YOU]. My biggest worries: [WHAT KEEPS YOU UP AT NIGHT — BE HONEST]. My current protections: [INSURANCE, SAVINGS, CONTRACTS, DIVERSIFICATION — OR NONE]. My constraints: [TIME, MONEY, ENERGY TO ADDRESS RISKS]. Produce a table of the 8 biggest risks: Risk | Likelihood (low/med/high) | Impact (low/med/high) | What I'd do if it happened | One action to reduce it now (costing under [AMOUNT] or under [HOURS]). Rank by likelihood × impact. Rules: be realistic — the risk of being hit by a meteor is not on this list; the risk of losing your main client is. For the top 3, give me a 3-sentence mitigation plan each. ### O18. Define my KPI dashboard from scratch **When to use:** When you're flying blind on numbers. Pick the few that matter, not the many that don't. You are a metrics consultant for solo founders. Define my KPI dashboard. My business model: [HOW YOU MAKE MONEY — E.G. ONE-TIME PRODUCT, SUBSCRIPTION, SERVICES, ADS]. My stage: [E.G. PRE-REVENUE, FIRST 10 CUSTOMERS, PROFITABLE BUT STUCK]. My goals this quarter: [WHAT SUCCESS LOOKS LIKE]. Tools I use: [WHERE THE DATA LIVES — OR "NOWHERE, I TRACK BY HAND"]. Produce: 1) The 5 metrics that actually matter for my business model at my stage — not the 15 vanity ones. For each: what it measures, why it matters now, and the formula. 2) The one "north star" metric I should optimize. 3) The leading indicator I should watch weekly that predicts the lagging number I care about. 4) A dead-simple way to track them (a weekly 15-minute ritual — where the numbers go, what counts as good vs. warning). Rules: no metric without a decision attached to it. ### O19. Draft an offboarding or "end of engagement" checklist **When to use:** When a contractor, employee, or client relationship ends. End cleanly; reputations follow you. You are an operations consultant. Build my offboarding checklist. Who's leaving: [EMPLOYEE / CONTRACTOR / CLIENT]. The relationship: [LENGTH, NATURE, ANY OUTSTANDING ITEMS]. What must be handled: [ACCESS, PAYMENT, HANDOVER, NDA, REFERENCES, FILES]. The tone I want: [E.G. GRATEFUL, CLEAN, BUSINESSLIKE]. Produce a checklist in order: 1) The conversation/notice (what to say, what to ask). 2) The handover (access, files, passwords, in-progress work — with a "done means" definition). 3) The money (final payment, timeline, any clauses). 4) The paperwork (NDA, IP, references). 5) The goodbye (the message, the tone, the door left open if appropriate). Then draft the actual goodbye message (under 100 words). Rules: no drama, no passive-aggression, protect both sides. ### O20. Draft a knowledge-base article from a support conversation **When to use:** When you answer the same question twice — turn it into an article so you answer it zero more times. You are a technical writer. Turn a support conversation into a help article. The question customers keep asking: [THE QUESTION]. What I know about it: [THE ANSWER, THE STEPS, THE GOTCHAS — FROM YOUR EXPERIENCE]. Who asks it: [CUSTOMER TYPE AND SKILL LEVEL]. My product: [WHAT IT IS]. Write the article: a title that matches how customers actually phrase the question; a 2-sentence intro saying what this solves and for whom; the steps numbered, with exact labels and clicks, screenshots marked as [SCREENSHOT: DESCRIPTION]; a "if this doesn't work" section with the 2 most common failure points and fixes; and a "still stuck?" line pointing to support. Under 400 words. Rules: no jargon unless customers use it; write for someone in a hurry who is already slightly annoyed. ### O21. Draft a crisis communication plan (worst-case, in advance) **When to use:** Once, now, before anything goes wrong. You hope you never need it. You are a crisis-communications advisor. Build my crisis plan. My business: [WHAT YOU DO, WHO YOUR CUSTOMERS ARE]. My reputation risk areas: [WHERE A CRISIS COULD COME FROM — E.G. PRODUCT FAILURE, DATA ISSUE, PUBLIC MISTAKE, BAD REVIEW]. My values: [WHAT YOU WON'T COMPROMISE]. My channels: [WHERE YOU'D RESPOND — WEBSITE, EMAIL, SOCIAL]. Produce: 1) A one-page response protocol: who decides, the 60-minute response window for anything public, the rule for what gets said publicly vs. privately. 2) Draft holding statements for the 3 most likely crisis types from my risk areas — short, factual, no blame-shifting, no "no comment," promising a follow-up with a real timeline. 3) The 3 mistakes that make crises worse (delay, deny, delete) and my personal commitment to avoiding each. 4) One line on what I will not do: fabricate, deflect, or disappear. ## Part 5: Finance Most founders hate the numbers until the numbers bite them. These prompts turn AI into a patient analyst who explains, models, and drafts — but never touches your money directly. Always verify the math yourself; AI makes arithmetic errors. ### F1. Explain my monthly numbers like I'm smart (because I am) **When to use:** When you have your numbers and want to understand what they actually mean. You are a finance coach for founders who are not accountants. Explain my numbers. My business: [WHAT YOU DO AND HOW YOU MAKE MONEY]. My numbers for last month: [REVENUE, EXPENSES BY CATEGORY, PROFIT OR LOSS, CASH BALANCE]. My questions: [WHAT YOU DON'T UNDERSTAND — OR "EXPLAIN EVERYTHING"]. Do: 1) Explain in plain English what the numbers say — the story, not the spreadsheet. 2) Point out the 3 most important things I should notice (e.g. revenue up but profit flat — why?). 3) Identify anything that looks off or worth investigating (unusual ratios, surprising categories). 4) Tell me the one number I should watch next month. Rules: no jargon without a definition, no judgment — just clarity. Where you make assumptions about my situation, say so. And explicitly: if my numbers don't add up, tell me instead of smoothing over it. ### F2. Build a simple cash-flow forecast **When to use:** Monthly, or before any big spending decision. Cash is the business; profit is a story. You are a cash-flow analyst. Help me build a cash-flow forecast. My business: [WHAT YOU DO]. My current cash balance: [AMOUNT]. Expected income next 3 months: [LIST EXPECTED PAYMENTS — WHO, WHEN, AMOUNT, HOW CERTAIN]. Expected expenses next 3 months: [LIST — WHAT, WHEN, AMOUNT, ONE-TIME OR RECURRING]. Seasonal patterns: [ANY KNOWN — OR "NONE"]. Produce a month-by-month table for the next 3 months: opening balance, income, expenses, closing balance. Then: 1) The month where cash gets tightest and by how much. 2) The 3 assumptions that would break this forecast if wrong. 3) Two concrete moves I could make today to protect the tightest month (e.g. shift an invoice date, delay a purchase, collect faster). Rules: mark estimates as estimates; show the math so I can check it; if the numbers don't tie out, flag it. ### F3. Analyze my pricing against the market **When to use:** Before a price change, or when you suspect you're too cheap (you usually are). You are a pricing strategist for small businesses. Analyze my pricing. What I sell: [PRODUCT/SERVICE DESCRIPTION]. My current price: [PRICE AND STRUCTURE — ONE-TIME, SUBSCRIPTION, PER HOUR]. My costs to deliver: [DIRECT COSTS — OR "NEARLY ZERO, DIGITAL"]. Who buys: [CUSTOMER TYPE]. What alternatives they have: [COMPETITORS OR DIY — WITH THEIR PRICES IF KNOWN]. The value they get: [THE OUTCOME — IN THEIR TERMS, QUANTIFIED IF POSSIBLE]. Produce: 1) An honest read on where my price sits vs. the value delivered and the alternatives (underpriced / fairly priced / premium). 2) A recommended price or structure, with the reasoning and the risk. 3) What a small test looks like (e.g. raise price for new customers only, add a higher tier) and what metric tells me it worked. Rules: no "charge what you're worth" fluff — give me a number and a reason. Flag anything you're inferring as [INFERENCE]. ### F4. Work out my break-even numbers **When to use:** Before pricing, before hiring, before any fixed cost. Know the number you must hit. You are a break-even analyst. Work out my numbers. My business: [WHAT YOU SELL]. My fixed costs per month: [RENT, TOOLS, SALARY, ETC. — LIST THEM]. My variable costs per sale: [COST TO DELIVER ONE UNIT — OR "ZERO"]. My price per unit: [PRICE]. My goal: [E.G. FULL-TIME INCOME / JUST SURVIVE / HIT [AMOUNT] PROFIT]. Calculate: 1) Units per month to break even, and revenue per month at break-even. 2) Units per month to hit my goal (with the math shown). 3) How each lever moves the number: price up 20%, costs down 20%, conversion up 20% — which has the biggest effect? 4) The "danger zone" number: the monthly revenue below which I'm burning cash, and how many months I can survive there with [YOUR CASH RESERVE]. Show all math explicitly so I can check it. ### F5. Draft a simple budget for the next quarter **When to use:** Quarterly planning. Decide where money goes before it's gone. You are a budgeting analyst for solo founders. Build my quarterly budget. My business: [WHAT YOU DO]. Expected income next quarter: [MONTHLY ESTIMATES — BE HONEST]. My fixed costs: [RENT, TOOLS, SALARY, INSURANCE, ETC.]. My planned investments: [HIRING, ADS, EQUIPMENT, SOFTWARE — WHAT YOU WANT TO SPEND ON]. My priorities: [WHAT MATTERS MOST THIS QUARTER — E.G. REACH BREAK-EVEN, LAUNCH, HIRE]. Build a month-by-month budget table: income, fixed costs, planned investments, discretionary, profit/loss, closing cash. Then: 1) The month with the tightest cash and what to pre-arrange now. 2) What to cut first if income comes in 20% lower (in order, from painless to painful). 3) What to add if income comes in 20% higher (in order of ROI). 4) The 3 budget lines I should review weekly vs. monthly. Rules: no spending I can't afford — if the plan doesn't work, say so and tell me what to cut. ### F6. Reconcile overdue invoices across clients **When to use:** Every time an invoice goes past due. Money owed is money you've already worked for. You are a small-business finance operations analyst. Help me reconcile and track overdue invoices across clients so my books stay accurate while I chase payment. My open invoices (one line each): [CLIENT — INVOICE NUMBER — AMOUNT — ISSUE DATE — DUE DATE — DAYS OVERDUE — LAST CONTACT — PROMISED PAYMENT DATE]. My accounting system/status labels: [LABELS I USE]. My payment terms and late-fee rules: [TERMS — DO NOT INVENT ANY]. My desired cash-collection target this month: [AMOUNT]. Produce: 1) a clean aging table grouped into current, 1–30, 31–60, and 61+ days overdue; 2) totals by client and aging bucket, flagging any arithmetic or missing data; 3) a reconciliation checklist for matching invoices, payments, credits, and the ledger; 4) a prioritized chase list based on amount, age, and promised date; 5) one concise, professional next-step message per client, tailored to their status. Keep collections practical, but do not recommend writing off, charging, or escalating anything outside my stated policy. Mark assumptions clearly. ### F7. Review my expenses and find the waste **When to use:** Monthly, or when profit feels smaller than it should. You are a cost analyst. Review my expenses. My expenses last month (list them): [CATEGORY OR ITEM — AMOUNT — RECURRING OR ONE-TIME — WHAT IT'S FOR]. My revenue last month: [AMOUNT]. My business: [WHAT YOU DO]. My non-negotiables: [WHAT YOU WON'T CUT — E.G. HEALTH INSURANCE, KEY TOOL]. Do: 1) Sort expenses into Keep / Question / Cut, with a one-line reason each. 2) Flag the "silent leaks": subscriptions you might have forgotten, costs that grew, overlapping tools. 3) Show the top 3 expense categories as % of revenue and compare to a rough healthy benchmark for my business type (mark as rough guidance). 4) Give me 3 concrete savings worth more than [AMOUNT] this quarter, with the effort each takes. Rules: don't suggest cutting something that makes me money — flag anything that's an investment vs. a cost. ### F8. Draft a tax-prep checklist (and a 30-day plan) **When to use:** Before tax season, so it's a weekend of organization, not a week of panic. You are a tax preparer for small businesses (not legal advice — I'll confirm with a professional). Build my tax checklist. My business structure: [SOLE PROP / LLC / S-CORP / OTHER]. My income sources: [WHERE MONEY COMES FROM]. My likely deductions: [EXPENSE CATEGORIES YOU KNOW YOU HAVE]. What I have so far: [RECEIPTS? BOOKKEEPING? BANK STATEMENTS? OR "NOTHING ORGANIZED"]. Deadline: [TAX DEADLINE]. Produce: 1) A complete checklist of what I need to gather, organized into Income / Deductions / Records / Prior-year info. 2) A 30-day plan working backward from the deadline: what to do each week, in order (gather → categorize → calculate → review → file), with a time estimate per week. 3) The 3 most commonly missed deductions for my business type. 4) The 3 mistakes that trigger audits (as general guidance, not legal advice) and how to avoid each. 5) What to pay in estimated taxes next quarter based on [YOUR INCOME], with the math shown. ### F9. Draft the numbers section for a pitch deck or investor update **When to use:** When you're fundraising or reporting to investors. Numbers must be truthful and self-consistent. You are a fundraising analyst. Help me present my numbers. My business: [WHAT YOU DO]. My metrics: [REVENUE, USERS/CUSTOMERS, GROWTH, CHURN, MARGINS, CASH — WHATEVER YOU HAVE, WITH TIME PERIODS]. My stage: [WHAT YOU'VE DONE SO FAR]. What I'm raising (if applicable): [AMOUNT AND WHAT IT'S FOR]. My honest weak spots: [WHAT DOESN'T LOOK GREAT — BE HONEST]. Do: 1) Tell me the 3 metrics an investor would care most about for my business type and stage. 2) Draft the numbers slide or update in plain, defensible language — trend over single numbers, context over spin. 3) Help me frame the weak spots honestly: what to say, how to say it without hiding it, and the plan that addresses it. 4) List the 3 questions I should expect and rehearse answers to. Rules: zero inflated claims — if a number looks better with context, add context, never distortion. ### F10. Draft an investor update (the honest version) **When to use:** Monthly or quarterly, to the people who gave you money. Consistency builds trust. You are a founder-communication writer. Draft my investor update. The period: [MONTH/QUARTER]. What happened: [YOUR RAW NOTES — WINS, FAILURES, SHIPS, METRICS, DECISIONS]. My metrics: [KEY NUMBERS VS. LAST PERIOD]. What I need: [NOTHING / INTRODUCTIONS / ADVICE / MORE MONEY]. My tone: [YOUR VOICE]. Anything bad I should be upfront about: [THE HONEST LIST — OR "NOTHING"] . Write the update (under 500 words): a 3-line summary up top (the good, the bad, the ask); the numbers in a small table (last period → this period → trend); the 3 most important things that happened, explained briefly; the 1-2 failures, owned plainly with the lesson; the ask, if any, stated specifically; and a one-line "what's next." Rules: no burying bad news, no spin on metrics, no "we're excited to share" filler. ### F11. Stress-test my financial model's assumptions **When to use:** Before you trust a forecast, a raise, or a hiring decision. Assumptions are where models die. You are a financial-modeling reviewer. Stress-test my model. My model's assumptions: [LIST THEM — PRICE, CONVERSION, CHURN, COSTS, GROWTH RATE, TIMELINE]. Where the numbers came from: [REAL DATA / EDUCATED GUESS / WISHFUL THINKING — BE HONEST]. What the model concludes: [THE OUTPUT YOU'RE RELYING ON]. What decision this model supports: [THE DECISION]. Do: 1) Rank every assumption by (how uncertain it is) × (how much the conclusion depends on it) — that's the danger list. 2) Run the conclusion under three scenarios: base case (my numbers), pessimistic (each key assumption 20-30% worse), and upside. Show the math. 3) Tell me which single assumption, if wrong, would change the decision — and what evidence would confirm it cheaply within 30 days. 4) Tell me honestly if the model is too fragile to decide on at all. ### F12. Draft a payment-terms negotiation for a big client **When to use:** When a client wants to pay on terms that will starve you. Big clients have slow payment cultures. You are a commercial negotiator. Help me negotiate payment terms. The client: [WHO THEY ARE, HOW MUCH THE CONTRACT IS WORTH]. The terms they want: [E.G. NET 60 / PAY ON DELIVERY / MONTHLY INVOICING]. The terms I need: [YOUR POSITION AND WHY — CASH FLOW, COSTS, SIZE]. My leverage: [WHAT I HAVE — UNIQUE VALUE, REPLACEMENT COST, RARITY]. My walk-away: [WHAT I'D ACTUALLY DO INSTEAD]. Produce: 1) My opening position phrased as a win for them (never as my problem). 2) 3 concession options that cost me little but look generous (e.g. small early-payment discount, milestone billing, deposit plus final). 3) The script for the conversation: what to say when they push back, including the line that holds my walk-away gracefully. 4) What to put in the contract so terms are enforceable (as general guidance). Rules: no threats, no ultimatums I won't carry out — leverage only what's real. ### F13. Explain the difference between profit and cash — with my numbers **When to use:** When your bank account contradicts your spreadsheet. This is the single most common founder confusion. You are a finance teacher for founders. Teach me profit vs. cash using my numbers. My numbers: [REVENUE THIS MONTH, INVOICES SENT BUT UNPAID, EXPENSES INCURRED, EXPENSES PAID, CASH BALANCE, DEBT]. What's confusing me: [YOUR QUESTION — E.G. "WE MADE A PROFIT BUT THE BANK SAYS WE HAVE NO MONEY"]. Do: 1) Explain the difference in plain words with a concrete example from my actual numbers. 2) Rebuild my month on a cash basis (money in vs. money out) and on an accrual basis (earned vs. incurred) side by side — the gap is timing. 3) Point to the specific line items causing the gap in my case. 4) Give me 2 habits that keep the gap from surprising me (e.g. track cash separately, invoice faster, hold a cash buffer). Show every calculation. ### F14. Draft my pricing page copy (honest, clear, no tricks) **When to use:** When your pricing page needs words that make people feel safe, not tricked. You are a pricing-page copywriter. Write my pricing page. My plans: [LIST YOUR PLANS, PRICES, AND WHAT'S IN EACH]. My target customer: [WHO THEY ARE]. What to highlight: [THE HONEST DIFFERENCES BETWEEN PLANS — E.G. MORE PROMPTS, PRIORITY SUPPORT, COMMERCIAL LICENSE]. My guarantee or refund policy: [WHAT YOU ACTUALLY OFFER — OR "NONE"]. My FAQ: [THE QUESTIONS YOU GET — OR "NONE YET"]. Write: a heading (under 10 words), a one-line explanation of how pricing works (simple, no fine-print surprises), each plan presented with name, price, 4-6 specific bullets (features written as outcomes), the recommended plan marked with an honest reason, and a 3-question FAQ handling the real hesitations (e.g. what happens after I buy, refunds, support). Rules: no fake strike-through prices, no "limited time," no hidden fees — the page should survive being screenshot. ### F15. Draft a simple monthly finance review ritual **When to use:** Once a month, same day, same time. Thirty minutes that stop money fires. You are a finance habits coach. Design my monthly finance review. My business: [WHAT YOU DO]. My money situation: [REVENUE BALLPARK, EXPENSES BALLPARK, CASH, DEBT — ROUGH IS FINE]. My problem areas: [WHERE MONEY FEELS FUZZY — INVOICING, TAXES, PRICING, PLANNING]. My tools: [BOOKKEEPING / SPREADSHEET / NOTHING YET]. The day I'll commit to: [E.G. FIRST SATURDAY MORNING]. Design a 30-minute monthly review: 1) The 5 numbers to pull (and where to pull them from) — e.g. revenue, cash, unpaid invoices, expenses, profit. 2) The 3 questions to answer: What did the money do this month? What surprised me? What's the one thing to fix before next month? 3) The 3 standing actions that close the month (pay estimated tax if due, send any late invoices, update my forecast). 4) One 10-minute "money therapy" step — looking at the trend, not just the month. Keep it so simple it actually happens. ### F16. Draft the financial questions to ask before raising prices **When to use:** Before a price increase. Decide whether you're ready and how to announce it. You are a pricing-strategy coach. Prepare me to raise my prices. My current price and what's included: [CURRENT PRICING]. My costs and margins: [WHAT YOU KNOW]. My customer base: [HOW MANY, HOW DEPENDENT ON PRICE, HOW MUCH THEY VALUE YOU]. Why I want to raise prices: [THE HONEST REASON — COSTS, VALUE, SCALE, SELECTIVITY]. My fear: [WHAT SCARES YOU ABOUT IT — E.G. LOSING A KEY CUSTOMER]. Produce: 1) The 5 questions I must answer honestly before raising (e.g. what's the delta in value delivered since the last price? who is price-sensitive and can I afford to lose them?). 2) A recommended approach: amount, timing, and whether to grandfather existing customers — with the trade-off of each. 3) The announcement message (under 150 words) that states the change plainly, explains the reason, and gives existing customers the terms. 4) What to watch in the 60 days after — the metrics that tell me it worked. ### F17. Draft a "can I afford this?" analysis for one purchase **When to use:** Any purchase over [YOUR THRESHOLD]. Decide with math, not mood. You are a finance advisor. Help me decide if I can afford a purchase. The purchase: [WHAT IT IS, ONE-TIME OR RECURRING, COST]. My cash: [CURRENT BALANCE]. My monthly cash flow: [INCOME AND EXPENSES — ROUGH IS FINE]. My buffer requirement: [THE MINIMUM CASH YOU NEED TO SLEEP — OR "UNKNOWN"]. What I'm giving up by buying it: [THE OPPORTUNITY COST — OR "NOTHING"]. Do: 1) The math: what this does to my cash this month and my run-rate (months of survival at current burn). 2) The honest verdict: comfortably affordable / affordable with a plan / not affordable now. 3) If not now: the conditions under which it becomes affordable (what has to happen — e.g. 2 more clients, [AMOUNT] in cash). 4) The one alternative that achieves 80% of the benefit for less (if one exists). Show the arithmetic — I want to check it. ### F18. Draft my annual plan numbers **When to use:** Annual planning. Set a year that's ambitious but real. You are a financial planner for solo founders. Draft my annual numbers. My business: [WHAT YOU DO]. This year's reality: [REVENUE, PROFIT, CUSTOMERS, LESSONS — HONEST]. Next year's goals: [WHAT YOU WANT — INCOME, CUSTOMERS, NEW OFFERS, OR "SURVIVE AND LEARN"]. My constraints: [HOURS, ENERGY, CASH, FAMILY]. My planned changes: [PRICING, NEW PRODUCTS, HIRING, CHANNELS]. Produce: 1) A month-by-month revenue and cash projection for next year, built from my real numbers and planned changes — with the math shown. 2) The 3 levers that move the year most (price, volume, cost) and my target for each. 3) The quarter where I'm most at risk and what to pre-arrange. 4) The number that means the year is working vs. failing, checked quarterly. 5) One sentence on the difference between this plan and wishful thinking — the assumption that would break it. Rules: honest upside, honest downside. ### F19. Draft a salary/draw decision for myself **When to use:** When you're profitable and need to decide what to pay yourself — the decision founders avoid most. You are a personal-finance planner for founders. Help me decide my own pay. My business: [WHAT YOU DO]. Business cash flow: [MONTHLY REVENUE, EXPENSES, PROFIT]. Business needs: [WHAT THE BUSINESS MUST KEEP — RESERVES, TAXES, INVESTMENT, DEBT]. My personal needs: [WHAT YOU NEED TO LIVE — MONTHLY BARE MINIMUM AND COMFORTABLE NUMBER]. My situation: [SAVINGS, OTHER INCOME, FAMILY SITUATION]. Do: 1) The math: how much the business can sustainably pay me, month by month, while covering its obligations — show the calculation. 2) A recommendation: a regular draw amount (and whether monthly or quarterly) with the buffer it leaves. 3) The tax reality of my structure (as general guidance): what I should set aside for taxes on that draw. 4) The rule for when I can raise my draw (the trigger, e.g. 3 months of profit above X). 5) One honest reflection: if the sustainable number is below my needs, tell me the options (grow revenue, cut business costs, reduce personal spend, take the risk) without sugar-coating. ### F20. Draft a "why I'm cheaper than I should be" check **When to use:** When you suspect you undercharge but keep avoiding the change. Name the fear, then price. You are a pricing psychologist (and a straight talker). Help me look at my pricing honestly. My price: [WHAT YOU CHARGE]. What it costs me to deliver: [TIME, COSTS — ESTIMATE IN MONEY]. What the customer gets: [THE OUTCOME, AND WHAT THEY'D PAY AN ALTERNATIVE FOR IT]. My fears about raising: [BE HONEST — LOSING CLIENTS, FEELING GREEDY, NOBODY BUYING]. What I tell myself to keep prices low: [YOUR RATIONALIZATIONS — BE HONEST]. Do: 1) Show me the actual math of my effective hourly rate or margin. 2) Challenge each fear with a question I can answer with evidence, not feelings (e.g. "what's your evidence that clients would leave?"). 3) Give me the 3 real reasons underpriced products hurt customers (e.g. they don't take it seriously, you can't invest in quality, you burn out) — argued honestly, not as manipulation. 4) A 90-day plan to test a higher price with minimal risk. Rules: no fake confidence-boosting; if you think I'm priced fine, say so. ### F21. Draft a simple monthly "money dashboard" template **When to use:** Once, to set up the sheet you'll fill every month forever. You are a spreadsheet designer for founders. Build my money dashboard template. My business: [WHAT YOU DO]. What I want to see at a glance: [REVENUE, CASH, PROFIT, UNPAID INVOICES, TAX SET ASIDE — WHATEVER YOU CARE ABOUT]. My tool: [SPREADSHEET / NOTION / PAPER — WHATEVER YOU'LL ACTUALLY USE]. My skill level: [BASIC / COMFORTABLE WITH FORMULAS]. Build a one-page dashboard template: the rows and columns to set up, the formulas (written out so I can type them in), the 5-7 numbers to enter monthly, and a "traffic light" rule for each (green = healthy, amber = watch, red = act). Then the 3 charts worth making (e.g. revenue trend, cash trend, expenses by category) and why. Keep it to something I can set up in an hour and fill in 15 minutes a month. ## Part 6: Product Building a product solo means deciding what to build, building it, and learning whether it was right — all alone. These prompts cover discovery, prioritization, specs, testing, and the learning loop. ### P1. Draft a customer problem interview script **When to use:** Before you build anything. Five honest conversations beat five hundred guesses. You are a customer-research interviewer. Write my problem-interview script. What I think the problem is: [YOUR HYPOTHESIS ABOUT THE CUSTOMER'S PROBLEM]. Who I'm interviewing: [THE TYPE OF PERSON — THEIR ROLE, SITUATION]. What I'm testing: [WHAT YOU NEED TO LEARN — THE PROBLEM'S EXISTENCE, FREQUENCY, COST, CURRENT WORKAROUNDS]. What I must NOT do: [E.G. LEAD THE WITNESS, PITCH MY IDEA, ASK "WOULD YOU BUY THIS?"]. Write a 30-minute script: 1) Warm-up (3 min) — getting them talking about their world. 2) Story of last time (10 min) — walk through the last time they hit this problem: what happened, what they did, how they felt, what it cost. 3) Current workarounds (7 min) — what they use today, what's wrong with it, what they've tried. 4) Priority check (5 min) — how much this problem matters vs. their other problems. 5) Wrap (5 min) — the honest question: "what would need to be true for you to switch?" Rules: open questions only in the middle section, no leading, and one reminder to shut up and listen. ### P2. Draft a short survey for existing customers or users **When to use:** When you have a small audience and need signal fast. Keep it short enough that people finish it. You are a survey designer. Write my customer survey. What I need to learn: [THE DECISION THIS SURVEY INFORMS — E.G. WHAT TO BUILD NEXT, WHY THEY BOUGHT, WHY THEY LEFT]. Who I'm sending it to: [E.G. 40 EXISTING CUSTOMERS / 100 SUBSCRIBERS]. What I already know: [CONTEXT — SO THE SURVEY DOESN'T ASK WHAT I KNOW]. What I'll do with the answers: [HOW THE RESULT WILL BE USED]. Write a survey of max 8 questions: mix of one multiple-choice (the easy warm-up), 3 scaled questions (1-5) with clear anchors, 3 open-ended questions phrased to get stories, not adjectives ("tell me about the last time…" beats "how satisfied are you?"), and one demographic. Order matters: easy first, sensitive last. For each question, note what a useful answer looks like. Rules: no double-barreled questions, no leading questions, no asking what I can measure myself. ### P3. Turn interview notes into findings and decisions **When to use:** After 3-5 interviews. Stop hoarding notes — extract the decisions. You are a research analyst. Turn my raw interview notes into findings. My notes: [PASTE YOUR RAW NOTES — QUOTES, OBSERVATIONS, SURPRISES]. What I was testing: [THE HYPOTHESES]. Who I talked to: [THE PEOPLE AND THEIR CONTEXT]. Produce: 1) The 5 strongest findings, each with the evidence (quote or observation) and how many people said it. 2) The findings that contradict my hypothesis — the uncomfortable ones, listed first. 3) What I still don't know, and the cheapest way to learn it. 4) Three possible product directions ranked by (evidence of demand) × (ease for me to build) × (fit with my business). 5) The decision you'd make now: build, pivot, or research more — and what would change your mind. Rules: quote people verbatim where possible, never smooth over disagreement between interviewees. ### P4. Score my feature backlog with RICE **When to use:** When everything feels important and you can't build it all. Let the math argue for you. You are a product manager. Help me prioritize my backlog. My backlog: [LIST FEATURES WITH ONE LINE EACH — AND ANY EVIDENCE OF DEMAND YOU HAVE]. My constraints: [TIME, SKILLS, USERS, MONEY — WHAT LIMITS ME]. My strategic goal right now: [E.G. FIRST 10 CUSTOMERS / REDUCE CHURN / LAUNCH V2]. My users: [WHO THEY ARE AND HOW MANY]. For each feature: estimate Reach (users affected per period), Impact (0.25-3, with your definition), Confidence (0.5-1, honest), Effort (person-months, realistic for a solo dev). Score RICE = (Reach × Impact × Confidence) / Effort. Then: 1) The ranked list with scores. 2) The 3 I should build next, with the strategic case. 3) The 2 I should cut or postpone, and why — challenge me if I'm attached to a low-score feature. 4) One feature not on my list that my goal suggests I'm missing. Rules: confidence must be honest — mark guesses as guesses. ### P5. Draft a one-page PRD (product requirements doc) **When to use:** Before you build a feature bigger than a day. One page keeps you honest. You are a product manager. Write a one-page PRD. The feature: [WHAT IT IS AND WHO IT'S FOR]. The problem it solves: [THE USER PROBLEM — IN THEIR WORDS, NOT YOURS]. The goal: [WHAT SUCCESS LOOKS LIKE — THE METRIC]. Constraints: [TECH, TIME, BUDGET, DEADLINE]. What it must NOT do: [SCOPE GUARDRAILS — THE THINGS THIS FEATURE WON'T INCLUDE]. Open questions: [WHAT YOU HAVEN'T DECIDED — OR "NONE"]. Write the PRD: title and one-line summary; problem (2-3 sentences, user's perspective); goal and success metric; the core user flow in 5-8 steps (what the user does, what the system does); the requirements as a short bullet list (functional and any non-functional like speed); out of scope; open questions; and a 2-line "done means" definition. Rules: no jargon, no implementation details I can't judge, every requirement testable ("works fast" is not a requirement — "loads in under 2 seconds" is). ### P6. Turn a PRD into user stories and acceptance criteria **When to use:** When you're about to build and need the work broken into testable chunks. You are a product owner. Turn my PRD into user stories. My PRD or feature description: [PASTE YOUR PRD OR DESCRIBE THE FEATURE]. My users: [THE USER TYPES]. My stack or constraints: [ANY TECH OR PROCESS CONSTRAINTS — OR "NONE"]. Write user stories in the format "As a [user], I want [action], so that [outcome]" — one story per outcome, no compound stories. For each story: 3-6 acceptance criteria in "Given / When / Then" form, covering the happy path, one edge case, and one failure case. Then order the stories by dependency (what blocks what) and mark the "vertical slice" — the smallest set of stories that delivers something a user could actually try. Rules: no stories without acceptance criteria, no criteria that depend on my judgment ("looks good" is not a criterion). ### P7. Define my MVP scope by cutting, not adding **When to use:** When your "minimal" product is anything but. This prompt forces the cuts. You are an MVP coach who is brutally honest. Help me cut my MVP. My product vision: [WHAT YOU IMAGINE THE FULL PRODUCT BEING]. My proposed MVP features: [LIST THEM]. My deadline and constraints: [WHEN AND WITH WHAT RESOURCES]. The core promise: [THE ONE THING THE PRODUCT MUST DO FOR A CUSTOMER TO GET VALUE]. Who the first 10 customers are: [THE EARLY ADOPTERS YOU'D TARGET]. Do: 1) Classify each feature: Core (the promise can't exist without it) / Enhancer (nice, adds value) / Distraction (costs time, no first customer cares). 2) Propose the MVP: core features only, with a one-line argument per cut. 3) Check my MVP against the "would the first 10 customers get value from this? would they tell someone?" test — if no, cut more. 4) Tell me the risk of cutting too far (the MVP that's too thin to be useful) and the one feature I should NOT cut. Be blunt. ### P8. Draft a competitive analysis from real research **When to use:** Before building or positioning. Know what exists so you can be different for a reason. You are a competitive analyst. Build a competitive analysis. My product: [WHAT YOU'RE BUILDING AND FOR WHOM]. My competitors (real ones): [LIST THEM — INCLUDE THE DIY OPTION: "DO IT MANUALLY"]. What I know about each: [NOTES — PRICING, STRENGTHS, WEAKNESSES, AUDIENCE]. What I can verify: [ANY RESEARCH I'VE DONE — OR "NONE, THIS IS FROM MEMORY"]. Produce a table: Competitor | What they do | Who they serve | Price | Strengths | Weaknesses | Where I beat them | Where they beat me. Then: 1) The gap I can honestly own (not wishful — something I can actually deliver). 2) The risk: a competitor adding my differentiator cheaply — how likely and what I'd do. 3) One paragraph of positioning that's true today. 4) The 3 facts I should verify before relying on this (I may be wrong about a competitor). Rules: no strawmen — competitors get their due, especially the free option. ### P9. Draft a usability test script for my own product **When to use:** When you have something usable and want to watch a stranger try it. You'll learn more in 20 minutes than in 2 weeks of guessing. You are a usability-testing expert. Write my test script. My product: [WHAT IT IS AND THE CORE FLOW]. What I want to learn: [E.G. CAN NEW USERS COMPLETE THE SIGNUP? WHERE DO THEY GET STUCK?]. Who I'll test with: [E.G. 3 PEOPLE WHO FIT MY TARGET CUSTOMER — NOT FRIENDS]. The task: [THE ONE TASK I'LL ASK THEM TO DO]. What I must not do: [E.G. HELP THEM, EXPLAIN THE INTERFACE, GET DEFENSIVE]. Write a 20-minute script: 1) Setup (3 min) — the warm-up, what I tell them (this is testing the product, not them), and consent to record. 2) The task (10 min) — how I introduce it neutrally, the prompts I use when they get stuck ("what are you looking at now? what would you click next?"), and the rule about staying silent for the first 30 seconds of confusion. 3) Debrief (5 min) — the 3 questions that surface real reactions ("what surprised you? what would you change? would you use this?"). 4) What I record: the 3 things to note per participant (where they hesitated, what they said aloud, where they went wrong). Then the rule: 3 testers, fix the top 3 issues, test again. ### P10. Triage customer feedback into decisions **When to use:** Weekly, when feedback piles up. Turn a pile of opinions into a short list of actions. You are a product triage analyst. Help me process customer feedback. My feedback: [PASTE THE FEEDBACK — SUPPORT EMAILS, REVIEWS, SURVEY ANSWERS, CONVERSATIONS]. My product: [WHAT IT IS AND ITS CORE PROMISE]. My goals: [THE METRICS OR OUTCOMES YOU CARE ABOUT]. My constraints: [TIME, ROADMAP]. Do: 1) Group the feedback into themes, with a count and one representative quote each. 2) For each theme: is it a bug (fix now), a quick win (small change, big relief), a real feature (worth building — say why), or noise (one person's idea — why I can skip it)? 3) The 3 themes that matter most for my goals and the smallest change that addresses each. 4) What to reply to the people who gave feedback — one template each for "fixed," "planned," and "not now" (honest, not dismissive). Rules: frequency + goal fit beats loudness; one angry email is not a trend. ### P11. Draft a changelog or release note **When to use:** Every release, even small ones. It's your proof of momentum. You are a release-note writer. Write my changelog. The changes: [WHAT SHIPPED — FEATURES, FIXES, IMPROVEMENTS]. Who it's for: [USERS OR CUSTOMERS — WHAT THEY KNOW ABOUT THE PRODUCT]. My voice: [YOUR TONE — E.G. PLAIN, DRY, WARM]. The headline change: [THE ONE THING WORTH LEADING WITH — OR "NOTHING BIG, SMALL RELEASE"]. Write the changelog: a one-line version tag and date; a 2-sentence summary for the headline change (what it does, in user language, not tech language); the rest grouped as New / Improved / Fixed, each item one line written as the user's outcome ("You can now…", "We fixed an issue where…"); and a closing line on what's next (only if true). Rules: no marketing puff, no jokes that obscure meaning, bugs fixed listed plainly — users love seeing their reported issues in print. ### P12. Draft onboarding copy for my product **When to use:** When new users get lost. Onboarding is a feature — arguably the most important one. You are an onboarding UX writer. Write my product's onboarding. My product: [WHAT IT DOES AND THE CORE ACTION USERS MUST LEARN]. The first-time user: [WHO THEY ARE, THEIR SKILL LEVEL]. The "aha" moment: [THE FIRST WIN — THE MOMENT THEY GET THE POINT]. The most common failure point: [WHERE NEW USERS GET STUCK — FROM YOUR ANALYTICS OR SUPPORT]. My voice: [YOUR TONE]. Write the full onboarding: 1) The welcome screen: headline (under 8 words), subhead (one sentence: what this is + why it's worth their time), primary button label (verb-first, specific). 2) The 3-step quick-start (max 3 steps — each step one sentence, plain language, no jargon). 3) The empty state: what to show when there's no data yet — a helpful message, a sample, and one action. 4) The first-use checklist: 3 tasks that get them to the aha moment, with honest progress language ("2 of 3 done" beats "33% complete"). 5) One microcopy detail per step (button, tooltip, error message) that prevents the known failure point. Rules: fewer words than I think I need. ### P13. Draft a bug report triage and communication **When to use:** When something breaks. Separate "fix it now" from "fix it later" and tell users the truth. You are a support engineer with product judgment. Help me handle a bug. The bug: [WHAT BREAKS, HOW IT BREAKS, WHO'S AFFECTED, WHEN IT STARTED — AS BEST YOU KNOW]. My product: [WHAT IT IS]. My current status: [REPRODUCED? KNOWN CAUSE? FIX IN PROGRESS? OR "NO IDEA"]. My constraints: [TIME TO FIX, ALTERNATIVE WORKAROUNDS]. Do: 1) Classify severity: critical (blocks everyone / loses data), major (blocks some users), minor (annoyance), cosmetic — with a one-line argument each. 2) For critical/major: draft the user-facing message (email or in-app banner) that states what's broken, in plain terms, what I'm doing, and the honest timeline — plus a workaround if one exists. 3) For minor/cosmetic: draft the "known issue" note for the changelog or status page. 4) The post-fix note: what to say when it's resolved (thanks + what was wrong, briefly). Rules: no "we're aware" without a timeline, no technical jargon in user messages. ### P14. Run a metrics review and pick one experiment **When to use:** Weekly. One number, one experiment, one week. You are a growth analyst. Run a metrics review with me. My metrics this week vs. last: [REVENUE, USERS/CUSTOMERS, ACTIVATION, RETENTION, CHURN, ANYTHING YOU TRACK]. My product: [WHAT IT IS]. My goal: [THE ONE NUMBER YOU'RE TRYING TO MOVE]. What changed this week: [RELEASES, CAMPAIGNS, MARKETING, SEASON — OR "NOTHING"]. Do: 1) Read the tea leaves honestly: which metric moved, and which story fits the evidence (not the story I want). 2) Identify the metric that moved for an unknown reason — the thing worth investigating. 3) The one experiment for next week: hypothesis in "If I [change], then [metric] will [move], because [reason]" form, the smallest possible implementation, and the number that tells me it worked. 4) What to ignore this week so I don't chase noise. Rules: correlation ≠ causation — say it out loud; if there's not enough data to conclude anything, say that and tell me what to watch instead. ### P15. Design a pricing experiment (features and tiers) **When to use:** When you're considering new tiers, feature-gating, or price changes — test cheaply before committing. You are a pricing-strategy analyst. Design a pricing experiment. My product: [WHAT IT IS]. My current pricing: [YOUR STRUCTURE]. My customers: [WHO THEY ARE AND WHAT THEY VALUE]. What I want to test: [E.G. A HIGHER TIER / GATING A FEATURE / RAISING THE PRICE / A FREE TIER]. My constraints: [CUSTOMER BASE SIZE, TIME, RISK TOLERANCE]. Design the experiment: 1) The hypothesis (what change, what effect, measured how). 2) The test design: what changes, what stays the same, which customers see it (new vs. existing, cohort), and for how long. 3) The metrics: the primary number and the 2 guardrail numbers (e.g. don't just watch revenue — watch support load and refunds). 4) The decision rule: what result means keep / revert / iterate. 5) The biggest risk of the experiment and how to de-risk it. Rules: no testing on all customers if a cohort works; no changing two things at once. ### P16. Draft a "kill the feature" review **When to use:** When a feature isn't earning its keep. Dead features cost you time and confuse customers. You are a product portfolio analyst. Help me decide whether to kill a feature. The feature: [WHAT IT IS, WHEN IT SHIPPED]. Evidence of use: [USAGE DATA, SUPPORT REQUESTS, FEEDBACK — OR "I DON'T TRACK IT"]. Why I built it: [THE ORIGINAL REASON]. What it costs me: [BUILD TIME, MAINTENANCE, SUPPORT, COMPLEXITY, CONFUSION]. What I'm afraid of losing: [THE HONEST WORRY — E.G. A FEW LOYAL USERS, A FUTURE VISION]. Produce: 1) The honest verdict using evidence, not nostalgia: keep / fix / kill — with the threshold that separates "fix" from "kill" (e.g. fewer than X active users in 90 days). 2) What keeping it actually costs me per month (time × your rate, plus the support and confusion tax). 3) If kill: the 3-week plan (announce, migrate or grandfather the few users who care, remove, update docs) and the message to affected users (honest, offers the alternative). 4) If keep: what must change for it to earn its place. Rules: sunk cost is not a reason; two loyal users are not a business case. ### P17. Draft a user story for a piece of feedback **When to use:** When a customer asks for something and you want to capture it properly before it disappears into your head. You are a product manager. Turn this customer request into a properly captured item. The request (verbatim or close): [PASTE THE FEEDBACK]. The customer: [WHO THEY ARE, HOW LONG THEY'VE USED THE PRODUCT]. My product: [WHAT IT IS]. What I think they actually want: [THE OUTCOME BEHIND THE REQUEST — YOUR READ]. Produce: 1) The user story: "As a [user], I want [action], so that [outcome]" — rewrite their words into the underlying outcome, not their proposed solution (if they ask for a button, find the job the button does). 2) Acceptance criteria in Given/When/Then form (3-5, happy path + edge case). 3) The quick check: is this a one-user request (capture and deprioritize politely) or a pattern (worth a deeper look)? 4) The reply to the customer: what I'm doing with their request — even if "captured for the backlog, here's where it stands" — because silence is what makes users leave. ### P18. Announce a product publicly to a cold audience **When to use:** The day you ship something worth telling people about. You are a product communications writer. Draft a public announcement for people who may have never heard of me or my product. The product/feature: [WHAT IT IS AND WHAT IT DOES]. The new audience and their context: [WHO THEY ARE, WHAT THEY CURRENTLY DO, AND WHAT THEY DON'T KNOW YET]. The problem and why now: [THE PROBLEM IN THEIR WORDS AND WHY THIS RELEASE EXISTS]. Evidence: [REAL DEMO, DATA, CUSTOMER FEEDBACK, OR "NONE YET"]. The honest difference: [WHY THIS IS WORTH THEIR ATTENTION — NO HYPE]. Where I'm announcing: [PUBLIC BLOG / SOCIAL / COMMUNITY / ALL]. What I want people to do: [TRY IT / BUY IT / GIVE FEEDBACK]. Write: 1) a public article or post (under 300 words) that gives cold readers the context, problem, what/why, evidence, limitations, and ask; 2) a social version (under 120 words) that links to the full announcement; 3) a one-line status update. Rules: explain unfamiliar terms, use only the evidence supplied, no "game-changing," no exclamation marks, and say plainly if this is a small release or if evidence is still limited. ### P19. Draft my retrospective (I shipped something — what now?) **When to use:** After every launch or milestone. Close the loop while it's fresh. You are a launch retrospective facilitator. Run my post-launch review. What I shipped: [THE PRODUCT/FEATURE AND ITS SCOPE]. What happened: [RESULTS — USERS, REVENUE, FEEDBACK, BUGS, SUPPORT LOAD]. How it went vs. plan: [TIMELINE, EFFORT, STRESS — THE REALITY]. What surprised me: [THE UNEXPECTED — GOOD AND BAD]. Produce a one-page retrospective: 1) What worked (3 bullets, with evidence). 2) What didn't (3 bullets, with evidence — no blame, including on myself). 3) The one thing I'd do differently next time, stated as a specific process change (not a feeling). 4) The follow-ups: what this launch revealed I should fix, capture, or kill — with a priority order. 5) The honest verdict: was this worth it? What would have made it more worth it? Rules: learn from the outcome, don't relitigate it — and don't let a success hide the process problems. ### P20. Draft my "roadmap for one" — next 90 days of product work **When to use:** Quarterly product planning. A roadmap is a decision about what you will say no to. You are a product strategist for solo builders. Build my 90-day product plan. My product: [WHAT IT IS, WHERE IT IS NOW]. My users: [WHO THEY ARE, HOW MANY, WHAT THEY ASK FOR]. My goals: [THE BUSINESS OUTCOME — E.G. 100 PAYING USERS, LESS CHURN, A PRICE INCREASE]. My constraints: [HOURS PER WEEK, SKILLS, CASH, OTHER WORK]. What I must not break: [THE CORE PROMISE — WHAT USERS COUNT ON]. Build the plan: 1) The one goal the next 90 days serve, in one sentence. 2) The quarter split into 3 sprints of ~4 weeks, each with: the outcome, the 2-4 pieces of work, and the "done means" definition. 3) The 3 things I will say no to this quarter (name them — every yes hides a no). 4) The weekly cadence that keeps me honest (what I check, when). 5) The milestone that tells me by day 45 whether the plan is working or needs a change. Rules: the plan must fit my real hours, and the customer's voice must appear — quote one piece of real feedback that shaped it. ### P21. Draft a customer-development question bank **When to use:** Whenever you talk to a customer or user — have good questions ready so you never waste a conversation. You are a customer-development coach. Build my question bank. My product: [WHAT IT IS AND THE PROBLEM IT SOLVES]. My current stage: [E.G. IDEA / MVP / EARLY REVENUE / GROWING]. What I need to learn next: [THE KEY UNKNOWNS — E.G. WILL THEY PAY? WHY DO THEY CHURN? WHAT'S THE REAL JOB?]. Build a question bank organized by stage of the conversation: 1. Opening (5 questions): getting them talking about their world, their work, their goals — no product talk. 2. Problem deep-dive (6 questions): the last time, the frequency, the cost, the workarounds, what they've tried, what they'd pay to fix. 3. Solution testing (5 questions): how they'd use it, what would make it a must-have, what's missing, what would make them NOT use it. 4. Payment and priority (4 questions): budget reality, who decides, what they'd trade for it, the honest "would you buy today?" question and its follow-ups. 5. Closing (3 questions): who else I should talk to, what they'd tell a friend, permission to follow up. Rules: every question open-ended, none leading ("would you pay $X?" is fine as a direct question, not as "surely you'd pay for this, right?"). Mark the 5 questions you'd ask if you only had 10 minutes. --- ## A last word: the point of this pack None of these prompts are magic. They're structured starting points — the difference between staring at a blank page and editing a decent draft. The magic is still yours: your product, your customers, your judgment. The AI writes faster; you decide better. A few things worth remembering as you work through the pack: - **Use it badly at first.** Pick one prompt, skip half the brackets, see what comes out. Then go back and fill them all in. The difference will teach you more than any advice. - **Steal the structure.** After you've used a dozen of these, you'll see the skeleton. That's the real skill — role, context, task, format, constraints. Now you can write your own prompts for anything this pack doesn't cover. - **Keep the receipts.** The prompts that produce drafts you actually ship are the ones to keep. When you find them, mark them, and build your own shortlist. - **Stay honest.** The pack is built to help you build a real business. Real testimonials, real numbers, real promises. AI drafts the words; you own the truth. You're running a whole company with one person. That's hard. This pack won't change that — but it will take some of the weight off the typing. Now go sell something. — The Founder's AI Toolkit, v1.1