Software adoption is a key component of success, most often a stumbling block.  Reality of software adoption often leads to inferior architectures such as server-based solutions that uses browsers like dumb terminals.  Most of web applications are based on such inferior architectures.  Lack of rich clients leads to complex and akward solutions for common problems like identity, discovery, session management, scalability, workflow, interactivity, and bandwidth.  Deeper understanding the dynamics of software adoption is essential for success.  Some observations on software adoption:

People dislike installing plugins.  With the exception of well known plugins such as Acrobat and Flash, plugin software adoption is a discouraging proposition.  I think this is because, for most plugins, the perception of security risk is higher than apparent benefits offered by those plugins.  Acrobat and Flash plugins both offer visible and significant benefits as well as being well known: a well travelled road to a place where people wants to go.  Another contributing factor is that plugin installation is encountered in route, that is while you are surfing, and people don't like being interrupted.

People don't mind installing programs.  It is strange that, while people don't usually install plugins which are usually small in size, they are perfectly willing to download and install programs which are much larger.  I think one of the reasons for this disparity has to do with visibility.  Programs are clear visible, their locations are known, and they sit until you invoke it.  On the other hand, plugins are often not visible, location is unknown, and they are invoked by artifacts from outside (aka web pages).

Above two observations leads me to think that a set of plugins packaged as a program has a better chance of adoption than a lone plugin.  An alternative is to package a set of plugins as a service that manages and updates plugins automatically.  I think Business Browser can benefit from such a service.