News for hackers. Stuff that matters.

A comment on Dispatch launches a discussion layer for Dropbox and Google Docs. Parent comment

Re:Dispatch launches a discussion layer for Dropbox and Goog... by nickstamas on Tuesday September 11, 2012 @04:11PM (#4507559)
Hi, I'm Nick, one of the founders. I really appreciate the thoughts on our product. We're focused on smaller teams for now, because we are a small team and are building Dispatch to be the tool we wanted to use. It's not just about being notified when something changes, (which Growl is great for), it's being able to have a discussion with the full context of whatever you're working on. We find that having a central place to facilitate this discussion is really valuable.

We also believe that the integration model, versus wholesale adoption of an entire platform, is what we prefer for our team. We love the products we integrate with for what they do, but we wanted something better than email to keep things organized and focused.

[ Parent | on HN ]
Re:Dispatch launches a discussion layer for Dropbox and Goog... by joewee on Tuesday September 11, 2012 @04:33PM (#4507652)
Nick thanks for the response. I think you guys are really sharp. Why not just add a way to migrate organizations off the disparate platforms into your single solution? Perhaps that's the transition into paid?

Wholesale adoption becomes important as a company gets bigger for a lot of reasons, security, centralized accounts, centralized billing.

[ Parent | on HN ]
Re:Dispatch launches a discussion layer for Dropbox and Goog... by nickstamas on Tuesday September 11, 2012 @04:46PM (#4507705)
Thanks :). That's an interesting thought, but right now we're focused on the value we can to these existing services. We have intentionally launched with a core set of features that we believe is the foundation for other things that become useful in this context, like search across integrations and versioning.

I totally agree that the game changes when you're trying to sell large enterprises on adopting something company-wide, but there is a precedent in products like Yammer that start by gaining adoption with small teams and organically grow out. That's the type of model we're interested in exploring.

[ Parent | on HN ]