15 prompts
Find 50 directories, launch sites and listing platforms that fit our product: startup and SaaS directories, AI tool directories, category-specific listings, review sites, alternative-to sites, and regional startup lists. For each give the URL, whether it is free, whether the link is followed if you can tell, rough traffic or authority signals, and the submission requirements. Rank by fit and save to growth/directories.csv. Skip anything that looks like a spam link farm.
WebWrite our listing copy in every length directories ask for: a 60-character tagline, a 160-character short description, a 500-character description, a 1,500-character long description, 10 tags and categories, a feature list, pricing summary, and a founder comment. Base it on the real product in this repo. Save to growth/listing-copy.md so I can paste into any form.
RepoUsing growth/directories.csv and growth/listing-copy.md, open each free directory submission form in the browser and fill it in with our details. Stop before any step that needs payment, a captcha, email verification or creating an account with a password, and log those for me. Keep a log in growth/directories-log.csv with the status of each.
BrowserPrepare a full Product Hunt launch: tagline options, the description, the first maker comment, 5 gallery image ideas with captions, a 30-second demo video script, the topics to pick, a hunter shortlist with reasons, a launch-day timeline in Pacific time, and messages to send supporters (asking for feedback, not upvotes). Save to growth/launch/product-hunt.md.
WebWrite a Show HN post for our product following the community guidelines: a plain title that says what it is, a first comment that explains why we built it, how it works technically, what is free, and what we want feedback on. Read the top 10 Show HN posts of the last month to calibrate tone. Also list the 10 hardest questions HN will ask and draft honest answers. Save to growth/launch/show-hn.md.
WebFind 15 subreddits where our product is on-topic and self-promotion is allowed (read each subreddit's rules and note them). For each, draft a post that leads with something useful to that community, such as what we learned, a free resource, or a story, and mentions the product naturally. Note the best day and time to post. Save to growth/launch/reddit.md.
WebList every marketplace where our product could be listed: browser extension stores, app stores, Slack/Zapier/Shopify/WordPress/Figma/VS Code marketplaces, cloud marketplaces, GPT and AI agent stores, MCP and plugin directories. For each, describe what we would need to build or package to qualify and the effort. Rank by audience fit. Save to growth/marketplaces.md.
Web RepoWrite complete profiles for G2, Capterra, GetApp, Software Advice, TrustRadius, AlternativeTo, SaaSHub and Slashdot: categories, description, features, pricing, screenshots to upload, and the competitors to list against. Draft a short email asking happy users to leave a review on the one that matters most for us. Save to growth/review-sites.md.
WebIf our product uses AI in any way, find 40 AI tool directories and newsletters that list tools (There's An AI For That, Futurepedia, Toolify and the many smaller ones). Check which are free, which still accept submissions, and their categories. Save to growth/ai-directories.csv with the listing copy adapted to how each describes tools.
WebIf any part of our product is or could be open source (SDK, CLI, examples, templates), make the repo discoverable: a README with a clear one-liner, a GIF or screenshot, install in one command, badges, topics, a good social preview description, and a contributing guide. Draft the changes in this repo and list the topics and awesome lists to submit to.
RepoWrite our profile for Crunchbase, Wellfound (AngelList), LinkedIn company page, BetaList, F6S, Indie Hackers products and any regional startup databases. Include the fields each asks for. Save to growth/startup-profiles.md and flag fields that need a decision from me (funding, team size, founding date).
WebPlan a 2-week launch: which directories and communities to hit on which day so traffic is spread out, what to post on each social channel each day, the emails to send, and the follow-ups. Base it on growth/directories.csv and growth/launch/ if they exist. Save as growth/launch/calendar.md with a checklist I can tick off.
Run the app locally and take a clean set of screenshots for listings: the hero view, 4 key features, mobile view, and an empty-to-done flow, at the sizes directories commonly need (1270x760, 1920x1080, square 1080). Use realistic demo data, hide anything personal, and save them to growth/screenshots/ with a caption file.
Browser RepoSearch for every place we are already listed online. Check each listing for out-of-date descriptions, old pricing, broken links, old logos or wrong categories. List what needs updating and the exact new copy for each. Save to growth/listing-audit.md.
WebFind the Slack groups, Discord servers, Facebook groups, LinkedIn groups and forums where our buyers hang out and that have a "show your project" or tools channel. List them with the rules for promotion. Draft a short, non-spammy post for each that fits its culture. Save to growth/communities.md.
Web
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.
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.
Rewrite copy, audit the sign-up funnel, design A/B tests and build new landing pages. These prompts work directly in your codebase so the output is ready to review as a pull request.
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.