Weet Replaces Synchronous Calls With Timestamped Async Video Messages

01 /The Concept

Zoom fatigue has a structural cause that no ergonomic chair fixes: synchronous video calls demand your full attention in real time, even when the information being exchanged doesn't require it. Heet is a bet that most of what happens on video calls can be handled better, asynchronously.

The core mechanic is straightforward – teams exchange video messages instead of scheduling calls. What makes Heet different is how it handles replies. Rather than piling on separate response videos or text threads, recipients comment on specific moments in the original recording. Those comments – video, text, or emoji – are anchored to a precise timestamp in the source clip. It's the same leap Google Docs made over email-with-attachments: instead of a chain of disconnected responses, you get a structured conversation organized around the original artifact.

The platform auto-generates a text summary, subtitles, and a full transcript for every message. That means recipients can scan the gist without watching a second of video and decide whether the full clip warrants their attention. For messages they do watch, playback at 1.5x or 2x is table stakes – something live calls can't offer. Add it all up, and the time cost of a video exchange drops dramatically compared to scheduling, joining, and debriefing a live call.

02 /Why It Matters

Weet wasn't built as a product strategy. It was built out of necessity inside Speach, a separate startup, after the founder noticed her work schedule had consumed her family time. Her daughter's drawing – a child asking "Mom, are you still on Zoom?" – made the problem concrete enough to act on. The team built an internal async video tool for themselves, found it worked, and turned it into a standalone product.

This origin story is worth noting because some of the most defensible B2B products come from exactly this pattern. Mailchimp started as an internal tool at a web design agency. Slack was built for the team at a gaming startup that never shipped its game. Internal tools built under real operational pressure tend to solve genuine problems in ways that market-research-driven products don't. The founders aren't hypothesizing about the pain – they lived it.

03 /Opportunities

The shift from synchronous to asynchronous communication follows a clear historical arc. Voice calls gave way to text messaging not because calling is inferior in every context, but because async text fits more naturally into how people actually organize their days. Video calls are the new voice calls – the default synchronous medium that will, over time, lose ground to async alternatives as better tools emerge.

Weet is an early signal of that shift in the video layer. The tools aren't fully mature yet, which is itself the opportunity.

For teams thinking about where to build: the internal-tool-to-product path is underexplored. If your organization has quietly built something to solve a workflow problem – something your team actually uses every day and would miss if it disappeared – that's worth examining seriously. The question isn't whether internal tools can become startups. The question is whether the problem your tool solves is specific enough to your team or universal enough to justify building a company around it.