A Texas car detailing owner had Claude Code research rival ads and build a full Google Ads campaign; the data cost was $0.46.
Try it · based on the source's workflow
I run a [local business type] in [city]. Research the top rival Google search ads for [main service and location]. Check the live results. List the cost of each data tool before you call it. Then draft a search campaign with ad groups, ad headlines and descriptions, and a negative keyword list, with the search volume and cost per click behind each keyword. Save it as a [spreadsheet] I can review. Do not launch anything or spend money without showing me first.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
A freelancer built his own invoicing system in four hours and saves about 90 minutes a week.
Try it · based on the source's workflow
Build a simple invoicing system for my freelance work. Keep client data, line items, and payment status in [file]. Make a PDF invoice from [template] for [client] for [work and amount], due [date]. Email it to [client email] and record the send date. If it is unpaid after [14] days, draft a reminder and show it to me before sending.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
An auto repair shop agent drafts supplier and customer invoices, with a morning review by the owner.
Try it · based on the source's workflow
Open supplier invoice mail in [inbox]. Read each PDF, find or create the vendor in [accounting software], and save a draft with [amount and due date]. For finished work orders, draft a customer invoice with [labour and parts lines]. Save drafts only. Show me all drafts each morning for review before anything sends.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
An owner prompts Claude Code once. It finds the invoice details in his email and sends the invoice with the PO number.
Try it · based on the source's workflow
Check my email for the invoice details for [client]. Build the invoice in [accounting tool] with the PO number from the email. Draft the sending email with the invoice attached. Show me the draft and the invoice before you send anything. Send only after I approve.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
Three Claude Code sub-agents post about 2,047 vendor invoices a day. In week one, 94.3% went in with no human touch.
Try it · based on the source's workflow
Extract the structured data from each [invoice] PDF I name. Return one JSON object only, no prose and no markdown fences. Fields: vendor name, [tax ID], invoice number, invoice date, line items with [item codes], each tax line, and the total. If the [tax ID] is missing or fails its format check, return {"error": "invalid_tax_id"} instead. Show me any invoice you cannot read clearly before you post it anywhere.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
A Claude Code tool cut about 90% of lead noise before cold emails went out.
Try it · based on the source's workflow
Browse [source] for leads that match [my criteria]. Enrich each lead with public facts, score it against [my criteria], and find the decision maker. Cut any lead with no clear fit. Draft a cold email for each survivor and show me the full list and drafts before anything sends.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
Operations fell from about eight hours a week to about four after the rebuild.
Try it · based on the source's workflow
Review the codebase for [my business app] for security problems, scaling risks and broken checks. List each issue with where it is, how serious it is, and a fix I can approve before you change anything. Show me the list before you make any change.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
A bookkeeping pipeline did a month of books at 94.5% and flagged its own doubt.
Try it · based on the source's workflow
Build a bookkeeping check I can run again each month for [business name]. Pull this month's transactions from [accounting platform]. Match each bank row to a receipt or invoice by amount and date. Propose a category for every row, with a one-line reason for each. Flag every row you are unsure about, with the reason for your doubt. Never guess in silence on a flagged row. Give me the full list, the flagged rows first, and a count of rows matched, flagged, and unmatched. Do not change any record in [accounting platform]: show me the result for approval first.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
It corrected a tax payment, matched a lost payment, and stopped a double payment.
Try it · based on the source's workflow
Run the daily accounting check for [company name] across [ledger], [bank exports], and [finance inbox]. Work read-only. Match each incoming payment to an open invoice by amount and sender. List any payment you cannot match, with the evidence you checked. Before any payment run, check each supplier bill: the supplier is known, the amount is plausible, the bank details match [the public register or our records], and the bill is not already paid. Flag anything that fails a check and stop. Never move money, send a payment, or change a record. Give me a decision list: one line per item, the evidence, and the action you propose.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
A solo founder runs marketing for six SaaS projects on about $250 a month in tools.
Try it · based on the source's workflow
Run marketing for [project name] as a daily 30-minute session. First, pick today's single best action from [SEO data, keyword list, past results] and tell me why. Then draft the piece for that action in my voice, using these past posts as the style guide: [paste]. Open the draft for my approval and change nothing live until I approve it. Keep a log of each action, its cost, and its result. I send all outreach myself.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
15 scheduled agents produce 10 to 12 content pieces a week for one solopreneur's business.
Try it · based on the source's workflow
Run content for [business name] as a weekly loop. On [day], gather signals from [sources] and plan [5 to 7] long posts and one newsletter. Draft each piece in my voice from these examples: [paste], and put every draft on my calendar for review. Publish only the pieces I approve, then adapt each approved piece into short posts for [platforms]. Report each week: pieces published, time I spent reviewing, and the best piece by [metric]. If a step fails, tell me the same day; never fail in silence.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
An e-commerce founder's agent reads stock data and drafts orders, but writes nothing on day one.
Try it · based on the source's workflow
Work on inventory for [store name] in read-only mode. Read margins and stock from [system] and propose this week's ad budget and a reorder list, with the figures behind each line. Build the catalog draft from these supplier price lists: [files], and flag any product you cannot match. Draft purchase orders only; save them as drafts and change no live stock. Keep a log of every read and draft. I approve each stage before you get write access.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
A lawyer's clause review fell from four days of back-and-forth to about three hours; the tool caught 92% of clauses on the first pass.
The prompt · from the source
Read each contract in this folder. For each one, extract the assignment, change-of-control, exclusivity, non-compete, and termination clauses. Output a markdown table with deal name, clause type, clause text, and your analysis of whether the clause is standard or unusual. Flag anything you can't find in a clear list at the bottom.
A freelancer got tired of chasing late payers, so he built three small agents to do the awkward part for him.
Try it · based on the source's workflow
Chase overdue invoices for [business]. First, scan [invoice list] and rank each overdue invoice by amount and days late. Draft a reminder for each one: polite at [3] days, firm at [30] days, formal at [60] days, matched to [email, text, or WhatsApp]. Read each reply. If a client promises payment, pause reminders for that client for [48 hours]. Send nothing yet. Show me every draft for approval first, because one wrong detail can make a good client angry.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
A one-person resale shop gave an agent about 20 listings; it answered buyers in under 40 seconds and closed 27 orders in 15 days.
Try it · based on the source's workflow
Run my resale listings on [marketplace]. Check unread buyer messages every [interval] and sort each one: availability, price haggle, or product question. Reply in my tone using [templates] plus the listing title. You may cut a price by at most [percent] at a time, never below my floor price of [amount] per item, and at most [number] changes per item per day. Show me any message outside these rules before you send it.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
Five Claude Code agents ran an accessibility SaaS for a week, sent 241 emails, and got zero replies.
Try it · based on the source's workflow
Run a one-week outreach test for [business name] with a small agent team. The sales agent may send at most [number] personalised emails to [target list], and every message shows me as the sender and stops for my approval of the template first. The analytics agent reports daily: sent, delivered, bounced, replies, and reply rate against the [target] goal. If replies are zero after [50] sends, pause outreach and report why before any more sends.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
Agents run marketing, sales, and CRM for a one-person company.
Try it · based on the source's workflow
Set up one approval queue for [business name]. Every agent draft (outreach, posts, replies, proposals) goes into [queue] and nowhere else. Nothing sends without my tap. Each item shows: the draft, who it goes to, and what it asks for. Add a daily alarm if the queue holds more than [number] items or any item older than [days]. Send me one summary a day: sent, waiting, and failed.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
A UK founder runs four small businesses with Claude Code as his operator, working from a folder of notes.
Try it · based on the source's workflow
Read my notes vault map and yesterday's daily note. List what is open and overdue across [businesses], with the date and source of each item. Then draft replies for every quote I sent that has had no answer in [number] days, using my notes for context. Show me every draft before sending. When anything changes, append a checkpoint to today's note. Never send, post, spend, or sign anything without my plain yes.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
A Claude Code agent ran a newsletter's Meta ads alone for 31 days, testing about 50 variants and deciding every pause and scale call.
Try it · based on the source's workflow
Run a paid ads test for [my newsletter or product] with a total budget of [amount]. Each day, pull performance from [ads platform], review your past decisions and results, and propose what to create, pause or scale next, with the reason and the numbers behind it. Generate new ad variants in the formats that are already working. Show me the plan and any budget increase before you spend it, and keep a daily log of every decision and result so I can review it.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
One project manager now runs an 8-client agency on a Claude Code brain that writes copy, builds reports and onboards clients.
Try it · based on the source's workflow
Build a knowledge base for my [agency or business] in a project folder. Organize it into sections for [client briefs], [our processes], [templates] and [performance benchmarks], with one short index file that tells you which section to check for each kind of task. Then create reusable skills for [ad copy, client reporting, new client onboarding] that read only the section they need. Show me the folder structure and one finished example before you build the rest.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
Raw meeting notes dropped in a folder come back as summaries plus one action list grouped high, medium and low.
The prompt · from the source
Process all meeting notes in /meetings/raw from today:
1. Create clean summaries in /meetings/summaries
2. Extract ALL action items to /tasks/active.md
3. Group by priority: [HIGH], [MEDIUM], [LOW]
4. Include who owns what and deadlines
Use this priority framework:
- HIGH: Blocks someone else or has a hard deadline this week
- MEDIUM: Important but flexible timing
- LOW: Good to do but no immediate dependency
An agency delivered a $20,000 taxi-kiosk app in about a month on $200 of Claude Code.
Try it · based on the source's workflow
Build this client project with me: [project description and client requirements]. Break it into milestones, build the smallest working version of each one, and show me the result before moving on. Keep a list of every decision and open question for the client. Do not contact the client or deploy anything live until I approve each milestone.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
He cancelled ten subscriptions, built his own replacements, and kept only a handful of tools.
Try it · based on the source's workflow
List the software tools [business name] uses, grouped by the job each one does for us. For tools that do one simple job, tell me whether a small internal replacement could do that same job, and outline what building it would involve. Show me the list and your proposals first. Do not cancel, change, or build anything until I approve.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.