Show Notes: Inside the 90™ Episode #35
Getting EOS running is one thing. Building the ecosystem around it is another.
On this episode, Andrew and Jami sit down with Cam Lawson to map out everything outside the core EOS toolset that strengthens an implementation — the software, the communities, the vendor relationships, and the team-health work that most companies discover too late they need.
Pick Your Software Early, Then Grow Into It
A dedicated EOS tool isn't optional overhead — it's what turns Traction concepts into daily habits. Cam's own EOS rollout in 2019 ran entirely in 90.io from day one, and he's watched teams gain traction faster simply because the tool was ready to go: L10 agenda, V/TO structure, and accountability chart built in, not bolted on.
The alternative is familiar to almost every leadership team.
Spreadsheets. Whiteboards. An issues list that only lives in one conference room.
Andrew ran his own team in ClickUp for years before switching, and both hosts agree the shift changes more than logistics — it changes how you think.
• Keep the separation. A dedicated EOS tool isn't your CRM or project management system — it holds you accountable to what you told your team you'd deliver, distinct from your day-to-day task list.
• Let scorecards nest. As you roll L10s out to more teams, metrics can roll up from department-level scorecards into a single smart measurable at the leadership level.
• Don't over-build on day one. Cam has seen a 300-person company try to onboard everyone into a tool at once before the leadership team had even internalized rocks and scorecards — it was, in his words, a nightmare.
You don't have to have all the answers on day one. Track the scorecard in Excel if that's what it takes to figure out the mechanics — the system comes next.
Find Your Community — But Don't Drown In It
EOS runs on shared language, and shared language is easiest to build inside a community of people also running it. Cam walks through the landscape, and it's bigger than most leadership teams realize.
• EOS Academy. Available through eosworldwide.com, with community access and tool training built in.
• Rocket Fuel University. Built specifically for visionary and integrator pairs.
• EOS Self Implementers Unite (Facebook). A help-first group for companies self-implementing EOS, with implementers like Andrew answering questions daily.
• Traction & EOS Users (LinkedIn). Skews toward key-executive and sales-driven roles, and toward implementers.
• The EOS subreddit. Heavy on early-stage questions and, per Cam, the most fear of any group — a good place to give newcomers quick, reassuring answers.
• ENRG chapters. Geographically based groups led by an experienced integrator, built around the idea that companies running EOS want to network with other companies running EOS. They went from one chapter to 60 in under a year.
The one Cam and Andrew put in a category of its own is the annual EOS Conference — next year in Kansas City, late April 2026.
Andrew describes it as the linchpin that connects every other community on this list, and the fastest way to figure out which of these groups actually fits your organization.
Work With Vendors Who Speak the Same Language
An EOS-run business doesn't just tolerate the framework — it filters who it works with by it. Andrew makes the case that shared language changes the nature of a vendor relationship, not just the vocabulary.
Wonder's own fit with EOS clients wasn't an arbitrage play.
It came from a natural overlap: clients who've done the work to define a V/TO already have the clarity a strong brand strategy requires, and shared core values make the working relationship easier to build accountability into.
• Ask the real qualifying questions. Current rocks, scorecard measurables, and when their L10 happens — if a self-described "EOS company" can't answer those, the shared value isn't there.
• Expect a proven process. Vendors built around EOS clients, like recruiting or sales-acceleration partners, tend to show up with a demonstrable process rather than a pitch.
Cam's warning to anyone eyeing EOS companies as a market to sell into: run on EOS yourself first.
With roughly 300,000 businesses on the framework, it's a visible opportunity — but treating it as an arbitrage moment instead of a shared discipline gets noticed fast.
Strengthen Team Health Every Quarter
Vision and traction are objective. Health is the hard one to measure — and the one most leaders quietly deprioritize. Cam frames this section around trust builders: the practice of doing something for team health roughly every 90 days.
• Kolbe. Measures conative instinct rather than personality or intellect — the natural, hard-to-articulate way someone approaches a problem. Cam credits it with resolving recurring friction with a former colleague once their Kolbe results made a quick-start/stabilizer mismatch visible.
• Six Working Genius. Pairs well with Kolbe by surfacing preference alongside instinct, and is especially useful for building a team that covers wonder, invention, discernment, and execution rather than clustering in one zone.
• Seven Critical Needs. A simple 1–10 survey tied to employee engagement — belonging, believing, being accountable, being measured, being heard, being balanced, and being developed — that maps straight back to existing EOS tools like L10s and quarterly conversations.
• The EOS Organizational Checkup. Measures how well the tools are being implemented from leadership's view, and pairs naturally with the Seven Critical Needs survey to compare the team's internal experience against it.
Cam's caution: use one assessment as your team's shared baseline rather than rotating through every option available.
The value isn't the test itself — it's the common language it gives a team for talking through friction.
Final Takeaway: Foundation First, Everything Else Second
Every tool, community, and partnership on this list is designed to support the five foundational tools of EOS — not replace them.
Cam's rough sequencing: bring in software from day one, get to the EOS Conference as soon as you can, hold off on the broader communities for six to nine months so they don't overwhelm early implementation, and build team health work into every quarter from the start.
Get the foundation solid first — the ecosystem only makes a strong implementation stronger, not a shaky one stable.
Recent Posts









