I went on travel and just built it right on spot with them. So on top of everything, Resco allowed me on-site development. Instead of sitting in the office, I said ‘Hey, let’s just do this, let’s build this kind of thing together.’ They were co-author of the built itself, which is a big success.

The ability to provide Mobile CRM functionality also to people who are not part of our organization, and to have them integrate directly with our Dynamics CRM data & processes, has allowed us to explore solutions to problems that we did not previously think possible.

Since Resco gives us the benefit of working offline we plan to deploy it with our service technicians as well. Those guys work remotely, in different factories at various customer locations. On site, they have to fill out all this paperwork with the service information and once they return to the office, they need to retype it into CRM. It is quite a tedious task which can affect the quality of the information. Having an iPad with the Resco app, the technicians will be able to put in the service data to the CRM right then and there. And even if there’s no Internet throughout the day, next time they get connected they just hit “Sync” and all the information is uploaded to the company CRM.

Resco CRM helped Bayer CropScience solve two challenges at once. The first and the major one –to complete the implementation within 4 months. The result? Only two people working on the project got it done in less than 100 days. The whole implementation experience didn’t interfere at all with other on-going work on the CRM project.

The team loves using the app. Any time we have any issues, the Resco Support Team is always there to help. But I mean, in depth help – it’s nice that we can talk to first-line support. But to even go as far as developers, it’s really a personal touch you have. With other providers, they seem 100 layers away, but with Resco, it feels like a partnership.

Resco Mobile CRM was easy to install and the configuration effort proved to be less than originally expected. When we have new developments on the Microsoft side, to have these developments available in the Resco client is less demanding than originally thought. We know we have an overhead if we do configuration in MS CRM—we have to change that in Resco as well. But it’s not huge, so it’s not a problem.