How to Roast Your Startup Idea Before Spending Money

On this page

1. Why your own idea is the hardest one to judge
2. What to examine: problem, customer, solution, business
3. Common startup idea mistakes a roast should catch
4. How to challenge your assumptions
5. How to get criticism that is actually useful
6. A worked example: roasting a meal-planning service
7. Turning criticism into real experiments
8. Your next step

A roast is a deliberate, structured attack on your own idea. The goal is not to talk yourself out of it, but to find the weak spots while they are still cheap to fix, before you pay a developer, order inventory or sign a lease.

This guide walks through why founders miss the flaws in their own ideas, what to examine, which mistakes come up again and again, and how to turn criticism into experiments you can run this month. There is a worked example near the end.

Why your own idea is the hardest one to judge

You are the person least qualified to evaluate your idea, simply because you have spent the most time imagining it working.

A few things get in the way:

• You fill in the gaps. When you picture a customer using your product, you supply the motivation, the budget and the free time. A stranger supplies none of those.
• You have already paid for it emotionally. Once you have told friends, bought a domain or sketched a logo, admitting a flaw feels like losing something.
• Your feedback is filtered. People who like you tend to say kind things. “That’s a great idea” usually means “I like you and don’t want to be rude.”
• You confuse your own problem with a market. Having a problem is a good starting point. It is not evidence that enough other people have it badly enough to pay.

A roast works because it forces you to argue the other side on purpose, with a fixed set of questions, instead of waiting for doubt to show up on its own.

What to examine: problem, customer, solution, business

Break the idea into four parts and judge each one separately. An idea can have a real problem and a weak solution, or a great solution aimed at people who will never pay.

The problem

• Can you describe the problem in one sentence without mentioning your solution?
• How does the person experience it today? What does it cost them in time, money, stress or missed opportunities?
• How often does it happen? A painful problem that comes up once every few years is hard to build a business on.

The customer

• Who exactly has this problem? “Small businesses” is not an answer. “Owners of one-location bakeries who do their own bookkeeping” is.
• Who pays, and is that the same person who uses it? Parents pay for kids’ apps; managers approve tools their teams use.
• Where can you actually reach these people?

The solution

• What are they doing instead right now? There is always an alternative, even if it is a spreadsheet, a phone call or doing nothing.
• Why would someone switch? “Better” is not enough. Switching costs effort, so the gain has to be obvious.
• What is the smallest version that would still solve the core problem?

The business

• Roughly what would someone pay, and how often?
• What does it cost you to deliver one unit, one month of service or one customer?
• How will the first hundred customers hear about you?

Common startup idea mistakes a roast should catch

These patterns show up across very different ideas:

1. A solution looking for a problem. The idea starts from a technology or a clever feature, and the problem is described vaguely afterwards.
2. “Everyone” as the target customer. If the idea is for everyone, the marketing reaches no one in particular.
3. Ignoring the “do nothing” option. Many problems are tolerated because living with them is easier than changing habits.
4. Underestimating trust. People hesitate to hand money, data, homes or children to a new, unknown company.
5. Assuming distribution will sort itself out. A good product nobody hears about is a hobby.
6. Pricing based on what you need, not what buyers value. Your costs set a floor; they say nothing about what a customer will accept.

How to challenge your assumptions

Every idea rests on statements you believe but have not proven. Write them down as plain sentences, for example: “Busy parents will plan meals a week ahead if it saves them money.”

Then, for each one, ask:

• What would have to be true for this to hold?
• What would I expect to see if it were false?
• How bad would it be if I am wrong?

The assumptions that are both uncertain and important deserve your attention first. If you want a deeper method for ranking them, the guide on identifying the riskiest assumptions in your startup idea covers that step in detail.

How to get criticism that is actually useful

General feedback (“looks good!”) is almost worthless. Useful criticism is specific, and you have to ask for it in a way that gives people permission to be blunt.

• Ask for the weakest part. “If this failed, what’s the most likely reason?” gets better answers than “What do you think?”
• Talk to people in the target group, not just people you know. A friend who never cooks cannot judge a meal-planning service.
• Ask about their past behavior, not your idea. “How did you plan dinners last week?” reveals more than “Would you use this?” The guide on writing customer discovery questions has examples.
• Separate the critic from the decision. Collect every point first, then decide what to act on later.
• Use an outside first pass. An AI roast or a structured checklist is useful precisely because it has no reason to be polite. Treat it as a list of questions to investigate, not a verdict.

A worked example: roasting a meal-planning service

Imagine you want to launch a paid weekly meal-planning service for busy parents. Each week, subscribers get a menu, a shopping list sorted by store aisle and quick recipes.

A roast might surface these points:

None of these kill the idea, but they do change it. Perhaps the sharper version is a plan built for families managing a specific food allergy, where free generic plans are a poor fit and the cost of a mistake is high. That version has a clearer customer, a stronger reason to pay and fewer direct alternatives.

Turning criticism into real experiments

A weakness you have written down is only useful if it leads to a test. For each important point, design the smallest experiment that would change your mind.

• “Parents won’t plan ahead.” Ask eight to ten parents in your target group how they decided what to eat last week. Look for people who already try to plan and struggle.
• “Free alternatives are good enough.” Ask people which free resources they have tried and why they stopped using them.
• “They won’t pay monthly.” Put up a simple page describing the offer with two pricing options and see which one people ask about or sign up for.

Write down, before you start, what result would make you continue, change direction or stop. Otherwise, it is easy to read any outcome as encouragement.

Once you have sharpened the idea, you can also see how a broad simulated audience reacts to it as a quick extra check before talking to real customers. The broader process is covered in how to test a business idea before you build it.

Your next step

Write your idea down in three or four sentences: who it is for, what problem it solves, how it works and what it costs. Then roast it, either with the questions above or with a free AI pass that lists weaknesses, open questions and one experiment to run. Pick the single riskiest point and test it with real people this week.

Written by the SellTo.us Team. Examples in this article are hypothetical. SellTo.us results come from AI-simulated participants, not real people, and don’t predict sales or guarantee success.