Velt Sells Collaboration Features So You Don't Have to Build Them

The Macro: Every SaaS App Wants to Be Multiplayer

There’s a pattern in B2B software that repeats itself with predictable regularity. A company builds a single-player tool. It gets traction. Customers start asking for collaboration features. And then an engineering team that was supposed to be building the next big product feature spends six months implementing comments, presence indicators, notifications, and real-time cursors instead.

Figma made multiplayer the expectation. Before Figma, most design tools were single-player experiences where collaboration meant exporting a file and emailing it. After Figma, every SaaS buyer started asking “can multiple people work on this at the same time?” The answer became table stakes.

The problem is that building real-time collaboration infrastructure is genuinely difficult engineering work. You need WebSocket connections, conflict resolution, presence tracking, permission systems, notification routing, and a comment system that actually threads correctly. Each of these is a meaningful engineering project on its own. Together, they represent months of work that doesn’t move your core product forward.

Liveblocks is probably the most visible company in this space, offering a real-time collaboration API with a developer-friendly approach. Tiptap has a strong position in collaborative text editing. And there’s always the option of building on top of Yjs or Automerge, the open-source CRDTs that handle conflict resolution. But those are primitives, not products. You still have to build the UI layer, the notification system, and everything else.

The market signal is clear: collaboration features are expected in B2B software, building them is expensive, and most teams would rather not do it themselves.

The Micro: A Google PM Who Noticed the Pattern

Velt provides drop-in collaboration components for SaaS applications. Comments, presence indicators, notifications, and real-time collaboration, packaged as components that developers can add to their existing apps. The pitch is that you can ship in days what would otherwise take months to build internally.

Rakesh Goyal is the co-founder and CEO. He spent nine years as a Product Manager at a large tech company, where he launched products including AR in Maps and Search. That background is relevant because he would have seen firsthand how much engineering effort goes into collaboration features inside large-scale products. He’s based in San Francisco, and Velt came through YC’s Winter 2022 batch.

The product positions itself as “The Collaboration Stack for B2B,” which is a clear statement of intent. Rather than offering one piece of the collaboration puzzle, Velt wants to be the entire layer. Comments, cursors, presence, notifications, all from a single SDK.

What makes this approach interesting is the component model. Instead of providing a framework that developers have to build on top of, Velt offers pre-built UI components that can be dropped into an existing application. For an engineering team that’s been told “we need comments by next quarter,” the difference between integrating a component library and building a comment system from scratch is potentially weeks of saved time.

The risk with component libraries is always customization. Every SaaS app has slightly different requirements for how comments should work, where presence indicators should appear, and how notifications should be routed. If Velt’s components are too rigid, teams will hit a wall when they try to make the experience match their product’s design language. If they’re too flexible, the setup becomes complex enough that the “days not months” promise starts to erode.

From what I can see on the site, Velt is live and actively positioning for the B2B market. The developer-facing documentation and component approach suggest they’ve thought carefully about the integration experience, which matters enormously for a product like this. Developers will try it in a weekend project before committing to it in production.

The Verdict

I think the market timing is excellent. The demand for collaboration features in B2B software is real and growing, and most engineering teams resent building them because it’s infrastructure work that doesn’t differentiate their product. That resentment is Velt’s best friend.

At 30 days, I’d want to see integration stories. How long does it actually take a real team to go from zero to working comments in their production app? The “days not months” claim is the entire value proposition, and it needs to hold up in messy, real-world codebases, not just clean demo apps.

At 60 days, the question is whether Velt’s components are customizable enough for production use. Every SaaS app thinks its collaboration needs are unique, and Velt has to thread the needle between opinionated defaults and enough flexibility to match different design systems.

At 90 days, I’d look at retention. Developer tools live and die by whether teams keep using them after the initial integration. If Velt becomes a dependency that just works, it’s extremely sticky. If teams find themselves fighting the component library to get the behavior they want, they’ll rip it out and build their own, which is the worst possible outcome for a product that’s supposed to save engineering time.

The competitive landscape is real but not crowded. Liveblocks is the most direct comparison, but there’s room for multiple approaches. Velt’s bet on pre-built components rather than lower-level primitives is a distinct positioning, and if the execution is clean, it’s a faster path to adoption for teams that don’t want to think about CRDTs.

I’d use it for a side project this week and evaluate it properly within 30 days.