01. Before You Build It, Find Out If Anyone Wants It

You have an idea.

You can already see the product in your head. You may have thought of the name, bought the domain, started designing the website, spoken to a developer, or even started building the first version.

But there is a question that should come before all of that:

Does anyone actually want it?

An idea can be clever.

It can be technically impressive.

It can solve a real problem.

It can even have a large potential market.

None of those things, individually, make it a business.

Start with the problem, not the product

Founders naturally talk about what they are building.

Customers usually care about what they are trying to solve.

That difference matters.

Instead of asking:

Would you use my app?

ask:

How are you solving this problem today?

Then ask:

What is difficult about the current solution?

And:

What happens if you don’t solve it?

The answers tell you whether you have found an actual problem or simply an interesting concept.

The intensity of the problem matters

Not every problem deserves a business.

A problem can exist without being important enough for someone to change their behaviour.

Think about the difference between:

This would be nice to have.

and:

I need this solved.

The second is much more commercially interesting.

Look for problems involving:

• lost revenue

• wasted time

• operational inefficiency

• risk

• compliance

• customer loss

• expensive manual work

• poor experiences

• missed opportunities

• recurring frustration

The more meaningful the consequence, the more reason someone may have to act.

Interest is not demand

This is one of the easiest mistakes to make

Someone says:

That’s a great idea.

You feel validated.

But they haven’t bought anything.

They haven’t changed their behaviour.

They haven’t given you access to the problem.

They haven’t committed time.

They haven’t introduced you to the person who makes the decision.

They simply liked the idea.

Positive feedback is useful. Behaviour is stronger evidence.

Look for existing behaviour

One of the strongest signals is that people are already trying to solve the problem.

Maybe they use:

• spreadsheets

• WhatsApp

• email

• freelancers

• agencies

• internal employees

• outdated software

• multiple disconnected tools

That behaviour tells you something important:

The problem already exists inside someone’s life or business.

Your job is then to understand whether your solution is sufficiently better, easier, cheaper, faster or more valuable to make them change.

You don’t need to build everything

You can test a surprising amount before building the final product.

You can:

• sell the service manually

• create a prototype

• create a landing page

• run a small paid pilot

• manually deliver what the software will eventually automate

• speak to potential customers

• collect actual commitments

The objective is not to prove that your idea is brilliant.

It is to discover which assumptions are wrong before those assumptions become expensive.

The question I would ask

Don’t ask:

Is this a good idea?

Ask:

What would have to be true for this to become a good business?

Now you have something to investigate.

Customer.

Problem.

Market.

Offer.

Competition.

Pricing.

Distribution.

Economics.

Execution.

An idea is only the starting point.

Before you build it, find out if anyone wants it.

02. How to Validate a Business Idea Before Starting

Business idea validation is often treated as a simple process:

Have idea → ask people → build MVP → launch.

Real validation is more uncomfortable.

You are not trying to prove your idea is good.

You are trying to find out where it might be wrong.

Every idea contains assumptions

Suppose you want to build software for restaurants.

You may be assuming:

• restaurants have the problem

• the problem is important

• restaurant owners recognise the problem

• they currently spend money solving it

• your solution is better

• they will pay

• you can reach them

• you can deliver the product profitably

Those are eight different assumptions.

Your idea is only as strong as the assumptions underneath it.

Start with the riskiest assumption

Don’t spend two months proving that you can build the product if the biggest uncertainty is whether anyone will pay for it.

Ask:

What could make this business fail even if we execute the product perfectly?

That is where validation should begin.

Talk about the past, not the imagined future

Instead of asking:

Would you use this?

ask:

Tell me about the last time this happened.

Real experiences are much more useful than hypothetical answers.

You want to understand:

• what happened

• what they did

• what it cost

• what they tried

• what they disliked

• what they eventually chose

People are often optimistic about future behaviour.

Their existing behaviour is usually more informative.

Validation is evidence gathering

You are looking for signals.

Some signals are weak:

Sounds interesting.

I would definitely use that.

Some are stronger:

We have this problem every week.

We currently pay someone to do this.

Can I try it?

Can you show this to my team?

How much is it?

And stronger still:

We’ll pay for the pilot.

The point isn’t that one signal guarantees success.

It is that different behaviours carry different levels of evidence.

Validation should be allowed to change the idea

You might discover that the problem is real but your customer is wrong.

Or that the customer is right but the offer is wrong.

Or that people want the solution but won’t pay enough.

That isn’t failure.

That is validation doing its job.

03. How to Know If a Business Idea Is Worth Pursuing

A business idea does not need to be revolutionary.

Many successful businesses solve familiar problems better, faster, more conveniently or for a more specific customer.

The question is whether the idea deserves the next level of commitment.

Look at the problem

Is it real?

Is it frequent?

Is it painful?

Is it expensive?

Does someone already spend money or effort dealing with it?

A problem that occurs once every five years is very different from one that occurs every Monday.

Look at the customer

Can you identify the person or organisation that cares about the problem?

Everyone is not a customer segment.

A specific customer gives you something to investigate.

Look at willingness to pay

A customer can care about a problem and still not pay you to solve it.

Perhaps the problem isn’t important enough.

Perhaps they don’t have budget.

Perhaps the person experiencing the problem doesn’t control the purchase.

Perhaps the existing alternative is good enough.

Look at alternatives

Your competition isn’t just another startup.

It could be:

• doing nothing

• doing it internally

• using Excel

• hiring someone

• using an existing product

• continuing with an inefficient process

You are competing against the customer’s current behaviour, not just companies in your category.

Look at access

This is often overlooked.

You may have a good idea and a large market.

But can you reach the people who might buy?

A market is not automatically accessible just because it is large.

Look at economics

If every customer costs ₹10,000 to acquire and generates ₹5,000 in gross profit, growth doesn’t automatically fix the problem.

It can make it bigger.

You don’t need perfect numbers at the idea stage.

But you should understand the basic economics.

The decision

You don’t need to know:

Will this definitely work?

You need to know:

Is there enough evidence to justify the next experiment?

That is a much more useful decision.

04. How to Test a Business Idea Before Building It

Building is satisfying.

Testing is uncomfortable.

Building gives you something tangible.

Testing can tell you that the thing you want to build may not be worth building.

That is exactly why testing matters.

Identify your biggest uncertainty

Write down what you currently believe.

For example:

Independent clinics will pay ₹5,000 per month for appointment software.

That’s testable.

You can now investigate:

• Do independent clinics have the problem?

• How do they solve it today?

• Who makes the decision?

• What do they currently pay?

• What would make them switch?

• Is ₹5,000 meaningful relative to the value created?

Test the assumption, not the product

If the biggest question is willingness to pay, building ten more features doesn’t answer it.

If the biggest question is whether the customer has the problem, improving the UI doesn’t answer it.

Build the smallest experiment that can answer the biggest question.

Useful tests

You could:

• Interview — Understand the current behaviour.

• Prototype — Test whether people understand and value the proposed experience.

• Landing page — Test the proposition and response.

• Concierge service — Deliver manually what you eventually want to automate.

• Paid pilot — Ask someone to commit money before building everything.

• Pre-order — Test whether there is enough commitment to justify production.

Don’t confuse traffic with validation

A landing page getting 10,000 visitors isn’t automatically validation.

What matters is what happens next.

Do people enquire?

Do they sign up?

Do they book?

Do they pay?

Do they return?

Do they recommend it?

The closer the behaviour is to the actual business outcome, the more useful the signal.

05. How to Find Out If People Will Pay for Your Idea

One of the most important questions in business is also one of the simplest:

Will someone pay for this?

Not:

Do they like it?

Not:

Would they use it?

Not:

Does the market need it?

Will they pay?

Start with the current alternative

Ask:

How are you solving this today?

Then:

What does that cost you?

And:

What happens when the problem isn’t solved?

You are trying to understand the economic importance of the problem.

There is more than one kind of cost

A customer might not currently pay money.

But they may be paying with:

• employee time

• lost sales

• delays

• errors

• missed customers

• management attention

• operational complexity

That can still represent economic value.

Price is not just a number

Pricing changes the business.

A ₹500 product may require a completely different acquisition model from a ₹5 lakh product.

The buyer may be different.

The sales cycle may be different.

The level of trust required may be different.

The service expected may be different.

So don’t leave pricing until the very end.

The strongest test is commitment

At some point, ask for a commitment.

That could be:

• a paid pilot

• deposit

• pre-order

• subscription

• paid consultation

• signed agreement

The exact mechanism depends on the business.

But the principle is the same:

Ask the market to do something, not just say something.

06. How to Find the Right Market for Your Business Idea

Founders often begin market research with:

How big is the market?

That is useful.

But it is not enough.

Look for concentrated demand

Ask:

Where is this problem particularly painful?

A problem that affects 100,000 businesses mildly may be less commercially attractive than a problem affecting 10,000 businesses severely.

You want to understand where the need is concentrated.

Start with a beachhead

You don’t have to serve everyone immediately.

A focused initial market can help you learn faster.

You can understand:

• customer language

• buying behaviour

• objections

• pricing

• distribution

• competitors

• use cases

Once you understand why one group buys, expanding becomes more informed.

Market size is not market access

A founder might say:

There are 20 million potential customers.

The next question should be:

How will you reach them?

If reaching each customer is expensive or slow, the theoretical market size matters less.

Look at urgency

A market becomes more interesting when customers have a reason to act now.

That could be because of:

• changing technology

• regulation

• cost pressure

• customer expectations

• operational problems

• new opportunities

• competitive pressure

Timing can influence whether a market is merely interesting or commercially active.

07. How to Identify Your Target Customer for a New Business

If your answer to:

Who is this for?

is:

Everyone.

you probably haven’t defined the market yet.

Start with the person who feels the problem

Who experiences it?

Who cares about fixing it?

Who can afford it?

Who makes the decision?

These aren’t necessarily the same person.

User, buyer and decision maker

Consider a business software product.

The employee may use it.

The department head may want it.

Finance may approve the spending.

The founder may make the final decision.

If you don’t understand this structure, your marketing and sales can target the wrong person.

Look for the strongest customer

Your first customer doesn’t have to represent the entire market.

Look for the people with:

• the strongest problem

• the clearest need

• existing spending

• urgency

• ability to buy

• easy access

That group can teach you more than a broad audience.

Don’t build fictional personas

You don’t need a document saying:

Rahul, age 32, likes coffee and watches cricket.

That’s not necessarily useful.

You need to understand:

What is this person trying to accomplish?

What is getting in the way?

What do they do today?

What would make them change?

That is customer understanding.

08. How to Build a Business Model Around an Idea

A product can be useful and still be a bad business.

Because usefulness and commercial viability are different questions.

Understand the transaction

Who pays?

What are they paying for?

How often?

How much?

What makes them stay?

What does it cost you to deliver?

Revenue is not the same as business health

Revenue tells you how much money comes in.

It doesn’t tell you:

• how expensive growth is

• how much it costs to serve customers

• how much cash is required

• whether customers stay

• whether margins improve with scale

You need to understand the relationship between:

Revenue → Costs → Margin → Cash → Growth

Think about customer economics

Even simple estimates are useful.

What might one customer be worth?

What might it cost to acquire them?

How much does it cost to serve them?

How long might they stay?

If those assumptions don’t work at a small scale, scaling the business may not solve the underlying problem.

Business model affects positioning

A premium service, subscription software product, marketplace and transaction business can all solve similar problems while requiring completely different strategies.

The business model influences the offer.

The offer influences the positioning.

The positioning influences the communication.

That’s why business thinking should come before many visible brand decisions.

09. How to Find Your Unique Selling Proposition (USP)

Most businesses think they need a USP.

Then they write:

High-quality solutions for modern businesses.

It says almost nothing.

A useful USP starts with relevance

Ask:

What does the customer care about?

Then:

What can we credibly be known for?

Then:

Why does that matter compared with the alternatives?

The answer should give the customer a reason to consider you.

Difference isn’t automatically value

You can be different and still be irrelevant.

A feature nobody cares about isn’t differentiation.

A different colour isn’t differentiation.

A different slogan isn’t differentiation.

A meaningful difference changes the customer’s decision.

You don’t need to invent a new category

You could win by being:

• specialised

• easier

• faster

• more trusted

• more convenient

• more focused

• better integrated

• better suited to a particular customer

The question is:

What can we be chosen for?

Your USP needs evidence

If you claim:

The fastest.

prove it.

If you claim:

Built specifically for…

show how.

If you claim:

The most trusted.

customers need a reason to believe you.

A proposition without evidence is simply a claim.

10. Is Your Business Idea Actually Different?

Nobody else is doing this sounds exciting.

It can also be a warning.

Competition isn’t only direct competition

Your customer might currently:

• use another company

• do it themselves

• hire someone

• use software

• use spreadsheets

• use WhatsApp

• ignore the problem

Every one of those is an alternative.

Find the real decision

What would this customer do if my product didn’t exist?

Now you are looking at the actual competitive landscape.

A crowded market isn’t necessarily bad

Competition can tell you something useful.

It may mean:

• customers already understand the category

• money is already being spent

• the problem is established

• buying behaviour already exists

The challenge becomes:

Why you?

An empty market needs investigation too

If nobody is solving the problem, ask why.

Maybe nobody has noticed it.

Or perhaps the problem isn’t valuable enough.

Or perhaps the economics don’t work.

Or perhaps customers have already found an acceptable alternative.

Don’t assume the absence of competitors means the absence of risk.

11. MVP vs Business Validation: What Should You Test First?

MVP has become almost synonymous with startup validation.

They are related.

They are not the same.

An MVP is a product concept

An MVP generally helps you learn about a product by putting a minimum usable version in front of customers.

But business validation is broader.

You may need to test:

• Problem — Does it matter?

• Customer — Who cares?

• Solution — Does it solve the problem?

• Demand — Will people act?

• Pricing — Will they pay?

• Distribution — Can you reach them?

• Economics — Can the business work?

Sometimes your MVP shouldn’t be software

Imagine you want to create software that matches businesses with specialist consultants.

Before building a marketplace, you could manually make the matches.

If customers don’t value the matches, you have discovered the problem before spending heavily on technology.

The smallest useful test

The best first version isn’t always the smallest product.

It is the smallest experiment capable of answering your most important question.

That could be:

• a prototype

• a landing page

• a sales call

• a manual service

• a paid pilot

• a pre-order

Build when building helps you learn.

Don’t build because building feels like progress.

12. What to Test Before Launching a New Business

Before launch, founders often prepare everything visible.

The logo.

The website.

The product.

The social accounts.

The pitch deck.

The packaging.

And sometimes forget to test the business itself.

Test the problem

Does it matter enough to solve?

Test the customer

Who has the strongest need?

Test the offer

Can they understand what they are getting?

Test the price

Will someone commit money?

Test the position

Why should they choose you?

Test acquisition

Can you reach enough of the right customers?

Test sales

Can interest become commitment?

Test delivery

Can you actually deliver the promised value?

Test economics

Does each customer contribute to a sustainable business?

And test what you are most afraid to discover

This is often the most important part.

If you’re afraid people won’t pay, test payment.

If you’re afraid the market is too small, investigate the market.

If you’re afraid the product isn’t differentiated, test the alternatives.

Don’t spend your time proving things you already believe.

Try to disprove the business.

If it survives serious questioning, your confidence becomes more useful.

Launch is not validation

A launch is another test.

The market will tell you things your internal planning cannot.

Some assumptions will survive.

Others won’t.

That’s normal.

The stronger loop is:

Idea → Assumption → Test → Evidence → Learning → Change → Test again

Not:

Idea → Build → Launch → Hope

The goal isn’t to remove uncertainty.

It is to reduce the uncertainty that could become expensive later.