The white papers already existed.
When I started at Illumio, the company had no Latin America channel program at all, with no regional partners and nobody on the ground in São Paulo or Mexico City. The marketing kit was mostly there, though. White papers, MDF budgets, the usual. What didn’t exist was any reason for a partner in São Paulo to believe Illumio would still be around in twelve months, with a real person on the other end of the phone who knew their book of business. Almost everything I believe about partner events comes out of that gap.
The guides that rank for planning a channel partner event agree on the front half of the job, and I’d sign off on most of it. Pick partners whose customers look like yours. Agree on goals before you agree on a venue. Decide up front who promotes and who owns the leads and who follows up, hand partners tracking links and ready-made assets so registration doesn’t depend on their marketing team’s spare Friday, and send a survey afterward. Sensible! They all treat the partner event as a lead machine with two logos on it, though. In a region where you’re brand new, I think that’s the smaller half of the job, because before a partner puts their customers in a room with you they need proof you’ll be back next quarter, and an event is the only proof I know of that arrives in person.
Go Before You Have Anything to Announce
I spent my first ninety days at Illumio on planes. São Paulo first, because that’s where the cybersecurity industry in Latin America clusters and where channel decision-makers actually take meetings. Then Mexico City.
Nobody would have called those trips event planning. They were, though. I learned which restaurants the regional CISOs actually go to, and which trade shows mattered and which were vanity, a list no global events calendar will ever hand you, since from a desk in San Francisco every show with a Latin American city in its name looks about the same size. I also learned which partners already had budget set aside for Zero Trust and which would take several quarters of persuading. That one quietly decided my guest lists for a year.
Four Small Ones Beat One Big One
We ran partner roundtables in São Paulo every quarter. The guides spend most of their energy on the single partner event, the summit or the co-branded webinar with a registration target, and I get why, because that’s the format with a clean number at the end. In a new region I’d trade one big event for four small ones every time.
A partner who sees you in March, and then again in June in the same city with the same faces from your side of the table, starts planning around you. I watched the same thing happen on a much louder floor. By our third year anchoring Arxan at RSA Conference, the CISOs and channel partners walking past had seen us in the same neighborhood with roughly the same message twice already, and pipeline contribution that year was the highest of the three. Showing up again costs a lot less than showing up bigger.
Run It on Their Clock
Localizing a partner event usually means translating the slides. Fine, do that. What we actually localized at Illumio was the cadence: meetings ran longer, hospitality went deeper, and follow-up still went out within 24 hours.
The agenda is where a team from headquarters gets this wrong without noticing, because a roundtable built in San Francisco tends to arrive as forty-five tight minutes of content with a hard stop, which is what respect for people’s time looks like at home, and if I were building one tomorrow I’d cut the content to half that and leave the rest of the afternoon on the schedule, on purpose, unclaimed.
That empty time is the event.
Bring the Same Polish You’d Bring to RSA
When we showed up at Latin American cybersecurity conferences, the brand looked exactly as finished as it did at the global conferences in San Francisco. The partners noticed.
It’s tempting to send the regional show last year’s booth graphics and whoever can be spared that week, since the budget line is smaller and nobody from headquarters will walk past. Partners walk past. They can see precisely which tier of effort their market is getting, and they size their own commitment to match. At RSA we built Arxan’s booth to read cleanly from 30 feet with one anchor message, and I’d hold a regional booth to that same 30 feet, because a tired booth in São Paulo tells every partner walking by exactly where they rank.
Seat the Roundtable Like a Customer Dinner
A partner roundtable has the same seating problem as a customer dinner during conference week: put two people from your own company side by side and you’ve wasted both chairs. I seat in small clusters, so every partner has at least one person next to them they’d actually want to meet. In a channel room that’s often another partner, or an anchor account. We co-marketed regional events with the right anchor accounts at Illumio, and if I were starting that program over, the roundtable seating chart is the first place I’d go looking for those pairs.
Partners also go into the same file as every other guest I look after, the one with allergies and the name of somebody’s kid in it. That file is most of what I mean by the concierge half of events. A partner who comes back in June should never have to answer the same question they answered in March.
The Video
If your executive can’t fly down for the regional conference, send someone who can, because every partner in that room knows what a plane ticket costs and what a recorded welcome costs.
Let the Region Set the Calendar
This is the thing I’d do differently. Some of our best LATAM co-marketed plays could have happened sooner if we’d lined the global event team up behind LATAM sequencing instead of the other way around.
Partner event advice is almost always written from headquarters, and it quietly assumes the global calendar is fixed and the partner event fills whatever slot is left. For a new region, I’d flip that for at least the first year. Ask your partners when their customers set budgets and which local shows already own the month, then hand those answers to the global events team as a constraint. They will grumble. Do it anyway.
Twenty-Four Hours, Then Next Quarter
Every guide ends with a thank-you note and a survey. Send both. The 24-hour follow-up rule we ran with partners is the same clock I used at Arxan to get every RSA lead to a rep (I wrote up how I measured that show’s ROI separately). With partners, those 24 hours belong to whatever you promised at the table. The intro to the account. The answer on MDF that someone on your team said they’d chase.
The longer follow-up is the next roundtable, already on the calendar before anyone leaves the room. Every partner I onboarded in those first ninety days is still in Illumio’s book today, and I don’t think that’s because of anything especially clever anybody said at a roundtable. We kept coming back.
The Takeaway
A channel partner event in a new region gets judged on registrations and pipeline, and it should be. It also has a second job none of the planning guides mention, which is showing a partner, in person and on a schedule they can predict, that you’ll still be there next year. Go before you have news, and keep going, at RSA polish, long after the novelty has worn off for everybody at headquarters.
If your team is opening a new region and the partner calendar is still a blank page, let’s talk. I’ll want to know where your partners actually eat.