The Organic Origin Pattern
Paul Graham, co-founder of Y Combinator, observed that the best startup ideas come from asking one question: "What do you wish someone would make for you?"
He identified two types of startup ideas — those that grow organically out of your own life, and those you decide from afar will be necessary for some class of users other than yourself. The most successful companies overwhelmingly fall into the first category.
Apple happened because Steve Wozniak wanted a computer. He could design one, so he did. And since lots of other people wanted the same thing, Apple was able to sell enough of them to get the company rolling. Google happened because Larry and Sergey wanted to search the web better. Facebook happened because Mark Zuckerberg thought it was absurd that Harvard students were still using a printed paper directory.
None of these started as "startup ideas." They started as projects — tools built to solve an immediate, personal frustration. The company emerged after the tool proved valuable.
Why "Scratch Your Own Itch" Produces Better Products
When you build something to solve your own problem, you have three structural advantages that no amount of market research can replicate:
Deep Problem Understanding
You don't need user interviews to understand the pain — you live it daily. You know every frustration, every workaround, every moment where existing tools fail. This gives you insight that's impossible to acquire through observation alone.
Immediate Validation Loop
You're user zero. Every feature gets tested in production from day one — not in a staged demo environment. If it doesn't work for you, you know immediately. There's no gap between building and validating.
Battle-Tested Before Launch
By the time you offer it externally, the tool has been refined through real operational use. It's not a prototype — it's production-grade software that's already proven its value under pressure.
Academic research on "lead user innovation" — studied extensively by MIT's Eric von Hippel — confirms this pattern at scale. Users who face needs ahead of the mainstream market are disproportionately likely to innovate, and their innovations are disproportionately likely to become commercially successful products. Mountain bikes, surgical equipment, semiconductor processes — all were pioneered by users solving their own problems, years before manufacturers caught up.
From Our Portfolio: Three Internal Tools That Became Companies
Every company in our portfolio started the same way — as something we built to solve a problem we faced daily. Here's how each one evolved:
RavenTrack
The internal need: Our performance marketing agency was promoting retail sportsbooks and casinos that had moved online. We were buying media at scale and managing large affiliate networks — but the brands we worked with had no technology to track which channels, websites, and affiliates were delivering the best traffic and customers.
The pivot moment: It turned out dozens of brands in the space faced the same tracking blind spot. We started licensing our internal tool on a revenue share basis. Then we realised something bigger — the established blue-chip affiliate platforms in the space lacked many of the features we'd built, because we'd developed them from the operator's perspective. We knew what was needed because we were doing the work ourselves.
The company: RavenTrack launched as a full affiliate tracking and intelligence platform — built by practitioners who had lived with the limitations of existing platforms and solved them from the inside out.
Adzooma
The internal need: We needed a way to track and optimise our own media buying across multiple platforms. Managing campaigns at scale across Google, Facebook, and Microsoft Ads was consuming enormous time — and we were supposed to be good at this.
The pivot moment: After being mystery shopped by Google's Ads Channel Partnership programme, we realised the real opportunity wasn't in our own campaign management — it was in helping thousands of other small-to-mid-sized businesses who lacked the time or internal expertise to effectively self-manage their campaigns. We pivoted into automated ad audits and optimisation.
The company: Adzooma became a Google Premier Partner platform serving tens of thousands of businesses, with eight-figure investment raised. The core insight — that the people managing the ads are often too busy or under-resourced to optimise them properly — was only visible because we were those people first.
Omni AI
The internal need: After educating career professionals, entrepreneurs, and small business owners on how to use AI tools via microlearning courses, we encountered a growing problem — one our own team at ClickTech was also facing. There were dozens of AI tools, platforms, and models. Each week the "best" model changed. This meant multiple logins, lost context across platforms, constant retraining, and subscriptions that quickly mounted.
The pivot moment: We realised that the fragmentation problem wasn't unique to us — it was universal. Everyone using AI was drowning in tool sprawl. The answer wasn't another AI tool — it was a single platform that aggregated the best of all of them.
The company: Omni AI launched as an AI tool aggregator — multiple models, one platform, one login, no loss of context. And true to our education-first philosophy, we lead customers into Omni AI via interactive courses in ClickTech HUB where they both learn and produce output simultaneously. By the time they start using Omni AI, they already know how to extract maximum value from it.
The Pattern Repeats: Five Famous Examples
Our experience isn't unique. Some of the world's most valuable companies followed the same internal-tool-to-product trajectory:
Slack
Originally an internal chat tool built by Tiny Speck, a gaming company, to coordinate development of their game Glitch. When the game failed, they realised the internal communication tool was the real product. The game died. The chat tool became a $27 billion company.
AWS (Amazon Web Services)
Started as an internal effort to untangle Amazon's own messy IT infrastructure. By standardising their backend into modular services, they inadvertently built a platform that could run the rest of the internet. AWS now generates over $90 billion annually — more profitable than Amazon's retail business.
Basecamp
Originally a web design firm called 37signals. The team built a project management tool to handle their own client work because existing tools were overcomplicated. The internal tool became more valuable than the agency. They eventually shut down the agency entirely and renamed the company after the product.
Apple
Steve Wozniak didn't set out to build a computer company. He simply wanted a personal computer for himself. As Paul Graham observed: "Apple happened because Steve Wozniak wanted a computer... and since lots of other people wanted the same thing, Apple was able to sell enough of them." They still rely on this principle — the iPhone is the phone Steve Jobs wanted.
Mountain Bikes
A classic academic example of lead user innovation. Manufacturers didn't invent mountain bikes — enthusiasts modified their own road bikes to handle rough terrain years before any company mass-produced them. The users were ahead of the market by nearly a decade.
The Internal-to-External Transition: What Actually Matters
Not every internal tool should become a company. The transition from "useful for us" to "valuable for the market" requires navigating several critical challenges. Here's what we've learned from doing it multiple times:
Your Customer Might Not Look Like You
The core hypothesis is that others face the same problem — but your ideal customer might experience it differently. When Facebook launched Workplace (their internal collaboration tool), they assumed tech startups would be ideal customers. The breakthrough actually came from Walmart and Starbucks connecting frontline workers. Validate who else has this problem and how they experience it differently.
Separate the Tool From Your Culture
Internal tools often work brilliantly because of surrounding cultural practices — rituals, norms, shared language — that won't exist at customer companies. If your tool only works within your specific culture, it's not yet a product. The product needs to create its own adoption path that doesn't rely on practices your customers haven't developed.
Solve Beginner Problems, Not Advanced Ones
By the time you commercialise, your team is already an expert user. You've built advanced features that leverage deep familiarity. But new customers don't have that familiarity. The product must solve first-day problems compellingly — nobody sticks around for your advanced capabilities if the beginner experience is confusing. This is where education-first principles become critical.
The Value Is In What Gets Used, Not What Gets Built
You start with something already built that creates value for you. But external value isn't automatic. You need to envision your tool as a set of capabilities to solve problems for potential customers — not as a finished product to be sold as-is. Set aside the internal value and focus entirely on how external users will adopt it, learn it, and succeed with it.
Five Signals Your Internal Tool Could Be a Company
Not every internal tool should be commercialised. Here's how to recognise the ones that could be:
Others keep asking about it. Partners, clients, or peers in your industry ask "what do you use for that?" or "can we use your thing?" Unsolicited interest is the strongest signal.
The problem is universal but existing solutions are terrible. You built it because nothing on the market worked. If the alternatives are still bad, there's a market waiting.
You've been using it long enough to know it works. Not a prototype. Not a weekend project. Something battle-tested through months or years of real operational use.
It solves a problem at a specific stage or scale. The best internal-to-external products serve a clearly defined user at a clearly defined moment — not everyone in all situations.
You can teach others to extract value from it. If the tool only works because of your specific expertise, it's consultancy wrapped in software. If you can educate others to succeed with it independently, it's a product.
The Unfair Advantage of Building for Yourself
There's a reason this pattern — internal tool to scalable company — repeats across industries and decades. It produces a structural advantage that's nearly impossible to replicate from the outside:
You understand the problem at a depth that no amount of customer research can match. You've lived with it. You've felt the frustration. You know every edge case, every workaround, every moment where existing solutions fail — because you've experienced them all yourself.
And when you combine this depth of understanding with the education-first approach — teaching customers the strategy before giving them the tool — you create something remarkable: users who arrive already knowing how to succeed, using a product built by someone who truly understood the problem.
That's not a product. That's a moat.
"The best way to come up with startup ideas is to ask yourself the question: what do you wish someone would make for you?" — Paul Graham
Related
Have an Internal Tool With Market Potential?
We help teams identify, validate, and commercialise internal tools — from market positioning through to education-first go-to-market strategy. If you've built something valuable internally, let's explore whether it could be your next company.
Start a Conversation