Of all the midmarket CRM packages we tested, UpShot is the only one that provides seamless integration with desktop applications, its own modules and back-office applications.
Of all the midmarket CRM packages we tested, UpShot is the only one that provides seamless integration with desktop applications, its own modules and back-office applications. Were it not for a moderately kludgy interface and some suspect performance numbers, UpShot would be about as perfect a solution as one can get in the hosted CRM space.
There is nothing inherently wrong with UpShots GUI: The systems designers have allowed an enormous amount of data to be displayed (see screen), and the buttons have been simplified to reduce performance drag on upload. Overall, every button does what it says it will do, and the menu items are most often well-thought-out.
Whats quirky is that UpShot mixes and matches at least four types of navigation items on single pages, and then doesnt carry them through in each section. For example, accessing the Calendar tab will display icons for the day, week and month. And in the same location on Whats Up (a generic task list) are Delete Selected and Delete All. In that same vicinity on the Task, Contacts and Deals tab are Info To Go, Search and Communicate. The interface forces users to continually focus on different parts of the screen to figure out what theyre doing.
However, UpShot is the CRM package that is best designed for integration. UpShot actually has three integration strategies: a wireless development framework that allows developers to build connections between wireless devices and the UpShot system; a desktop integration strategy that connects Microsoft Office products to the UpShot service; and an enterprise integration strategy based on XML and SOAP.
UpShot is based completely on Microsoft Windows technologyusing SQL Server 7 and SQL Server 2000 as the core database and Internet Information Services as its Web server. UpShot requires IE on Windows or the Macintosh for full functionality. UpShot also offers a "modem view" that provides a simplified but functional view into the CRM data from any browser on any operating system. However, the modem view is displayed over an unsecured connection.
Architecturally, UpShot uses separate systems for secure log-in, core CRM functionality and XML API activity. Changes made during customization are automatically detected and replicated across to the other application servers.
This multitier architecture provides a high degree of flexibility. The sacrifice may be performance, however. It took UpShot significantly longer to do record lookups than its core competitors, according to our Keynote benchmark. However, while there is a significant performance gap between UpShot and the fastest hosted CRM application, the performance is satisfactory across the board.
Where UpShot is clearly better than its competitors is in the area of desktop integration. UpShot includes downloads for Outlook e-mail integration; a nicely designed, fat offline client; a template for Microsoft Word, Excel and PowerPoint; and some syncing capabilities between Outlook and UpShot. In fact, UpShots desktop integration is better in some ways than Microsofts own MS-CRM, which uses Outlook as its client access software.
As the director of eWEEK Labs, John manages a staff that tests and analyzes a wide range of corporate technology products. He has been instrumental in expanding eWEEK Labs' analyses into actual user environments, and has continually engineered the Labs for accurate portrayal of true enterprise infrastructures. John also writes eWEEK's 'Wide Angle' column, which challenges readers interested in enterprise products and strategies to reconsider old assumptions and think about existing IT problems in new ways. Prior to his tenure at eWEEK, which started in 1994, Taschek headed up the performance testing lab at PC/Computing magazine (now called Smart Business). Taschek got his start in IT in Washington D.C., holding various technical positions at the National Alliance of Business and the Department of Housing and Urban Development. There, he and his colleagues assisted the government office with integrating the Windows desktop operating system with HUD's legacy mainframe and mid-range servers.