Most MSPs Sponsor the Event, Write the Check, and Never Build a Plan. That's Why It Never Works.
October 16, 2026

Most MSPs Sponsor the Event, Write the Check, and Never Build a Plan. That's Why It Never Works.

Most MSPs have a starting line problem. They never decided, specifically, what they needed to get done before they started, so there is nothing real to measure once the work is underway. A lot of owners do not even know if they are running the right race in the first place, because nobody ever sat down and defined what the race actually was.

Here is where that shows up the most, and you have probably lived this yourself. You decides to sponsor an event. There is real excitement about it. A check gets written. A booth gets built, maybe some swag gets ordered, somebody picks out a good shirt for the team to wear.

Nobody stops to define a specific outcome before any of that happens. No target number of leads. No follow-up plan for the names collected at the booth. No one person responsible for working those leads once the event is over.

The sponsorship happens. People show up and have good conversations. And a few weeks later, nothing has come of it. Not because the event was a bad opportunity. Because nobody defined what success looked like before saying yes, and nobody built a plan to execute once the opportunity was already in hand.

I want you to notice something about that story. You spent a lot of money to be at the event and your goal was to get your name out there. Yes, you wanted to get leads coming into from the event and yes you also wanted to get assessments lined up for the weeks to come. You wanted an ROI for the event (that’s a no brainer). The problem is what you thought was a plan (getting your name out there) was actually not even a clear outcome. That is a planning problem wearing a marketing costume and no one on your team was the wiser to even do anything differently next time you sponsor something.

The planning gets skipped in the excitement of saying yes. Signing up for the event feels like progress, because it feels like doing something. It is not progress. It is a starting gun going off with no course mapped out yet.

Here is the part most people get backwards. The hard part, and the part almost everyone skips, is deciding the specific metric and the plan to hit it before anything starts. That front loaded work feels like it is slowing you down in the moment, because you are sitting there thinking instead of doing. But once it is done, everything after it actually gets easier, because every decision you make from that point forward has something real to check itself against. Skipping that step does not save you time. It just moves all the confusion to the end, right when it is too late to fix anything.

Think about this the way you would think about a race. If you do not know what race you are running, it does not matter how fast you run it. You can work harder than anyone else in the industry and still finish nowhere because effort without a defined target is not the same thing as progress toward one.

Even if you are running the right race, if you take it slow in the first half planning to make it up later, you almost never do. The gap you create early just keeps compounding against you the rest of the way. This is true in a five kilometer race. It is true in a ninety day technician evaluation. It is true in a quarter long initiative you are running across your whole team.

This exact failure happens with people just as often as it happens with events. An owner sets a vague expectation for a technician, something like be better at communication or be more proactive. Ninety days later, nobody can say with any confidence whether that person actually improved, because there was never a number attached to check it against. Compare that to a technician given a specific target from day one, say resolving eighty percent of tickets without escalation.

Everyone involved, the technician, their manager, you, knows exactly where that person stands at any point along the way. One of these situations gives you a real answer at the end. The other one gives you a feeling, and feelings are a terrible way to run a business.

Here is the fix, and it applies whether you are deciding on an event, a new hire's evaluation period, or any new initiative you are about to roll out. Before you commit to anything, write down the specific metric that defines success, and write down the plan for actually hitting it.

If you cannot state that metric as a number or a clear yes or no, you are not ready to start yet, no matter how good the opportunity looks sitting in front of you. This applies to the next event somebody pitches you on sponsoring. It applies to the next technician you hire. It applies to the next big idea that gets everyone in the room excited before anyone has asked what winning actually looks like.

When you do this up front, you always know whether you are on track, which means you get to adjust early instead of finding out three months in that the money or the time is already gone and nothing came of it. That is the real value of front loading this work. It is not more effort. It is knowing, the entire way through, whether you are actually winning or just staying busy.

 

Before any hire, any initiative, any dollar spent outside your core service delivery, define the metric and the plan first. If you want help building that discipline into how your business runs day to day, that is exactly what we work on at www.builttorunmsp.com.

 

Frequently Asked Questions

Why do event sponsorships often fail to produce results for MSPs?

Because the outcome is never defined before the money is spent. Without a specific target, like a number of qualified leads or booked follow-up meetings, and a plan for working those leads afterward, the sponsorship ends with good conversations and nothing to show for them.

What does it mean to front load a project or initiative?

It means deciding the specific metric for success and the plan for hitting it before any work begins, rather than figuring it out as you go. This feels slower at the start but makes every decision afterward easier, because there is something concrete to measure progress against.

How should an MSP owner evaluate a new technician's performance?

Set a specific, measurable target from day one, such as a percentage of tickets resolved without escalation, rather than a vague expectation like being more proactive. A specific target lets both the technician and the owner know exactly where things stand at any point during the evaluation period, instead of only finding out at the end.

Why does a slow start matter so much if there is still time left to improve?

Early progress, or the lack of it, sets the ceiling for everything that follows, because a gap created early compounds rather than staying fixed. This is true in a race and it is equally true in a quarterly initiative or a new hire's evaluation window.

About the author
Adam Kuester

Adam Kuester

Adam Kuester has a PhD in genetics and a career built inside managed services, an unusual combination that shapes how he works. He spent time designing operations at an MSP before joining Bruce McCully to build Galactic Advisors, where he's served as VP of Special Projects. His focus has been operational: finding gaps, building systems, and turning expertise into tools MSP owners can use across a partner base of nearly 1,000 companies. Built to Run MSP is that same work in a different form, practical frameworks for MSP owners who are good at winning business and want to get equally good at running it.