We aim for a 15-20% cost reduction in identified savings opportunities.
Generally, 60% of our identified savings require less than a month of engineering time to implement.
The findings and recommendations in a Cost Optimization project are a scintillating cocktail of:
Say goodbye to constantly wondering, “Why does the bill have to be that high?”
With a Cost Optimization project, you’ll be able to address what’s in your AWS environment today in a way that accounts for both the technical and financial perspectives.
Because we take the time to understand your business, AWS environment, and what you want to accomplish, our bill analysis and recommendations go far beyond what Amazon’s Trusted Advisor or other SaaS offerings provide. You don’t just get a report breaking down AWS spend based on team and environment. You get specific, tailored insights and guidance, including:
- A proper, in-depth analysis of your bill
- Recommendations to optimize costs that speak to how your business and underlying AWS framework work
- Actionable next steps for your team to discuss and your engineers to implement
Working with The Duckbill Group (versus handling this internally) is advantageous because we have a deep level of expertise in Cost Optimization and AWS billing, require no ramp-up time, and we find the savings quicker.
You’re covered by our
What you get
A succinct report with 5-8 “big win” optimizations to reduce your bill. Plus, quick billing wins we find along the way. (We can’t help it. We get excited about saving you money.) You and your team can implement these recommendations quickly — so quickly, in fact, that you’ll likely see the effects on your very next bill.
You’re probably thinking…
Couldn’t we just take care of this internally?
Most people (Corey Quinn excluded) don’t join a company to work on the Amazon bill. Let your engineers dedicate their time to delivering value for your customers instead of babysitting the AWS bill for unexpected changes.
If you do decide to tackle your bill internally, it’ll likely be the first time your team approaches a problem like this in an AWS environment. Altogether, you’ll need:
- Someone who can understand the business strategy for your company and turn it into meaningful cost KPIs that support the direction your teams, products, and company are going.
- Someone who can bridge the gap between Finance and Engineering and translate those vastly different languages across your company to help create a culture of cost savings.
- Someone to handle the engineering piece and dive deep on your AWS architecture, design patterns, and the nuances of AWS billing. And who’s fluent in engineer-speak, so they can help lead your engineers to implement the changes.
- Someone who’s tied into what AWS is doing right now, who can sift signal from noise, and understand what the opportunities look like for your organization. (It’s our job to stay on top of the 20+ daily AWS updates and releases, but it’s a waste of your valuable engineering time to expect the same of your team.)
Approaching a complex problem like this doesn’t rattle us one bit. In fact, the reason that The Duckbill Group can do all this (and revel in your AWS environment) is that our team of Cloud Economists and Cloud Analysts have extensive experience in finance, engineering, and AWS.
Isn’t it usually pretty obvious where the savings are?
Yes and no.
At Duckbill, we see a new AWS environment every single week, on average. And as you know, there just aren’t that many new things under the sun. Thanks to this combination of experience and exposure, we see common patterns continue to emerge. For example: globally, 65% of spend is on EC2, and the top five are the usual suspects (EC2, EBS, RDS, data transfer, and S3). It’s rare that we go into an account that doesn’t tend to follow that model.
Other insights are less obvious, and thus virtually invisible to anyone who doesn’t spend week after week digging into different environments. So that’s why the answer to this question is “Yes and no,” or “It depends.” Because knowing when to work on cutting costs, when to stop, and when to spend more is valuable knowledge that’s highly dependent on your unique situation, architecture, and business. Simply put, there’s no API for business insight
What does an engagement
Well, assuming you’ve played your cards right, somebody’s getting a diamond.
To ensure the smoothest, most productive engagement for your organization, we start our work with a discovery portion where we strive to become informed about your unique environment.
We meet with your engineering teams associated with crucial cost savings at both scales. We spend several days of effort in our initial investigation to understand your application and all the unique constraints you have with it. Engineering effort required from you during our analysis is low (we’ll only need about 5-10 hours of engineering time over the engagement for conversations about your environment). Rest assured that our involvement will be minimally disruptive to your team.
The engagement wraps with a report, a presentation where we walk you through our findings, and Q&A.
Can you help manage our relationship
In a word, yes, though we can’t officially promise it.
You get the benefit of our extensive network of AWS staff, where we can work on problems on your behalf. We spend significant time building relationships inside Amazon beyond the account teams — in fact, we count many AWS staff among our personal friends and valued colleagues. This inside knowledge gives us an unusually clear perspective and an uncanny ability to get tricky situations resolved quickly (should the need arise).
What other problems can
As consultants, we’re here to take problems off your plate, not dish up new ones.
We recognize that your organization is facing its own unique set of painful challenges, so our services can be customized to your needs. Some of our clients also ask us for help with:
Add-On: AWS contract negotiation (EDP, PPA, MAP)
We can act as agents of your company in liaising between you and AWS, as well as discussing desires, constraints, and strategy with internal stakeholders (e.g., Product, Engineering, Finance). Our role is to help you get the best deal for your organization.
Why work with The Duckbill Group?
Working with us gives you certainty about your AWS infrastructure.
You’ll have a clear roadmap to improving and controlling your AWS spend, which will equip you with the knowledge you need to explain and justify three important things:
- Where all the money is going
- Why those expenditures are valuable
- What you’re doing to control costs
We work for you, not AWS
We don’t get a dime from anyone for recommending you do something. You can trust us.
We don’t take a percentage of your savings
We only bill one way: fixed-fee. You’ll always know what our help will cost before you sign anything.
We tailor recommendations to your business
You get advice that’s tailored to your unique situation, not a one-size-fits-nobody binder, or fancy-sounding suggestions with a negative ROI.
We get to the point
We give you a concrete plan that considers your current architecture, future goals, and what makes you unique and different from the average bill. We focus on big wins, not minutiae.
AWS cost optimization is complex and time-consuming.
Our experts can give you a succinct report with 5-8 “big win” optimizations to reduce your bill. Plus, quick billing wins we find along the way. (We can’t help it. We get excited about saving you money.)
You and your team can implement these recommendations quickly — so quickly, in fact, that you’ll likely see the effects on your very next bill.
If you’d like some help from experts (we see an average of one new AWS bill a week!), let’s chat.
Prefer the phone? Give us a call: +1 (833) AWS-BILL