20 prompts
From the product in this repo, define our ideal customer in one paragraph (company type, size, role, trigger). Then find 20 real companies or people who match, using public sources only. For each give the name, website, why they fit, the signal you found (a job post, a tweet, a forum question, a tech stack, a funding round), the best person to contact and a public way to reach them. Save to sales/leads.csv. Do not guess email addresses.
Web RepoSearch Reddit, Hacker News, Twitter/X, LinkedIn posts, Indie Hackers, Stack Overflow and niche forums from the last 60 days for people asking for a tool, recommendation or workaround for the problem we solve. List 30 threads with the link, date, what they asked, and a helpful reply draft that answers their question first and mentions us only if it truly fits. Save to sales/intent-threads.md.
WebLook at whatever customer data exists in this repo (seed data, analytics events, admin views, test fixtures, CRM exports) and the product's features. Write an ideal customer profile: firmographics, roles, the job they hire us for, triggers that make them look, objections, where they hang out, and words they use. Then write 3 anti-personas we should not chase. Save to sales/icp.md.
RepoSearch job boards for companies hiring for roles whose work our product automates or supports (for example a company hiring 3 support agents needs support tooling). Find 25 such companies posted in the last 30 days. For each list the role, link, company size, and a one-line reason we can help right now. Save to sales/hiring-signals.csv.
WebFind public complaints about our competitors: G2 and Capterra reviews of 3 stars or less, Reddit threads, tweets, app store reviews, GitHub issues. List 30 with the source, the specific pain, and whether we solve it. Summarise the 5 most common complaints and how we could speak to them. Save to sales/switchers.md. Do not contact anyone; this is research.
WebOur product works best with certain tools (check integrations and dependencies in this repo). Find 30 companies that publicly use those tools (case studies, "built with" pages, public job posts naming the stack, GitHub orgs). Note which tool, the evidence, and the company size. Save to sales/stack-leads.csv.
Web RepoList 30 online communities where our buyers talk shop: subreddits, Slack and Discord groups, forums, LinkedIn and Facebook groups, newsletters with comment sections. For each give the size, activity level, rules on promotion, and the 3 most common questions asked there recently. Save to sales/communities.md with a plan to be useful in the top 5.
WebFind 20 companies that announced funding in the last 90 days and fit our customer profile. For each list the round, date, what they do, and why new funding makes our product timely for them (hiring, scaling, new launch). Save to sales/funded.csv.
WebList 20 agencies, consultants, freelancers, educators, and complementary tools whose clients are our ideal customers. For each, explain the overlap, what a partnership could look like (referral, integration, bundle, co-marketing), and who to contact. Draft one partnership email I can adapt. Save to sales/partners.md.
WebLook through whatever user data, logs, analytics queries or database seed scripts this repo exposes and write the query that would find our most engaged users (usage frequency, features used, team size). Then draft a personal message to send each one asking for a 20-minute call, and the 8 questions to ask. Do not run anything against production; save the query and drafts to sales/power-users.md.
RepoSearch GitHub issues, discussions and READMEs for people struggling with the problem we solve (for example issues asking for a feature we have, or repos that hand-roll what we offer). List 25 with the link, what they are trying to do, and a helpful comment that solves their issue. Save to sales/github-signals.md. Do not post anything.
WebI will list our 3 best customers in sales/best-customers.md (or infer them from case studies on our site). For each, find 10 lookalike companies: same industry, size, model and stack. Explain the match for each. Save to sales/lookalikes.csv.
WebIf our product could serve local businesses, pick 3 cities and find 20 businesses in each that fit, using public listings. Note their website, what they currently use if visible, and an observation about their site or service that shows how we could help. Save to sales/local-leads.csv.
WebFind 40 people on Twitter/X and LinkedIn who are our ideal buyers or influence them, and who post regularly about the problem we solve. List their handle, follower range, what they post about, and 2 recent posts I could reply to with something useful. Save to sales/people-to-engage.md.
WebUsing sales/icp.md and the leads in sales/*.csv, design a simple 100-point lead scoring model: fit signals, intent signals, timing signals, each with points. Score every lead we have, sort them, and explain the top 10. Save the model to sales/scoring.md and the scored list to sales/leads-scored.csv.
Find 15 conferences, trade shows, meetups and webinars in the next 6 months where our buyers attend. For each give the date, location, cost, audience, and a cheap way to be present (attend and meet, speak, sponsor a small slot, host a side event). Save to sales/events.md.
WebFind places where people post projects or requests we could fulfil: public RFPs, government tenders, freelance job boards, "looking for a tool" posts and procurement portals in our niche. List 15 current opportunities with the deadline and requirements. Save to sales/opportunities.md.
WebWrite the query (do not run against production) that finds users who signed up but went inactive, grouped by where they stopped in onboarding. Draft a different win-back message for each group that addresses the likely reason, offers help, and asks one question. Save to sales/win-back.md.
RepoDesign a small free offer that gets ideal customers to talk to us: an audit, a teardown, a setup session, or a custom report. Write the landing page copy, the booking form questions, a deliverable template, and the follow-up email that leads into the product. Save to sales/free-offer.md.
Write a script that I can run each week to collect new buying signals from public sources (RSS feeds, subreddit searches, job board feeds, GitHub search) for our keywords, dedupe against sales/leads.csv, and write a short markdown report of new leads with links. Add instructions for scheduling it. Keep it within each site's terms.
Repo 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.
Get listed everywhere your buyers look: startup directories, app stores, marketplaces, launch sites and review platforms. Claude prepares every listing so submitting takes minutes.
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.