Spent some time yesterday putting together a document for a prospect on the age old question:
Slack + Tightknit 🆚 Slack Standalone.
Would love all of your feedback! What's missing? What doesn't seem right?
Immediate thoughts:
“Slack standalone” is weird, rephrase it so it sounds like how you’d talk to a peer (maybe something like, “just a Slack workspace”)
Set it up more like a traditional compete page with Slack only, slack + Tightknit, no community program at the org, and remain with a tradition community platform
Add proof — companion site links, LinkedIn posts from Tightknit, customer quotes, customer stories, etc. for each platform section you’re highlighting (branding, SEO, etc.)
Not why Tightknit fills gaps, but how ✨
Shape the future of Tightknit to best serve your community is a point for your work with clients plus:
Share retention rate of customers
CSAT of customers
Tightknit wrapped
— events promoted, badges awarded, certificates delivered, posts on social with badges, etc. Not wordsmithing the whole thing for ya, Zach H.
Let me do Este L. first:
who would be reading this? Where are they in their journey? what decision are they making?
This is primarily enterprise prospects early or in the middle of cycle making the decision on to start with Slack alone or start with Slack and Tightknit
Also, where would this document live? A leave-behind after a demo? First touchpoint before a call?
Yes, I see it as a leave behind after a demo. Also useful for that person to share internally with other stakeholders. It could be sent before a call too although if they are already taking a call, the interest in learning is still worth having them in there.
Okay now Joel P. :
“Slack standalone” is weird, rephrase it so it sounds like how you’d talk to a peer (maybe something like, “just a Slack workspace”)
Ya agree. Okay so maybe "Just Slack"
Set it up more like a traditional compete page with Slack only, slack + Tightknit, no community program at the org, and remain with a tradition community platform
I wouldn't call this a compete slide. I do think we will also have a compete slide against a traditional community platform
Add proof — companion site links, LinkedIn posts from Tightknit, customer quotes, customer stories, etc. for each platform section you’re highlighting (branding, SEO, etc.)
Ya this would be a good next iteration. I don't want it to get too lengthy so many only a few will get that treatment
Not why Tightknit fills gaps, but how
Not sure I understand this one.
Shape the future of Tightknit to best serve your community is a point for your work with clients plus:
Share retention rate of customers
CSAT of customers
Tightknit wrapped
— events promoted, badges awarded, certificates delivered, posts on social with badges, etc.
Ya definitely need to start sharing more of this data!! We have retention though.
Im thinking something along the lines of:
You’ve chosen Slack. Now you’re deciding when to add the community layer. The cost of waiting:
6+ months of lost conversations
6-12 months of lost SEO momentum
30-50% lower event attendance
No engagement visibility
The infrastructure communities need compounds when built from the start. Retrofitting costs 3x more in time, lost data, and member re-training.
Not just SEO but AEO 🤩
yes, that too :p
Zach H. Joel P. I threw something together here: https://docs.google.com/document/d/1awEbVm9yonXLX8Le9Du-SNwmoBGkva2NlgF4gbkot9E/edit?usp=sharing
Oooooo. commenting. thanks
So far so great. Falling asleep as I'm getting through the end but that's on me having a busy week. I'll look over the rest this week Este and will incorporate back. Thanks
1
