Virtual Summit Community-Building Case Study: Digital Nomads Beyond 50

When members of a new community keep asking questions that no one can answer yet, a summit can turn that uncertainty into a shared learning experience. That was the starting point for Siobhan Farr and Digital Nomads Beyond 50 (DNB50): a community for people in their late 40s and beyond who were planning, exploring, or already living a location-flexible life.

In June 2021, Farr organised a three-day virtual summit around those questions. A current DNB50 first-party retrospective records 28 speakers, 32 topics, and 278 participants. The original HeySummit interview also contains older organizer-reported measures and quotations, including an “over 130” audience framing and a later “group of 300” statement. Those figures describe different moments or measures in the surviving story; they should not be added together or treated as one conversion result.

This is a historical case study, not a current membership count. It is useful because it shows how to turn recurring member questions into an event, how to reduce speaker-admin work, and how to keep the event system separate from the community space that continues afterwards.

Case study at a glance

Source-labelled facts from the DNB50 summit story

Question	What the evidence says	Source and boundary
Who organised it?	Siobhan Farr, founder of Digital Nomads Beyond 50 and an experienced event organiser.	Historical HeySummit interview; the DNB50 site describes Farr as the network's originator.
What problem came first?	Members were asking practical questions about becoming digital nomads, and the growing group did not yet have all the answers.	Historical interview narrative; retained as organizer-reported context.
When and how long?	June 2021; a three-day virtual summit.	DNB50 first-party retrospective.
How many speakers and topics?	28 speakers and 32 topics.	DNB50 first-party retrospective; this is distinct from the original interview's “21 other” recruitment description.
How many participants?	278 participants in the DNB50 retrospective.	Dated first-party event figure; not a current audience or membership count.
What did the original interview say?	It described over 130 aspiring digital nomads, more than 100 Facebook-group members in the first month, and later quoted a group of 300.	Historical organizer-reported material preserved from the original article. The surviving copy does not define the denominator or reconcile it to the 278-participant retrospective.
Where did the community live?	The event workflow and access sat around the summit; the continuing member community used Facebook and later other community channels.	Historical article plus the current DNB50 public community site. HeySummit was not the community forum or live video room.

Evidence note: The event figures are intentionally labelled by source and date. The 278 figure is the strongest public first-party event total now available; the other numbers and the direct quotations remain useful historical context but are not presented as a single funnel or as proof that the summit caused later community growth.

1. Start with the community problem

Farr left Dallas for Ecuador on 4 March 2020 intending to travel for six months. The pandemic changed that plan, and she began looking for people who were also trying to understand how travel and work could fit together. She created a Facebook group for Digital Nomads Beyond 50 and used member questions to learn what the community needed.

The original article records that the group passed 100 members in its first month. It also preserves Farr's explanation of why she created it:

“I just created a Facebook group. I wanted to find out, how do you do this? I’ve travelled a lot. But how do you travel and work?”

That is a strong event brief because it starts with a member job, not a format. Before choosing a summit, write down the unanswered questions, who has practical experience, and which answers would benefit from more than one perspective. If you are still deciding whether an event is the right intervention, why run an online event is a useful framing exercise.

2. Turn recurring questions into a three-day event

Farr recognised that the group needed a structured learning experience rather than another unorganised thread. She described moving into her “learning and development professional mode” and deciding that the community needed a conference or summit.

The event was not the community itself. A video or webinar provider delivered the live rooms, while the community could keep using Facebook or another dedicated member space. The event-management layer handled the public event experience around those rooms: pages, registration and access, speaker coordination, emails, ticketing or other monetisation choices, integrations, and post-event reporting.

That separation still matters. HeySummit’s online event workflow is designed for the planning, registration, ticketing, integrations, and post-event measurement around a multi-session event. It does not replace a native community forum or claim to be the live video room.

3. Make speaker recruitment a repeatable workflow

The original interview says Farr recruited 21 other digital nomads for Q&A lounges and topic sessions. The current DNB50 retrospective counts 28 speakers and 32 topics. Because the sources use different descriptions, this article does not claim that “21 plus Farr” equals the final speaker total. The practical lesson survives either way: define the intake process before invitations go out.

1. Send one structured intake form for a bio, headshot, talk title, links, consent, and promotion assets.
2. Set a real submission deadline and name what happens if a field is missing.
3. Centralise edits so the event team is not chasing assets across email, documents, and social messages.
4. Give each speaker a clear page, event link, and sharing instructions.
5. Check the final schedule, names, time zones, access rules, and recording or replay expectations before publishing.

Farr learned this by being interviewed herself: the interviewer sent a document for her bio, social links, and photographs, with a deadline before the interview. A current speaker onboarding workflow can centralise profiles, links, talk details, referral links, and optional audience insights. It reduces manual collection; it does not replace consent or make every speaker a guaranteed source of leads.

For a broader operating checklist, see event speaker management. The goal is not to collect the most names. It is to make the right contributors easy to brief, publish, and support.

4. Design participation, not just a schedule

The DNB50 story describes Q&As and networking sessions alongside talks about tax, being a good guest in a foreign country, isolation, and new revenue ideas. That mix worked because it connected information with the decisions people were trying to make.

For each session, decide what participation should look like: a question, a peer exchange, a worksheet, a follow-up conversation, or a next event. Keep the format visible on the event page and in reminders. If you use a webinar or streaming integration, test the handoff from registration to the live room and explain where replays will live.

Do not measure an ongoing community with one event number. Keep separate records for registrations, participants or attendees, speakers, topics, questions, replay use, and continuing community membership. A current event reporting and analytics workflow can help organise event-level page views, conversion, attendee, content, live, replay, and revenue measures; it cannot prove that an event caused every later community outcome.

5. What happened after the 2021 summit

The old article ended with plans for 2022. Those plans are now historical. The DNB50 first-party retrospective records a first CoLIVEwork in Medellín in June 2022, a second in Lisbon in 2023, and the 2024 Medellín LifeMap CoLIVEwork. These are later dated community milestones, not evidence that the 2021 summit alone caused them.

When your event finishes, publish the next step with the same care. Keep the member destination clear, schedule follow-up questions or workshops, and record which people attended or engaged without calling every member a participant. The community event ideas guide can help turn one summit into a measured series rather than an isolated peak.

What organizers can copy

• Discover the questions: collect recurring member problems before choosing the event format.
• Choose the intervention: use a multi-session event when different experts and shared participation will improve the answer.
• Standardise speaker intake: one form, one deadline, one owner, and one place for updates.
• Design interaction: give Q&A, networking, and follow-up a clear job instead of treating them as filler.
• Separate systems: keep event registration and reporting distinct from the community platform and live-room provider.
• Measure honestly: distinguish registrations, attendees, speakers, topics, replays, and ongoing members.
• Continue the rhythm: invite the community into a dated next conversation, workshop, or retreat only when it is actually planned.

Run the workflow around your next event

Farr’s story is a useful reminder that an event can be a response to a real community question, not just a promotional campaign. If you want to coordinate the event site, registration, speakers, integrations, access, and reporting in one workflow, explore HeySummit’s product tour and review the current pricing and trial options. The platform can organise the event around your community; it is still your job to choose the right member space, live provider, speakers, and follow-up promise.

Sources and evidence

• Digital Nomads Beyond 50, 2024 LifeMap CoLIVEwork — dated first-party retrospective for the June 2021 summit figures and 2022–2024 milestones.
• Digital Nomads Beyond 50 — current public description of the community’s audience and destination.
• HeySummit online events, speaker dashboard, and reporting and analytics — current product boundaries and workflow descriptions.

Historical evidence note: Direct quotations and older organizer-reported figures retained from the original HeySummit article are presented as historical source material. They are not current counts, independently audited performance claims, or a substitute for the dated first-party event figures above.