fred_h

:wave: Great to hear from you, Jesse — and so interesting that we’re both still thinking about these same challenges all these years later. Collaboration is tough to get right, and we’ve definitely heard plenty of painful stories along the way too.

Wishing you the best with your work — I’ll be keeping an eye out for your launch. Good luck!

We do! In theory, we support infinite nested threads within conversations. In practice, we found that most folks don't go deeper than 3 levels. However, the functionality is there.

Thanks for flagging this use case for us and agree that Zoom/Teams are better suited for presenting vs supporting.

To your specific points:

#1 makes a lot of sense and I sense the "low friction" part of this is the key distinction.

#2 is something we have thought about through the lens of a yet to be built Zapier integration. This would effectively allow you to create more custom methods to route data from emdash into your CRM/other systems of record for customers. Curious if this approach would be interesting.

#3 is in theory supported today. There are several ways you could store/share playbooks for support engineers. For example, you can create a Team and upload the playbooks as shared resources.

Appreciate the feedback on this. We do want to focus folks on the product's value prop and remove distractions. I wouldn't say we are attached to the animations by any means and will have a chat with our team. Cheers.

Thank you for the feedback. That’s exactly the idea. We see it as "write once, share everywhere." Conversations, meetings, and decisions can generate useful context, and having summaries automatically show up right where people are already working saves time down the road.

Appreciate you reaching out about the summarization feature. Teams have been making use of it to save time. They like jumping directly to key moments of the meeting and also outright skipping meetings.

Thanks! We’ve definitely put a lot of thought into making emdash feel smooth, intuitive, and frictionless. We are constantly looking at all the seams where pieces connect and making sure they fit tightly.

We probably over-invested in some details, but we believe those small touches add up, kind of like getting that nice “thunk” when closing a well-built car door. Glad you noticed the polish—it’s something we really care about!

Hi, Fred here – I’m one of the founding team members. Thanks for the comment.

First, to the question about team sizes. We view "Startups" as generally teams with <25 users, followed by small/mid-sized "Growth" companies that have <250 employees. Beyond that, we anticipate most companies falling into the "Scale" category. That said, this could all be revised based on usage data and I will also update our website later today to reflect the above.

Regarding pricing, we haven’t finalized it yet because we’ve prioritized understanding how teams actually use emdash—what works, what doesn’t, and where we should focus.

Pricing is important, and we want to get it right. Typical usage patterns, evolving AI and cloud/infra costs, and where we fit competitively in the market are all variables we still need to explore. We’ll need to strike the right balance and be competitive enough with vis-a-vis the market.

It would be smart to start with a free trial before transitioning users to a paid plan. We’re still figuring out whether that should be time-based (e.g., 60-90 days), usage-based (e.g., after your 20th video meeting).

I get it – no one likes unexpected pricing shifts and when the time comes, we will be transparent about our thinking and communicate changes well in advance. Our goal is to build something sustainable, not just for us, but for the teams that rely on emdash. Hope this helps clarify.