How Implementing EOS Fueled Fuelius' Growth and Efficiency
Key Takeaways
- Starting with an honest EOS assessment exposes the real gaps in your organization - even when the scores are uncomfortably low
- The accountability chart forces clarity about roles that informal structures avoid - every seat needs the right person
- Rocks should be specific, measurable quarterly objectives - not vague goals that are easy to claim as complete
- Scorecards and KPIs only work when the team reviews them weekly and takes action on off-track numbers
- The visionary and integrator roles need clear boundaries - overlap creates confusion and slows decision-making
- Involving the right people in EOS implementation from the start prevents resistance and rework later
Gray MacKenzie is joined by Paul Earnden, Managing Director and Integrator at Fuelius, to explore how EOS (the Entrepreneurial Operating System) fueled the agency’s growth and operational efficiency. Fuelius is a UK-based growth marketing agency that operates as a sub-brand of Prodo, working with scaling companies to connect their customer journey through CRM enablement, inbound marketing, and web development. Paul brings a candid perspective on what it actually takes to implement EOS - including where they struggled and what made the difference.
Fuelius’ Origin Story and the Visionary-Integrator Dynamic
Paul shares the backstory of Fuelius and how it emerged from the broader Prodo organization. The decision to create a focused sub-brand for growth marketing required not just a new go-to-market strategy but a rethinking of internal operations. As Managing Director, Paul naturally fell into the Integrator role - the person responsible for running the day-to-day operations, managing the team, and executing on the vision.
The visionary-integrator dynamic is one of the foundational concepts in EOS, and Paul discusses how establishing clear boundaries between the two roles eliminated confusion and accelerated decision-making. Before EOS, the overlap between strategic direction and operational execution created bottlenecks. With clear role definitions, both sides could operate with autonomy while staying aligned on the bigger picture.
The Honest Starting Point: A Low EOS Assessment Score
One of the most revealing moments in Fuelius’ EOS journey was their initial organizational checkup. The assessment scored the agency well below where leadership expected. Rather than getting defensive, Paul and the team used the low score as a catalyst for change.
Paul explains that the assessment revealed blind spots that informal management had been masking. The team had built workarounds for communication gaps, unclear ownership, and inconsistent goal-setting. The EOS assessment stripped those away and forced honest conversations about where the organization actually stood versus where they thought they were.
Accountability Charts, Rocks, and Scorecards
The episode dives deep into the practical EOS tools that made the biggest difference at Fuelius.
The accountability chart replaced the traditional org chart with something more functional. Rather than just showing reporting lines, it defined the key responsibilities for each seat and made it clear who was accountable for what. Paul describes how this exercise surfaced cases where responsibilities were shared or unclear - and how resolving those ambiguities immediately improved execution speed.
Rocks - the quarterly objectives that drive the EOS rhythm - became Fuelius’ primary tool for translating annual goals into actionable work. Paul emphasizes the importance of making Rocks specific and measurable rather than broad and aspirational. A Rock like “improve client satisfaction” is too vague to drive behavior. A Rock like “implement a monthly client review process for all accounts by end of Q2” gives the team something concrete to deliver against.
Scorecards and KPIs rounded out the operational picture. Paul discusses how the team established weekly scorecard reviews to track the leading and lagging indicators that matter most. The key is not just collecting the data but actually using it - when a number is off-track, the team has a structured process for identifying the root cause and assigning corrective action during their L10 meetings.
Implementation Mistakes and Lessons Learned
Paul does not shy away from discussing where Fuelius stumbled during implementation. One significant challenge was timing - bringing the right people into the EOS process at the right stage. Early on, they involved team members who were not yet in the right seats, which created confusion and resistance. The lesson was that the leadership team needs to be aligned and committed before cascading EOS to the broader organization.
Another mistake was underestimating the ongoing discipline required. EOS is not a one-time setup - it is a weekly, quarterly, and annual operating rhythm. Paul describes periods where the team let meeting cadences slip or allowed Rocks to go unreviewed, and how quickly the benefits eroded when that happened.
The Tech Stack for Running EOS
Paul shares how Fuelius manages the tooling side of running EOS. The team uses Ninety.io as their dedicated EOS platform alongside their broader project management and marketing technology stack. The conversation covers the practical considerations of managing EOS data in a dedicated tool versus trying to run everything through a general-purpose platform.
The team also uses Harvest for time tracking, Jira for development work, and Riverside for podcast production - illustrating how a well-defined tech stack with clear tool boundaries supports operational clarity.
Resources Mentioned
- Paul Earnden on LinkedIn - Managing Director at Fuelius
- Fuelius - Growth marketing agency
- Prodo - Parent organization
- Ninety.io - EOS software platform
- Fuel Your Funnel Podcast - Fuelius’ podcast