Stress-test a business idea before spending time on it
Have agents argue against a new business idea and recommend whether to reject it, park it, test it small or make it a task.
What the agent did
Source-reported example · as described by Jenna Brinning
A solo business owner adds ideas to an R&D area of her self-built dashboard, and her OpenClaw agents review each one from several specialist perspectives and argue against it. The outcome is a recommendation to reject, park, run a small experiment, or turn it into a task.
What the author reported
The author reports that the review documents the agents' discussion and outcome so ideas don't have to be reconsidered repeatedly. She says the agents challenge ideas; they don't make the decisions. No metrics are given.
Limitations
Part of a larger self-hosted setup the author built herself.
Try it in your business
What you'll need
An always-on OpenClaw installation and a place to record ideas and outcomes (the author built a custom dashboard). The prompts, model and agent setup for the review are not disclosed.
The original is a custom-built system. The prompt below is a simpler starting point and won’t reproduce it.
Starting prompt
The author didn't publish their prompt, so this is our adaptation.
How ours differs from the original setup: The original runs several agents inside a custom dashboard; ours asks one OpenClaw agent for three viewpoints and saves the result to your own notes.
Here's an idea I'm considering: [idea]. Review it from three viewpoints: a skeptical customer, a finance-minded advisor, and the person who would have to run it. List the strongest objections, the cheapest test I could run in a week, and your recommendation: drop, park, test, or do. Save the review to [notes location]. I make the final call.
Replace the [bracketed] parts with your own files and tools.
Get examples like this every Tuesday and Friday
Practical ways to put AI agents to work in your business. We check the original sources, explain the setup and point out the limits. Free.
Unsubscribe any time. Privacy policy
Related use cases
Summarize and file saved research and bookmarks
Turn a backlog of saved articles and bookmarks into short takeaways you can find again.
Our suggested starting prompt — not the author's original · untested
You'll need: An always-on OpenClaw installation, access to where you save research, a knowledge base app, scheduled jobs and an approval step. The model, prompts, cost and integration details are not disclosed.
Go through the articles and bookmarks I saved this week in [location]. Skip duplicates. For each, write a 2-line takeaway and a relevance score for my business ([one-line description]), and file it under a topic in [knowledge base]. Send me the top 3 worth reading in full.
Get scheduled trend and opportunity reports
Keep up with your field through short reports on what might be an opportunity or a risk.
Our suggested starting prompt — not the author's original · untested
You'll need: An always-on OpenClaw installation, scheduled jobs and a place for reports to land (the author uses her own dashboard). The sources monitored, model, prompts and cost are not disclosed.
Every Friday, scan news and posts about [my industry topics]. Ignore hype and repeats. Send me at most 5 items, each with what happened, why it might matter to my business, and whether it's an opportunity or a risk. Include links.
Turn manufacturer emails into service calls and draft replies for your approval
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.

