# Running a SaaS user group program

> Run regional and virtual user groups: leader recruiting, event kits, budget per event, virtual versus in person economics, and pipeline produced per chapter.

Source: https://saas-marketing.net/playbooks/saas-user-group-program/
Topic: SaaS Customer Marketing
Type: playbook
Published: 2026-09-11
Last updated: 2026-09-11
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/playbooks/saas-user-group-program/

## Short answer

A SaaS user group program is a network of local or virtual chapters run by volunteer customer leaders, supported by the vendor with content kits, a small event budget and a speaker bench. It is the cheapest community format to start, typically $600 to $2,500 per in person event and under $300 virtual, and it produces references, case study candidates and expansion conversations faster than a full online community launch.

## Key takeaways

- Chapter events run by customer volunteers cost roughly a tenth of a company run regional roadshow per attendee.
- Fund volunteer leaders with budget, content and swag, never with speaking fees, or they stop reading as peers.
- In person events cost $600 to $2,500 each and produce references; virtual events cost under $300 and produce reach.
- A chapter needs 25 registered members before its first event or attendance will not clear single digits.
- Track references produced and expansion conversations opened per chapter, not attendance, or the program gets cut.
- Most programs die because nobody owns leader support after month four, not because customers lost interest.

---

If you're choosing between launching an online community and starting user groups, start the user groups. They cost less, need less staffing, and produce the thing your sales team keeps asking for: customers willing to take a reference call. An online community needs daily attention for eighteen months before it holds a conversation on its own. A chapter needs a volunteer, a room and a date.

This playbook covers the model, the leader program, the event kit, the money, and the part almost everyone forgets, which is converting attendance into something the business can see.

## Chapters or company run events, and who owns each?

Chapters are run by customer volunteers with vendor support. Company run events are run by your team with customers invited. They serve different jobs and you need both, in different proportions.

Chapters produce peer trust and references. Company run roadshows produce pipeline and product awareness. If customer marketing owns chapters and field marketing owns roadshows, the split works. If one team owns both under a pipeline target, chapters quietly turn into roadshows within two quarters because pipeline pressure always wins.

HubSpot User Groups are the clearest public example of the chapter model at scale, with volunteer leaders running local sessions across dozens of cities. Atlassian Community Events run the same way. Snowflake's user groups sit closer to the middle, with heavier vendor involvement in content and a more technical agenda.

The broader argument for where this sits inside [SaaS customer marketing](/saas-customer-marketing/) is that user groups are the lowest cost entry point into community work, and the one most likely to survive a budget review because the outputs are concrete.

## Recruiting volunteer leaders without turning them into contractors

Look inside your existing power users. The best chapter leaders are already answering questions in your support forum, already presenting at your annual conference, or already the person your customer success manager calls when they need a friendly voice.

Make the ask specific and small. Not "would you like to lead a community" but "would you host one ninety minute session in Manchester in November, and we'll handle registration, food and a speaker if you want one." Leaders who say yes to a single event renew into a role. Leaders recruited into a twelve month commitment tend to disappear by event three.

Fund expenses, event budget, swag and travel to your annual conference. Never a fee or retainer. A paid leader is a vendor representative to everyone in the room, and the whole value of the format is that the person at the front is a peer with nothing to sell. This is the single design decision most likely to kill or save the program.

What you give leaders instead:

- A content kit per event: agenda template, slide shell, two discussion prompts, a product update deck they can choose to use
- A swag budget, typically $150 to $400 per event
- A speaker bench of customers and internal experts they can request, with response within three working days
- Early roadmap briefings, which is the benefit leaders actually name when you ask them
- A named person at your company who replies to them within a day

That last one is where programs die. Nobody owns leader support after month four, messages go unanswered for a week, and three leaders quietly stop scheduling. Put leader support in one person's job description with a response SLA.

## The event kit: agenda, run of show, follow up

Give leaders a default so they don't have to invent one, and make it obvious they can change it.

A ninety minute in person agenda that works: fifteen minutes arrival and food, twenty minutes customer talk about something they built or fixed, twenty minutes open troubleshooting where attendees bring a problem, ten minutes vendor product update, twenty five minutes networking. The vendor slot is the shortest thing on the agenda and never opens the event.

The run of show matters more than the content. Who greets people at the door, who runs the timer, who takes the photo, who collects the attendee list. Assign those four in writing before the day.

Follow up within 48 hours or it doesn't happen. Send the slides, the recording if virtual, a three question survey, and a single named next step. The survey question that earns its place is "what problem did you bring that we didn't solve", which feeds directly into your [voice of customer program](/guides/voice-of-customer-program/) and gives product a queue of real friction.

**Running one chapter event end to end**

## Virtual or in person: where each one actually wins

Cost per attendee is not close. A virtual session runs under $300 all in and can reach forty people. An in person event with catering and vendor travel can cost $2,500 plus $900 of flights for twelve attendees.

But the reference conversion is not close either, in the other direction. People who spent ninety minutes in a room with your team say yes to reference calls at a noticeably higher rate than people who attended a webinar with their camera off. In practitioner experience the gap is large enough that in person events justify their cost on references alone at any ACV above roughly $15K.

| Factor | Virtual chapter | In person chapter |
| --- | --- | --- |
| Cost per event | Under $300 | $600 to $2,500 plus travel |
| Typical attendance | 20 to 40 | 8 to 20 |
| Registration to attendance | 25% to 40% | 35% to 50% |
| Reference conversion | Low | High |
| Leader effort | 3 to 4 hours | 10 to 15 hours |
| Best use | Feedback, reach, new regions | References, expansion, retention |

The practical pattern: run virtual quarterly to keep the chapter alive and in person once or twice a year as the anchor. Regions with fewer than thirty customers should stay virtual until the customer count supports a room.

**Under $300** All in cost of a virtual chapter event, versus $600 to $2,500 in person

## Turning attendance into references, stories and expansion

This is the step that decides whether the program survives its first budget review. Attendance is not an outcome. An attendee list sitting in a spreadsheet is a cost.

Within a week of every event, route three things. Reference candidates go to whoever runs your [customer reference program](/playbooks/customer-reference-program/), with a note on what they said and who heard it. Expansion signals, meaning anyone who described a use case you sell separately, go to the account team with the quote attached. Product friction goes to the product team as a tagged theme.

The people who speak at chapter events are your best advocacy pipeline, which is why the program feeds naturally into [building a customer advocacy program](/playbooks/customer-advocacy-program/) rather than competing with it. The same names surface repeatedly, and after two events they'll usually say yes to a case study.

Some of those leaders belong on your [customer advisory board](/playbooks/customer-advisory-board/) within a year. Track that path explicitly. A person who hosts three chapter events and then joins your CAB is worth more than any single campaign you'll run this quarter.

## What to report, and the honest failure mode

Report four numbers per chapter per quarter: references produced, case study candidates identified, expansion conversations opened, and renewal rate for accounts with an attendee versus accounts without. That last comparison is directional, not causal, because engaged customers self select into events. Say that in the meeting rather than letting someone else say it for you.

The honest failure mode: user groups skew heavily towards customers who are already happy. They will not tell you why the quiet accounts are churning, and a healthy chapter program can coexist with a retention problem you cannot see. That blind spot is one of the patterns covered in [why customer marketing programs fail](/guides/why-customer-marketing-fails/), and it's the reason chapters should never be your only listening channel.

The second failure mode is quieter. Chapters drift towards vendor content because it's easier to fill twenty minutes with a product update than to find a customer speaker. Once three consecutive events lead with a product slide, attendance halves and never recovers.

## Where this fits and what to do first

If you're building community work into a wider plan, a chapter program is the first phase of a [SaaS customer community strategy](/guides/saas-customer-community-strategy/), not a substitute for one. Chapters give you the advocates who later seed an online space. Attempting it in the other order is why most vendor communities read as empty rooms.

Chapters also feed referral volume, because people who present to peers about your product generate introductions without being asked. If referrals matter to your number, read this alongside [referral lead generation for SaaS](/guides/referral-lead-generation-saas/) and connect the two tracking systems early. For patterns from companies already running this well, the [SaaS customer marketing examples](/examples/saas-customer-marketing-examples/) collection has the formats worth copying.

Start with one city. Find the customer who already evangelises you there, ask for one ninety minute session, and give them a content kit and $400. If twelve people show up and two of them agree to a reference call, you have a program. If three people show up, you had a leader without a network, and the fix is a different leader, not a bigger budget.

## Frequently asked questions

### How is a user group different from an online community?

A user group is event shaped and local or time bound, run by a customer volunteer, with a handful of gatherings a year. An online community is always on, needs daily moderation, and fails without constant seeding. User groups need far less staffing and produce stronger references because people meet face to face or in small live calls.

### How much does it cost to run a SaaS user group event?

In person events typically run $600 to $2,500 depending on venue and catering, or free when a member company hosts in their own office. Virtual events cost under $300, mostly platform and a small prize budget. Add vendor staff travel for in person events, which is often the largest single line and the first one to cut.

### Should you pay volunteer chapter leaders?

Pay their expenses and give them budget, content and swag, but do not pay speaking fees or retainers. The moment a leader is compensated for their opinion, attendees read the group as a vendor channel and the peer dynamic that made it valuable disappears. Recognition, early roadmap access and conference tickets work better and cost less.

### How many members does a chapter need before its first event?

Twenty five registered members is the practical floor. Registration to attendance for free B2B events runs roughly 35% to 50% in person and 25% to 40% virtual, so twenty five registrations gives you eight to twelve people in a room, which is enough for a real conversation and not so few it feels awkward.

### What do you actually do at a user group meeting?

A workable ninety minute agenda: fifteen minutes of arrival, a twenty minute customer talk on something they built, twenty minutes of open troubleshooting, a ten minute product update from the vendor, then open networking. The vendor slot should be the shortest item on the agenda and never the first.

### How do you measure whether a user group program is working?

Count references produced, case study candidates identified, expansion conversations opened and renewals where an attendee is on the account. Attendance is an input, not an outcome. A chapter producing two references and one expansion conversation a quarter pays for itself several times over at most ACVs.