If you’ve read Traction and decided your business needs an operating system, the next question lands fast: do you actually need an EOS® Implementer, or can your leadership team run this on your own?
It’s a fair question. Engagements with an EOS Implementer are a meaningful annual investment, and the EOS® toolkit is designed to be teachable. Plenty of teams give self-implementation a shot. Some pull it off. Many stall out somewhere between Quarter Two and Quarter Four.
We have a particular vantage point on this. Strety was built by operators who self-implemented EOS at our previous company, BrightGauge, and at Strety, our CEO Brian Dosal has spent two years moving us from self-implementation to working with EOS Implementer Lisa González. He’s been writing about that journey in a weekly newsletter ever since. We’ve felt the difference from both sides, and this post is our attempt to lay it out honestly.
Table of Contents
- What “getting started on EOS” actually means
- What an EOS Implementer actually does
- What Brian Dosal got right as a self-implementer
- What Brian missed as a self-implementer
- Implementer-led vs. self-implemented: the practical differences
- A practical way to decide
- Fractional integrators and other operator partners
- Where Strety fits, regardless of path
- Frequently asked questions
- Choosing the path that actually fits
What “getting started on EOS” actually means
EOS® is a set of practical tools and disciplines for running a small or mid-sized business — the V/TO, Rocks, the Scorecard, Issues, the Level 10 Meeting™, the Accountability Chart, IDS®, and the People Analyzer™. Together they cover the Six Key Components™: Vision, People, Data, Issues, Process, and Traction.
EOS Worldwide reports that more than 250,000 companies have adopted EOS to run their businesses, which gives you a sense of how widely the toolkit has spread since Traction was first published in 2007.
There are three main ways to start using it:
- Self-implementation. Your leadership team reads the books, watches the videos, and runs the rollout internally.
- Working with a certified EOS Implementer. An external coach trained by EOS Worldwide teaches, facilitates, and coaches your team through the early sessions and beyond.
- Working with a fractional integrator or other EOS-fluent operator. A practitioner who often blends EOS with hands-on operational support.
The first two are the most common paths, and the third is increasingly relevant for teams that need an Integrator-shaped person in the seat alongside the framework.
What an EOS Implementer actually does
Most people picture an Implementer as a coach who runs your meetings. The role is bigger than that. A certified EOS Implementer fills three functions at once:
Teacher. They explain the EOS tools the way the model defines them, so your team learns the real version from the start. This matters more than it sounds. The most common failure mode of self-implementation is teams subtly redefining the tools as they go.
Facilitator. They run your Focus Day™, Vision Building™ Days, and quarterly sessions. They keep the IDS® process honest. They sit in the middle of hard conversations and stay neutral because their job depends on staying neutral.
Coach. Between sessions, they hold leaders accountable to the discipline of the system. A weekly L10 that has stretched to 90 minutes? A Scorecard nobody updates? Those are the things an Implementer notices and pushes back on.
An Implementer specializes in EOS — the framework, the cadence, the tools. They’ll help your team have the right conversation about pricing or hiring or firing, while leaving the business decisions themselves to you.
What Brian Dosal got right as a self-implementer
Brian self-implemented EOS at BrightGauge, the company he founded with his brother in 2010 and sold successfully in 2019. He picked up Traction and rolled out as much as he could on his own. He also got rare second-hand experience by sitting in as a fly on the wall during a full Implementer-led engagement at his father’s low-voltage cabling company, which used Certified EOS Implementer Brent Sprinkle. That combination shaped how he thought about which parts of EOS a self-implementer can genuinely run well.
In his newsletter, Brian wrote about the BrightGauge years:
“I credit EOS with allowing us to grow calmly and turn over a well oiled machine to our acquirers.”
Self-implementation worked at BrightGauge because Brian had the right inputs. A bootstrapped budget that justified the DIY approach. Direct exposure to how a real Implementer runs sessions. A genuine commitment to the model from Day 1. And the discipline to keep running the tools through an acquisition.
The Forte case study tells a similar story from a different angle. Asher Carr joined Forte as their first operations leader with a mandate to roll out EOS, and he did it without an Implementer — using Traction and Rocket Fuel as his guide, plus the experience he’d built running adjacent systems in real estate. He phased the rollout deliberately, starting with the V/TO and Rocks before adding Scorecards and L10s. By his first quarterly off-site, the team described it as the most organized one they’d ever had. They hit three out of five Rocks in their first real quarter and pulled off their largest-ever client launch — 8,000 members in four waves — using Strety Projects to manage the cadence.
“What was great about bringing Strety on is that it created this middle ground for people to come to every day.”
— Asher Carr, Operations Manager at Forte (read the full case study)
The pattern in both stories: self-implementation works when an operator with prior structured-system experience runs a phased, disciplined rollout and treats the tools as the real version, not a hybrid.
What Brian missed as a self-implementer
The other half of Brian’s story is the part that pushed him to engage Lisa González. As Strety grew through 2025 to 17 full-time employees, profitable and scaling fast, the limits of self-implementation became visible to him in a specific way.
He attended an EOS Worldwide Great Boss Workshop in May 2025 and took a lot of notes. The realization that hit him there is the line he keeps coming back to in the newsletter:
“Wow, we’re only scratching the surface here.”
By the fall of 2025, he wrote, self-implementing EOS “started to feel like I was being negligent.” He felt in command of the Traction, Issues, and Data components from his BrightGauge years. He could see — clearly — that Strety wasn’t using the full depth of People, Vision, and Process. There were tools below the surface of the Six Key Components he hadn’t internalized.
The specific gaps Brian has named in his weekly newsletter:
- Process mastery. Lisa literally co-authored the EOS Traction Library book on Process. Strety’s Core Processes existed but weren’t getting the attention the Process Component requires.
- Mastery of the deeper tools. EOS has dozens of tools beyond the headline eight. Self-implementers tend to use the ones they’re already comfortable with and let the rest sit on the shelf.
- Outside perspective on blind spots. Brian’s framing: Strety hadn’t hit a ceiling, but the team was self-aware enough to know there were blind spots they couldn’t see on their own heading into a year where they planned to double ARR.
- Coaching on leadership growth. Brian has been clear that he wants Strety as a team to be “fluent and actively working toward mastery in the EOS tools, which can only be achieved with expert guidance.”
This is the part that’s hard to see from inside a self-implementation. The tools are running. The L10 happens every week. Rocks get set every quarter. The system looks healthy until someone with hundreds of session days under their belt asks the question that surfaces the gap.
Implementer-led vs. self-implemented: the practical differences
We’ve watched teams succeed and stall on both paths. The honest differences come down to four things:
| Implementer-led | Self-implemented | |
| Speed to traction | Most teams hit a working rhythm in 1–2 quarters | Often 4–6 quarters, frequently longer |
| Purity of adoption | High — Implementer keeps you honest to the model | Slippage is common (more on this below) |
| Objectivity in hard conversations | A neutral third party leads people-level talks | Whoever facilitates has skin in the game |
| Annual investment | Typically $18,000–$50,000 per year | Time, books, and internal facilitation hours |
The cost gap is real. EOS Implementers commonly charge $4,500–$6,600 per session day, with most engagements running 5–7 session days a year over a two-year period. That math is meaningful for a 15-person team.
The cost of skipping an Implementer is also real, just harder to see on a budget line.
EOS slippage is the biggest self-implementation risk
The biggest hazard of self-implementing is slow, mostly unintentional misapplication of the tools over time. Rocks become to-do lists. Issues become status updates. The L10 stretches into a 90-minute meeting that runs over every week. The Scorecard fills with vanity numbers nobody reviews.
This happens because no one in the room is positioned to push back. The CEO is too busy running the company to also be the EOS purist. The Integrator runs the meeting and has skin in every conversation they’d need to call out.
An Implementer’s value in those moments is the seat at the table. They’re paid to interrupt patterns the internal team can’t see anymore.
As Brian puts it in the newsletter: “EOS is simple, but not easy.” Mastery of simple-but-not-easy tools is where an Implementer earns the engagement.
Speed and “purity” of adoption
When you watch a leadership team run their first Focus Day with an experienced Implementer, the pace is jarring if you’re used to internal-only rollouts. The Implementer doesn’t let the team relitigate every term. They’ve seen 200+ V/TOs. They know which questions are about understanding the tool and which are about avoiding a hard answer.
That’s the speed advantage in practice. It comes from reps — hundreds of session days across dozens of leadership teams.
“Purity” is the related idea. An Implementer runs the EOS model the way it was designed, with all the discipline that comes with it — annual planning, quarterly sessions, weekly L10s, the Scorecard reviewed every week, the Accountability Chart kept current. Self-implementing teams tend to keep the parts that feel productive and let the parts that feel like overhead fall away. That’s usually where the value compounds.
A practical way to decide
If you’re genuinely on the fence, walk your team through these four questions:
- Does your leadership team struggle with accountability between meetings? An outside voice helps more than another internal initiative will.
- Do you need traction within the next two quarters? Implementers compress the timeline meaningfully.
- Can you absorb $18,000–$50,000 annually for the next two years? This is the honest budget conversation.
- Is your leadership team genuinely open to outside coaching? If half the team will dismiss an external voice, the engagement won’t work no matter how good the Implementer is.
A common pattern we’ve seen: companies self-implement for a year or two, learn what they don’t know, and then engage an Implementer with much sharper questions than they would have had on day one. That’s exactly Strety’s path, and Brian has been clear that it’s a fine route — the self-implementation years built genuine fluency in parts of the model, and the engagement with Lisa is sharpening the rest.
Fractional integrators and other operator partners
For some teams, the right next step isn’t an Implementer engagement at all — it’s a fractional Integrator or operator-for-hire who knows EOS and can sit in the seat with you.
Fractional Integrators are a real and growing category. Many run on EOS themselves, work alongside Visionaries who need help operationalizing the system, and bring deep operating experience that an Implementer (by design) doesn’t. At Strety, we partner closely with fractional Integrators and consider them part of the operator ecosystem we serve. Plenty of our customers run a combination — a fractional Integrator embedded in the business and an EOS Implementer coaching the leadership team quarterly. That stack works well.
Suzy Joeckel is a good example of how the seats relate to each other. She’s a Professional EOS Implementer and a fractional Integrator, having held the Integrator seat at multiple companies before becoming an Implementer. After watching an Implementer take one of her engagements from a year-long buildout down to 60 days, she changed how she works:
“From that point on, I never went into another company as an integrator without an Implementer.”
— Suzy Joeckel, EOS Implementer and Fractional Integrator (read the full case study)
The honest framing: fractional Integrators and Implementers solve different problems. An Implementer coaches your team on the EOS framework over a multi-year cadence. A fractional Integrator is an operator in your business. The combination is often stronger than either seat alone — which is exactly the pattern Suzy advocates for.
A few other adjacent categories worth knowing about:
- Unaccredited EOS coaches may have read the books and run sessions. Quality varies — without the EOS Worldwide accreditation, peer community, and ongoing training, the experience depends entirely on the individual.
- Industry consultants who layer EOS on top of vertical expertise can be helpful for technical problem-solving. They’re operating in a different lane from accredited Implementers, so evaluate them on that basis.
The short version: for pure EOS coaching, an Official EOS Implementer is the credentialed path. For operating support inside the business, fractional Integrators and EOS-fluent operators are a strong option, often in combination with an Implementer.
Where Strety fits, regardless of path
Software complements an Implementer. The right software changes how much value you get from either path.
Self-implementing teams use Strety as the system of record for their EOS tools — Rocks tracked between L10s, the Scorecard updated weekly, Issues captured as they surface. Implementer-led teams give their Implementer a real-time view of how the operating system is running between sessions, which is when the work actually happens. Teams working with fractional Integrators get a shared workspace that connects the operator’s day-to-day work to the broader leadership team’s cadence.
We’re an Official EOS Licensee™ and we built Strety to run the pure EOS tools faithfully, and to extend into the People, Projects, Performance, and Playbooks work that EOS doesn’t cover natively. Whichever path you pick, the tools should follow the process you’re running.
Frequently asked questions
Do I need an EOS Implementer to get started with EOS? You don’t strictly need one, and most teams get to working traction faster with one. Self-implementation is workable if your leadership team is disciplined and has prior experience running structured operating systems. Otherwise, the cost of an Implementer often pays back in time saved.
How much does an EOS Implementer cost? Typical engagements run $4,500–$6,600 per session day, with most companies investing $18,000–$50,000 annually over a two-year initial engagement. Costs vary by Implementer tier (Professional, Certified, Expert) and geography.
How long does a typical EOS Implementer engagement last? Most run roughly two years, covering Focus Day, two Vision Building Days, and quarterly sessions — usually 5–7 session days per year. After that, many teams move to a lighter cadence or graduate to self-management.
What’s the biggest risk of self-implementing EOS? Slow misapplication of the tools. Without an outside facilitator to push back, the model erodes over time. Rocks become to-do lists, the L10 stretches past 90 minutes, the Scorecard gathers dust. The pattern is hard to see from inside.
Can I switch from self-implementation to an Implementer later? Yes, and many companies do. Strety did. The handoff usually surfaces gaps the internal team had been working around, and the team comes in with sharper questions than they would have had on day one.
Will EOS work for my business? EOS is designed for owner-led businesses roughly 10–250 people across most industries. It works best for companies with a real leadership team, a willingness to be honest about issues, and the discipline to run weekly L10s consistently.
Choosing the path that actually fits
The right answer depends on your team’s discipline, budget, timeline, and tolerance for being told you’re doing it wrong.
If you’re starting from scratch and can afford one, engaging an Implementer is the most impactful step you can take to get EOS working in your business this year. If you’re going to self-implement, do it with eyes open about how easily the model erodes without an outside voice — and read Brian’s newsletter for what the eventual transition looks like in practice.
Either way, start your free 30-day trial of Strety and run your EOS tools in one place from day one. The software will make whichever path you pick easier to run.