OK; twitter for enterprise, nice UI, not really seeing how you differ from Yammer.
Side topic; has anyone succeed long-term with get[name].com? Or do you always end up buying your dot-com name?
Side topic; has anyone succeed long-term with get[name].com? Or do you always end up buying your dot-com name?
This is how we currently aim to differentiate ourselves:
* Focused solution: do one thing well. We tried to avoid the urge to include extraneous features.
* Very low barriers to adoption. Start with one click.
* Simple, intuitive interface.
* True real-time, across browsers.
* Fast (e.g. no page reloads)
I hate to see yet another product become "a better twitter for ____." You'll get more press if you actually solve a real business problem in there.
How about making it integrate with ticketing systems, so that it's automatically updated? How about integrating with version control, so that commit messages share the story?
Obviously these things are developer focused, but these are the things that get missed in apps like this. Tell me what I'm doing, not the other way around. (obviously I should be able to talk too.)