Loading page…
A team workspace for small businesses to run EOS-style meetings, goals, and follow-through.
over $1M ARR · 10 employees
Selling the weekly operating rhythm to a whole team turns a founder’s business playbook into recurring seat revenue.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Strety is a bootstrapped SaaS product for small businesses using EOS and related operating practices. It gives leadership teams tools to organize goals, meetings, tasks, and business execution. Founder Brian Dosal returned to the idea after a first, half-hearted attempt, when he and former BrightGauge colleague Larry saw stronger market adoption; Dosal cited 250,000 companies running EOS as the opportunity signal. In the interview, he reported about 700 paying customers, more than $1M in ARR, and a 10-person team, while noting the company was still losing money and expected profitability by year end. The team was self-funded by Dosal, his brother, and partners. Strety sells per user, competes around ease of use and a more polished experience, and grows through partners and word of mouth. The exact channel mix is not supported by audited customer attribution.
For an operating system SaaS like Strety, the first customers are easiest to reach through people already helping small companies adopt the method: implementers, coaches, and peer communities. Build a demonstrable version around one recurring leadership ritual, then ask coaches to use it with a real client team.
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.
Data credibility: Brian Dosal reported Strety’s approximate paying customers, ARR, team size, funding status, and operating loss in a founder interview. Figures are self-reported and unaudited.
At Strety’s per-user model, the first dollar should arrive when a real leadership team commits to running its operating cadence in the product. Make the initial sale straightforward: a time-bounded setup session, creation of the team’s goals, and an agreed first recurring meeting.
Strety’s natural growth loop combines team adoption, per-user expansion, and partner recommendation. When a small business uses the product in weekly meetings and goals, every teammate has a reason to return; a satisfied coach can bring the same workflow to another client.
Workflow software often faces a quiet stretch between initial enthusiasm and habitual use. Strety’s founder had already tried the concept once without full commitment, then reconsidered when the EOS market appeared to be maturing.
Strety organizes recurring management work for small businesses using EOS and related operating systems. Teams use software to prepare leadership meetings, maintain goals and scorecards, assign tasks, and see whether commitments are moving. The buyer is a founder or operator who wants a repeatable cadence; users include the leadership team and possibly a coach helping the company adopt it. The founder described per-user pricing, a more polished experience, and support for EOS as well as related ways of running a company. That flexibility can widen the audience if each workflow stays coherent. A practical MVP should make one weekly meeting easier from agenda through follow-up instead of attempting to encode every framework. Onboarding should help a team reach a real outcome quickly: a meeting completed, priorities recorded, owners assigned, and the next check-in scheduled.
Strety monetizes through SaaS subscriptions priced per user. At the interview point Dosal reported around 700 paying customers and over $1M ARR, alongside a 10-person team. He said the business was still losing money and expected profitability by year end; no margin, pricing tiers, or churn rate were given. Per-seat expansion can work when an entire leadership team adopts the workflow, because adding teammates increases product value and recurring revenue. But seat growth alone is not enough if support and acquisition costs rise faster. The business was bootstrapped by the founders and partners, with no outside funding mentioned. A new operator should test pricing through complete team adoption rather than isolated seats, then track activation, weekly active teams, expansion, renewal, and support hours. Keep forecast revenue distinct from cash collected and distinguish customer accounts from paid seats.
The interview describes Strety’s staffing and operating model but does not identify its software stack or hosting costs. It had ten employees and was bootstrapped, with the founder and his brother plus partners supporting the company. Dosal said Strety was above $1M ARR but still losing money, illustrating that meaningful recurring revenue does not automatically create profitability for a growing team. Likely cost centers include engineering, customer support, partner enablement, payment fees, and help adopting a new routine. A small competitor should keep implementation light and use product analytics to find where teams stall. Support can be part of the sale, especially for coaches onboarding client companies, but needs repeatable materials and clear scope. The founder expected profitability by year end; that was forward-looking, not a reported result. Evaluate contribution margin by cohort and avoid hiring ahead of durable retention.
Copy Strety’s focus on a recurring business ritual and its connection to practitioners who teach that ritual. The product can become part of a team’s operating habit, while coaches offer a route into companies that may not discover a standalone tool. The founder also described word of mouth and land-and-expand, so make team invitations, progress sharing, and seat additions natural. Change the market framing carefully: EOS is a specific methodology, while some teams combine or adapt operating systems. Let customers configure terminology and workflows, and respect relevant licensing and trademark boundaries. Treat the reported 700 paying customers and more than $1M ARR as founder-reported traction rather than proof a new entrant will reach similar scale. A copyable first step is a meeting-and-follow-up workflow with partner-led pilots. Expand only when teams use it weekly and referrals repeat.
Our read: Strety’s central risk is whether teams sustain a management routine after initial setup. If leaders stop preparing meetings or updating scorecards, a per-user subscription can churn even when features are broad. The category also depends on coaches and implementers whose referrals can be valuable but uneven; avoid making one partner channel the sole source of customers. A larger competitor can match surface-level meeting and goal features, so the product needs smoother workflows, strong onboarding, and a reason to return weekly. The founder described the company as unprofitable despite more than $1M ARR, making payroll and acquisition efficiency important. Measure retained active teams, not just paid accounts. Be careful with methodology terminology, and ensure integrations, templates, and coach access respect customer privacy and licensing requirements.
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