Should We Bother?
Test an idea before you commit to it: is the problem worth solving, what must be true, and what to try first.
Use this when you are excited about an idea, or someone has brought you one, and you want a straight answer before spending money on it.
Fill in your details and we’ll drop them in. It happens in your browser, and nothing you type is sent to us.
The prompt, explained
The boring details, for anyone interested in the engineering behind the prompt. If you just want to get on with it, here you go.
What it asks the AI to do
Before I commit time or money to an idea, find out whether the problem behind it is worth solving, what has to be true for it to work, whether there is a simpler way, and the cheapest useful way to test it.
The actual wording, line by line. Yes, we dressed it up as code.
- 1
Language and tone
SharedKeeps the answer clear, positive and understandable. It prevents the AI from hiding simple ideas behind jargon or presenting useful criticism as a fault-finding exercise.
language-and-tone1Write in clear, unambiguous, plain English.
2Assume the reader runs a business and may have no specialist knowledge of marketing, websites, search engines, analytics or social media.
3Do not use jargon when an ordinary word or short phrase will do.
4If a technical or specialist term is genuinely necessary, use the term, explain it immediately in plain English and say why it matters here. Explaining a term needs no source; add a reference only if you have opened one that genuinely helps the reader.
5Keep the framing positive, balanced and constructive.
6Where something genuinely is working, say so before describing the issue or risk that remains. Never invent a positive.
7Do not soften a serious issue so much that it becomes unclear.
8The aim is to reduce ambiguity and create clarity.
- 2
Facts you cannot confirm
SharedWhat an AI remembers about laws, rules, prices and products can be out of date or simply wrong. So anything your advice depends on is either checked, with the source named, or comes back as a question to check and who can answer it, never as a fact from memory.
working-without-the-web1Laws, regulations, official guidance, prices and what a product or service can do change over time and are easily misremembered. Do not state them as fact from memory.
2Claims about what is normal, usual or common, or about how customers, markets, lenders or suppliers generally behave, count too: state them as fact only if my details support them. Words like often, many or most do not change that.
3If you can search the web, check them and name the source you opened. If you cannot, or did not, add them to a final list headed To check before acting. Phrase each item as a question and say who could answer it, such as the regulator, an accountant, an insurer or the supplier. Do not comment on your own web access or tools in general.
4The list is only for outside facts like these. Questions that only I, my staff or my customers can answer belong under the heading they relate to, not in this list.
5Never give a link or name a source you have not opened in this conversation. Where another instruction asks for a reference, say where to look instead.
6Leave the list out if nothing needs checking.
- 3
Understand the idea and why I want it
An idea can only be judged against what it is for. A hobby project and a business need very different answers.
understand-the-idea1My idea is the last item under My details. Work out why I want to pursue it, and judge it against that. Learning, enjoyment and doing some good are real reasons, not just making money.
2Keep what I said apart from your interpretation of it.
- 4
Look at the problem before the solution
Most ideas that fail had a solution looking for a problem. Pulling the two apart shows whether the problem is real and big enough to matter.
problem-first1Describe the underlying problem separately from my proposed solution. Ask who has it, how often, how much it costs them in time, money or frustration, and what happens if nobody solves it.
2Separate demand you can see, such as people paying, asking or complaining, from demand that is assumed.
3An interesting thing to build is not the same as something people will pay for. Say so where it applies.
- 5
Be fair to what people do now
People always do something today, even if it is nothing. The idea has to beat that, not an empty field. And an AI must never make up rival products to sound well-informed.
what-people-do-now1Consider what the people with the problem do today: existing products or services, workarounds, their own processes, or simply living with it. Judge whether my idea offers a real advantage over these.
2Name a specific product or company only if I named it or you have checked it. Never invent its features or prices. Otherwise describe the kinds of alternative that exist and say what to look into.
- 6
Look for a simpler way
The same outcome can often be had for a fraction of the effort. Building software is rarely the cheapest way to find out whether an idea works.
simpler-way1Consider whether the same outcome could come from a smaller version, an existing tool, a service done by hand, a spreadsheet or simple process, a rough prototype, or a different approach altogether. Do not assume the answer is to build software.
2Think about what it would take to run, not just to start: the skills, the dependencies, the ongoing work and costs. Do not invent timelines or costs; say what information would allow an estimate.
3Keep the advice within what I could put in: [MY TIME AND MONEY].
- 7
Judge the evidence, not the excitement
Neither cheerleading nor knocking ideas down helps anyone decide. An unproven idea is not a failed one; it is one that needs testing.
evidence-not-excitement1Challenge claims about market size or income that have no figures behind them. Do not invent research, customer quotes or financial projections.
2A lack of evidence is not evidence the idea will fail. Where something is unknown, say whether it needs investigating or can reasonably be assumed for now.
3Look for a way to make it work before listing reasons it might not, and consider what I lose by not pursuing it.
- 8
Recommendation discipline
SharedPrevents the AI from defaulting to rebuilds, subscriptions or fashionable tools when a smaller change would solve the problem.
recommendation-discipline1Prefer simple, realistic improvements over large projects.
2Fix or improve what already exists before recommending replacement.
3Do not recommend a paid product, subscription, redesign, rebuild or new platform simply because one exists.
4Keep recommendations proportionate to the business and the evidence found.
5Do not create an exhaustive improvement list when a smaller set of meaningful actions will do.
- 9
How to set out your answer
Eight headings that end in one small experiment and a clear verdict, so you finish with a next step rather than an opinion.
answer-layout1Use these headings, in this order: The idea in plain English; Is this a problem worth solving?; What are people doing today?; What must be true?; Is there a simpler way?; What would it actually take?; The cheapest useful experiment; Should we bother? Then, only if anything needs checking, To check before acting, with no more than five questions.
2The idea in plain English: the problem, who has it, the solution and the intended benefit, marking which parts are mine and which are your reading.
3What must be true?: the few assumptions that matter most, worst first. For each: why it matters, what evidence exists, what would prove it wrong, and how to test it.
4The cheapest useful experiment: one small test of the most important open assumption. Say what question it answers, what to make, show, research or ask, who takes part, what to record, and what would mean carry on, change direction or stop. Prefer what people do, such as signing up, paying or coming back, over what they say they like. No finished product needed.
5Should we bother?: one of Pursue, Test first, Simplify or change direction, or Park it, with the reasons, judged against this: [WHAT I WANT FROM IT]. It is a judgement, not a guarantee.
6Keep the whole answer under 1,000 words, and well under that for a small idea. No startup jargon and no pep talk.
- 10
Keep the answer in shape
SharedIn testing, answers ran up to twice their intended length, praised things nobody had mentioned and trailed off into caveats. These rules keep the answer to the length and shape it was designed for.
answer-shape1Start with the first heading: no title, introduction or summary above it. Put nothing after the last heading or list: no closing note, caveat or offer to do more. If a caveat matters, put it under the heading it belongs to.
2Treat the word limit this prompt sets as a ceiling, not a target: aim for about three-quarters of it. If the answer would run over, cut minor points and shorten lists before you reply.
3Where a heading asks for strengths, what is working or what is already in place, include only what my details actually show. If they show nothing, write None given.
4Give every field this prompt asks for, for every item, writing Unknown rather than leaving one out. Where it asks you to choose one rating or verdict from a list, choose exactly one, with no ranges or blends.
5Describe effort as small, moderate or larger. Never give effort or time in minutes, hours, days or evenings, even as an estimate, unless you have worked it out from my own figures.
6Mention instructions aimed at an AI only if my material contains some.
- 11
Limits of this particular prompt
The boundaries that apply to this prompt specifically, on top of the general research limits.
scope-notes1Do not write a business plan; this is about whether and how to take the next step.
2Do not discourage an idea just because it is unproven, or encourage one just because it is exciting.
3Do not suggest the experiment proves demand for certain; say what it does and does not show.
SharedSections marked shared are word for word the same in every prompt that uses them. The rules on tone, evidence, recommendations and limits are deliberately identical wherever you meet them, so you only have to learn them once, and no prompt can quietly hold itself to a lower standard than the others.
What it deliberately will not do
- Do not write a business plan; this is about whether and how to take the next step.
- Do not discourage an idea just because it is unproven, or encourage one just because it is exciting.
- Do not suggest the experiment proves demand for certain; say what it does and does not show.
Ready to use it?
Fill in your business details once and we will write them into the prompt, ready to copy or download.
Make this prompt yours