Mark Abbott learned that entrepreneurs cannot arbitrarily decide their culture. The marketplace—its pace and ambiguity—determines the culture required to thrive. If an industry moves at 120 mph, you must build a culture of resilience that can match that speed to survive.
To use official EOS trademarks, Ninety entered a license requiring approval for all marketing and software changes. This created "excruciating" friction and slowed development. However, it was a necessary trade-off to align with their core coaching community and its established terminology.
Mark Abbott openly shared his idea for an EOS software, only to have an acquaintance take it and beat him to market. Instead of quitting, he played the long game, focusing on a superior product and deeper community relationships, ultimately building a more successful company.
After raising $20 million, Ninety hired executives who brought conflicting playbooks and cultural norms. This created a "mess" where the founder began to lose control, demonstrating how venture capital can introduce chaos and lead to poor hiring decisions if not managed carefully.
Using his PE background, Mark Abbott deliberately bootstrapped Ninety to a $100M valuation before taking outside capital. This strategic patience allowed him to raise a $20M Series A with only 17% dilution, thereby maintaining majority ownership even after a second, larger round.
In its early days, Ninety's entire paid acquisition budget was a mere $500/month on Facebook. This minimal spend was highly effective because it supplemented a primary strategy of deep engagement within the EOS coaching and entrepreneurial communities, which drove most of the growth.
To truly understand his target market, Mark Abbott became a certified EOS implementer years before building his software. This deep immersion built trust and established relationships within the coaching community, which became his primary and most effective distribution channel.
Contrary to modern agile norms, Mark Abbott started with a clear, long-term product vision conceived years earlier. He spent the first six months meticulously designing the data schema with future AI capabilities in mind, prioritizing robust architecture over rapid, iterative development.