Our suggested starting prompt — not the author's original · untested
Source sponsored by Manus.
You'll need: A Manus account (credits; app building uses more). The exact prompts, hosting after the build and whether real data was moved over are not disclosed.
Build me a simple internal web app to track sponsorship deals, replacing my spreadsheet. Fields: sponsor name, contact, deal amount, payment status, deliverable, publish date and status. Use these status stages: [your stages, e.g. negotiating, confirmed, in production, scheduled, published, paid]. Give me a board view with drag-and-drop between stages and a table view. Start with 10 sample rows so I can test it. Don't import my real data or connect any accounts until I've reviewed it.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork via the Claude desktop app, plus criteria or a seed list of suppliers. Exact prompts and table columns are not disclosed.
I run a shared-office business and need a supplier outreach list. From [seed list, directory, or search criteria], find each supplier's website and the best contact or inquiry page. Build a table with columns: supplier name, website, contact page URL, email if visible on that page, notes, and source URL. Skip anyone you cannot verify. Do not contact anyone. Work in batches of about 200 and stop for my review between batches. Save the table to [file].
Our suggested starting prompt — not the author's original · untested
You'll need: Grok Bot; Amazon seller API access connected to the bot; Sellerboard (or similar) with cost-of-goods data and a bot user login; several months of sales/refund history. Exact thresholds, table columns, API setup details, and model are not disclosed.
Using my connected Amazon seller data and Sellerboard, look at the last 6 months for every ASIN. Build a table with units sold, revenue, refund count and refund rate, Amazon fees, cost of goods (from Sellerboard) and net profit. Flag ASINs with high sales but a high refund rate and little or no profit. Then check which flagged ASINs are back in stock or due for a reorder and, for each one, say whether it looks worth replenishing and why, showing the numbers. If cost data is missing for an ASIN, write 'unknown' instead of guessing. Don't place, change or cancel any orders, listings or shipments; this is a recommendation for me to review.
Have Claude Code pull inventory and sales data, project the next twelve months of sales and stock by product, and recommend when to reorder each one, using written notes on supplier lead times and holidays.
You'll need: Claude Code; sales and inventory data by SKU (the author pulled it from Amazon with scripts Claude Code wrote); written notes per brand covering supplier lead times, holiday closures, off-platform stock and past stockouts; an instruction file or command listing the projection steps. Not disclosed: The scripts' code and how the Amazon credentials were connected; the full text of the instruction file and per-brand context files; the number of brands and SKUs; how accurate the projections turned out against actual sales.
1. Check to see if the sales/inventory data we have locally is >5 days old, and if not, pull fresh data from Amazon.
2. Check the context notes for the brand it's working on.
3. Pull inventory and sales data from the local cache.
4. Display the trailing twelve month sales data by SKU and by month.
5. Describe any factors it's going to use to make adjustments to TTM sales data when projecting NTM sales.
6. Review its stated adjustment factors, then project NTM sales by SKU on a monthly basis, and display the amount of stock remaining at the end of each month based on those projections. Use Python for the math here.
7. Recommend when to reorder each SKU, factoring in CNY and other holidays.
Have Claude Code run a new client's standard first-week audits and draft a strategy brief with recommended priorities for you to review before the kickoff call.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Code; read access to the client's website and, for the analytics and CRM reviews, the client's Google Analytics/Tag Manager and email/CRM tools; a written audit checklist; a brief template; the owner's review before anything is sent
We're onboarding a new client: [client name], website [URL], industry [industry], main goal [goal] (from their intake form in [file]). Please prepare a first-week audit and a draft strategy brief for me to review. 1) Technical SEO: check the public site for crawlability, page titles and descriptions, broken links, page speed and mobile issues. 2) Analytics: from the export or read-only access I've given you [path/access], note whether Google Analytics and Tag Manager are set up and tracking key actions. 3) Competitors: for these competitors [list], compare the main keywords and topics they appear to target. 4) Email/CRM: from my notes [file], summarize their current setup and gaps. Save each audit as a separate file with findings, evidence and what you couldn't check. Then draft a one-to-two page strategy brief with the top 3–5 recommended priorities, each tied to the audit findings, and list open questions for the kickoff call. Keep everything as drafts in [folder]: don't send anything to the client, don't change any site, analytics or CRM settings, don't buy any tools and don't delete anything. Ask me before using any login or access I haven't listed.
Have Claude Code read the mailbox, turn manufacturer emails into service calls and draft the replies, with anything that has consequences waiting for the owner's approval on his phone.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Code access; a business system that holds service calls (the author built his own ERP) plus an MCP server or similar connection that lets the agent read the mailbox and create records in it; an approval step on your phone or desktop (the author uses Telegram with approve/reject buttons and a decision log); written procedures the agent must read before it writes anything (the author's company has about 1,500); your own review and approval of every service call and reply before it is created or sent
You help me run the office of my equipment service company. Check the mailbox [mailbox] for new emails from the manufacturers we service for [manufacturer names]. Before doing anything, read our written procedures for handling manufacturer requests [procedures file or folder]. For each email that asks for a service visit, prepare a draft service call (do not save it in [our job or service system] until I approve) with the customer site, machine model, fault reported, manufacturer reference and urgency, taken only from the email; mark anything missing or unclear instead of guessing. Then draft a reply to the manufacturer confirming what we understood and asking for any missing details. Put each draft service call and draft reply in my approval queue [where] with a one-line summary. Do not create, change or close any record, send any email, order parts, or delete anything; I will review and approve each one myself.
Have Claude run a client-onboarding skill that drafts the client's contract, creates their shared Slack channel, adds them to your client database, and prepares samples, website mockups and a podcast feed for your review, while you send the invites, grant access and write the client messages yourself.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude with skills (or saved instructions) describing your onboarding process; your internal docs, past contracts and the client's correspondence; access to your documents (for example Google Drive and Docs) and, if you let it do setup steps, to your team chat (the author used Slack via Claude's browser use) and client database; your own review of the contract, every account, channel or access change, and every client message. Building the skills was a one-off investment of about a day of the author's time, by his estimate.
Help me onboard a new client for my [type of service] business. Work in stages and stop for my approval at the end of each one.
Stage 0 (first time only): Read my internal docs and past client notes in [folder]. Write a short overview of what my business does and how it works, then draft a step-by-step client onboarding checklist. I'll correct it. Once I approve it, save it as reusable instructions I can run for future clients.
Stage 1, contract: Using the client emails and call notes I've attached and my past contracts in [folder], draft a service contract for [client] as a document. Look up their public details (legal name, registered address, registration number) and list where you found each one. Highlight anything that differs from my usual contract or that you're unsure about. Don't send it or upload it to a signing service. I'll review it and send it myself.
Stage 2, setup: List every channel, record and account this client needs (for example a shared [Slack] channel that follows my naming pattern, or an entry in my client database), and wait for my OK before you create each one. Don't invite the client, grant access, change permissions, or enter any password or payment details. Give me the invite link or the exact page to open, and I'll do those steps.
Stage 3, tailoring and samples: Review [the client's website or materials], list the special cases my service needs to handle for them, and propose a rule for each. After I approve the rules, prepare [sample deliverables] for me to check, and flag anything you're unsure about.
Stage 4, mockups and delivery setup: Make mockups of [how my deliverable would look on their website], using their public branding, and draft [the feed, page or other delivery setup] privately. Don't publish anything until I approve it.
Stage 5, client update: Don't write or send messages to the client. Give me a bullet list of points to cover in my update, then check my draft for clarity and for anything I've missed.
Finish with a checklist of what's done, what's waiting for my approval, and what I need to do myself.
Have Grok Bot build an estimate and job-cost tracker connected to QuickBooks, email and OneDrive, as the author says he did to replace his construction-management software.
Our suggested starting prompt — not the author's original · untested
You'll need: Grok Bot with access to your QuickBooks, email and OneDrive (the post does not say how it was connected); the estimate and job-cost categories your current software uses, ideally with a sample from one job; your own review of the tracker and of anything the bots prepare.
I want an estimate and job-cost tracker to replace [current software or spreadsheet]. Build it as a workbook saved in [OneDrive folder] with: an estimate sheet per job ([line items and cost codes]), a bills and actual-cost sheet per job, and a summary of budget against actual cost per job. Fill the cost data from QuickBooks ([company file]) and from bill emails in [mailbox or label], read-only: do not change anything in QuickBooks, send any email or delete anything. Match each bill to a job and cost code, and list the ones you cannot match, with the reason. First show me the structure and a sample for [one job] before you fill in the rest. For draws: when I ask, prepare the draw package for [job], draw number [n], using only invoices that were not in earlier draws, and list any issues from the last draw request. Save it as a draft and write a draft email to [bank contact]. Do not send anything to the bank; show me the package and the draft first.