15 prompts
For each lead in sales/leads.csv, research their company and the signal that made them a lead. Write a cold email under 100 words: a specific observation about them, the one problem we solve for companies like theirs, a proof point, and a low-effort ask. No flattery and no "I hope this finds you well". Add 2 follow-ups. Save to sales/outreach.csv with subject, body, follow-up 1 and follow-up 2 columns.
WebList the 20 objections prospects raise about products like ours (price, switching cost, security, "we built it ourselves", timing, a competitor). Use reviews, forums and our own docs as evidence. For each write a short, honest response, a proof point, and a question to ask back. Save to sales/objections.md.
WebWrite a one-page sales sheet for our product: the problem in the buyer's words, what we do, 3 outcomes with numbers where we have them, how it works in 3 steps, pricing, security and compliance notes, a customer quote, and a call to action. Make a markdown version and a print-ready HTML version. Save to sales/one-pager/.
RepoWrite a 15-minute demo script for a sales call: discovery questions for the first 3 minutes, a demo path that shows the "aha" moment within 5 minutes, the 3 features to show for each persona, how to handle the top questions mid-demo, and a close. Base it on the real product flows in this repo. Save to sales/demo-script.md.
RepoWrite a LinkedIn connection note (under 300 characters) and a 3-message follow-up sequence for each of our 3 personas. Each message should give something (an insight, a resource, a relevant post) before asking for anything. Save to sales/linkedin.md.
Draft a case study template and then a full example using what I can tell you or what is in our testimonials: the customer's situation before, why they chose us, how they rolled it out, results with numbers, and a quote. Also write the 10 interview questions to send a customer to collect this. Save to sales/case-study.md.
Read our pricing page and plans in this repo. List every question a buyer would have that the page does not answer (limits, overages, annual discount, cancellation, what counts as a seat, refunds, data export). Write the answers as an FAQ section and suggest any plan naming or layout changes. Save to sales/pricing-faq.md.
RepoRead this codebase and infra config and draft honest answers to a standard security questionnaire (data storage, encryption at rest and in transit, access controls, backups, logging, incident response, subprocessors, compliance). Mark every answer as "verified in code", "assumed" or "needs input". Save to sales/security-answers.md. Never claim certifications we do not have.
RepoWrite 6 follow-up email templates for after sales calls: no-reply after demo, needs to talk to the team, price concern, timing not right, went with a competitor, and trial started but inactive. Each under 120 words with one clear next step. Save to sales/follow-ups.md.
Design a referral program that fits our pricing and audience: who refers, what both sides get, how it is tracked, abuse rules, and the emails and in-app copy. Then outline the code changes this repo would need to support it. Save to sales/referrals.md.
RepoBuild a simple ROI model for our product: inputs a buyer knows (team size, hours spent, current tool cost), the savings we create, and payback period. Write it as a spreadsheet-ready table and as a short paragraph a champion can paste into an internal email to get budget. Save to sales/roi.md.
Write what an internal champion needs to sell our product to their boss: a 5-sentence summary, a comparison against doing nothing, risks and how we handle them, a rollout plan, cost, and a draft email to their manager. Save to sales/champion-pack.md.
For the top 10 leads in sales/leads-scored.csv, draft a short forwardable intro request: a note to a mutual connection plus a 3-sentence blurb they can forward as is. Save to sales/intros.md.
Review every sales and outreach email template in this repo or sales/ folder. Score each for clarity, length, personalisation, proof and call to action. Rewrite the weakest 5 and explain each change. Save to sales/email-teardown.md.
Write the 25 questions prospects ask before buying, with clear answers based on the actual product in this repo: setup time, integrations, data, support, contracts, migration, team plans. Add it to the site as a FAQ section with FAQPage structured data.
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.
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.