Has your best idea already happened?

21 Apr

There is a moment most SaaS companies reach after funding where the nature of thinking inside the product team begins to shift.

The original idea was strong enough to secure funding because it did something important. It did not just describe a feature gap, it identified a shift in behaviour that others had not fully acted on yet. It reframed what the product category could be. That early thinking is usually the most distinctive the product will ever be. Because once funding arrives, the nature of the work changes.

It is rarely visible at first and from the outside, it looks like success. Roadmaps are full and features are shipping out faster than ever to meet investor demand and there is a strong sense of momentum. Metrics might even be improving. The original idea that secured funding is still present in the narrative of the company.

But the reality is that the focus moves from proving a new idea is possible to scaling what already exists. Roadmaps expand. Delivery expectations increase. Competitive pressure becomes more visible. And gradually, the product stops being shaped primarily by the original insight and starts being shaped by what is easiest to ship next, or what competitors are already doing.

This is where the tension begins. The first version of the product was built on a question that reframed behaviour. The later versions are built on decisions that refine execution within an already established frame. Over time, the quality of questions begins to shift. Not because teams are less capable, but because the environment rewards certainty over exploration. What often gets lost in that shift is the original curiosity about user behaviour itself. Not just what users are doing, but why the behaviour is changing in the first place.

A useful example of this is the evolution of social platforms and the creator economy.

Twitter had early exposure to one of the biggest behavioural shifts in modern internet use through Vine. Short-form video had started as entertainment, becoming a new form of cultural expression, driven by creators rather than just social sharing between friends. Vine ultimately did not capitalise on that shift and after Twitter’s acquisition it died a death. The behaviour was visible, but the deeper question was not fully explored: what happens when content creation itself becomes the primary reason people come to a platform?

TikTok approached that same shift differently, starting from Musical.ly and evolving it into something much bigger. The focus was not just on short-form video as a format, but on understanding why people were creating in the first place, and what would make that behaviour scale.

The curiosity was in the questions. Not just “what content works?”, but “what would make ordinary users want to behave like creators?” and “what systems would need to exist for that to become sustainable?”

That led to a fundamentally different product logic built around creators, trends, and discovery. Content was designed to surface based on interest and behaviour, not existing networks. Music, formats, and participation loops were all part of making creation itself feel rewarding.

The difference was not execution speed. It was the quality of the questions asked about user behaviour. They asked curious questions like:

“What behaviour is actually changing here, beneath the surface of what users are saying?”
“What would this product look like if creators were not just users, but the primary economic unit?”
“What assumptions are we making about value exchange between platform and user that may no longer be true?”

Under pressure, those kinds of questions are often deprioritised because as companies scale, the operational demands increase. Investor expectations require predictability. Competitive pressure encourages feature parity. AI acceleration increases the speed at which teams can build, which often increases the pressure to decide faster rather than think more deeply. And in that environment it isn’t that curiosity is removed deliberately it just gets gradually compressed.

Customer feedback is still collected, but it is increasingly used to validate planned direction rather than reshape it. Data is still available, but it is often interpreted through existing assumptions about what the product already is. The result is not that teams stop building, it’s that they build more confidently in directions that are less frequently challenged.

Curiosity, in product terms, is not about slowing delivery. It is about maintaining the ability to question the framing of the product itself before committing to execution at scale.

Curious product teams do something slightly different. They resist the early closure of interpretation. They stay closer to uncertainty for longer. They are more willing to revisit the assumptions that shaped the original version of the product, particularly as new behaviours emerge. They ask questions like:

“What has changed in user behaviour that we are not fully accounting for?”
“What role are we assuming we play in the user’s life, and is that still true?”
“If we were designing this today from scratch, what would we prioritise differently?”

These are not abstract strategy questions. They are the difference between incremental product evolution and category-level relevance over time. Because the real risk for scaling SaaS and tech companies is not that they lose execution capability, it is that they maintain execution speed while gradually losing the quality of thinking that created the original opportunity in the first place.

The companies that continue to define categories are not simply those that move faster than others. They are the ones that continue to interrogate whether they are still responding to the same version of reality that made the product valuable at the start. That is what protects the original idea. And that is what curiosity makes possible.

Not curiosity as a vague cultural value or personal trait, but as a practical capability in how product decisions are made under pressure. The ability to keep questioning the framing of the problem, even when everything in the organisation is pushing towards faster execution and clearer answers.

And this is where most teams struggle. Not because they lack insight, but because they are rarely supported to sustain this way of thinking when pressure increases.

That is where we come in.

We work with SaaS and tech teams to rebuild curiosity as a core product capability, helping founders and teams strengthen the quality of questions they ask under pressure so they can protect the thinking that made their original idea valuable in the first place, and scale it without losing what made it different. If you want to explore how to embed that into your product and team culture, get in touch.