How-to guide

How to launch an in-person user group your customers want to come back to

An in-person user group is a lightly gated, city-based meetup where your customers come together to swap workflow tips, hear one or two of their peers talk about real work, and build a small professional network around your product. The best user groups become the single most durable retention and expansion lever a B2B software company has, because the attendees stop renewing with your account team and start renewing with the room. The worst ones become a quarterly product pitch in a hotel ballroom, run out of steam after two cities, and get written up as a cautionary line item in the next planning cycle. This guide walks through how to pick the right cities, recruit a local champion in each one, scope a first meeting that earns a second one, invite the right customers in-market, host without pitching, capture themes, scale the cadence, and measure whether the program is actually moving retention and expansion inside the group versus outside it.

Start free trial See pricing
Before you start

What you need.

Time: 90 days per city

  • Customer density in the target city of at least 10 active in-market accounts, drawn from your CRM with the primary user named on each account, so the invite pool is large enough to carry a first meeting even after decline rates
  • A local champion recruited from your existing customer base, someone who already evangelizes the product, lives or works in the city, and will co-host and co-brand the invitation with your team
  • A meeting venue secured for a 1 to 2 hour evening session, ideally hosted by the local champion's company, a partner office, or a quiet private room at a restaurant that will not try to upsell a full plated dinner
  • A catering budget approved for light food and drinks for 20 to 40 attendees, plus a small travel budget for the Strkr host and any guest speaker, so the economics are set before invitations go out
  • An invite list of 30 to 50 named customers in-city with a planned email cadence of save-the-date, formal invite, two reminders, and a day-of confirmation, all sent from the local champion's name where possible
Launch an in-person B2B customer user group program

Step by step.

  1. 1

    Pick cities with at least 10 in-market customers before you plan anything else

    User groups fail before the first meeting when the host team picks cities based on where leadership happens to travel, where a conference is already landing, or where a loud customer asked for one. Start instead with the CRM. Pull a report of active customers by metro area and set a hard floor of 10 named accounts in-market, each with a primary user you can invite by name. CMX community research and SaaStr's writing on customer councils both reach the same conclusion: user groups below critical density produce thin rooms, thin conversation, and no second meeting. Rank candidate cities by density first, then by expansion potential and by whether you have a credible local champion in the room already. Launch into the top three to five cities one at a time, not all at once, so you can carry a learning from the first city into the second.

    • Pull a CRM report of active customers by metro area with the primary user named on each row.
    • Set a hard floor of 10 in-market accounts per city before the city is eligible for a launch.
    • Rank eligible cities by density, expansion potential, and whether a credible champion already exists in-market.
    • Launch into one city first and carry what you learned into the second, instead of three cities in parallel.
    Tip: Do not launch a city because an exec is flying through next month. The room has to carry itself after the exec goes home, and the only variable that reliably predicts a second meeting is in-market customer density on the day you send the invite.
  2. 2

    Recruit a local champion from the customer base, not from your sales team

    The single best predictor of whether a city user group reaches its second meeting is whether a real customer, not a Strkr employee, is standing at the front of the room on night one. Pick a champion who already shows up in your advocacy and NPS data, who works in-city, and who is senior enough to carry a room but not so senior that peers feel they are performing for them. Walker Information's advocacy research is consistent on this: peer-led communities retain members at meaningfully higher rates than vendor-led ones because the social contract is customer-to-customer, not customer-to-sales. Ask the champion to co-brand the invitation, co-host the night, and introduce the first speaker. In exchange, give them real influence on the agenda, early access to roadmap conversations, and a seat at your annual advisory moments. Avoid any arrangement that pays or discounts them for the role, because the moment money enters the room the peer dynamic collapses.

    • Shortlist two or three candidate champions per city from your advocacy, NPS, and customer success data.
    • Confirm the champion will co-host, co-brand the invitation, and introduce the first speaker on night one.
    • Give the champion real influence over agenda and speaker selection, not a scripted welcome.
    • Do not pay the champion or offer product discounts in exchange for the role.
    Tip: If your account team cannot name a champion in-city within a week, the city is not ready yet. Build the account relationship first and come back to the user group in the next quarter.
  3. 3

    Scope the first meeting as a 1 to 2 hour evening with a light agenda

    The first meeting is a trust exercise, not a program launch. Scope it as a single 1 to 2 hour evening session, ideally weeknight 5:30 to 7:30 so busy practitioners can get there after work and still get home at a reasonable hour. Keep the agenda light: 20 minutes of open networking with food and drinks, 20 to 30 minutes of one customer giving a short talk about real work, 20 minutes of structured peer discussion in small groups, and a 10 minute close from the local champion. No slide deck from Strkr. No product roadmap. No pricing. Gainsight's advocacy writing and CMX community research are consistent that first meetings designed as mini-conferences fail to build the peer dynamic that keeps a user group alive, while first meetings designed as structured networking with one credible talk give people a reason to come back and bring a colleague.

    • Hold the first meeting to 1 to 2 hours on a weeknight evening, with a clear start and end time on the invite.
    • Build the agenda as 20 minutes networking, 20 to 30 minute customer talk, 20 minutes structured peer discussion, 10 minute close.
    • Do not run a product demo, roadmap preview, or pricing conversation at the first meeting.
    • Capture a short list of topics the room says they would want to discuss next time, so meeting two writes itself.
    Tip: The temptation to turn the first meeting into a product showcase is strongest when a product leader is traveling through the city that week. Resist it. The room will remember whether they left with new peers and new ideas, not whether they saw a feature they could have seen on a webinar.
  4. 4

    Invite 30 to 50 customers in-city with a real email cadence

    Attendance math on the first night usually lands between 30 and 50 percent of invited, so plan the invite list accordingly. Pull 30 to 50 named customers in-city from the CRM, mix practitioner-level users with the occasional buyer, and send the invitation from the local champion's name where possible rather than a Strkr marketing address. Run a four to five touch cadence: a save-the-date three weeks out, a formal invitation two weeks out, a reminder one week out, a reminder two days out, and a day-of confirmation with the venue address and a mobile number for lost attendees. Make RSVP one click. Confirm the headcount with the venue 48 hours before the meeting and over-order food by 10 percent, because a cold-food room is the fastest way to lose the second meeting.

    • Target 30 to 50 named in-city customers on the invite list, mixing practitioner users with a few buyers.
    • Send the invitation from the local champion's email where possible, co-signed by the Strkr host.
    • Run a four to five touch email cadence: save-the-date, formal invite, two reminders, day-of confirmation.
    • Over-order food by 10 percent and confirm the venue headcount 48 hours before the meeting.
    Tip: If the day-of confirmed headcount is below 15, consider pushing the meeting a month and running one more invite cycle. A thin first room sets the ceiling for every meeting after it, so protect the first-night energy even if it costs a month.
  5. 5

    Host the first meeting with networking and one customer talk, no product pitch

    Night one has one job: send the room home willing to come back. Open with 20 minutes of unstructured networking while food is out. Have the local champion welcome the room in two minutes, not ten, and introduce one customer speaker. The speaker should talk for 20 to 30 minutes about real work, including what did not go well, not about how great the product is. Follow with 20 minutes of structured small-group discussion on one or two prompts the room will actually have opinions on, such as how they staff the function or how they measure success. Close with 10 minutes from the local champion naming the themes they heard and committing to a next date. The Strkr host says hello, pours drinks, and otherwise stays out of the way. No product talk, no sales conversations in the room, and no capturing emails for a nurture.

    • Open with 20 minutes of networking and food, not with a presentation.
    • Have one customer speaker share real work for 20 to 30 minutes, including what did not work.
    • Run 20 minutes of structured small-group discussion on one or two prompts the room will have opinions on.
    • Close with the local champion naming themes and announcing a tentative next date in the same city.
    Tip: Train the Strkr host to resist two instincts on night one: pitching the product and running account-management conversations in the hallway. Both will be felt by the room immediately and both reduce the probability of a second meeting more than almost anything else you can do.
  6. 6

    Capture themes and what the room wants to discuss next time

    The quality of meeting two is set by how carefully you captured meeting one. Within the week after the first meeting, write a short internal recap covering who attended, which themes came up in the small-group discussion, which topics the room explicitly asked to discuss next time, and any one-on-one feedback the champion or host heard during networking. Send a short public thank-you to the room from the local champion, with a two-sentence recap of what the group discussed, the name of the next speaker if you have one, and a save-the-date for the next meeting. Feed the themes into product, customer success, and marketing so the signal from the room reaches the teams that can act on it. CMX community research is consistent on this point: communities that visibly act on member input retain members at meaningfully higher rates than communities that only broadcast at them.

    • Write an internal recap within one week covering attendance, themes, requested topics, and hallway feedback.
    • Send a short public thank-you from the local champion within one week with a save-the-date for the next meeting.
    • Route themes from the room to product, customer success, and marketing with named owners.
    • Credit the room by name when a theme they raised turns into a shipped change or a published piece.
    Tip: Keep a running document per city with the running list of topics the room has asked to discuss. The agenda for every future meeting should start from that list, not from what Strkr marketing wants to say that quarter.
  7. 7

    Scale the cadence to quarterly in each city and add cities one at a time

    Once a city has run two successful meetings, lock the cadence at quarterly, publish the full year of dates, and move your attention to launching the next city. Quarterly is the cadence most working user groups converge on, because monthly burns out volunteer time from champions and busy practitioners, and anything lighter than quarterly loses the social fabric between meetings. Walker Information's community research and SaaStr's writing on customer councils both reach this same quarterly default from different starting points. Resist the urge to run five cities in parallel from day one. Launch city by city, carry the learnings forward, and only add a new city when the previous one has crossed its second meeting and still has a healthy headcount. The slower launch cadence protects the quality bar and prevents the program from becoming a logistics operation that no one on the team wants to own.

    • Lock the cadence at quarterly once a city has cleared two successful meetings and publish the year of dates.
    • Launch new cities one at a time, with a 90 day gap between city launches to carry learnings forward.
    • Rotate speakers so the same two or three customers do not carry every meeting in a city.
    • Stand up a light cross-city alumni channel so a customer who moves cities stays in the program.
    Tip: The hidden cost of running too many cities in parallel is not travel, it is attention. The program needs one owner on your side with real capacity to run it, and that owner's bandwidth is the actual rate limit, not the catering budget.
  8. 8

    Measure retention and expansion inside the group versus outside it

    A user group program is only worth running if it moves the business. Set up a measurement loop that compares the retention and expansion of customers who have attended at least one user group meeting against a matched cohort of in-city customers who have not. Track gross and net retention, expansion ARR per account, product adoption of the top three workflows, NPS, and reference willingness. Walker Information's advocacy research and Gainsight's published community benchmarks both show that engaged community members retain and expand at measurably higher rates than non-members, often by double digits, and the gap widens the longer the program runs. Report the delta to leadership quarterly and use it to defend the catering budget. Programs that cannot show the delta in year one almost always get cut in the next planning cycle, even when attendees love them.

    • Build a matched cohort of in-city customers who have attended at least one meeting versus those who have not.
    • Track gross retention, net retention, expansion ARR, product adoption, NPS, and reference willingness per cohort.
    • Report the delta to leadership quarterly so the program defends its own budget on real numbers.
    • Share the delta back with the local champions so they see the business impact of the room they are building.
    Tip: Do not measure the program on attendance alone. A room of 60 that does not change retention is a worse outcome than a room of 25 that moves net retention three points. Attendance is a proxy for health, not a proof of value.
Avoid

Common mistakes.

  • Launching a city with fewer than 10 in-market customers. The invite math never carries a first meeting, the room feels thin, and no one on the invite list bothers with the second one.
  • Letting a Strkr employee host instead of a local customer champion. Peer-led rooms retain members at meaningfully higher rates, and vendor-led rooms slide into product-pitch mode by the second meeting.
  • Treating the first meeting as a product showcase. A slide deck from the product team on night one tells the room this is a sales event, and the practitioners who would have become the backbone of the group quietly stop coming.
  • Running the account team or sales reps as hallway operators during the meeting. The moment attendees feel a renewal or expansion conversation starting in the room, the peer trust the group depends on collapses.
  • Trying to launch five cities in parallel in year one. The program owner's attention is the actual rate limit, and spreading thin across cities produces five mediocre rooms instead of two excellent ones.
FAQ

Frequently asked questions.

How many customers do you need in a city to launch an in-person user group?

At least 10 active in-market accounts, each with a named primary user you can invite, is the working floor for most B2B software companies. Below that threshold the invite math does not carry a first meeting after normal decline rates, and the room feels thin from the start. Above 10 you can usually count on 30 to 50 percent attendance from a 30 to 50 person invite list, which is enough to produce a working room on night one. Rank candidate cities by density first before considering anything else.

How often should an in-person user group meet in each city?

Quarterly is the cadence most working user groups converge on. Monthly burns out volunteer time from champions and busy practitioners. Lighter than quarterly loses the social fabric between meetings and attendance decays. Once a city has cleared its second successful meeting, lock a quarterly cadence, publish the full year of dates in one email, and let members protect the time on their own calendars. Pair the group meetings with a lightweight cross-city alumni channel so members stay connected between the quarterly nights.

Should the user group be hosted by a customer or by the vendor?

By a customer, every time. Peer-led communities retain members at meaningfully higher rates than vendor-led ones because the social contract is customer-to-customer, not customer-to-sales. Recruit a local champion from your existing customer base, give them real influence over the agenda and speaker selection, and have them open and close every meeting. The Strkr host is there to handle logistics, say hello, and otherwise stay out of the way. Do not pay the champion or discount their contract in exchange for the role.

What is the right agenda for a first user group meeting?

Keep it to 1 to 2 hours on a weeknight evening. Open with 20 minutes of unstructured networking while food and drinks are out. Have the local champion welcome the room in two minutes and introduce one customer speaker, who talks for 20 to 30 minutes about real work including what did not go well. Follow with 20 minutes of structured small-group discussion on one or two prompts the room will have opinions on. Close with the champion naming the themes they heard and announcing a tentative next date. No slide deck from Strkr, no product roadmap, and no pricing.

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

Build a matched cohort of in-city customers who have attended at least one meeting against those who have not, and track gross retention, net retention, expansion ARR, product adoption, NPS, and reference willingness across both groups. Walker Information and Gainsight community benchmarks both show engaged community members retain and expand at measurably higher rates than non-members, often by double digits. Report the delta quarterly so the program defends its own budget on real business numbers, not on attendance counts alone.

How is a user group different from a customer advisory board?

A user group is an open or lightly gated community of practitioners in a city who meet to swap workflow tips, hear one or two of their peers, and build a small professional network around your product. A customer advisory board is a small, invitation-only group of 10 to 15 strategic buyers that meets on a published cadence under NDA to inform roadmap, positioning, and strategic direction. Both are useful and they are not substitutes. The user group is where your customers teach each other how to get more value from the product. The advisory board is where you take hard questions under NDA.

See it in Strkr

Related product surfaces.

Strkr CRM Strkr platform features

Run your in-person user group program on the same platform you run the business

Strkr gives customer success, marketing, and the local champions one place to tag user group attendees, track themes raised in each city, measure retention and expansion inside the program versus outside it, and link every meeting back to the accounts and renewals it influenced.

Start free See the platform
Related guides

More how-to guides.

How to launch a customer advisory board → How to launch a customer community → How to run a quarterly business review (QBR) → How to plan a field marketing event →
Deep dives

Related answer pages.

What is customer advocacy? → What is field marketing? → What is customer success? → What is net promoter score (NPS)? → What is event marketing? →
More topic FAQs

Related FAQ hubs.

Customer success Referrals and advocacy Content marketing Webinars and events
Sources

Further reading.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing