By the time you add the sponsorship, the booth build, flights, hotel at conference rates, and four people off the floor for most of a week, an annual ERP user conference runs somewhere between $40,000 and $90,000. That is real money for an ISV at the stage where the channel is still being built.
The return is usually reported as badge scans, which is a number that has never once predicted anything.
I have worked these events from both sides. What separates the ISVs who come home with something from the ones who come home tired is almost entirely decided before they get on the plane.
The room is mostly partners, and that is the point
An ERP user conference is billed as a customer event, and customers are there. But the density of VARs, implementation firms, and other ISVs is high, and those are the people who can send you deals for the next five years.
If your booth strategy is built for end customers, you will spend the week explaining your product to people who cannot buy it and missing the people who could sell it.
That reframing changes what you do. The goal is not to scan 400 badges. It is to have 20 substantive conversations with partner firms, of which maybe 6 turn into a real follow-up and 2 into partners.
Book the meetings before you go
This is the whole thing, and it is what most ISVs skip.
Three to four weeks out, get the attendee or exhibitor list if the publisher will share it. Identify the partner firms you want. Look up who from each firm is going, and email them personally with a specific reason to meet.
Not "come by our booth." Something like: you have several manufacturing customers on the platform, we solve a problem those customers have, twenty minutes on Tuesday to see whether it fits your practice.
A dozen booked meetings, spread across the days, changes the entire economics of the week. It converts a random walk into a schedule. And the partner who agreed to a meeting in advance arrives having thought about you for at least a minute, which is more than any badge scan represents.
Where you meet matters less than that it is scheduled. Coffee in the lobby is fine. Some of the best conversations I have had at these events were in a hotel bar at 10pm with a practice lead who had had a long day and wanted to talk shop.
Booth work, honestly
You need a booth if the publisher's program expects one, and it is the address people find you at. It is not where the value is.
What makes a booth useful:
Have something to show that runs in 90 seconds. Not a slide deck, not a video loop. The live thing, on real data, short. Partners are evaluating whether their own consultants could demo this, and a 90 second version tells them yes.
Staff it with someone who can answer implementation questions. Partners ask about deployment, upgrade impact, and support model within the first two minutes. A booth staffed only by marketing loses those conversations immediately.
Skip the raffle. A drawing for a gift card fills your scan list with people who wanted a gift card, and then somebody has to work that list.
Sessions beat booths
If you can get a speaking slot, take it over a bigger booth package every time. A 45 minute session with 60 attendees who chose your topic is worth more than three days of foot traffic.
Getting one usually means submitting early, proposing something that is not a product pitch, and often having a customer or a partner co-present. Publishers accept sessions that teach their audience something and reject sessions that sell. A talk built around what you have learned across your customer base, with your product as an incidental part of the story, gets accepted and does more for you anyway.
If sessions are closed to you, look at the partner-run side events, the user group meetings, and the pre-conference days. Those are often less contested and the audiences are more concentrated.
The publisher's own people
The publisher's field team, practice leads, and product managers are all at this event and they are more accessible than at any other time of year.
Have a short list of internal people you want to meet and a reason for each. A product manager wants to hear what your customers are asking for that the platform does not do. A field rep wants to know which of their deals you can help close. Neither wants your pitch.
These are the relationships that later turn into introductions, and introductions from a publisher's own team are the highest quality channel leads that exist.
Follow up in the week, not the month
The follow-up window closes fast. Everyone comes home to a backlog, and by day ten your conversation has blurred into the other forty they had.
Send the follow-up within 72 hours, personally, referencing the actual thing you talked about. If you promised a demo, propose two times rather than asking when works. If you committed to send something, send it before you sleep.
Then track those conversations as a cohort. Twelve months later, look at how much registered pipeline traces back to that week. That number is the real event ROI, and almost nobody calculates it, which is why the badge scan count survives as a metric.
Whether to go at all
If you are early and cash is tight, going as an attendee rather than a sponsor is underrated. You lose the booth and keep everything that matters: the meetings, the sessions, the hallway conversations, the evening events. It costs a fifth as much.
I would rather see an ISV attend three conferences as a well-prepared attendee than sponsor one badly. The booth is a signal that you are established. Meetings are what produce partners, and nobody has ever needed a booth to have coffee with someone.