If you’re here, you’re probably staring at your AWS bill wondering what’s going on and why you didn’t just become a peanut farmer. You're not alone. 

Lucky for you, I’m here to help. I work with people just like:

  • CFOs who want to gain visibility and insight into their infrastructure spend breakdown
  • Engineering managers who want to be able to budget more effectively, without having to change your application architecture
  • Even engineers who want to be able to keep costs down via 'good citizen' efforts without slowing down the release of new features

How can I help you?

Let's face facts. AWS lets you move far more quickly than traditional datacenter deployments do, until the monthly bill gives you an unpleasant shock. Twenty-six cents an hour per instance seems so welcoming-- but at scale, adds up to tens or hundreds of thousands of dollars a month. By the time you realize it, you're unclear as to what's running in your environment, who built it, and where to even start digging in.

You open the AWS billing console to look around, but it manages to make things worse instead of better. Giant spreadsheets with costs broken out by service are great, but you need to actually make decisions about your spend—not get mired in endless analyses.

Amazon would like to have you think that all you need to sort this out is billing reports saved to an S3 bucket, imported to your RedShift cluster that you then query using a SQL client-- since you must obviously moonlight as a data scientist. How... straightforward.  

Imagine if you had an analysis of what you're spending money on that went beyond what Amazon's Trusted Advisor or other PaaS offerings provided. Not just a report that broke down AWS spend based upon team and environment, but analysis of your bill that spoke to how your business works-- with actionable next steps. You'd be able to address what's in your AWS environment today, without having to spend days of your time in Excel every month.

It's not just beneficial to you, either: think about the impact on your corporate culture. Your engineers would be happier with more specificity- "we've got to cut costs" becomes "that dev cluster you spun up last week is costing us $22,000 a month; can we scale that back a bit?" And your finance team would vastly prefer your newfound forecasts over your old "best guess."  

Sounds great, right? I'll have a brief discussion with one of your team members to understand what your cloud workloads look like, and then query AWS's systems to get visibility into where your money is going. From there, I'll be able to assess where you are, where you want to be, and how to get there without disrupting the day to day work your team is doing. 

Worried I won't find anything to optimize in your environment?

I totally understand. In all my years of helping companies just like yours optimize their AWS bill, not once have there been no actionable improvements found. I’m so confident that I can identify improvement opportunites that if I can't I'll refund your entire assessment fee AND partner with you to write a case study on how you've achieved such a remarkable feat. 

I can have Amazon's Trusted Advisor give me a pile of suggestions. Why would I pay you?

Trusted Advisor (and the other cloud costing vendors) are fantastic at analyzing savings improvements such as Reserved Instance purchase opportunities, resizing of over-specced instances to more cost-efficient sizes, and identifying idle EBS volumes. What they lack is context into how your business functions, and insight into your specific needs-- they just give you a list of changes to make that don't reflect the reality of your organization's infrastructure.

Unlike Trusted Advisor, I'm not dropping a report on your desk and walking out the door-- or worse, charging you a percentage of your bill in perpetuity! I offer more than an assessment of where you stand today: I give you a concrete set of next steps and a plan for the future that shows consideration for your goals and architecture. 

Any number of people can give me a report of what my AWS spend looks like, and then ride off into the sunset. What makes you different?

My analysis isn’t "a report" so much as it is as it is a way to understand what you’ve got, what you’re doing, and where your pains are. Think of it like a first date. It’s impossible to say what date #2 looks like (or if there even will be one!) without the first date.

Every analysis I deliver features not just what you're spending money on today, but concrete next steps to reduce cost-- which you can implement with or without me. 

What comes after the initial assessment?

That depends entirely upon what the assessment discovers, as there's no one-size-fits-all solution. If your development environments take up 3% of your monthly bill, it may not make sense to turn them off when they're not in use as a first step.

A few of the followups my clients have found helpful include:

  • Lambda functions to handle cost management for you-- automatically
  • An interactive training / brainstorming session with your engineers around costing principles, and how to architect applications for your business with those in mind
  • "Tips and Tricks" for negotiating with AWS account managers (yes, you really CAN negotiate with Amazon!)

My engineers can do this for me. Why should I pay you?

Your engineers are fantastic across a broad range of skills that are specific to your business's needs. They likely excel at provisioning resources, troubleshooting performance issues, writing the code that keeps your environment working-- and doing it all with dedication and drive.

However, remarkably few companies have dedicated personnel who focus purely on cost control approaches in AWS. Amazon's offering is constantly changing, as are their pricing tiers. This is all that I focus on-- leaving your engineers free to focus on doing what they do best.

I'm busy. I don't have time to sit with you for days on end explaining how my environment works.

I've been a consultant for a long time. I understand that time is the most precious resource you have, and am skilled at getting the relevant data in very short order. My discovery discussions don't take much time-- far less time than your monthly scrutiny of your AWS bill probably takes!

What kind of access will you need? I’m not comfortable giving you access to my confidential data.

I'm a strong advocate for the Principle of Least Privilege, and the good news is that I don't need much. I won't need access to your servers, application, or configuration data at all. I simply need a AWS account that has read-only access to AWS usage and billing metrics. (I will provide you with an IAM policy to use when you create my account.)

Working with the Quinn Advisory Group is a unique experience compared to other consulting firms:

  • I focus solely on AWS cost control, which means you get the benefits that come with deep specialization and experience in one area.
  • I don’t bill hourly, daily, or weekly— I only offer fixed prices. The final price will never be a surprise. The price I give upfront is the price you pay and never a penny more. 
  • I am selective with my clients to ensure I provide the highest value possible. If your monthly AWS bill is around $20K or more, you are a great fit for my services. If you are under this size, my services are not a good fit for you-- but I'd be thrilled to refer you to someone who specializes in solutions at your scale.

Let's see how we can improve your bill together.

My schedule fills up quickly, so act soon! I give my clients my full attention, which limits my ability to take on new clients to only one or two a quarter, so act now to reserve a spot in my calendar.