8 sure-fire ways to screw up a cloud contract

Read these tips before you sign anything

1 2 3 4 Page 2
Page 2 of 4

3. Don't vet the contract for hidden charges that might come back to bite you

Even people used to scrutinizing contracts for on-premises software can be tripped up by cloud service contracts, Scavo says. "Someone on your team needs to know what to look for, particularly when it comes to hidden charges such as exceeding a certain storage or bandwidth threshold. I've had a few customers get burned by that."

Scavo consulted with a seasonal business that saw its monthly bills soar by as much as 20% when daily transaction counts exceeded the contractual threshold. "Vendors aren't typically going to call your attention to things like that during the contract phase," so it's up to you to think it through and push back, he says.

4. Sign off on the contract before shopping around for better terms

Cloud vendors take different approaches to licensing, and one plan may fit your needs far more cost effectively than another, says Scavo. While many vendors base monthly subscription fees on the number of users or seats, some offer variations on that model. For example, with cloud ERP vendor Acumatica the price you pay depends on the amount of system resources you use, such as projected transaction counts, "so a growing business can add users without buying additional seats," Scavo says.

This is especially important with large-scale CRM or ERP systems because moving off those isn't easy. "There's a certain amount of vendor lock-in with SaaS providers that goes beyond what you have on premises," Scavo says, so get the right contract terms in place before you start down that road.

5. Don't worry about how multiple SLAs will affect the end-to-end performance of your business processes

When businesses use a combination of cloud services within the context of a single business process, end-to-end performance is only as good as the weakest service level agreement. "We're just starting to see the proliferation of cloud service-oriented architectures where you're piecing together numerous cloud capabilities to deliver a business process. If your SLAs are not aligned across that, you may have a weak link in the chain," says Mike Pearl, principal at PwC's advisory practice.

This has been a particularly painful problem for PwC clients that have allowed individual business units to sign contracts.

One client, a CIO of a multibillion dollar corporation, received a copy of a SaaS contract, signed by someone at one of the business units, that contained no language pertaining to backup, storage or access to data stored by the provider. "The biggest failure I see is organizations with a technology buying pattern that doesn't go through IT," Pearl says. "People think they have the background to negotiate these kinds of contracts, but often times they don't know what they don't know."

Pearl thinks that IT will eventually see the rise of a new breed of external integration brokers that can stitch together the cloud services that make up an end-to-end business process and make sure the SLAs are aligned. "They will act as resellers, and overlay their SLA over the SLAs they're getting from various cloud providers," he says, adding that he's had conversations with some vendors that have expressed an interest in entering that business. Today, however, it's up to IT and its procurement partners within the business to do all of the contract spadework.

6. Let the salesperson talk you into adding services that you're not ready to use

If you're thinking of deploying a new service next year, buy it when you're ready to implement rather than allowing it to roll into a renewal contract. Microsoft's Office 365 -- a SaaS suite that includes back-office components for Exchange, SharePoint and Lync as well as the familiar desktop apps -- is a prime example, says Paul DeGroot, principal at Pica Communications, which specializes in helping his clients navigate the Microsoft licensing maze.

1 2 3 4 Page 2
Page 2 of 4
Shop Tech Products at Amazon