@fra_dechirico @bradleyjrodgers @ropesandhopes At @CampaignMonitor, our design team ran entirely on Photoshop workflows. When we tried switching to @sketch + @InVisionApp, it wasn’t just about new tools. We had years of assets, templates, and team processes tied to Photoshop.

The switch took months. Not because of the files. But because we had to rebuild our collaborative workflow. That’s the real friction in churn.

It’s the same with sales tools where mutual action plans become the source of truth. Or text docs where annotations are the conversation - tied to specific paragraphs, in context.

The best companies make leaving painful at the team level, not just the individual. This is what I call collaborative switching costs.

When workflows are built around shared data: comments, notifications, multiplayer editing, etc Your product becomes embedded in how teams work together.

The data backs it up: When 3+ people interact around shared content, network effects kick in. Time spent rises, and churn plummets. Because leaving isn’t just swapping tools. It’s retraining teammates + rebuilding processes from scratch.

Most SaaS founders are trying to solve individual churn. But the real opportunity? → Build team-based workflows. When collaboration lives inside your product, churn looks very different.

If you’re working on collaborative features and want to see how teams are killing churn like this in just a few days with our SDK, DM me.

@stevenfabre @fra_dechirico @bradleyjrodgers @ropesandhopes Tired: churn Wired: team-based workflows

@TurnerNovak @fra_dechirico @bradleyjrodgers @ropesandhopes Spot on! 🫡

@stevenfabre @fra_dechirico @bradleyjrodgers @ropesandhopes Agreed but not every product lends itself to team based workflows. These are also notoriously hard to shape accurately and engineer. These ideal is that it’s already baked into the product and audience

@markojak_ @fra_dechirico @bradleyjrodgers @ropesandhopes « These are also notoriously hard to shape accurately and engineer » 💯 and that’s exactly why I started @liveblocks

@stevenfabre @fra_dechirico @bradleyjrodgers Great thread, very well put @stevenfabre 🙌 Still reminisce over that design team we had back then, from time to time ✨

@ropesandhopes @fra_dechirico @bradleyjrodgers Thank you! I miss those days!

@stevenfabre @TurnerNovak @fra_dechirico @bradleyjrodgers @ropesandhopes Most SaaS backs are broken on churn: patch vs. fundamental value. Retention's about whether they'd fight to keep you, not another nudge.

Building with AI? Your vector database choice will make or break it. @Jrowny just published a guide breaking down the real trade-offs between @pinecone, @qdrant_engine, @pgvector, @weaviate_io, @milvusio, and more.