B2B customer and user conferences
Balancing product updates, peer learning and independent expertise
The product team wants more time on the roadmap, customers keep asking to hear from each other, and someone has suggested an outside speaker.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A user conference works when each content type has a job. Product updates tell customers what is changing. Peer sessions show how others made it work. Independent experts give a view the vendor cannot give about itself.
Decide the share of programme time for each before inviting speakers, and name who approves each type. The split is an editorial decision for the event owner, not a result of whichever team submits the most sessions.
What each content type is for
| Content type | Job in the programme | Risk if it dominates |
|---|---|---|
| Product updates | Announce changes, explain what they mean for current users, show direction. | Reads as a sales event and practitioners find nothing practical. |
| Peer learning | Customers explain real use, trade-offs and mistakes. | Quality varies and sessions can drift into complaints or promotion. |
| Independent expertise | A neutral practitioner, academic or industry voice puts the product in context. | Can feel detached from daily use if not briefed on the audience. |
Setting the balance
Start from the audience, not the vendor's agenda. If most attendees are existing users, peer learning and practical product content deserve the largest share.
Write the intended split as a range, for example product 30 to 40 per cent of session time, and review it when the draft programme is complete. The numbers are a prompt for discussion, not a rule.
- List every proposed session with the team that wants it.
- Tag each as product, peer or independent. Mixed sessions get the label of their main purpose.
- Add up time by tag and compare with the range you agreed.
- Ask who in the audience each session is for (see buyer and practitioner journeys) and move sessions until each group has a full day.
- Have the event owner, not the product team, sign off the final split.
Choosing and briefing independent voices
- Decide what independence means here: no commercial relationship with the vendor, or a disclosed one.
- Ask the speaker to confirm in writing how they are being engaged and whether any fee or sponsorship is involved.
- Brief them on the audience, the product's position and any topics the vendor does not want avoided or forced.
- Agree who may edit their slides. A neutral speaker whose content is rewritten by the vendor is no longer neutral.
- Use the standard speaker invitation pack and a clear session brief so expectations are visible from the start.
Curating customer sessions
Customers speak for free and for their own reasons. Give them a short brief, a rehearsal slot and a review of any figures that mention their organisation.
Agree what happens if the customer's legal or communications team requires changes late. Have a backup session so the slot is not lost.
Common failure points
- Roadmap sessions expand every time the product team has news, squeezing out practitioner time.
- Customer sessions are chosen because the vendor likes the story, not because attendees would learn from them.
- Independent speakers are not told that the room is full of the vendor's customers.
- No single owner of the running order, so time is traded session by session.
Worked example · Fictional example
A fictional logistics-platform user conference
Fictional organisation and figures, for illustration only.
Kargo Hub, a fictional logistics platform, has 24 session slots across two days. The first programme gives 14 slots to product and engineering, 8 to customers and 2 to an outside speaker.
In review, the event owner finds that practitioner attendees would see only 6 sessions with direct use. She asks for a range of 8 to 10 product slots, 10 to 12 peer slots and 3 to 4 independent slots. Product moves two sessions into one combined slot, and the freed time goes to customer-led working sessions.
Use this yourself
Programme balance worksheet
Copy this table, fill the target range first, and compare it with the draft programme.
| Content type | Target share of session time | Draft slots | Approver | Review question |
|---|---|---|---|---|
| Product updates | Range | Count | Event owner and product lead | Does each update tell users what changes for them? |
| Peer learning | Range | Count | Event owner and customer success | Would an attendee learn something they can reuse? |
| Independent expertise | Range | Count | Event owner | Is the relationship with the vendor disclosed? |
| Mixed or unclear | Aim for none | Count | Event owner | Which main purpose should it carry? |
Handle it in-house, or bring in help?
Your team can usually handle this when
- One person has authority to say no to a session request from any team.
- The customer base is small enough that speakers are already known.
- The previous conference's feedback already shows which types worked.
Outside planning help earns its fee when
- Product, marketing and customer success each lobby for time and nobody arbitrates.
- Speaker briefs, rights and disclosure questions need tracking for many speakers.
- The programme needs rebalancing late and each change affects rooms and run order.
Need someone to hold the programme balance?
A conference project lead can keep the session tagging, speaker confirmations and brief status in one view, and bring the balance back to the event owner for decision whenever requests change it. Programme content and approvals stay with you.
Questions organisers ask
Is there an ideal ratio?
No. It depends on the audience, the stage of the product and how often customers meet. Use the ratio to open a discussion, then review it against feedback.
Should independent speakers be paid?
That is a budget and policy decision. Whatever is agreed, record whether the speaker has any other relationship with the vendor and tell the audience if it matters.
How do we stop customer sessions turning into complaints?
Brief the session objective, agree a facilitator, and use the unhappy customers guide for feedback that belongs in another channel.
Who signs off the final balance?
The event owner, with product and customer success consulted. Avoid leaving it to whichever team submitted last.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.