Knowledge is like time. It has a starting point, and much of what we know today began with something that existed yesterday. Ideas rarely appear in isolation. They develop through observation, experimentation and the gradual accumulation of what others have discovered before us.
Software is no different. Every new system, tool or product builds on existing ideas, technologies and lessons. The chances of creating something entirely new, without any reference to existing knowledge, are very small. Even the most original inventions usually have roots somewhere.
What makes an idea valuable is often not its originality, but the connection it creates. A technology developed for one purpose may solve an entirely different problem. A business model that works in one industry may be even more effective in another. Much of innovation comes from recognising connections that others have overlooked.
Knowledge needs bridges. Individually, an idea may have little commercial value. But when connected with another idea, an existing problem or an underserved market, it can become something extraordinary. This is particularly important for anyone thinking about starting a business.
You do not need to invent a new problem. You need to understand an existing problem better than others, and find a more useful way to solve it.
Businesses and Lessons
There has probably never been a better time to study how businesses are created. We have access to an enormous collection of companies, founders, products and business models that would have been difficult to investigate twenty years ago. Much of this information is freely available, yet surprisingly few aspiring founders study it systematically.
Y Combinator has funded over 6,000 startups, including more than 100 unicorns. Andreessen Horowitz (a16z) has invested in over 1,300 companies, with more than 150 unicorns. Behind these numbers are thousands of decisions about markets, products, customers, distribution and capital. Each company represents an attempt to turn an observation about the world into a functioning business.
Some of these companies became extraordinarily successful. Others disappeared despite having experienced founders, talented engineers and substantial funding. Both outcomes are valuable because they reveal something about the relationship between an idea and the market in which it operates.
The Y Combinator directory, for example, allows you to explore what companies do, when they were founded, who founded them, their websites and often the founders’ professional profiles. From there, you can investigate competitors, business models, customer segments and how products have evolved. A single company can lead you to several others addressing the same problem.
A business school might charge thousands to teach you a selection of case studies. Here you have thousands of real businesses to investigate for free, including companies that are still developing and others whose outcomes are already known.
The problem is no longer access to knowledge. It is knowing how to extract value from it.
Reading Vs Studying
Most people approach startup directories looking for ideas. They browse a few companies, read descriptions, visit websites and occasionally find something interesting. This can be useful, but it rarely produces a deeper understanding of why a business exists or whether its approach is commercially viable.
A more useful approach is to treat each startup as an experiment. At some point, a founder believed a particular problem existed, that enough people cared about it, and that a solution could become a business. They made assumptions about customers, pricing, competition and growth. Some of those assumptions proved correct, while others probably changed along the way.
Your task is to reconstruct the reasoning behind those decisions. Why did the founders choose that market? What alternatives existed? What made customers willing to switch? Was the opportunity created by new technology, changing behaviour, regulation or simply a poorly served market?
Start with five questions.
What problem was the founder trying to solve?
Why was this problem worth solving at that particular time?
What made the solution different from what already existed?
How could the company acquire its first 100 customers?
Why might investors have believed this business could become much larger?
These questions move your attention away from the appearance of a product and towards the economics of the business. A beautifully designed application may struggle to acquire customers, while an ordinary looking product may generate substantial revenue because it solves an expensive and recurring problem.
The fourth question is especially important. Many founders spend months building products without understanding how their first customers will discover them. The fifth forces you to distinguish between a useful product and a business capable of expanding into a much larger market.
You may not find definitive answers to every question. That is fine. The objective is not to pretend you know what happened inside the company, but to develop reasonable hypotheses and test them against whatever evidence is available.
Patterns Matter
Study ten startups in the same industry and something interesting begins to happen. You start noticing similarities that are difficult to recognise when looking at companies individually. Different founders may have identified the same customer frustration, entered the same market at different times or adopted similar approaches to acquiring customers.
Some businesses succeed by simplifying complicated products. Others make expensive services affordable, remove intermediaries or automate tasks that previously required substantial human effort. A few take an existing idea from one industry and apply it to another where the same problem has not been addressed effectively.
Consider how many software businesses exist simply because an established industry still relies on spreadsheets, emails and manual processes. The underlying technology may not be particularly sophisticated. The opportunity comes from understanding the workflow, identifying where time or money is wasted, and designing something that customers find sufficiently useful to pay for.
This is why studying competitors should not discourage you. The existence of several companies addressing the same problem can indicate genuine demand. The important question is whether you can serve a neglected group of customers, offer a simpler product, distribute it more effectively or operate with better economics.
But there is another lesson worth understanding.
Funding is not proof of success, and success is not always proof of a superior idea.
Investors make mistakes. Founders misjudge demand. Markets change, customer acquisition becomes expensive and products fail to retain users. Companies with millions in funding sometimes achieve less than competitors operating with a fraction of their resources.
It is tempting to study a successful company and construct a convincing explanation for its success. The difficulty is that the same explanation might describe several companies that failed. Without comparisons, we risk confusing an attractive story with an actual cause.
This makes unsuccessful startups just as interesting as successful ones. Studying both gives you a better chance of identifying which assumptions mattered, which advantages were temporary and which problems founders underestimated.
One startup gives you a story. Thirty startups give you a chance to discover a pattern.
30 Days
My suggestion is simple. Study 30 startups over 30 days. Spend 20 minutes each day investigating one company, preferably within industries you understand or are interested in entering. Read its website, investigate its founders, identify its competitors and examine the problem it claims to solve.
Try to understand who pays for the product, why they would choose it over existing alternatives and how the company might acquire customers. If pricing is public, examine it. If the company has changed direction, investigate why. Look for interviews, launch announcements and earlier versions of the product that reveal how its thinking developed.
At the end of each session, write down three things you learned. These should be observations rather than descriptions. Instead of recording that a company provides scheduling software, you might observe that it serves a particular industry, charges per employee and competes by simplifying a process that existing products make unnecessarily complicated.
After ten companies, review your notes and compare the businesses. Which problems appear repeatedly? Which customer groups seem underserved? Where are companies charging substantial amounts for relatively simple solutions? Are several founders making similar assumptions about the future of an industry?
After thirty days, you will have spent approximately ten hours investigating thirty real businesses. You will have developed your own library of case studies, including observations about markets, distribution, competition, pricing and business models.
More importantly, you will begin asking different questions when encountering problems in your own work. Instead of immediately wondering what you could build, you may start asking who experiences the problem, how they currently solve it, what the existing solution costs and why nobody has improved it.
That change in thinking is worth considerably more than a collection of startup ideas.
The Gaps
There is a difference between knowing that a company succeeded and understanding the conditions that made its success possible. The first gives you information. The second helps you develop judgement, although even a detailed case study cannot establish with certainty why a business succeeded.
When you build something yourself, you will encounter problems that other founders have already faced. You may discover that your proposed solution has been attempted several times, that a particular customer segment is difficult to reach, or that a business model which failed elsewhere could work under different circumstances.
You may also discover that the most interesting opportunities are not always found in fashionable industries. Some exist in ordinary businesses where customers have been tolerating inefficient processes for years. These markets rarely attract the same attention as emerging technologies, but their problems can be real, expensive and worth solving.
The purpose of studying startups is not to copy what someone else has built. It is to understand how ordinary observations become useful products, how those products become businesses, and why some businesses grow while others disappear.
The more examples you study, the more connections you can make. An approach from one industry may help you recognise an opportunity in another. A failed product may reveal a problem that remains unsolved. An overlooked customer group may turn out to be a better market than the one everyone is competing to serve.
Originality is often the result of understanding existing knowledge deeply enough to make a new connection.
Thousands of founders have already spent years testing ideas, building products, acquiring customers and discovering what does not work. Much of that experience has left a public record that anyone willing to investigate can learn from.
The case studies are already there. You do not need permission, an expensive qualification or access to a private network to begin studying them.
The difficult part is learning to see what others have missed.
Start here:
Y Combinator: https://www.ycombinator.com/companies
Andreessen Horowitz: https://a16z.com/portfolio/