Happy Wednesday! π I'm making new resources for the Tightknit community and would love your input π I put together a B2B SaaS Community Playbook. It covers: β Defining your community's job β Week 1 setup β Activation tactics β Engagement loops that scale β Proving value to leadership Would love your feedback: What topics do you want to see more of? Drop your thoughts in the thread π
1: Community β Revenue: π°π How community drives pipeline, expansion, and sales influence This is kind of a touchy one for community managers, as often the balance is skewed TOO MUCH toward pipeline generation, by the business. π€ I think in the short and medium term, if the community is engaged and thriving, then pipeline should follow (medium and long term.) But it could be healthy for us as community managers to confront this conversation head-on, get ahead of the inevitable business pressure, and start to build the arguments for why we need room in the short-term, to set things up the right way:
rich soil, π±
fertilizer, πͺ΄
sunshine, βοΈ
water, πΏ
air... ποΈ π¨
...so the pipeline fruits can grow. π π π
2: Community as a Content Engine: Turning conversations into media, distribution, and brand I experimented with this in my first year as community manager at dbt Labs, by creating a podcast that featured community members as the star. I didn't center the product, I centered the humans who happen to use the product I didn't have executive sign-off - I just did it in my spare time But I've since been able to use those 25 episodes as:
A resource to identify community champions
A resource to surface product superusers, and potential pipeline
A way to signal belonging, because I featured a diverse set of community members
A way to repay those super community members by platforming them, and building their personal brand in the industry
A source of video shorts for social, content for newsletters, and evergreen mentoring advice for new members
A source of speakers at our annual conference
I continue to look for ways to syndicate that content... and I'm looking to use that pilot season 1 as a business justification to get budget for an even better season 2. π Sample episodes:
3: Champion Systems: Structured progression + recognition + identity. I'm a big fan of David Spinks' book: "The Business of Belonging." I've been using the community commitment curve framework, to meet people where they are, not ask too much of them, but also set a goal to nudge them "one level up" from where they are currently. Or rather, to always make that option clearly available to them. This is very much a work-in-progress. LOL! I spent my first year working on the bottom of the commitment curve - trying to get passive members into the active zone. My new manager recommended I start on the other end of the commitment curve, though. Hence my spending the last 3 months exclusively focused on building and launching our first Champions program. π
4: Belonging & Emotional Design
Beyond participationβidentity, status, and culture
This is a fun one - and probably ties into the previous point around the commitment curve.
While we're just trying to get the 90% at the bottom of the curve to just show up and leave a
, π , or
... some sign of life... LOL! π
At the other end of the curve, our super community members may be bumping up against a ceiling. They may be running out of ways to grow in our community.
They probably show up not just for the transactional information, but also for the relationships, the identity, the status, and the culture.
How can we community managers systematically invest in this group?
Among other things, I piloted a community-designed t-shirt program in my first year, focused on increasing belonging and identity.
I tried to find funny inside jokes from the community, and then present them to the community as potential t-shirt slogans. Each month I asked the community to vote on their favorite, then I made it a t-shirt!
These shirts then became collector's items, and ways to reward community contributors every month.
5: Going deeper on the WHO/WHAT/HOW step. I don't know how many other communities struggle with this, but this foundational step is... hard. LOL! π
It's SIMPLE to understand...
but not EASY to implement.
My challenge is that the community I adopted 1.5 years ago, when I took this job, was (and still is) tackling too many WHOs, WHATs, and HOWs. π± Everything, everywhere, all at once. π± And the challenge? Even after a community manager / community team prioritizes, without organizational support, to changes necessary are unlikely to succeed. Bootstrapping it is great for proof-of-concepts, but trying to turn a cruise ship with an oar will probably only end up one way. πΆ π³οΈ π₯ π© Right now, I'm struggling with wanting my community to be:
A helpdesk (transactional, technical unblocking)
Why they show up: "I'm stuck"
Behavior: "Ask, get answer, leave."
Group dynamic: Individualistic. With a few looping back to answer questions.
A school (structured member upskilling)
Why they show up: "I want to improve."
Behavior: "Learn, practice, repeat."
Group dynamic: Individualistic, but could be persuaded into study groups
A career accelerator (belonging, identity, mentoring, and evolution)
Why they show up: "I belong here.
Behavior: "Help, relate, build, reinforce"
Group dynamic: Communal. Nonlinear growth. Explorers and pathfinders.
All three require completely different systems. LOL! π Help!

