20 prompts
Read our homepage and product. Write 3 alternative versions of the hero (headline, subheadline, CTA, supporting line) based on different angles: outcome, pain, and audience. Then rewrite the full homepage in the strongest angle using voice-of-customer phrases from research/ if available. Make the change in a branch and save the alternatives to growth/homepage-copy.md.
RepoWalk through our funnel in the browser from homepage to paid: landing, pricing, sign-up, onboarding, upgrade. At each step list friction (extra fields, unclear copy, slow loads, distractions, missing trust signals) with screenshots, and score it. Give me the 15 highest-impact fixes ranked by impact and effort. Save to growth/cro-audit.md.
Browser RepoWrite 20 A/B test ideas for our site and app, each with the hypothesis, the change, the metric, the minimum sample size needed at our likely traffic, and expected impact. Rank them with ICE scores. Then implement the top one behind a feature flag if this repo has a flag system. Save to growth/ab-tests.md.
RepoUsing research/personas.md (or infer personas from the product), build a dedicated landing page for each persona in this codebase: their headline, their pains, the features they care about, a relevant proof point, and a CTA. Reuse existing components and set unique metadata for each.
RepoReview our pricing page against the best SaaS pricing pages. Propose a clearer structure: plan names, the recommended plan, feature comparison table, annual toggle, FAQ, guarantees and trust signals. Implement it in a branch using existing components, keeping current prices unless I said otherwise.
RepoFind every piece of social proof we have or could get: testimonials, logos, user counts, GitHub stars, reviews, press, case studies, awards. Then add the right proof next to each major decision point in the funnel (hero, pricing, sign-up). List what is missing and how to get it.
Repo WebFind every field and step in our sign-up and onboarding forms. For each, decide if it is needed now, can be asked later, or can be inferred. Remove or defer what is safe, add social sign-in if it exists in the stack, improve validation messages, and make sure the form works with password managers and autofill.
RepoDesign a few non-annoying ways to recover leaving visitors: an exit-intent offer on pricing, a "send me this later" email option, a lighter free plan or trial extension. Write the copy and implement the one that best fits our product, with a way to turn it off.
RepoFor each main feature, check whether we have a dedicated page. Write or improve each one: the problem it solves, how it works with a screenshot or GIF, a use case, a mini FAQ, and a CTA. Implement them in the codebase with unique metadata.
RepoReview every button, label, tooltip, placeholder and confirmation message in the app. Replace vague labels ("Submit", "OK", "Click here") with specific actions, make sure tone is consistent, and fix any truncated or awkward copy. Apply the changes and list them.
RepoFind where free users hit limits or would benefit from paid features. Design upgrade prompts that show up at those moments, explain the value in context, and never block work without warning. Implement them using existing UI patterns, and add events so we can measure them.
RepoWrite a trust page covering how we handle data, security practices, uptime, privacy, subprocessors and how to contact us about security, based on what the code and infra actually do. Add it to the site and link it from the footer, pricing and sign-up. Mark anything I need to confirm.
RepoMeasure the load time of our top 5 landing pages. Find the heaviest assets and scripts, defer non-critical third-party tags, compress images, and preload the hero. Report the before/after numbers and the changes.
Repo BrowserList 10 concrete use cases for our product from reviews, docs and support. For each build a page with a specific scenario, the workflow step by step, a template or example output, and a CTA. Target "[use case] tool" or "how to [use case]" keywords.
RepoMap what a trial user experiences from day 1 to the end of the trial: emails, in-app messages, limits and nudges. Find gaps where they get no help, and write the in-app messages and emails to fill them, each tied to a specific action that predicts conversion.
RepoWrite 50 headline variations for our homepage in 10 styles (outcome, how-to, question, number, contrarian, before/after, audience call-out, speed, comparison, story). Score each for clarity and specificity, and pick the 5 to test first. Save to growth/headlines.md.
Find every call to action across the site and app. Check they are consistent, specific about what happens next, visible above the fold where needed, and not competing with each other on the same screen. Fix the weak ones and output a table of changes.
RepoDesign a way for visitors to try the product without signing up: a read-only demo account, a sandbox with sample data, or an interactive tour. Outline the code changes, the risks (abuse, cost) and how to limit them, then build the simplest safe version in a branch.
RepoWrite an honest "us vs the old way vs alternatives" comparison block for the homepage that answers why someone should choose us. Keep it to 6 to 8 rows of things buyers care about. Implement it with existing components, responsive on mobile.
RepoCheck which funnel steps we track with analytics events in this codebase. Add missing events for each key step (viewed pricing, started sign-up, completed onboarding step, first key action, upgrade clicked) with consistent names and properties, and document them in docs/analytics-events.md.
Repo
How to run these while you sleep
- Open your project and start a fresh branch or git worktree, so the whole night is one diff you can review or delete.
- Add your product context above and keep overnight mode on. Claude will log its assumptions instead of waiting for answers.
- Paste one prompt into Claude Code, or save a few to a
queue/folder and loop over them headless. - In the morning, read the files it wrote and the diff. Merge what is good and send what needs sending yourself.
Want it off your laptop? Claude Code on the web runs each session in a cloud sandbox, so you can start a few before bed and close the lid.
Queue a night of prompts
git switch -c overnight/$(date +%F)
mkdir -p logs
for f in queue/*.md; do
claude -p "$(cat "$f")" \
--permission-mode acceptEdits \
--allowedTools "WebSearch" "WebFetch" "Bash(npm run *)" \
> "logs/$(basename "$f" .md).log"
doneOnly allow the tools a task needs. Browser prompts also need a browser MCP server such as Playwright; find one in the MCP directory.
More spare compute prompts
Free tools, calculators, templates and data pages that rank for long-tail searches and earn links on their own. Run these overnight and wake up to shippable pages.
Keyword research, content briefs, technical SEO audits and article drafts you can leave running overnight. Each prompt saves its output to a file so nothing gets lost.
Find link opportunities, draft pitches and build lists of podcasts, newsletters and journalists. These prompts do the slow research so you only do the sending.
Get listed everywhere your buyers look: startup directories, app stores, marketplaces, launch sites and review platforms. Claude prepares every listing so submitting takes minutes.
Lead lists, buying signals and the places your next customers are already asking for help. Claude does the digging; you decide who to contact.
Cold emails, follow-ups, sales pages and objection handling written from what your product actually does. Claude drafts; you review and send.
A month of posts, threads, carousels and replies drafted from your product, changelog and lessons learned. Wake up to a content queue instead of a blank page.
Demo videos, short-form scripts, animated explainers and screenshots generated with code. Use Remotion, Playwright and ffmpeg to render while you sleep.
Synthetic personas, simulated usability tests and interview prep built from your real product. Use them to find obvious problems before you spend time with real users, not instead of them.
Teardowns, pricing tracking, feature matrices and screenshots of competitor user flows. Leave a browser running overnight and come back to a full picture of the market.
Welcome sequences, onboarding emails, newsletters and re-engagement campaigns written from your actual product, plus the templates to send them.
Polish passes, onboarding fixes, feature specs and prototypes. Good for overnight runs because each one ends in a branch or a document you can review over coffee.
Tests, refactors, type safety, dependency upgrades and dead code removal. The classic overnight job: long, careful, and easy to review in the morning as a pull request.
Security reviews, secrets scans, load tests, bundle diets and backup checks. The work everyone puts off, done while your machine would otherwise sit idle.
Documentation, help centre articles, support macros, metrics, finance tidy-ups and the admin that piles up. Hand it to Claude when you have compute to spare.
Make Claude better at these jobs with skills, MCP servers and mods, or turn a prompt you run often into a skill with the skill generator.