011011
Back to Blog
Operations

How We Use EOS to Run PiCode Solutions

March 27, 20257 min read

Introduction

Running a software company isn't just about writing good code — it's about building a system that keeps the team aligned, focused, and accountable. That's why we adopted the Entrepreneurial Operating System (EOS) at PiCode Solutions.

EOS is a practical framework for running a business. It gives us a shared language and a set of tools to manage priorities, solve problems, and track execution — without drowning in process.

Here's how we use it day to day.

The Level 10 Meeting (L10)

The L10 is our weekly pulse. Every week, the team meets for a structured 90-minute session that follows the same agenda:

  • Scorecard review — Are we hitting our numbers?
  • Rock check-in — Are we on track for our quarterly priorities?
  • To-do review — Did last week's commitments get done?
  • IDS (Identify, Discuss, Solve) — We surface issues, discuss them, and resolve them with clear action items.

The consistency is the point. We don't waste time deciding what to talk about — the format keeps us efficient and focused on what matters.

Scorecard

The Scorecard is how we measure the health of the business on a weekly basis. Instead of waiting for quarterly reviews to find out something's off, we track a handful of key numbers every week:

  • Active project count
  • Sprint velocity
  • Client satisfaction scores
  • Revenue targets
  • Support response time

If a number is off track, it surfaces in the L10 and goes straight into IDS. No surprises, no delayed reactions.

Rocks (Quarterly Priorities)

Every quarter, each team member sets Rocks — the 3 to 7 most important things they need to accomplish in the next 90 days. Rocks are specific, measurable, and time-bound.

For example, a Rock might be:

  • "Ship v2 of the billing module by end of Q1"
  • "Complete Azure migration for Client X"
  • "Hire and onboard a senior .NET developer"

Rocks keep us honest. They prevent the classic trap of being "busy" without making progress on what actually matters.

Quarterly Conversations

At the end of each quarter, we do a Quarterly Conversation with every team member. This isn't a formal performance review — it's a two-way check-in:

  • How did your Rocks go?
  • What's working? What's not?
  • Are you in the right seat?
  • What do you need from the company?

These conversations build trust and catch issues early — before they turn into bigger problems.

The Accountability Chart

EOS replaces the traditional org chart with an Accountability Chart. Instead of job titles, we define seats by function and the key responsibilities each seat owns.

This clarity matters. When everyone knows who owns what, there's less confusion, fewer dropped balls, and faster decision-making.

The Vision/Traction Organizer (V/TO)

The V/TO is our one-page strategic plan. It captures:

  • Core Values — What we stand for
  • Core Focus — Our purpose and niche
  • 10-Year Target — Where we're headed long-term
  • 3-Year Picture — What the company looks like in 3 years
  • 1-Year Plan — Revenue targets, priorities, and budget
  • Quarterly Rocks — The next 90 days

Having this on a single page means everyone can see the big picture and understand how their work connects to the company's direction.

Why It Works for Us

EOS isn't about adding bureaucracy — it's about removing ambiguity. For a team our size, the framework gives us just enough structure to:

  • Stay aligned on what matters most
  • Surface problems early through weekly check-ins
  • Execute consistently with 90-day planning cycles
  • Maintain accountability without micromanaging

We're not a massive enterprise — we're a focused team building software for clients who depend on us. EOS gives us the discipline to deliver reliably, sprint after sprint, quarter after quarter.

Conclusion

If you're running a small to mid-size software team and feel like things are slipping through the cracks, EOS is worth a serious look. It won't solve every problem, but it will give you a framework to find and fix them faster.

We've been running on EOS since early on at PiCode, and it's become a core part of how we operate. The tools are simple — the consistency is what makes them powerful.

Need help with your architecture?

We'd love to discuss your technical challenges.