Cloud Presales

3/31/2023
Digital Innovations for the Present
and Future

DAVID JOSEPH,JOSEPHJAVA@HOTMAIL.COM
What is Cloud Presales
Cloud presales refers to the process of working with prospective customers to understand
their needs and requirements for cloud computing solutions, and then demonstrating how a
particular cloud service or solution can meet those needs. Cloud presales typically involves
working closely with the customer to understand their business requirements, technical
infrastructure, and current and future IT needs.

During cloud presales, the presales team will typically provide detailed technical information
and product demonstrations to the customer, and work to address any concerns or
questions they may have. They may also work closely with the customer to create
customized proposals and solutions that meet their specific needs.

The ultimate goal of cloud presales is to help the customer understand the benefits of cloud
computing and how a particular cloud solution can help them achieve their business
objectives. By providing detailed technical information, product demonstrations, and
customized proposals, cloud presales teams can help customers make informed decisions
about which cloud solutions are right for their organization.

Cloud Presales Process

The cloud presales process typically involves the following steps:

1. Discovery: This is the initial phase of the presales process where the presales team
works with the customer to understand their needs and requirements. This includes
gathering information about their current IT infrastructure, business objectives, and
any pain points they may be experiencing.

2. Solution Design: Based on the information gathered during the discovery phase, the
presales team works to design a solution that meets the customer's specific needs.
This includes identifying which cloud services and products would be best suited for
the customer's requirements and designing a customized proposal.

3. Demonstration: The presales team will often provide a demonstration of the

proposed cloud solution to the customer. This may include showcasing specific
features and functionalities of the cloud service and answering any questions the
customer may have.

4. Proposal: Based on the solution design and demonstration, the presales team
creates a detailed proposal that outlines the scope of the project, the expected
timeline, and the cost of the proposed cloud solution.

5. Proof of Concept: Depending on the complexity of the proposed cloud solution, the
presales team may provide a proof of concept to the customer. This involves setting
 up a test environment to demonstrate how the proposed cloud solution would work
in the customer's specific use case.

6. Closing: Once the customer has reviewed and accepted the proposal, the presales
team works with the customer to finalize the details of the project and prepare for
implementation.

Overall, the cloud presales process is designed to help customers make informed decisions
about which cloud solutions will best meet their needs and provide a smooth transition to
cloud computing.

Creating a Cloud Sales Pitch

Creating a cloud sales pitch involves understanding the customer's needs and
communicating the value proposition of cloud computing in a clear and concise way. Here
are some steps to create an effective cloud sales pitch:

1. Understand the customer's needs: Before creating a cloud sales pitch, it's important
to understand the customer's business and IT requirements. This includes
understanding their current infrastructure, pain points, and business objectives.

2. Identify the value proposition of cloud computing: The next step is to identify the
benefits of cloud computing that will be most relevant to the customer's needs. This
may include cost savings, scalability, flexibility, and improved security.

3. Customize the pitch for the customer: Using the information gathered in step 1 and
2, create a customized pitch that speaks to the customer's specific needs and pain
points. This may involve tailoring the language and examples used to make the pitch
more relevant to the customer.

4. Use real-world examples: To make the pitch more compelling, use real-world
examples of how cloud computing has helped similar businesses achieve their goals.
This may include case studies, testimonials, or industry statistics.

5. Address potential objections: Anticipate potential objections that the customer may
have and address them proactively in the pitch. This may involve addressing
concerns around data security, compliance, or cost.

6. Provide a clear call-to-action: Finally, provide a clear call-to-action that encourages

the customer to take the next step. This may involve scheduling a follow-up call or
providing a demo of the cloud solution.
Creating a Cloud theme/roadmap
1. Define the objectives: The first step in creating a cloud roadmap is to define the
objectives of the migration. This may include reducing IT costs, increasing agility,
improving scalability, or enhancing security.

2. Assess the current environment: The next step is to assess the current IT
environment, including hardware, software, and applications. This will help to
identify any dependencies or compatibility issues that need to be addressed during
the migration.

3. Determine the target architecture: Based on the objectives and current

environment, determine the target architecture for the cloud migration. This will
include identifying the cloud services and providers that are best suited for the
organization's needs.

4. Plan the migration phases: Once the target architecture is defined, plan the
migration phases. This may include a phased migration approach that prioritizes
critical applications or business units, or a "lift and shift" approach that migrates all
applications at once.

5. Identify the migration tools and resources: Identify the migration tools and resources
that will be required to support the migration. This may include cloud migration
tools, DevOps tools, and resources such as cloud architects and engineers.

6. Define the migration timelines and milestones: Define the timelines and milestones
for each phase of the migration. This will help to ensure that the migration stays on
track and that any issues are identified and addressed in a timely manner.

7. Plan for post-migration support: Once the migration is complete, plan for post-
migration support. This may include ongoing monitoring, performance optimization,
and security management.

Designing a Cloud Infrastructure

Designing a cloud infrastructure involves several steps that are critical to ensuring a scalable,
secure, and cost-effective cloud environment. Here are some steps to design a cloud
infrastructure:

1. Define your requirements: Before designing your cloud infrastructure, you need to
identify your business and technical requirements. This includes factors such as
workload demands, scalability needs, security and compliance requirements, and
budget.
 2. Choose your cloud service model: Decide which cloud service model is best for your
business - Infrastructure as a Service (IaaS), Platform as a Service (PaaS), or Software
as a Service (SaaS).

3. Choose your cloud provider: Select a cloud provider that offers the services and
features that align with your business and technical requirements. Major cloud
providers include Amazon Web Services (AWS), Microsoft Azure, and Google Cloud
Platform (GCP).

4. Choose your cloud deployment model: Decide which cloud deployment model is
best for your business - public cloud, private cloud, or hybrid cloud.

5. Architect your cloud infrastructure: Create an architectural design that outlines the
components of your cloud infrastructure. This includes compute resources, storage
resources, networking, security, and backup and recovery mechanisms.

6. Choose your cloud tools and services: Select the cloud tools and services that will
help you manage and optimize your cloud infrastructure. This includes cloud
management platforms, automation tools, and monitoring and analytics tools.

7. Implement your cloud infrastructure: Implement your cloud infrastructure, including

provisioning compute and storage resources, configuring networking, and deploying
applications and services.

8. Test and optimize your cloud infrastructure: Test your cloud infrastructure to ensure
that it meets your performance, scalability, and security requirements. Optimize
your cloud infrastructure to ensure that it is cost-effective and delivers the expected
benefits.

Cloud Design Models

There are several types of cloud design that an organization can choose from, depending on
their business needs and technical requirements. Here are some of the most common types
of cloud design:

1. Public cloud design: A public cloud design involves using shared infrastructure
provided by a cloud service provider. The resources are accessible over the internet,
and users only pay for the resources they consume. Public cloud designs are typically
used by small businesses, startups, and enterprises that need scalable infrastructure
and services without having to invest in on-premise infrastructure.
 2. Private cloud design: A private cloud design involves deploying cloud infrastructure
within a company's own data center. The resources are not shared with other
organizations, and the infrastructure is managed by the organization's IT staff.
Private cloud designs are typically used by enterprises that need more control over
their infrastructure, have specific security or compliance requirements, or require
high levels of customization.

3. Hybrid cloud design: A hybrid cloud design involves using a combination of public
and private cloud infrastructure. Organizations can choose to use a public cloud for
some workloads and a private cloud for others, depending on the specific
requirements of each workload. Hybrid cloud designs are typically used by
enterprises that need to balance cost, scalability, and security requirements.

4. Multi-cloud design: A multi-cloud design involves using multiple cloud service

providers for different workloads. Organizations can choose to use different cloud
providers for different services or applications, depending on the specific
requirements of each workload. Multi-cloud designs are typically used by enterprises
that need to avoid vendor lock-in, reduce risks associated with relying on a single
cloud provider, or optimize costs by choosing the most cost-effective cloud provider
for each workload.

How to build a Cloud Development Environment

Building a cloud development environment can be a complex process, but here are some
general steps that you can follow:

1. Choose a cloud provider: There are several cloud providers available, such as
Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure.
Choose a provider based on your needs, budget, and the features they offer.

2. Create a virtual machine (VM): A VM is a software emulation of a physical computer

that can be used to run applications. Create a VM on the cloud provider's platform
and install an operating system of your choice.

3. Install necessary software: Once you have a VM set up, you will need to install the
necessary software for your development environment. This may include text
editors, IDEs, compilers, and other tools.

4. Configure the network: Set up the network to allow you to connect to your VM
securely. This may involve configuring firewalls, setting up a VPN, or configuring
access control.
 5. Configure backups and disaster recovery: It's essential to have a backup and disaster
recovery plan in place to prevent data loss. Configure regular backups and test your
disaster recovery plan.

6. Scale up or down: As your development needs change, you may need to scale up or
down your cloud environment. Cloud providers offer scalability features that allow
you to add or remove resources as needed.

7. Continuously optimize the project: Continuously monitor and optimize the project to
ensure that it meets the desired performance, security, and scalability requirements.

Overall, building a cloud development environment requires careful planning and

configuration to ensure that it meets your needs and is secure and reliable.

How to prepare a cloud proposal

1. Understand the client's needs: Start by understanding the client's business
requirements and objectives. Identify their pain points and the problems they want
to solve with a cloud solution.
2. Research cloud service providers: Research and compare cloud service providers that
align with the client's needs and budget. Consider factors such as pricing, features,
security, reliability, and support.
3. Define the project scope: Define the scope of the project, including the timeline,
deliverables, and budget. Ensure that the project's scope aligns with the client's
needs and objectives.
4. Identify the cloud architecture: Define the architecture of the cloud solution,
including the necessary components such as virtual machines, storage, networking,
and security. Ensure that the architecture aligns with the client's needs and
objectives.
5. Provide a cost analysis: Provide a detailed cost analysis of the cloud solution,
including the initial setup costs and ongoing operational costs. Include any potential
cost savings that the cloud solution may provide.
6. Address security and compliance: Address security and compliance concerns by
outlining the security measures and compliance standards that will be implemented
in the cloud solution.
7. Develop a migration plan: Develop a migration plan that outlines the process for
migrating the client's existing infrastructure and data to the cloud environment.
8. Provide a project roadmap: Provide a project roadmap that outlines the timeline,
milestones, and deliverables of the cloud solution implementation.
9. Consider ongoing support: Consider the ongoing support that will be required to
maintain and optimize the cloud solution. Include a plan for ongoing support and
monitoring in the proposal.
 10. Review and refine the proposal: Review the proposal for completeness, accuracy,
and alignment with the client's needs and objectives. Refine the proposal as
necessary before submitting it to the client.

Remember to tailor your cloud proposal to the specific needs and objectives of the client,
and to provide clear and concise information to help the client make an informed decision.

Cloud Solution Blueprint

A cloud solution blueprint is a detailed plan that outlines the architecture, design, and
implementation of a specific cloud solution. It provides a comprehensive overview of the
cloud environment and the solution that will be implemented in it.
Here are some key components of a cloud solution blueprint:
1. Solution overview: The blueprint should provide an overview of the cloud solution,
including its purpose, benefits, and expected outcomes.
2. Architecture: The blueprint should define the architecture of the cloud environment,
including the necessary components such as virtual machines, storage, networking,
and security. The architecture should be aligned with the requirements of the
solution.
3. Design principles: The blueprint should outline the design principles that will be
followed in the cloud environment and the solution, such as scalability, availability,
and security.
4. Resource allocation: The blueprint should define the allocation of resources, such as
virtual machines, storage, and networking components, to support the workload
requirements of the solution.
5. Security measures: The blueprint should outline the security measures that will be
implemented in the cloud environment and the solution, such as access controls,
encryption, and monitoring.
6. Integration with existing systems: The blueprint should address the integration of
the cloud environment and the solution with existing systems and applications, such
as on-premises infrastructure and third-party services.
7. Disaster recovery and business continuity: The blueprint should define the disaster
recovery and business continuity plan for the cloud environment and the solution,
including backup and recovery procedures, failover mechanisms, and testing
procedures.
8. Performance optimization: The blueprint should address performance optimization
for the solution, including workload placement, load balancing, and performance
tuning.
9. Cost optimization: The blueprint should address cost optimization for the solution,
including the selection of cost-effective resources, optimization of resource usage,
and monitoring of costs.
10. Implementation plan: The blueprint should provide a detailed implementation plan
for the solution, including the timeline, tasks, and responsibilities for each phase of
the implementation.
Remember to tailor the cloud solution blueprint to the specific needs and requirements of
the project and to document any assumptions and constraints that may impact the
implementation. Regularly review and update the blueprint as the project progresses to
ensure that it remains relevant and accurate.

Overview of AWS Cloud Lens

Cloud Lens is an AWS Well-Architected Tool that provides an automated approach to
reviewing workloads based on the AWS Well-Architected Framework. The tool enables users
to identify any areas of their workload that may require further attention or optimization.

The AWS Well-Architected Framework provides a set of best practices and guidelines for
designing and operating reliable, secure, efficient, and cost-effective systems in the cloud. It
consists of five pillars: operational excellence, security, reliability, performance efficiency,
and cost optimization.

The Cloud Lens tool uses automation to perform a comprehensive review of the workload
against the AWS Well-Architected Framework pillars. It then generates a report that
highlights areas of the workload that require improvement or optimization.

Some of the key features of Cloud Lens include:

1. Integration with AWS Well-Architected Tool: Cloud Lens integrates with the AWS
Well-Architected Tool, enabling users to view their workload's compliance with the
AWS Well-Architected Framework.
2. Customization: Cloud Lens enables users to create custom lenses based on their
specific requirements and use cases. This allows users to focus on the specific areas
of their workload that are most important to them.
3. Automated review: Cloud Lens uses automation to perform a comprehensive review
of the workload, reducing the time and effort required to identify areas of
improvement or optimization.
4. Continuous monitoring: Cloud Lens provides continuous monitoring of the workload
to ensure that it remains compliant with the AWS Well-Architected Framework over
time.
Using Cloud Lens can help users to identify any areas of their workload that may require
attention or optimization, enabling them to improve the reliability, security, performance,
and cost-effectiveness of their cloud-based systems.

Overview of Azure Well Architected Tool

For Azure, there is a similar tool called Azure Well-Architected Review. This tool provides an
automated approach to reviewing workloads based on the Azure Well-Architected
Framework. The Azure Well-Architected Framework is similar to the AWS Well-Architected
Framework and consists of five pillars: cost optimization, operational excellence,
performance efficiency, reliability, and security.
The Azure Well-Architected Review tool helps users to identify any areas of their workload
that may require attention or optimization. It provides a report that highlights the
workload's compliance with the Azure Well-Architected Framework pillars and recommends
improvements and optimizations.

Some key features of the Azure Well-Architected Review tool include:

1. Integration with Azure Advisor: The Azure Well-Architected Review tool integrates
with Azure Advisor, which provides recommendations for improving the
performance, security, and cost-effectiveness of Azure workloads.
2. Customization: The tool allows users to customize their review by selecting the Azure
services and features they want to include.
3. Automated review: The tool performs a comprehensive automated review of the
workload against the Azure Well-Architected Framework pillars.
4. Continuous monitoring: The tool provides continuous monitoring of the workload to
ensure that it remains compliant with the Azure Well-Architected Framework over
time.

Using the Azure Well-Architected Review tool can help users to identify any areas of their
workload that may require attention or optimization, enabling them to improve the
reliability, security, performance, and cost-effectiveness of their Azure-based systems.

Overview of Google Cloud Well Architected Review.

In Google Cloud, there is a similar tool called the Google Cloud Well-Architected Framework.
The Well-Architected Framework provides a set of best practices and guidelines for
designing and operating reliable, secure, efficient, and cost-effective systems in the cloud. It
consists of four pillars: operational excellence, security, reliability, and performance
efficiency.

Google Cloud's Well-Architected Framework provides a structured approach to reviewing

workloads based on the framework's pillars. The framework helps users identify any areas
of their workload that may require attention or optimization and provides guidance on how
to improve them.

The Google Cloud Well-Architected Framework includes a tool called the Well-Architected
Review. The tool provides an automated approach to reviewing workloads based on the
pillars of the Well-Architected Framework. It generates a report that highlights areas of the
workload that require improvement or optimization.

Some key features of the Google Cloud Well-Architected Review tool include:

1. Integration with Google Cloud Console: The Well-Architected Review tool is

integrated with the Google Cloud Console, making it easy to use and accessible.
 2. Customization: The tool allows users to customize their review by selecting the
Google Cloud services and features they want to include.

3. Automated review: The tool performs a comprehensive automated review of the

workload against the pillars of the Well-Architected Framework.

4. Continuous monitoring: The tool provides continuous monitoring of the workload to

ensure that it remains compliant with the Well-Architected Framework over time.

Using the Google Cloud Well-Architected Review tool can help users identify any areas of
their workload that may require attention or optimization, enabling them to improve the
reliability, security, performance, and cost-effectiveness of their Google Cloud-based
systems.

Comparison /Equivalence Table of Services across AWS,Azure and

Google Cloud
Analytics

AWS Service Azure Service GCP Service Description

Athena Serverless
Interactive Analytics
Service
AWS Clean Rooms Easily and Securely
Collaborate on
Collective Datasets
without Sharing on
Revealing underlying
raw data
Cloud Search Managed Search
Service
AWS Data Exchange Easily find,subscribe
to and use third
party data

Compute Services
Services AWS Azure GCP
IaaS Amazon Elastic Compute Virtual Machines Google Compute
Cloud Engine
PaaS AWS Elastic Beanstalk App Service and Google App
Cloud Services Engine
Containers Amazon Elastic Compute Azure Kubernetes Google
Cloud Container Service Service (AKS) Kubernetes
Engine
Serverless AWS Lambda Azure Functions Google Cloud
Functions Functions

Database Services
Services AWS Azure GCP
RDBMS Amazon Relational SQL Google Cloud SQL
Database Service Database
NoSQL: Key– Amazon DynamoDB Table Google Cloud
Value Storage DatastoreGoogle Cloud
Bigtable
NoSQL: Amazon SimpleDB Azure Google Cloud Datastore
Indexed Cosmos DB

Storage Services
Services AWS Azure GCP
Object Amazon Simple Blob Storage Google Cloud Storage
Storage Storage Service
Virtual Server Amazon Elastic Managed Disks Google Compute Engine
Disks Block Store Persistent Disks
Cold Storage Amazon Glacier Azure Archive Google Cloud Storage
Blob Storage Nearline
File Storage Amazon Elastic File Azure File Storage ZFS/Avere
System

Networking Services
Services AWS Azure GCP
Virtual Amazon Virtual Private Virtual Networks Virtual Private Cloud
Network Cloud(VPC) (VNets)
Elastic Load Elastic Load Balancer Azure Load Google Cloud Load
Balancer Balancer Balancing
Peering Direct Connect ExpressRoute Google Cloud
Interconnect
DNS Amazon Route 53 Azure DNS Google Cloud DNS