If you’re thinking about doing something new in the cloud, there is a good chance you’re wondering how much it is going to cost you. The thing is, it’s not just the price tag for the cloud itself but also additional software, professional services, and work of your team.
We have been delivering cloud projects for 6+ years across multiple project types, technologies, industries, and geographies. It makes us pretty comfortable to discuss the project cost, cloud cost, and all the elements which form your cloud project price tag.
Still, it is based solely on our experience, and so these estimates might vary to some extent. Why? Because the prices here are based on averages, and there are many variables.
The final cost always depends on multiple factors and business needs. I will try to cover and explain it in this guide, so you can have an idea of what it may look like in your case.
So, let’s break it down!
Your project will have two major cost variables:
Let’s deal with professional services costs first.
A typical organization starts its cloud project with partner selection. It allows you to move faster and leverage the experience of someone who did it before.
In some cases, partner support might also come with your cloud vendor package – either attached to the cloud purchase you’ve made or in subsidized project support.
Professional services for the cloud are delivered in two main models:
Here’s a summary of features that easily shows the differences.
It will vary across geographies, as in some countries T&M is a standard way to do it. However, here are the general guidelines.
That’s a good question. We know that hourly rates might vary greatly depending on the industry, geography, and current demand on the market
Typically, you can expect the hourly rates in the range between $60/hr and $180/hr but it depends on many factors. What influences these rates?
You can expect different rates for junior-level people who deliver tasks that are well defined (lower price range) and for senior / architect-level people, who can define the overall task and break it down into smaller stages (higher price range).
There are cloud areas that are easier to implement and those which are more complex and in demand. For standardized cloud services, you can get rates in the lower ranges. For cloud areas that are still complex or in great demand, you can expect a higher range of rates.
No time to read? Watch the video instead!
What are the more complex or in-demand cloud roles?
It always changes but at the time of writing, here are the most frequent roles:
Typically, you will experience a blended labor rate, dependent on the assigned team structure, with an average between $90-120/hr.
These are the usual rates in our case. They might be higher or lower than your local partners (depends on your geography). For us, there are additional factors that may affect project rates:
You can typically expect higher rates than those discussed here if you engage with big brands, e.g. Microsoft Consulting Services, or the Big 5 in consulting.
Fixed-fee project cost is defined in two areas:
The size and price of these projects will vary across providers. Here are some examples of a typical project delivered across many organizations, where I have averaged the prices of our services and those of companies we know.
Microsoft 365 security services deployment
Projects in this area vary based on the scope and size of the organization. Typical project cost is between $20,000 (initial services deployment, advisory) and $200,000 (full-service deployment of all M365 services, enterprise-scale customer 10k+ employees).
Cloud governance and landing zone deployment
A typical project in Cloud Governance and landing zone deployment area is done by larger-scale customers with more than one cloud subscription.
Its size varies depends on the scale and needs of the organizations between $45,000 (mid-size enterprise with few resources deployed already in the cloud and simpler on-premises environment) and $150,000 (enterprise-grade environment, complex security, and compliance requirements, complex network environment).
Cloud DevOps engagements
It is hard to speak of a typical DevOps engagement, but usually, we see two types of projects delivered in the organization:
The cost of those projects will vary between $20,000 (entry-level project, mid-size organization) and $100,000 (full DevOps deployment, enterprise organization with 10k+ employees).
In short, you can expect three sizes of projects related to cloud deployment:
Disclaimer: as I wrote earlier, these are averages we see across the industry and geographies. Your actual cost of a project will land somewhere on this scale, depending on your organization size, type of project, area, and overall complexity.
Now we have professional services covered, let’s look at the cloud service cost profile.
Your cloud project cloud resources project cost will vary depends on the following factors:
Your cloud bill depends on what you consume in your project. That’s a given. (Almost) every resource in the cloud will increase your costs. It isn’t true that it can’t be predicted up-front, at least to some degree.
What you need to remember when thinking about cloud resource cost is:
You can estimate your expenses with tools provided by your cloud vendor. For Azure, you can use Azure Pricing Calculator to estimate your cloud bill based on your planned resources.
The cost of your cloud resources might depend on the method you purchased from your vendor. Here are the typical options to purchase cloud.
You attach your credit card to the subscription(s) and pay for resources as you consume them. Most convenient and easy to use, but in most cases not the best from a financial point of view.
It’s good for a start and the initial phase of using cloud resources, or if you don’t want to engage in any other kind of relationship. You process all payments and invoicing directly with your cloud vendor.
Cloud Service Provider (CSP)
Purchase of cloud through a dedicated partner of your cloud vendor. For Microsoft Azure, this option is called Cloud Service Provider (CSP).
How is a CSP different from Pay-as-you-Go?
You sign a cloud agreement directly with a cloud vendor. This option is used typically by a larger organization and requires some up-front commitment or pre-purchase of the volume of cloud credits towards your usage. With Microsoft, this option is available through Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA) options.
In direct comparison, Pay-as-You-Go is typically the most expensive option with CSP being optimal for many customers and EA providing some negotiation options with a vendor but requires up-front commitment and is reserved for the largest accounts.
Your final cost will depend on the last, but crucial factor – cloud optimization methods you use in your environment.
Every cloud vendor provides multiple ways to optimize the cost of resources in the cloud. Cloud providers have different ways to deploy these services and names for them. I will cover here the most typical methods for Microsoft Azure but if you use other vendors, they will have similar options available.
Reserved resources or usage
Reserved resources or usage of resources can cut your bills up to 40% – basically, you commit to using those resources for a longer time and you pay this cost up-front or in specific installments for a discount.
It is a great way to cut the cost of resources like Virtual Machines or Storage accounts. If you finish using those resources earlier – no problem. There is a model to re-calculate the costs and settle them with a vendor.
Using specific types of subscriptions
Cloud vendors typically provide subscriptions for development and test purposes. The limitation might be in the legal agreement or SLA on these subscriptions, which makes it less suitable for production workloads, but for dev/test purposes it provides a great reduction in cost.
Bring your own license
For many resources (VMs, appliances, SQL databases) you can bring your licenses if you have them and apply them to the cloud resources. It can cut the cost of the services up to 40-50%, depending on the type of resource.
Those optimization models can be combined with the way you purchase your service. For example, you can get your purchase through a CSP provider and get a volume discount, and on top of that apply those optimizations to reduce the total cost further under your discount.
As you can see, cloud project costs might vary – key factors are the type of the project and the size of your organization. The way you purchase the cloud resources and how you optimize it also is important, especially when the size of your cloud bill will increase.
I hope this guide gives you an idea of what the cost of your project might be. You should also have an indication of the main areas where you can look out for cloud cost itself to try to optimize it. Feel free to post questions below or contact us if you’d like to know more.
If you're thinking about doing something new in the cloud, there is a good chance you’re wondering how much it is goin...
Predica started back in 2009, and since then a lot has changed in terms of how we operate, deliver, and achieve our goal...