Most owners register for a channel event hoping to level up. They want to think differently, fix something they have been stuck on for a year, and come home a better operator.
Then they walk the vendor hall.
Four days later they land with a backpack full of branded socks, a demo scheduled with a vendor they had never heard of on Monday, and 20 items on a list they will never finish. The development goal quietly turned into a purchase decision. Nobody planned that. It happens anyway.
This page treats an event the way you should treat any other line item over $4,000. A budget decision with a defined return. The return is not leads. It is not swag. It is one change in your business inside 30 days.
Built on the Sales and Marketing Checklist for Technology Vendors Attending a Channel Event, published by the GTIA Channel Development Advisory Council. The original is written for the people working the booth, with a 12 week runway, a marketing team, and a budget for staff t-shirts. This version flips it for the owner walking the floor.
First, run the real number
Ask most owners what an event costs and they quote the ticket price. The ticket is the smallest part.
Fill this in before you register.
- Conference ticket
- Flights
- Hotel, nights times rate, including the two travel days you forget about
- Ground transportation, parking, bags
- Meals not covered by the event
- Any pre-day or post-day workshop fees
- Your time out of the business, four to five days
- Your team's time if anyone goes with you
For a single owner at a national event, most shops land between $3,500 and $5,500 all in, before you count the time. Add two team members and you are past $12,000. That is a real hire's worth of training budget spent in four days.
Write the number down in a note on your phone. You will look at it again in four weeks. Owners who skip this step never actually know if the trip worked.
What you are actually buying
Three things come out of a channel event. Only one of them is worth planning for.
Stack decisions. You replace a tool, consolidate two vendors, or renegotiate terms. Real money, easy to measure. Also the thing you will drift toward without meaning to, because the vendor hall is engineered to produce it.
Owner and leadership development. You stop doing something that has cost you for two years because someone three steps ahead told you to stop. Slower to show up in the P&L. Worth far more.
Peer relationships. Overflow work, subcontracting, warm intros, someone to call when you are about to make a bad decision. This compounds.
The pattern I see in the field is that owners budget for development and come home with purchases. They pay for a leadership investment and receive a procurement event.
Development is the priority. Make the trip about your own capability as an operator, and treat any stack change as a side effect you deliberately chose, not something that happened to you in aisle three.
The rule: one change in 30 days
You do not measure an event at the event. Everyone feels great on day three. The energy in the hallway is not data.
Thirty days after you get home, has something in your business actually changed?
Not a new idea. Not a document. A change. You fired a client. You raised your minimum. You changed how you run your Monday meeting. You moved a person out of a role they were failing in. You put a number on a metric you had been guessing at.
One change. Not five. Owners who come home with five changes make zero.
Write the change on your calendar before you leave for the airport. Put a reminder 30 days out with the words "did this happen." That reminder is the entire scoreboard.
Choosing which event to attend
There is a channel event every week. You cannot attend them all and still run your shop. Filter on the change you are trying to make.
Start with the problem, not the agenda
Before you look at a single event website, finish this sentence in writing.
"The thing I am stuck on in my business right now is ____________."
Be specific. "Growth" is not a problem. These are problems:
"I cannot get my techs to document anything." "My service manager is drowning and I do not know whether to hire under him or replace him." "My EBITDA is 8 percent and I do not know which of my three service lines is dragging it down." "My close rate on new MRR dropped and I do not know why."
Now judge every event against that sentence. Does the agenda address it? Do the peers in that room have it solved? Is there a track, a workshop, or a peer session where you get to say it out loud to people who have been there?
If the honest answer is no, that is not your event this year. Pick a different one.
Then check the rest
- Look at the published lists at the start of the year and again each quarter. Dave Seibert's industry calendar, Channel Program, Tech Degenerates, and Tubblog all track them.
- Regional events cost a fraction of national ones. For a first event or a tight budget, start regional.
- Check whether your state or region funds training grants. Some cover conference fees outright.
- Check whether your trade association membership already includes access.
- Look at pre-day and post-day workshops. That is often where the real work happens, in a smaller room, with fewer vendor pitches.
- Ask your accountant how you are categorizing this. Training and development, not marketing.
- Consider stepping outside the channel entirely. A general business operations or leadership event has no vendor hall trying to sell you a PSA, and the peer conversations are frequently better.
Who goes
Default answer for a shop your size is one person, usually you.
Send someone else instead of you when they own the problem. If the problem is service delivery, your service manager goes and you stay home. If the problem is you, you go alone.
Send a second person only when all three are true. They own a problem you want solved. They will talk to strangers, because some of your best people will hide and watch sessions on the hotel TV, which is a waste of $4,000. And you can cover their seat for three days without it turning into a fire.
Do not send someone as a reward. Do not send your most technical person to evaluate AI tooling, because they will optimize for the most interesting problem in the room instead of the one that moves margin. That mistake costs shops real money every year.
If you do send someone, send them with an assignment. Word for word, before you book their flight.
You are going to [EVENT NAME] with me on [DATES]. This is not a trip, it is work.
Your job while you are there:
- Own this problem: [SPECIFIC PROBLEM]. Come back with three ways other shops handle it.
- Meet five people who do your job at other MSPs. Get their contact info, not their business card in a pile.
- Eat every meal with people you do not know. Not with me, not with each other.
- Sit in [SPECIFIC SESSIONS OR TRACK].
When we get back we are going to sit down for 30 minutes and go through what you learned. Take notes as you go so you are not reconstructing it from memory.
The timeline
12 weeks out
- Write the problem sentence. One problem. In writing.
- Write the decision you want to make when you get home. "By September 30, I will have decided whether to hire a service manager or promote from inside."
- Pick the event that fits that decision. Register early for the discount.
- Build the full cost number and put it in the budget.
- Book travel while it is cheap. Room blocks fill.
8 weeks out
- Build your people list. Eight to twelve names. Weight it toward owners at your size or one step ahead. A shop at 40 seats has already solved what you are hitting at 22. A shop at 400 solved it a different way and their answer will not fit you.
- Reach out now. This is the highest return 20 minutes of the whole trip and most people skip it.
- Book the pre-day or post-day workshop if one fits your problem.
- Pick three sessions for the whole event and leave the rest of your calendar open. The open time is where the value is. Pick by speaker, not by title. Session titles are marketing. An owner who has run a shop your size gives you something different than a vendor's channel chief with a slide deck.
Reach out on LinkedIn. Keep it this short.
Hi [NAME], I saw you are going to be at [EVENT]. I run a [SIZE] person MSP in [CITY] and we are wrestling with [PROBLEM]. Looks like you are a couple steps ahead of us on that.
Any interest in grabbing coffee or breakfast one of the mornings? I am not selling anything, I just want to hear how you handled it.
Roughly half will say yes, and the ones who say yes turn into the relationships that outlast the event.
6 weeks out
- Confirm the meetings you requested. Chase the quiet ones once.
- Block your calendar for the event days. Fully block them.
- Tell your team you are actually gone. Name the escalation path, who decides what while you are out, and what actually reaches your phone. Give whoever is covering decision authority in writing so they do not have to call you.
4 weeks out
- Sharpen your question. Write the two or three sentence version of your problem you will say out loud to a stranger at breakfast. Practice until it is short.
- Finalize your gap list for the vendor hall. Which products in your stack are failing, expiring, or getting replaced this year.
- Order business cards with white space on the back so you can write on them. Yes, still. Digital cards fail when the WiFi does.
2 weeks out
- Confirm everything. Meetings, flights, hotel, workshops.
- Put the debrief on your calendar now. Ninety minutes, two days after you land.
- Put the 30 day check on your calendar now. Same reminder, same words.
- Pack. Chargers, cards, medication, bandages, hydration packets, antacids, gum, a water bottle, snacks. Conference floors are hard and the food is unpredictable.
At the event
Meals are the event. Breakfast, lunch, dinner, and the hallway between them. Two rules. Never eat alone, and never eat with your own team. You can talk to your service manager any Tuesday. Sit at a table with an empty chair, stick your hand out, and start. Breakfast is the most underused networking hour of the entire event.
Lead with your problem. Small talk goes nowhere. "How's business" gets you "busy" and then you both look at your phones. Try this instead.
"What are you stuck on right now?"
Then shut up and listen. When they finish, tell them yours. You will get better answers in six minutes than in a full day of sessions.
Three questions that open people up:
- What are you stuck on right now?
- What did you try that did not work?
- Who else should I be talking to here?
That third one matters most. One good conversation turns into three introductions.
Say your problem out loud to at least ten people. That is the job. The answer usually comes from the fourth or fifth person, not the first.
Take notes the same day. Not later. Your memory of day one is gone by day three. Keep it to five lines per person.
- Name and company
- Size and market
- What they are struggling with
- What they told me that I want to steal
- What I promised them
That last line is the one people skip and the one that builds trust. If you said you would send your onboarding checklist, send it.
Take session notes in two columns. Left column, things that move my change. Right column, everything else. The right column is the shiny object pile and you will deal with it later.
Connect in the moment. Send the LinkedIn request while you are standing there, with a one line note about what you talked about. Not in the cab, not on the plane.
Do not work from the event. If you are answering tickets in the back of a session you paid $4,000 to sit in, go home. That is the most expensive way to answer email ever invented.
Set a limit on the evenings. The parties are real and the conversations there are good. You are also worthless at 8am if you close the bar, and the 8am conversations are better than the 11pm ones. Pick your nights. Two out of three. Manage your drinking. Nobody hires the guy who was a mess on night two.
Check in with your people nightly if you brought any. Fifteen minutes, standing up, in the lobby. Who did you meet, what did you learn, what are you doing tomorrow. It keeps them from disappearing into their room and it doubles what you bring home.
The vendor hall
Do not skip it. Vendors underwrite these events and cut your ticket price by more than half. Walk the floor, be respectful, thank the reps for being there. Then go in with rules.
You make no buying decisions at the event. None. Not a signature, not a verbal, not a "send me the paperwork." Everything goes on a parking lot list.
Only shop your gaps. A vendor solving a problem you do not have is not an opportunity. It is a distraction with a booth.
Thirty day cooling period on any new spend. If the tool is still the right answer a month later when the energy has worn off, buy it then. Most are not.
Cap your demos at two or three. Twelve demos scheduled from the floor means twelve hours of your team's time next month and eleven no thank yous.
Vetting questions worth preparing:
- Who is your smallest happy customer, and how many seats do they have?
- What does month one actually look like, hour by hour, for my team?
- What breaks most often for shops my size?
- Who owns the integration when it fails, you or me?
- What does this replace in my stack, and what does it not replace?
The best conversations are frequently in the back row, at the smaller booths, with the people who built the thing. Walk the whole floor.
After
Within 48 hours
Everyone waits a week. By then you are a name they cannot place.
Hi [NAME], good meeting you at [EVENT]. You mentioned [SPECIFIC THING THEY SAID] and I have not stopped thinking about it.
Here is that [THING YOU PROMISED] I said I would send.
I would like to keep talking. Are you open to a 30 minute call in a couple weeks?
Short, specific, referencing the actual conversation. Ten good ones beat sixty templates.
Two days after you land, run the debrief
Ninety minutes, already on your calendar. Alone, or with whoever went.
Everything in the right column of your notes moves to a parking lot list you review next quarter. Do not action it now. From the left column, pick the one change. Just one. Put an owner and a date on it. Then throw the rest away. You can go back to the notes next quarter.
If you sent someone, give them 30 minutes and four questions.
- What did you learn about the problem I gave you?
- Who did you meet that we should stay in touch with?
- What are other shops doing that we are not?
- What is one thing you want to change here?
Then actually let them change one thing. If you send someone to a conference and nothing they bring back gets implemented, you taught them the trip was theater.
Share one thing you learned with your team. Not twenty. One.
Week one
Make the decision you went there to make, now, while the input is fresh. Tell someone out loud so you are on the hook for it. Schedule any vendor demos that survived your gap list, and only those.
Book the second conversation
Peer relationships die without a second touch. A conference handshake with no follow up is a contact, not a relationship.
Get one call on the calendar with three of the people you met. Thirty minutes each, no agenda beyond comparing notes on the problem you both have. Two of those three turn into people you call when something breaks. That is the entire return on the trip.
Day 30, score it against your number
Open the note on your phone with the cost in it. Two questions.
Did I change anything in my business because of this? Do I have two or three people I can now call?
If yes to both, the event paid for itself. Write down what made it work so you repeat it, and book the next one early. If no, figure out why. Wrong event, wrong problem, or no follow through. Then decide whether you are going back.
Mistakes that waste the money
Seagulling. You fly in, generate 20 new initiatives, dump them on your team, and fly out. Your team hates event season because of this. One change.
No goal. Showing up to see what happens produces exactly what happens, which is a bag of swag.
Working through it. You paid for the room, the flight, and the ticket, then spent the event on Teams.
Sending the wrong person. Send the person who owns the problem, or do not send anyone.
Measuring at the event. Everyone feels great on day three. Feelings are not the scoreboard. Thirty days is.
Buying on the floor. Every stack change should trace back to a gap you identified before you got on the plane.
The part nobody tells you
The owners who get the most out of these events are not the smartest people in the room. They are the ones who show up with a specific problem, ask for help out loud, and follow up when they get home.
That is it. Everything above is scaffolding around those three things.
Talk it through
Go in with one problem. Come home with one decision. Make one change in 30 days. The harder question is which problem is worth taking to a room full of your peers in the first place, because most owners pick the loudest one instead of the expensive one.
Everything above is a template. Run it yourself this week and never talk to me. What I will not do is hand you a system and tell you your shop is wrong for not matching it.
Not sure this is your actual constraint? Take the MSP Owner Reality Check. Five questions, nine minutes, and it names the two or three things quietly capping your growth. https://themsphero.com/resources/msp-owner-reality-check-assessment
If you are about to spend real money on an event and want to walk in with a plan instead of a badge, book a 30 minute fit call at https://letschat.themsphero.com
Mike Kolb The MSP Hero
Adapted from the Sales and Marketing Checklist for Technology Vendors Attending a Channel Event, published by the GTIA Channel Development Advisory Council. The original is written for vendors working the booth. This version is rebuilt for MSP owners attending. GTIA is a vendor-neutral nonprofit trade association serving the IT channel.