I've had plenty of business ideas over the years. Some have been genuinely good, some have sounded brilliant at the time and considerably less brilliant a few weeks later, and some have made it far enough that I've had to stop talking about them and actually build something.
That's where things get interesting, because there's a massive difference between having an idea for a business and building a business. One happens in your head. The other happens in the real world, where customers don't behave as expected, assumptions turn out to be wrong, and enthusiasm doesn't pay the bills.
The idea is the easy part. Finding out whether it deserves to exist is where the work begins.
Nobody cares about your idea as much as you do
This is probably the first uncomfortable lesson of building a business. You've spent weeks thinking about an opportunity, imagining how the product will work, what the website will look like, how customers will use it and where the business could be in five years. You're excited, you've convinced yourself there's something genuinely valuable here, and you're ready to tell the world.
Then you tell someone about it. They say, "Sounds interesting," and that's about as far as the conversation goes. No questions, no follow-up and certainly no immediate desire to hand over their money. It's easy to interpret that as a failure to understand your vision, but the reality is usually much simpler. Your enthusiasm is not evidence of demand.
People are generally polite about business ideas. Friends and family are particularly good at telling you something sounds fantastic, but encouragement isn't validation. The questions that matter are much harder. Does someone actually have the problem you're trying to solve? Is it painful enough that they'll do something about it? And is your solution sufficiently better than what they're already doing?
Until you've answered those questions, you've got a hypothesis, not a business.
Stop protecting your idea from reality
One of the biggest traps founders fall into is spending too long developing an idea before exposing it to potential customers. It's understandable. Talking to customers is uncomfortable because they might tell you the problem isn't important, point out something you've completely overlooked or, worse, explain that they're perfectly happy with the way things are.
So instead, you work on the product. You improve the design, add another feature, refine the business model and build a more impressive presentation. All of these feel productive, and some may eventually be necessary, but none necessarily brings you closer to knowing whether someone will pay for what you're creating.
I've learned that you need to get comfortable having conversations before you've got all the answers. You don't need a finished product to ask someone how they currently solve a problem, and you don't need a polished website to understand what frustrates them. You certainly don't need to spend six months building something before discovering that your assumptions were wrong.
The earlier your idea meets reality, the cheaper your mistakes become.
That's not an argument for rushing out a terrible product. It's an argument for testing the assumptions that could kill your business before spending money on the things that make it look like a business.
A product isn't a business
You can build a fantastic product that nobody buys. You can have an elegant website, impressive technology and a genuinely clever solution. You can even have users who love it. But if you can't acquire customers, deliver value consistently and generate enough revenue to sustain the operation, you haven't yet built a viable business. You've built a product.
There's nothing wrong with that. Creating a product is an achievement in itself, but it's important to recognise the distinction. A product is something you've built. A business is an organisation capable of delivering value to customers in a way that can sustain itself.
When you're starting out, it's tempting to spend most of your time on the parts you enjoy. For a technical founder, that might be architecture, integrations or product features. For someone with a marketing background, it might be branding, messaging and campaigns. The problem is that businesses don't care what you enjoy doing. They require you to deal with whatever is currently preventing them from moving forward.
Sometimes that's product development. Sometimes it's sales. Sometimes it's a difficult conversation about pricing, cash flow or whether the entire proposition needs to change. Building a business means doing the important work, not just the interesting work.
Customers don't buy your vision. They buy a solution to their problem.
Founders spend a lot of time talking about their vision, and there's nothing inherently wrong with that. Vision gives a business direction, helps attract people and provides a reason to keep going when things get difficult. But customers rarely buy something because the founder has an exciting five-year plan.
They buy because they believe it will make their life easier, save them money, help them make money, reduce a risk or solve something that frustrates them. If your product doesn't address something they genuinely care about, your vision isn't going to convince them otherwise.
That's particularly important when selling to businesses. You might be presenting an innovative platform that could transform an industry, while the person across the table is thinking about their budget, their team's workload, existing systems, procurement processes and what happens if your solution doesn't work. They're not necessarily resistant to innovation. They're assessing risk, and that's a perfectly reasonable thing to do.
If you can't explain the value in terms that matter to them, it doesn't matter how impressive your technology is. This is something I keep coming back to when thinking about new businesses: don't start by asking how to sell your product. Start by understanding why someone would want to buy it.
Those sound like similar questions, but they're fundamentally different.
Raising money doesn't prove you've built a business
I've been involved in building a startup and raising seed capital. It's an experience that teaches you a lot, particularly about how differently investors and customers evaluate an opportunity. Raising money is difficult. It takes persistence, preparation and the ability to convince people that an opportunity is worth backing, often before the business has demonstrated everything you hope it eventually will.
When funding comes through, it's a significant milestone, and rightly so. But it's important not to confuse that milestone with the destination. Investment is fuel. It isn't proof that the engine works.
Investors can believe in a market, a team and a strategy before the business has demonstrated that it can operate profitably. That's part of the purpose of early-stage funding. The money gives you an opportunity to test, build, recruit and grow, but it also creates expectations, commitments and a finite amount of time to prove that the opportunity is real.
A funding announcement can look like success from the outside, while inside the business the work has often just become more demanding. The same goes for media attention, pitch competitions and impressive-looking partnerships. They can all be useful, but none replaces the need to build something customers genuinely value.
You need to know when to change your mind
There's a strange tension in entrepreneurship. You need enough conviction to pursue something when other people don't see the opportunity, but you also need enough humility to recognise when your original thinking was wrong. Too much conviction and you become stubborn. Too much flexibility and you never commit to anything long enough to make progress.
Getting that balance right is difficult, particularly when you've invested significant time, money and emotional energy into an idea. A founder can become so attached to a particular solution that every piece of negative feedback gets explained away. Customers don't understand it. The market isn't ready. The sales team isn't positioning it correctly. The product just needs one more feature.
Sometimes those explanations are valid, and sometimes they're excuses. The challenge is knowing the difference, which means being willing to look at evidence that contradicts what you want to believe.
Changing direction doesn't automatically mean you've failed. It might mean you've learned something important before running out of time or money. Equally, changing direction every time something gets difficult isn't strategy either. The goal isn't to defend your original idea. It's to build a business that works.
If the evidence tells you there's a better way to do that, you should be willing to listen.
Execution isn't about working harder
There's a romantic version of entrepreneurship that involves endless hours, personal sacrifice and a founder who simply refuses to give up. Persistence certainly matters, but working harder on the wrong things doesn't make them right.
Good execution is about making decisions, setting priorities and being disciplined enough to focus on what actually moves the business forward. That means knowing which assumptions need testing, understanding what success looks like before spending money and recognising when a feature, meeting or opportunity is a distraction. It also means being honest about the numbers, even when they're telling you something you'd rather not hear.
I've seen how easy it is for work to become a substitute for progress. Everyone's busy, the roadmap is full, there are plenty of meetings and an impressive list of things being delivered. From the outside, everything looks like it's moving forward, but the more important question is whether you're actually getting closer to having a sustainable business.
Activity feels productive. Progress is measurable. The two aren't always the same, and founders need to be particularly careful not to confuse them.
The best founders fall in love with the problem
There's plenty of advice about falling in love with the problem rather than the solution. It's repeated so often that it's become a startup cliche, but there's a reason people keep saying it.
When you're attached to a particular solution, every challenge feels like a threat. When you're focused on solving a genuine problem, new information becomes useful. You can change the product, reconsider the business model, discover that a different customer has a more urgent need or even realise that the opportunity you started pursuing isn't the one worth building.
What matters is whether you're creating something valuable enough that people want it, use it and are willing to pay for it. That's the part you can't manufacture with enthusiasm, and it's the part that makes building businesses both frustrating and fascinating.
The strongest founders aren't necessarily the ones with the most original ideas. They're often the ones who are best at listening, learning, adapting and making difficult decisions without losing sight of the problem they're trying to solve.
So, is your idea actually a business?
If you're working on something new, there are a few questions worth asking yourself. Have you spoken to people who experience the problem, rather than people who simply like you? Do you understand what they're doing today and why they would change? Have you found evidence that they'll commit time, money or effort to your solution?
It's also worth asking whether you know how you'll reach customers, not just how you'll build the product. Can you explain why someone would choose you over the alternatives? Do you have a realistic understanding of what it will cost to deliver your solution? And perhaps most importantly, are you willing to discover that parts of your idea are wrong?
You don't need perfect answers to start. In fact, you almost certainly won't have them. But you do need to be willing to find out, because a good idea can be exciting, clever and full of potential, while a business has to survive contact with reality.
The difference isn't how brilliant the idea sounds. It's whether you can turn it into something people genuinely value.