Community-Led SaaS Growth: How Ninety Hit $44M ARR

Summary of Community-Led SaaS Growth: How Ninety Hit $44M ARR

by Omer Khan

50m•May 21, 2026
Listen to Episode

Overview of the SaaS Podcast Episode with Mark Abbott

In this episode of SaaS Podcast, Omer Khan interviews Mark Abbott, founder of Ninety (90.io), a SaaS platform that helps leadership teams align around vision, planning, metrics, meetings, and execution using the EOS framework. Mark shares the long, non-linear path from a 2005 idea to a business now nearing $44M in ARR, with 18,500+ companies as customers. He explains how he built trust inside the EOS community, why he spent years becoming an EOS implementer before building software, how he acquired the first customers with a tiny ad budget and community relationships, and what changed after raising capital.

Key Takeaways

  • Ninety is built to help leadership teams get aligned and execute consistently.

    • The product supports planning, scorecards, meetings, rocks, issues, and accountability.
    • Its core purpose is to make businesses run more smoothly by keeping teams on the same page.

  • The business was built slowly and intentionally.

    • Mark first conceived the idea in 2005.
    • He spent years learning the EOS methodology and building relationships before launching software.
    • The first customer arrived in 2017.

  • Community was the initial growth engine.

    • Mark leaned heavily on the EOS implementer community and related entrepreneurial networks like EO, Vistage, and YPO.
    • The earliest marketing spend was only $500/month on Facebook.

  • Raising money created both scale and complexity.

    • Mark bootstrapped until the business reached roughly a $100M valuation, then raised capital.
    • He later said growth accelerated, but so did hiring mistakes and organizational chaos.

  • AI is becoming a major part of the product strategy.

    • Ninety is moving toward an AI-enhanced product experience, including a companion bot called Maz.
    • Mark sees AI as both an opportunity and a competitive threat, but believes the company’s community moat and customer data are strong advantages.

How Ninety Started

From Boardroom Frustration to Software Vision

Mark’s original insight came from his private equity and board experience: building great companies felt harder than it should be. He believed success required a clear vision, a strong plan, tools, and disciplined execution — similar to building a house. That idea eventually became the foundation for Ninety.

The EOS Connection

  • Mark discovered EOS through the book Traction by Gino Wickman.
  • He realized EOS matched the product he had originally envisioned.
  • Instead of rushing to build software, he immersed himself in the EOS community and became an implementer to learn the system deeply.

Negotiating with Gino Wickman

Mark approached Gino directly and asked permission to build software around EOS. Gino’s response was essentially: EOS was not a software company’s DNA. That answer opened the door for Mark to build Ninety, eventually under license from EOS Worldwide.

Product Strategy and Early Build Choices

Five Foundational Tools

Mark said the first version of Ninety included the core EOS tools from the start:

  • Vision/Traction Organizer
  • Meetings
  • Rocks
  • Scorecard
  • Issues list

Built for the Long Game

He emphasized that he had a clear product vision from the beginning and did not follow a purely agile “ship tiny and iterate” approach. He spent the first six months designing the data schema because he believed data would be central to the platform’s future.

Licensing Tradeoffs

The EOS license brought credibility and community access, but also major constraints:

  • Marketing approvals were required.
  • Product changes needed approval.
  • The team had limited freedom to teach or promote the product.

Despite the restrictions, the license helped validate the offering and gave the company access to the broader EOS ecosystem.

Go-to-Market and Growth

Early Distribution

For the first couple of years, growth came mainly from:

  • EOS implementers
  • Entrepreneur communities
  • Word of mouth
  • Lightweight paid ads

Customer Acquisition

  • Early customers were largely pulled from the coaching/implementer network.
  • Mark stressed that service quality was a major differentiator from the start.
  • The team offered strong support and a hands-on customer experience.

Pricing

  • The first customer paid $12 per seat, and that entry-level pricing still exists in the current model.
  • Mark said pricing will likely evolve as AI features become more central, potentially toward:
    • Two product tiers: with AI and without AI
    • Some amount of AI consumption included, then usage-based charges beyond that

Funding and Scaling Lessons

Bootstrapped for a Long Time

Mark initially funded the company himself and deliberately avoided raising money early. His plan was to wait until the company had significant value before bringing in outside capital.

What Changed After the Raise

After raising capital, the company moved faster — but not always in a good way:

  • Hiring accelerated quickly
  • New executives brought their own playbooks and cultures
  • Organizational alignment got harder
  • Mark acknowledged making several bad hiring decisions

He said the experience reinforced an important lesson: every stage of growth requires different kinds of leadership and different types of hires.

AI, Competition, and the Future of Ninety

AI as an Opportunity

Mark has thought about AI for years and said he had already been considering it back in 2012. He views AI as a way to:

  • Improve product intelligence
  • Help teams understand what’s working and what’s not
  • Increase operational efficiency internally
  • Expand the platform’s value over time

AI Embedded vs. AI Native

He described the industry tension between:

  • AI embedded software
  • AI native software

Ninety is currently AI embedded, but Mark is actively thinking about how to evolve it further.

Competitive Moat

Mark believes Ninety has several advantages:

  • Over a decade in the EOS community
  • Strong relationships with implementers
  • A large customer base and data set
  • Deep understanding of the problem space

Still, he said he stays “paranoid” about competition and wants to move faster.

Lightning Round Highlights

Startup Advice He Disagrees With

  • The idea that all early hires should be “top-tier” regardless of stage
  • Mark believes hires must fit the company’s current stage and pace

A Hard Lesson Learned

  • Founders do not fully control culture
  • The market and operating environment shape culture more than leadership slogans do
  • Fast-moving, ambiguous environments require resilience and tolerance for change

Favorite Tool

  • Claude is his current favorite productivity tool

What He Does for Fun

  • Hiking
  • Running
  • Free diving and spearfishing with his son
  • Skiing / snowboarding
  • Spending time outdoors

Final Thoughts

Mark Abbott’s story is a strong example of patient, community-led SaaS growth. Instead of chasing speed early, he built credibility inside a niche ecosystem, learned the customer’s operating model deeply, and turned that understanding into software. Ninety’s growth came from a mix of:

  • deep product-market alignment
  • trust-based distribution
  • strong service
  • long-term thinking
  • disciplined, if sometimes painful, scaling decisions

The big theme of the episode: lasting SaaS companies are often built through patience, community, and operational excellence — not just rapid product shipping.