Loading page…
Ninety turns the EOS operating system into software that keeps leadership teams aligned and executing.
18,500 companies · $12–$16 per seat for core plans
Mark spent years earning trust inside the coaching community before writing code; that embedded expertise became a distribution channel and product council.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Mark Abbott’s idea for software to help companies operate better began in 2005. After encountering EOS through companies he invested in, he spent years learning the framework and becoming an implementer before building a product. A competitor, Traction Tools, reached market first, but Abbott proceeded with an EOS-compatible tool in 2016 and began coding in 2017. Ninety landed its first customer that year and entered a formal EOS license in 2018. Abbott said he used six months to design the data schema before shipping the five foundational EOS tools. He bootstrapped through roughly 1,000 customers and a $100 million valuation before raising outside capital. The company now reports nearly $44 million in revenue, 18,500 companies, almost one million employees across those companies, and about 25% of employees as paid seats. Core seat pricing was described as $12, $14, or $16. Abbott said Ninety has raised $55 million in total.
Ninety’s first customers came from being useful to a community before asking it to adopt software. Abbott became deeply involved in the EOS implementer network, learning how coaches guided leadership teams and building relationships with the people who could introduce the product.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself. The exact words are quoted below, with a timestamp that jumps to the second each figure is said.
“He's grown it to nearly 44 million in ARR and has over 18,000 companies as customers.”
0:13 · hear it in the videoData credibility: Mark Abbott reported nearly $44 million in revenue, 18,500 customer companies, almost one million employees across them, and about 25% paid-seat penetration. He also described $12–$16 per-seat pricing and $55 million raised. These are founder statements in a podcast interview; no audited financials or dashboard were cited. The video description repeats these numbers, but it is not independent verification.
Ninety’s first customer arrived in 2017, after the team began coding in 2016. Abbott said he charged that first customer $12 per seat, and the least sophisticated plan still cost $12 at the time of the interview; other stated seat levels were $14 and $16.
Ninety’s growth loop connected a practitioner community, client companies, and recurring software usage. Coaches could introduce the product to multiple leadership teams; those teams used the tools to set priorities, track issues, and run their operating rhythm.
For a category-specific SaaS, the early quiet period can stretch across years while the founder learns the buyer’s language and earns distribution access. Abbott’s path took time: the idea dates to 2005, while the first customer arrived in 2017.
Ninety is software for leadership teams using the EOS operating system. Abbott described the product as helping teams align on who they are, what they are doing, where they are going, whom they serve, and how they execute. It turns a management framework into recurring tools for planning, accountability, and team communication. The initial product included five foundational tools. The product must serve more than one user type: a coach or implementer may introduce it, while the leadership team uses it to run the business. That creates a workflow with both guided setup and ongoing self-service. Abbott said around 18,500 companies were using Ninety, representing almost one million employees, with about a quarter of those employees on paid seats. A new entrant should resist building an all-purpose business dashboard. The value comes from making a particular operating cadence easier to follow and keeping the team’s shared commitments visible between meetings. Because the framework itself has licensing and trademark boundaries, product language and templates need careful review.
Ninety sells seat-based subscriptions to companies. Abbott quoted core seat prices of $12, $14, and $16, with pricing varying by plan and a lower per-seat cost at larger company sizes. He said the company had nearly $44 million in revenue and 18,500 companies, while almost one million employees worked at those companies and about 25% were paid seats. These are founder-reported figures in the interview. The business also raised $20 million in a Series A in 2021 and later $35 million, bringing total funding to $55 million. Its early model was bootstrapped through approximately 1,000 customers and a $100 million valuation, according to the founder. The strongest monetization design aligns the software with a company-wide operating practice while letting a coach bring in accounts efficiently. A new entrant should test pricing by team size and by the value of coordination, not assume every employee needs a paid account. The transcript describes ongoing work on AI-related packaging and pricing, so future monetization was still evolving.
Abbott said Ninety spent its first six months developing the data schema because he expected the company’s data to matter to its long-term direction. The early system used MongoDB; he said it later used both MongoDB and a relational database. The interview does not provide a detailed hosting bill, gross margin, or engineering headcount. This product category rewards careful modeling of teams, goals, meeting records, issues, and accountability over time. A new build should establish clear tenant isolation and permission rules before accumulating sensitive leadership discussions. Start with a relational model for organizations, memberships, cycles, goals, and meeting outcomes; keep audit history for edits to commitments. Costs will likely center on product development, customer support, and account onboarding rather than unusually heavy compute. Add AI features only where they reduce meeting preparation or make a team’s existing information easier to use, and preserve human review for decisions that affect people or business priorities. Avoid migration pain by testing schema changes against representative multi-year account data.
Copy the practice of learning the operating system and its practitioner community before building. Ninety’s founder had spent years inside the world the software served, which helped him understand where a digital product fit and who could introduce it. Also copy the focus on a real operating cadence rather than a broad promise to “run a better business.” Change the route to market if you lack a trusted community: partner with a narrow group of consultants, accountants, or fractional operators and earn referrals by improving a repeated client workflow. Validate willingness to pay before investing six months in infrastructure; use a paid pilot to expose the minimum data model needed. Be precise about trademark and licensing requirements, since Ninety itself began EOS-compatible and later entered a license. Build customer support into the plan: practitioners’ reputations are attached to tools they recommend. Finally, do not copy the founder’s long bootstrapping timeline or later fundraising targets mechanically. His reported scale is a reference point; the replicable insight is community access joined to software that becomes part of a team’s weekly habits.
The biggest strategic risk is dependence on a framework’s brand, licensing terms, and practitioner ecosystem. A competitor beat Ninety to market, demonstrating that relationships and execution matter as much as the idea itself. A new entrant should establish permission to use framework language before designing its brand or sales materials. Another risk is weak seat expansion: Ninety reported that only about 25% of employees at customer companies were paid seats, so broad company counts do not equal universal adoption. Per-seat pricing can also feel misaligned when AI features increase value but reduce the number of human interactions required. Product quality must support sensitive leadership workflows, and a confusing or unreliable meeting experience can quickly erode practitioner trust. Fast hiring and funding can create organizational costs; Abbott described conflicting executive playbooks and culture as a difficult period after raising capital. Founders should grow the team in response to an operating bottleneck, preserve a clear decision process, and watch retention and paid-seat depth—not just revenue or customer totals. The nearly $44 million figure was reported by the founder and was not independently audited in the interview.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,403 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click