How to Build an EOS® Implementer Practice From Day One

Most Implementers who stall don't stall because they lack ability. They stall because they treat building a practice as a knowledge problem, when it's really a discipline problem.

I've watched it happen the same way for years.

Someone finishes boot camp, does a bit of biz dev, hits a stretch where it isn't working yet, and decides the answer must be more learning. So they go on a search. This tool, that course, some other methodology. Meanwhile the thing that actually builds a practice, the boring repeated checklist, sits half-done.

I built my practice from January 2015 while still running nine other companies, and as Visionary I've watched 762 Implementers come into the community since 2020. The ones who take off don't know more than the ones who don't. They do a small number of things relentlessly. This is what those things are.

Get a Focus Day on the calendar in your first 90 days

If you take one thing from this, take this.

There's a direct line between when you land your first Focus Day and whether you build the practice you want. The Implementers who get their first Focus Day within ninety days of boot camp, in my experience, every one of them makes it. On the other side of that line, over the last six years, I can count the Implementers still in the community who didn't have a Focus Day in their first ninety days. It's about two.

So point everything in your first quarter at one outcome: a booked Focus Day. Not more learning, not polishing your materials, not getting comfortable. A paying client with a date on the calendar.

Treat your first seven days like you were shot out of a cannon

The first week out of boot camp matters more than any week that follows, because it's when an identity shift has to happen, and identity shifts don't wait politely.

You're known in your network as whatever you were before. I was the pharma biotech guy, former Johnson & Johnson. That's who my contacts thought they knew. Becoming an Implementer meant becoming someone else in their eyes, and I had to force it.

A mentor of mine, Ed Callahan, told me to go into my LinkedIn "and just unfriend every pharma biotech person because you have to go through an identity change."

So I did: I literally disconnected from my old world, made the shift, and then reconnected. It sounds drastic, but that was the point. You have to leave the past in the past and put on the identity of an Implementer, deliberately, in week one.

Do your own version of that. Whatever you were before, make the break clean enough and public enough that you start to believe it yourself.

Learn just in time, not just in case

New Implementers burn enormous energy learning content they can't use yet.

Don't sit in base camp trying to learn everything. If you don't have a Focus Day booked, you have no business learning VB1 or VB2 content. It's a waste of time, and worse, it feels like progress while you avoid the real work.

Master the 90-minute meeting first. That's the thing standing between you and a booked Focus Day. 

Then book a Focus Day, have your oh-crap moment, and learn Focus Day content because you finally need it. Book a VB1, then learn VB1. These are tomorrow problems, and you solve them tomorrow, not today.

Lead with help, and let the 4-2-1 do its work

I never charged a dime for a Vistage talk. I did countless SCORE talks, chamber talks, and EO forum talks, all for free. Not out of charity, though it felt good, but because it worked.

The old Zig Ziglar idea holds up: help enough people get what they want and you'll get what you want. Follow the 4-2-1 biz dev rhythm, keep generating the activity, stay in motion, and the clients come. They tend to arrive in batches rather than a smooth trickle, so don't panic in the quiet stretches. Your job is to keep feeding the top of it.

If you want the masterclass in this, Don Tinney and I recorded a video on our YouTube channel in Australia, about an hour and twenty minutes, walking through how Don built his practice. It's the most help-first, relational, intentional method you'll find. I'll be honest that I always ran more transactional than Don does, but the principle underneath is the same. Be useful first, at volume, without keeping score.

Understand the 15 and the 85

This split reorganized how I think about the job.

Being EOS® pure, teaching the tools exactly as they're meant to be taught, is about "fifteen percent of what it is we do in a day."

That fifteen percent matters, because teaching the tool purely is how you set the context and sell it. But it's only fifteen percent.

The other eighty-five percent is the client sitting there thinking “Huh, I'm not sure what to do with that”.

That eighty-five percent is you: storytelling, coaching, facilitating, and above all concluding. You pull every arrow out of your quiver to get the team to a decision with a tidy bow on it.

Nobody can hand you that eighty-five percent in a classroom. The way we learn it is experiential: "we teach you something, we send you off, you go do it, you come back, we clean you up."So stop waiting to be trained into competence. The competence is on the other side of the reps.

Sell in your own style

There's a persistent rumor that some Implementers can't sell but are brilliant in the session room. I think that's "like chupacabra." There are rumors of it, but I've never seen one.

The reason it can't exist is simple. Everything you do in the session room is selling. When you're in front of a leadership team, "you are selling the crap out of a tool to get them to go do things that are good for them." That's the eighty-five percent. If you can't do that, you can't sell anything, and the room falls apart.

So don't imagine selling and facilitating are two different muscles, they're the same. Learn to sell, but in your own style, because everyone has their own way of helping. The one rule I'd hold you to is the one Shelley Woodrow puts well: the you who gives the talk has to be the same you who runs the room.

If those are two different people, prospects feel it.

Be someone worth hiring

Come back to the thing underneath all of it: your clients want to become you.

They live in chaos, so you need to be the calm, disciplined, focused person they wish they were. That's not a pose, it's a standard you hold yourself to. I built my week around it using the free, focus, and buffer day discipline I learned from Dan Sullivan at Strategic Coach. 

Monday is a buffer day: you take your calls, watch the videos, clean up your pipeline. Session days are focus days. Then you buffer, then you take real free days. The discipline is visible to clients, and it's part of what they're buying.

I invested like I believed it, too. I spent about $150,000 a year on my own development, every year, on facilitation, coaching, negotiation, speaking, and storytelling. Not because I had money to burn, but because clients deserve the best version of me, and the person they want to become is not standing still.

One small tell of this: keep your VTH call short. Mine averaged about seven minutes. Who wants to hire someone who has infinite amounts of time? A short call signals that you're busy and disciplined, and it gets them into the 90-minute meeting where the real work starts.

What goes wrong

A few predictable ways this breaks, all of which I've either done myself or watched up close.

You stop selling the moment you get busy delivering. There's an up-down, up-down rhythm to this work. You can only onboard about four clients a quarter well, and when you're heads-down on delivery you go quiet on biz dev. Then delivery ends and your pipeline is empty. Keep a trickle of biz dev alive even in your busiest stretches.

You wait on referrals you can't predict.

I got lucky with a couple of super connectors, one of whom has referred something like three hundred Focus Days by my count. But most clients are not super connectors, and you can't build a plan on lightning striking. Keep asking, keep helping, and treat a super connector as a gift rather than a strategy.

The differentiating moment "is when you don't think it works and you keep going doing it anyway." The Implementers who take off are the ones who kept running the checklist through the stretch where they were sure it was broken. The ones who stall are the ones who went looking for a better checklist instead.