Let’s expand on what we discussed last week in terms of a managed services offering versus an SMSA. To be entirely honest, there’s not a huge functional difference between ad hoc support hours and managed services hours, except that the latter offers significantly more scope flexibility. Rather than outsource a managed services contract to another company, RPI resources are available to assist with whatever helps you derive maximum value from your software, be it Hyland’s Perceptive Content, Infor CloudSuite, or another software RPI specializes in.
One thing managed services contracts are not intended for are new implementations. While RPI can perform a lot of really cool things within the context of a managed services contract, including upgrades, some custom development, system enhancements, Learnsets or OCR training, a separate statement of work for new designs and implementations is required because managing and delivering these projects is significantly more complicated.
One of RPI’s overriding themes is flexibility. We want all current and potential customers to know that we can be extremely flexible with how we approach support for you. If we’ve done an implementation for you recently and ad hoc support is the right fit for your organization, then that is a path we can definitely go down. There’s a joke in here somewhere about RPI being flexible and naming our software Yoga, right?
Please join us next week as we continue this managed services discussion!
