Hi, I run a site called www.twibs.com and work with a lot of businesses on twitter and I can tell you that twitter is not completely over-crowded at this point and your ability to reach customers will not be dominated by large media. More importantly, the open conversation of twitter allows your message to travel without limits through the network, so you can potentially reach as many people who want to listen, which is very very valuable. FYI, this list is more for development issues and less business case, but I would say that you should without a doubt utilize twitter. The api is an up-and-running in an hour system with 100% feature replication. I have yet to find another offering like it.
On Thu, Feb 19, 2009 at 6:41 AM, retep70 <[email protected]> wrote: > > Hi there: > > We're in the midst of developing our own, in-house community for a > fairly robust existing website. We're planning on having a status > feature that allows people to convey things not unlike Facebook's > status update product. However, I'm interested in exploring the > incremental business benefit of utlizing Twitter's API and adding its > features. So basically the question is: how do I evaluate the > business benefits of implementing an in-house status feature versus > Twitter's? > > Thank you. >
