I spent close to a decade in Silicon Valley, at Salesforce and then DocuSign. I have sat in a lot of customer conference rooms, on both sides of the badge.
The pattern is consistent. The product sessions are good. The roadmap keynote is polished. And somewhere on the second afternoon the energy drops, because everything has been about the tool and nothing has been about the job.
What your customers are actually turning up for
Not the features. They will read those in a release note in less time than it takes to sit through a demo.
They came because they are accountable for something and they are not certain they are measuring it right. The admin who runs your platform reports a number to a director every month. The director reports a version of it upward. Nobody in that chain is confident it is the number that matters, and nobody will say so in a session about integrations.
That is the gap worth programming into.
If an attendee cannot describe, on Monday morning, one thing they will do differently because of a session, that session was entertainment. Sometimes that is what you wanted. You should know which one you bought.
The number nobody programs a session around
Every SaaS company teaches its customers to watch adoption. Seats activated, workflows live, tickets closed. Those numbers get reported religiously and, past a certain point, they stop changing behaviour. They become a status update.
The interesting question is which of those numbers actually moves the outcome the customer is judged on, and which are just the ones that were easy to instrument. Almost nobody has done that work, because it is uncomfortable and it is nobody's job.
A session that walks a room through separating the two is worth more than any feature preview, and it makes your platform look like the place where serious thinking happens.
Where sustainability quietly became a tech conference topic
I run Clever Carbon, so I am biased about the subject and I will be plain about why it belongs on a software agenda anyway.
It is no longer an ethics slot. Your customers' procurement teams are being asked for supplier emissions data, often including yours. Someone in their organisation has been handed a reporting obligation with no training and a spreadsheet. That is a measurement problem in a room full of people who work on measurement problems.
Programmed as values, it empties the room. Programmed as "here is a dataset you are now accountable for and here is how to make it legible", it is one of the more useful hours you can offer.
A shape that works
| Slot | Job | Common mistake |
|---|---|---|
| Opening keynote | Vision and roadmap, from you | Running long, so everything after it compresses |
| Mid-morning, day one | Outside voice reframing their work | Booking a celebrity with no connection to the theme |
| Afternoon | Hands-on, practitioner-led | Sessions pitched at buyers instead of users |
| Day two opening | The hardest idea of the event | Wasting the freshest room on housekeeping |
| Closing | One specific thing to do next week | A rousing call to be better, forgotten by Tuesday |
What audiences are tired of
- The customer story that is really a testimonial. People can tell. Pick the customer who will describe what went wrong.
- The AI session with no specifics. Every agenda has one. Most say the same six things.
- Panels of four. Nobody says anything sharp with three peers watching.
- The motivational closer with no connection to the product or the work. Pleasant, and gone by the airport.
If you only change one thing
Write down what each session is for before you invite anyone to fill it. Most disappointing agendas are not badly booked, they are undefined, and no speaker can fix a slot that was never given a job.
If it helps, the questions I would ask any speaker start from exactly that.
Frequently asked questions
Should the keynote be given by our CEO or an outside speaker?
Both, in that order, doing different jobs. Your CEO owns the vision and the roadmap because only they can. An outside speaker can say the thing your customers need to hear but would discount coming from a vendor. Putting the outside voice after the internal one also stops the whole morning sounding like one long pitch.
Our attendees are practitioners, not executives. Does a big-picture keynote land?
It lands better with practitioners, in my experience, provided it is about their work rather than their industry. Executives get abstraction all day. Practitioners rarely get someone to make their daily metric feel consequential, and they are the ones who can act on it on Monday.
How do we stop the agenda becoming all product?
Decide the ratio before anyone submits a session. If product owns 60% of the programme, say so in writing, and protect the rest. Agendas do not drift toward product by accident; they drift because nothing was defended.
Is sustainability still relevant at a software conference?
Only if you treat it as a business measurement problem rather than a values statement. Procurement teams now ask software vendors for emissions data, and most of your customers have been handed a reporting obligation nobody trained them for. Framed that way it is operational, not political.
Sources: Attendir - User Conference Playbook · Gainsight - customer experience conferences 2026
If you programme for a technology or software audience, there is a version of this keynote built for that room.