All articles

Articles in English

Choosing an idea

How do you choose when you have a few business ideas?

If you keep switching between ideas, try giving each one a small, fair test. A few real conversations and a clear offer can help you decide what to try next.

Three blue paper boats on separate winding tracks leading toward one orange flag, representing a fair comparison of business ideas
A PLACE TO START

Ask similar questions and offer a small, honest trial for each idea. Compare what people actually do before deciding where to spend more time.

You might have one idea saved in your phone, another you've talked about with a friend, and a third that keeps coming back whenever work gets frustrating. They all seem possible, but choosing one feels like giving up on the others too soon.

You can give yourself a little more information before deciding. Pick a few ideas, make each one specific, and try a small test of whether anyone needs what you're offering. There's no need to build three complete products to do that.

The plan below uses two weeks to keep the exercise manageable. That's an editorial suggestion, rather than a scientifically tested deadline. Some buyers take longer to reach, and some decisions need more time. You can adjust the schedule while keeping the basic idea of giving each option a fair look.

First, get clear about what each idea would actually do

For each idea, write a short description of the person you'd help, the problem they have, when it happens and how they deal with it today. Add what you'd offer and how you could reach someone who might buy it.

Try to make the descriptions equally specific. “Something with AI for shops” is hard to test. Preparing a weekly stock-order draft for an independent pet shop gives you a job and a person to ask about it.

You may find one idea needs a bit more thought before it belongs in the comparison. That's fine. Bring it down to a size where you could explain a first version in an ordinary conversation.

Also write down what might show that you're wrong. Perhaps the shops already have good stock software. Perhaps the task is annoying but only takes ten minutes a month. If every possible answer counts as encouraging, the test won't help you choose.

A September 2026 r/SaaS discussion included a founder who kept losing interest in ideas after wondering whether the problems mattered enough. Replies offered different approaches, with customer behavior and payment coming up repeatedly. It's a community conversation, not research proving a method, but it reflects a familiar difficulty when you're starting out. [1]

Spend the first few days asking about real situations

For roughly days one to four, find a small group of relevant people for each idea. Professional contacts, local businesses and focused communities can be useful starting points. Be honest about who you are and why you're asking. Generic messages sent to huge numbers of people are unlikely to give you the kind of detail you need.

Ask about the last time they did the job you're interested in. What started it? What did they do first? Where did they get stuck? Did a delay or mistake cause any real trouble? If they wanted to pay for help, who would need to agree?

Let them describe the experience before explaining your idea. People can be kind about something you've thought up without having much reason to use it themselves. A recent example gives you more to work with than a cheerful “sounds useful.”

Where it's appropriate, you could ask them to walk you through a form or spreadsheet with private details removed. Don't press for documents they can't share. An explanation of the steps can be enough to reveal where the hassle is.

Try to keep the questions similar for all your ideas. Otherwise, it's easy to ask gentle questions about your favorite and much harder ones about the rest.

Around the end of the first week, make a small offer

During days five to eight, turn each idea into something you could reasonably deliver now. Explain what the customer would give you, what they'd get back, how long it would take and what it would cost. If you're proposing a trial, say what the trial includes.

As hypothetical examples, you might offer to prepare one reviewed stock-order draft from a shop's records, or one attendance report for a training session. You could do some of the work by hand while learning what's needed. Be clear about the service people are signing up for.

Give the offers roughly the same amount of care. Comparing a polished website for one idea with a vague sentence about another won't tell you much about which has more promise.

A simple page or a clear written explanation is enough to start. Tell people what to do next and what will happen after they do it. Don't make it look as though a finished product or working checkout exists when it doesn't. You'll learn more from an honest offer than from numbers based on a misunderstanding.

Ask people to take a sensible next step

Use days nine to twelve to see whether interested people will make a specific commitment. What you ask for depends on the service. Someone might be ready to buy a small consumer product straight away. A business handling sensitive records may need a conversation and permission before it can even try your offer.

You could ask for a booked meeting, a sample they can appropriately share, or a paid trial. If you take a deposit, make the terms and refund conditions clear. The next step should match what you're genuinely ready to provide.

Keep a note of exactly what happened. A meeting tells you someone gave you time. A sample tells you they made an effort. A payment tells you they were willing to spend money on those terms. They all help you learn, but don't put them in one big column called “customers.”

Another September r/SaaS thread asked how experienced founders judge an idea before spending time on development. Like the first discussion, it shows people working through uncertainty. It doesn't establish that the advice in the replies is proven to work. [2]

Put the results somewhere you can compare them

A page for each idea is enough. Write down what you learned about the problem, how people currently manage it, what they agreed to do, how you found them and how hard the service would be to deliver. Include the main doubt you still have.

Keep simple counts too. How many relevant people did you contact? How many replied? How many took the next step? With small groups, one or two responses can change the picture a lot.

Take your relationships into account. Three interested people out of six friends isn't automatically a better result than five out of fifty strangers. Your friends may trust you already, or they may be trying to help. On the other hand, knowing a market well is a real advantage when you need to find your first buyers.

Both the level of interest and your ability to reach people matter. Write them down separately so you can see what you're choosing between.

Finish by deciding what deserves another try

Around days thirteen and fourteen, look for an idea with a problem people recognize, buyers you can reach, and a result you could deliver at a reasonable cost. You're deciding where to put your next bit of effort. You can change direction when you learn more.

If none of the offers got much interest, look through the conversations before throwing everything away. Did people keep mentioning a related problem you hadn't considered? That could give you a more useful version to try.

If two ideas still look promising, ask what would help you choose between them. Delivering one paid job might teach you more than another round of interviews. So might finding a customer outside your contacts or seeing whether someone wants to buy again.

By the end, you should have more than your original hunches. You'll have a few real experiences to compare and a clearer reason for giving one idea more time.

Sources and a few notes

We checked these sources on . The examples and suggested steps are our own unless we say otherwise.

  1. How do you validate ideas? (opens in a new tab)

    r/SaaS ·

    Founder discussion, not a controlled study. The two-week framework in this article is editorial guidance.

  2. Looking for advice from experienced SaaS founders (opens in a new tab)

    r/SaaS ·

    Community questions about validation and first customers. No claim that the advice is empirically proven.