How Do I Know If My Business Idea Is Actually Viable?

An idea can be good and still not become a business

This is the first distinction that matters.

You can have a clever idea.

A useful idea.

An original idea.

Even an idea that people genuinely like.

And still not have a viable business.

Why?

Because a business has to do more than create something interesting.

It needs customers.

Those customers need a reason to act.

They need to be reachable.

They need to pay enough.

You need to be able to deliver what you promised.

And after all the costs are counted, something economically sensible needs to remain.

If one of those pieces breaks badly enough, the whole thing can fall apart.

That's why I don't ask:

Is this a good idea?

I ask:

Can this idea actually become a business?

Very different question.

Start with the customer, not the product

Entrepreneurs naturally fall in love with what they're building.

The app.

The service.

The product.

The platform.

The clever feature nobody has thought of.

Unfortunately, customers are rarely waiting around hoping somebody will build your feature.

They're busy dealing with their own problems.

So before obsessing over what you're going to build, ask:

Who is this for?

What are they trying to achieve?

What is frustrating them today?

What are they already doing instead?

How painful, expensive or annoying is the current situation?

And most importantly:

Is the problem important enough for them to do something about it?

A problem can be real and still not matter enough to create a business.

People tolerate irritating problems every day.

Sometimes fixing them isn't worth the money, effort or change in behaviour.

That's not a customer problem.

That's your business problem.

Understanding that customer properly takes more than a name and an age. I've written a practical guide on how to define your ideal customer, with a one-page map you can fill in.

Will they actually pay?

This is where a surprising amount of "validation" becomes theatre.

People ask:

"Would you use this?"

"Do you like this idea?"

"Would this be useful?"

And people say yes.

Of course they do.

It costs them nothing.

The useful question is closer to:

Would you exchange something valuable for this?

Usually money.

Sometimes time.

Sometimes effort.

Sometimes switching from an existing solution.

Because interest is cheap.

Commitment is more revealing.

Someone saying:

"That's a great idea."

is pleasant.

Someone saying:

"Where do I pay?"

is more interesting.

Can you actually reach enough customers?

This one kills good ideas quietly.

Suppose you've found a genuine problem.

Customers care.

They will pay.

Excellent.

Now:

Where are they?

Can you identify them?

Can you reach them?

How expensive is it?

How long does it take?

Can you do it repeatedly?

A business with willing customers you cannot economically reach is a very frustrating hobby.

This is why I care about reachability almost as much as demand.

The market may exist.

That doesn't mean you have practical access to it.

Does the math work?

Eventually the romance has to meet arithmetic.

How much will customers pay?

How often?

What does it cost to acquire them?

What does it cost to serve them?

What are your fixed costs?

How much margin remains?

You do not need a 52-page financial model.

I usually want the first version on something closer to a napkin.

If the basic math is ugly before we've even added reality, making the spreadsheet more sophisticated won't improve the business.

It will just make the bad news look professionally formatted.

This is why one of my favourite principles is:

If the math doesn't work on a napkin, it probably won't work in reality.

Look for evidence, not encouragement

This is where founders get themselves into trouble.

They ask people who want them to succeed.

Friends.

Family.

Colleagues.

Mentors who don't want to sound negative.

And increasingly, AI.

Then they collect encouragement and call it validation.

It isn't.

Useful evidence is behavioural.

Someone booked the call.

Someone joined the waitlist.

Someone introduced you to the decision-maker.

Someone agreed to a pilot.

Someone paid a deposit.

Someone bought.

Someone came back.

Someone referred another customer.

Those things are not perfect proof.

But they are much more useful than applause.

The stronger the commitment, the stronger the evidence.

You don't need certainty

This is important.

The objective of validation is not to eliminate risk.

You can't.

Entrepreneurship doesn't come with a certainty button.

The objective is to reduce the biggest unknowns enough to justify the next commitment.

Maybe the next commitment is ten customer conversations.

Maybe it is a landing page.

Maybe it is manually delivering the service before automating it.

Maybe it is a prototype.

Maybe it is asking someone to pay before building the expensive version.

The test should match the uncertainty.

You do not need to prove the entire business before moving.

You need enough evidence to earn the next step.

Test the dangerous assumptions first

Not all assumptions matter equally.

Suppose your business requires:

1,000 paying customers.

You can build the product.

You can deliver it.

The technology works.

But nobody has demonstrated that you can find those 1,000 customers at a sensible cost.

That's probably the dangerous assumption.

Test that before spending six months polishing the product.

Or perhaps customers clearly exist, but your entire model requires them to pay $500 and nobody will pay more than $75.

Again, dangerous assumption.

Or perhaps people will pay, but the service costs $600 to deliver.

That's not a marketing problem.

That's economics.

The smartest validation work attacks the assumptions that can kill the business first.

Be willing to change the idea

This is where validation becomes emotionally difficult.

People say they want validation.

What they often mean is:

Please confirm that the thing I already want to build is brilliant.

That's not validation.

That's reassurance.

Real validation may tell you:

Wrong customer.

Wrong problem.

Wrong price.

Wrong channel.

Wrong business model.

Wrong product.

Or occasionally:

Wrong idea.

Good.

That information is valuable.

The objective is not to prove the original idea correct.

The objective is to find the business.

Sometimes the real opportunity is sitting beside the idea you started with.

When should you kill the idea?

There isn't one universal rule.

But I become concerned when several things happen at once:

People understand the problem but don't care enough to act.

Customers like the idea but consistently refuse to pay.

The economics only work under heroic assumptions.

Acquiring customers appears prohibitively expensive.

The problem exists, but the market is too small for what the entrepreneur wants.

The business requires capabilities, capital or risk the founder does not realistically have.

The evidence keeps contradicting the story, and the only thing keeping the idea alive is the founder's attachment to it.

At that point, continuing is not perseverance.

Sometimes it's denial with a logo.

Killing an idea can be an excellent business decision.

What does "viable" actually mean?

For me, viability sits at the intersection of several things:

Customer

A clear enough group of people with something they care about.

Demand

A reason for those people to act.

Willingness to pay

Enough economic value for a transaction to make sense.

Reachability

A practical way to find enough customers.

Economics

Pricing, acquisition, delivery and costs that can work together.

Founder fit

A business the entrepreneur can realistically build and wants to live with.

Evidence

Real-world behaviour supporting the important assumptions.

You do not need all of this perfectly proven before starting.

But if too many of these are built entirely on hope, you don't have a viable business yet.

You have a hypothesis.

If you want to understand how these components—customer, offer, economics, delivery, and acquisition—connect into a coherent whole, I explain that separately in What Is Business Architecture.

A simple way to test your idea

Ask yourself:

Who is the customer?

What problem matters enough for them to act?

What are they doing today instead?

Why would they choose this?

Will they pay?

Can I reach enough of them?

Can the economics work?

What am I assuming?

What evidence do I actually have?

What is the cheapest next test?

And finally:

What evidence would make me change or kill this idea?

That last question matters.

Because if the answer is:

"Nothing."

you aren't validating the idea anymore.

You're defending it.

The simplest answer

So how do you know whether a business idea is viable?

You don't know because it sounds clever.

You don't know because people like it.

You don't know because ChatGPT tells you it has "strong market potential."

You know because enough evidence starts connecting:

a real customer, a meaningful problem, willingness to pay, practical reachability and economics that have a chance of working.

And until those things start appearing?

Don't fall in love yet.

The idea still has something to prove.