3 Steps to Selling Cloud-enabled Business Continuity, Disaster Recovery

Examine client policies and standards. The client’s specialized needs are the foundation of subsequent data protection and disaster recovery work. MSPs need an understanding of the operating requirements and environment. Also, revenue-producing systems and regulatory requirements can greatly influence BC/DR decisions.

Critically review existing systems. Scrutinize existing equipment with an eye toward systems that should be upgraded or consolidated. Outdated, unreliable underlying hardware, networking, storage, security, applications and bandwidth often can’t support sufficient BC/DR mechanisms and should be replaced or optimized. The same goes for software and management systems.

Develop a business impact assessment (BIA): The BIA maps BC/DR priorities including lines of jurisdiction, areas of primary business concern and the order in which systems will be restored. Here, you need to understand the client’s vital business processes, the interdependencies and relationships between the client’s systems and services, and, ultimately, the customer’s data loss tolerance. The BIA is an excellent tool for framing the continuing discussion on BC/DR needs with the customer and for selling long-term BC/DR engagements.

Deliver a comprehensive BC/DR plan: The assessment phase concludes with a follow-up to the BIA in the form of a more comprehensive BC/DR plan. This complete plan adds technical specifications, data recovery stratification mapping, and additional details such as testing schedules, contact trees and the parties responsible for reporting and mitigating disruptive events.

The value proposition: Real value is defined by what the service provider does, not the tools it uses. Consider the inherent value in the plans, policies, processes and professional support the solution provider brings to the BC/DR engagement. This demonstration of technical expertise, experience in supporting customers and the unique requirements of the target market encapsulate the value proposition in a way that will resonate with SMB buyers looking to entrust a partner with critical services such as BC/DR.

Product packaging: All of the constituent products, technologies and third-party services the solution provider collects when crafting a BC/DR offering are merely pieces of the puzzle. In aggregate, they make up the differentiated, value-added service SMB customers seek. Solution providers should conspicuously brand these products and services with proper names so that users will identify with the partner’s brand and unique value proposition.

Contracts and SLAs: In BC/DR services, performance is more than a promise; it’s a contractual function between provider and subscriber. Proper service-level agreements list the terms under which the MSP guarantees the restoration of data, applications and processes in the event of disruptions. These provisions are typically expressed as the recovery time objective (RTO), a measure of how quickly IT managers can find, access and retrieve protected assets; the recovery point objective (RPO), the time in which the service provider should be able to recover or roll back systems; and the recovery granularity objective (RGO), the level of detailed storage architecture recovery by file, block and transaction level.

Launch a small, manageable number of BC/DR offerings to start. Limiting the menu to one or two key offerings gives you an opportunity to focus on customer segments and gain experience from repeatable implementations. Going too broad at the start could overtax support resources.

Scout out early adopters. These first-line BC/DR customers will likely come from your existing SMB accounts. Leverage your existing knowledge of the client’s business and IT systems to help hone the continuity and recovery offering.

Set firm sales objectives. These should be defined in metrics such as number of leads, meetings and sales conversions, as well as in actual sales. This is the best way to test sales methodologies and determine if the BC/DR practice can generate sufficient revenue to recoup initial investments and support operations.

Field test and collect feedback. Though the BC/DR systems were tested early in the development phase, it is important to test them again under real-world conditions during the launch phase. Here, you can make adjustments and solicit feedback from early adopters to make sure client perceptions are positive. If the perceptions are negative, call a time out and determine next steps to improve your BC/DR service.