Why the Customer You End Up With Is Rarely the One You Started With.
By Creatives Takeover Editorial Team · August 27, 2026
The market always chooses your final customer.
1. The Snowboard Store That Never Really Sold Snowboards
In 2004, a burned-out programmer named Tobias Lütke decided he wanted to do something less abstract than writing code for a living. He opened an online store called Snowdevil, selling snowboards from third-party brands. It should have been a simple project. Instead, every existing e-commerce tool he tried to use to build the store frustrated him. None of them did what he actually needed in a way that felt simple or usable.
So, on a Friday evening, in a moment of real frustration, he decided to just build the store's infrastructure himself. Over the following weeks, working with the tools he had, he built a functioning e-commerce platform from scratch, just well enough to get Snowdevil running. What happened next is the part of the story that actually matters. Lütke and his co-founder Scott Lake gradually noticed they were more energized by building and refining the underlying store software than they were by selling snowboards. The software, originally a means to an end, quietly became more interesting than the business it was built to support.
That software became Shopify. The snowboard store that started it all is now, at best, a footnote. The actual customer Shopify ended up serving, other online retailers who needed exactly the tool Lütke had built for himself, was never the customer the business was originally created for.
2. The Game That Failed and the Tool Nobody Meant to Build
Stewart Butterfield's path to Slack ran through an almost identical shape of accident. In 2009, he founded a company called Tiny Speck to build a multiplayer online game called Glitch. The team worked on it for years. It launched, struggled to attract enough players, and by 2012 Butterfield had concluded, publicly and directly, that the game simply was not viable as a business.
While building Glitch, the distributed team, split across offices in the US and Canada, had built an internal communication tool for their own coordination, nothing more than a practical solution to the ordinary problem of a team working across time zones and locations. When the game failed, that internal tool was the one piece of the entire effort that had genuinely, unambiguously worked. Rather than abandoning everything and starting over from a blank page, Butterfield's team turned their attention toward that tool specifically. It became Slack, which Salesforce eventually acquired for $27.7 billion.
The detail worth noting here is not just that the pivot happened, but what actually carried over when it did. Slack did not start from nothing. It reused a substantial share of the messaging infrastructure originally built for Glitch. The customer changed entirely, gamers became enterprise teams, but a meaningful portion of the underlying technical asset did not need to be rebuilt from scratch. What changed was who the thing was actually for.
3. The App With Too Many Features and One Feature That Actually Mattered
Instagram's founders, Kevin Systrom and Mike Krieger, did not set out to build a photo-sharing app either. Their original product, called Burbn, was a location-based check-in app layered with a long list of additional features: photo posting, point-earning mechanics for check-ins, and several other functions competing for the same small amount of user attention inside one cluttered interface.
What the founders eventually noticed, by watching how people actually used the product rather than by debating internally what the product was supposed to be, was that one specific behavior stood out clearly above everything else: users cared, almost exclusively, about the photo-sharing feature. Everything else, the check-ins, the points, the location layer, was mostly being ignored. Rather than continuing to invest evenly across every feature the original product roadmap called for, Systrom and Krieger made a deliberate decision to strip almost everything else away and rebuild the product entirely around the one behavior users had already shown them mattered. That stripped-down, single-purpose product became Instagram.
What These Three Stories Actually Have in Common
It would be easy to read these as three unrelated stories of lucky accidents, three founders who happened to stumble into something better than what they originally set out to build. The more useful reading treats them as three examples of the same underlying pattern, one that shows up far more often than the popular, tidy version of a startup's origin story usually admits.
In each case, the founders started with a specific customer and a specific plan in mind. In each case, that original plan turned out to be wrong, not catastrophically or obviously wrong, but wrong in a way that only became visible once real people were actually interacting with what had been built. And in each case, the founders' most important skill was not the original idea. It was the willingness to notice what was actually happening, a feature getting disproportionate engagement, an internal tool solving a real problem better than the product it supported, and to follow that signal even though it meant abandoning a plan they had already invested real time and belief in.
That noticing is harder than it sounds. Founders are, almost by necessity, deeply attached to their original vision, and the businesses that never manage to pivot are frequently not the ones that lacked a good underlying asset. They are the ones that failed to notice, or refused to act on, a signal that was already visible in how real customers were actually behaving.
Why the Real Market Is Rarely Visible From the Whiteboard
There is a specific reason this pattern shows up so consistently, and it is worth naming directly rather than treating each of these stories as a one-off surprise. A target market defined before any real product exists is, by definition, a hypothesis. It is built on the founder's own assumptions about who has the problem, how painful that problem actually is, and what a solution should look like, assembled entirely without the benefit of watching a single real person interact with a real version of the thing.
Once a product actually exists, even in a rough, early form, that hypothesis gets tested against reality for the first time, and reality is a far more precise and far less forgiving teacher than any amount of pre-launch planning could ever be. Burbn's founders could have debated internally for months about which feature mattered most to users. Watching actual behavior settled the question in a way no internal debate ever could have. The market you discover this way is not a lesser, accidental version of the market you planned for. It is frequently a more accurate one, because it is built on evidence rather than assumption.
How to Actually Notice When This Is Happening to You
The practical challenge is not understanding that this pattern exists. It is recognizing it while you are inside it, in real time, rather than only in hindsight once the pivot has already succeeded and become a tidy story.
A few concrete signals are worth watching closely. If one specific feature or behavior is generating disproportionate engagement relative to everything else you have built, the way photo-sharing did inside Burbn, that imbalance is data, not a distraction from your actual plan. If an internal tool you built purely to solve your own operational problem turns out to work better, and generate more interest, than the actual product you are trying to sell, the way Slack's internal chat tool did inside Tiny Speck, that is worth taking seriously as a genuine signal rather than dismissing it as a side project. And if your sales conversations or customer feedback keep drifting toward a different, adjacent problem than the one you built your product to solve, that repeated drift is rarely a coincidence. It is usually customers telling you, indirectly, what they actually need.
The instinct to protect and push through the original plan is understandable, and grit genuinely matters in building anything difficult. But the specific skill on display in each of these three stories was not stubborn persistence toward an original vision. It was the willingness to treat a strong, repeated, real-world signal as more important than the plan that predated it.
Five Things Worth Taking From This
Your original target market is a hypothesis, not a commitment. Every one of these companies started with a clear, specific idea of who they were building for. In every case, that idea turned out to be incomplete or wrong, and the businesses that succeeded were the ones willing to revise it once real evidence arrived.
A pivot rarely means starting over completely. Slack reused a substantial share of Glitch's underlying messaging infrastructure. Instagram kept its core mobile photo pipeline from Burbn. The valuable asset you have already built is frequently more transferable than it feels in the moment, even when the customer it ends up serving looks nothing like the one you originally imagined.
Disproportionate engagement with one feature is a signal worth acting on, not an interesting footnote. Instagram's entire existence traces back to founders paying close attention to which single feature users actually cared about, rather than continuing to invest evenly across a roadmap built before any real usage data existed.
An internal tool that solves your own problem well is worth taking seriously as a product. Both Shopify and Slack originated from founders building something purely to solve their own operational frustration, and discovering, sometimes reluctantly, that the tool was more valuable than the original business it was meant to support.
Noticing the signal matters more than defending the original plan. The hardest part of each of these pivots was not technical. It was psychological: the willingness to treat real customer behavior as more authoritative than a plan the founders had already invested real belief and effort into.
The customer you end up building for is rarely the one you set out to serve, not because your original plan was foolish, but because no plan made before real customers interact with a real product can fully account for what they will actually do with it. The founders behind Shopify, Slack, and Instagram did not succeed because they picked the right market on day one. They succeeded because they were paying close enough attention to notice when the real market revealed itself, and were willing to follow it even after they had already committed to a different plan entirely.