Market Size Triangulation: Top-Down vs Bottom-Up with Source Grading
Builds a transparent market size estimate from discoverable sources, compares top-down and bottom-up methods, and flags weak assumptions before a go or no-go call.
341 prompts · last added
56 results for “keep the room's real size” · page 1 of 3
Builds a transparent market size estimate from discoverable sources, compares top-down and bottom-up methods, and flags weak assumptions before a go or no-go call.
Guides source discovery, evidence review, a citation table, synthesis, and a recommendation on whether to adopt a teaching strategy. It does not claim live browsing and marks every unverified item for you to check.
Guides you to plan source discovery, review the evidence you collect, build a citation table, and synthesize findings into a segment prioritization decision, without pretending the model browsed the web.
Combines your Docs, Sheets, meeting notes, and outside sources into one decision memo. Separates internal evidence from external research and logs conflicts, gaps, and next actions.
Diagnoses what a price objection really means and builds response scripts, trade-based concession rules, and escalation criteria. It helps a rep decide whether to hold price, trade scope, or walk away.
Turn a crawl export and Search Console data into a scored, sprint-ready technical SEO fix list. It separates facts from assumptions and flags what needs verification before developers start work.
Builds a source discovery plan, evidence review, and citation table for a video's factual claims so a producer can decide which claims to keep, soften, or cut before scripting.
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then making small, reversible commits. Helps you decide whether the refactor preserved behavior and is worth merging.
Has Cursor lock in current behavior with characterization tests before restructuring a legacy module in small steps, so you can decide whether the refactor preserved behavior and is safe to merge.
Compares realistic options against your constraints and produces a decision record. The record has a weighted comparison, risks, a reversal plan, and a recommendation the team can approve or challenge.
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then applying small reversible steps with verification after each. Delivers a diff, risk register, and rollback plan.
Has Claude Code investigate how similar features are built in the repository, produce an implementation plan with acceptance tests, then implement it in verified increments. Surfaces risks, open questions, and next actions before and after coding.
Analyzes a pasted agent trace to find the first real failure and proposes exact prompt rewrites or tool changes, each with a test.
Analyzes a recurring manual task and produces an automation blueprint with trigger, steps, data mapping, error handling, and a test plan. It also helps you decide whether the task is worth automating at all.
Turns a pasted feature spec into independent coding-agent tasks with file ownership, interface contracts, a merge order and a done command for each task.
Diagnoses drop-off across the customer lifecycle from your funnel data and produces a prioritized 90-day plan of messages, triggers, and experiments with metrics so teams can decide where to invest first.
Turns an error report, stack trace, and logs into ranked root-cause hypotheses. Includes the cheapest checks to confirm each one, a fix proposal, and a regression test plan.
Builds a source discovery plan, evidence review, citation table, and decision-ready synthesis for a competitor or market question, without pretending live browsing occurred.
Gives codex exec a non-interactive procedure to diagnose a failing CI output, apply a minimal fix, rerun the checks and stop after three attempts with a clear report.
Designs a three-agent content pipeline where a researcher, writer and editor pass structured handoffs, with the exact fields each agent receives and returns and checks between stages.
Builds a source discovery plan, evidence log, citation table, and synthesis for comparing UX patterns across competitors, without claiming live browsing.
Turns an agent idea into a build-ready design: the job, the tools with their inputs and permissions, guardrails, failure handling and a set of evaluation cases to test it.
Turns a set of abstracts into a comparison matrix of methods, samples, findings and limits, then maps where studies agree, conflict and leave gaps for your review.
Writes a ready-to-deploy orchestrator system prompt that delegates to your workers, tracks progress in a ledger, merges results and stops on defined conditions.
Guide
Nothing that fits? Write a prompt with AI.
341 copy-ready prompts for productivity, writing, business and coding and more. Each one sets the role, the steps and the output format, and marks the parts you fill in with curly brackets.
Most are written for ChatGPT (285), Gemini (260), Claude (217) and Claude Code (42); the number is how many prompts list that tool. Each prompt page lists its tools, and most text prompts also work in any capable chat model.
Words in curly brackets, such as {audience}, are the parts you replace with your own details. Choose “Ready to use (no blanks)” in the filters to see prompts you can paste as they are.
By how often they are copied, unless you choose another order. Newest shows the latest additions first. Trending ranks prompts by copies, opens and saves over the last two weeks.
No. Every prompt is free to copy or open in your AI tool. A free account lets you save prompts to your vault.
Yes. Write with AI asks what you need, builds a short form for it, and writes the prompt as you fill it in.