When pivoting from a product with existing revenue, avoid the binary choice of killing it or splitting focus. Blue Jay successfully transitioned by putting their V1 product into "maintenance mode"—servicing existing customers but halting all new feature development—and committing the entire team to building the V2 for a defined six-month period.
Related Insights
Avoid a fixed allocation of resources between core products and new initiatives. Instead, treat the investment mix as "seasonal." Periodically and purposefully reassess the balance based on the most pressing business needs—whether it's stabilizing the core for large customers or pushing aggressively into new markets for growth.
The Browser Company's pivot required spending the "trust points" they'd built with their team and community. Leaders must be prepared for this painful drawdown and the internal/external backlash, even when they have high conviction in the new direction. It's a necessary but difficult part of a major strategic shift.
The tension between growth and profitability is best resolved by understanding your product's "runway" (be it 6 months or 6 years). This single piece of information, often misaligned between teams and leadership, should dictate your strategic focus. The key task is to uncover this true runway.
Don't force your sales team to learn and sell a completely new product. Instead, integrate the new capability into an existing, successful product, making it "first" or "default" for that channel. This reduces sales friction and complexity, leveraging established momentum for adoption.
To grow an established product, introduce new formats (e.g., Instagram Stories, Google AI Mode) as separate but integrated experiences. This allows you to tap into new user behaviors without disrupting the expectations and mental models users have for the core product, avoiding confusion and accelerating adoption.
Before a major business pivot, first identify what can be let go or scaled back. This creates the necessary space and resources for the new direction, preventing overwhelm and ensuring the pivot is an extension of identity, not just another added task on your plate.
Rather than making an abrupt turn, Sure managed its pivot from a B2C app to a B2B platform gradually. They kept the original mobile app running while they built and validated the new B2B distribution model, only sunsetting the app once the new strategy proved viable and began to ramp up.
The pivot from Arc to Dia was also a cultural and technical reset. The Browser Company gave their team a "blank page," allowing engineers to build a new, faster architecture and designers to rethink the experience. This chance to fix old problems and pursue new ideas was key to getting team buy-in.
When hypergrowth causes you to fail internal stakeholders (like Operations), apologies are insufficient. Rebuild trust by going to the CEO and board *together* with the slighted team to advocate for a drastic roadmap pivot that prioritizes their needs, demonstrating true commitment to their success.
When Fal was debating its pivot, their investor Todd Jackson asked which idea would get to $1M ARR faster versus $10M ARR faster. This framework forced them to evaluate not just immediate traction but long-term market size and velocity. It provided the clarity needed to abandon a working product for one with a much higher ceiling.
