Reduce Cloud Costs & Improve Performance
Lower your AWS or Azure bill without slowing anything down, with every change backed by your actual usage data.
Shane Schlabach · AWS Solutions Architect – Professional · 12+ years in AWS & Azure · Remote across the US
Overview
I start by looking at where cloud spend is actually leaking: idle dev environments running overnight, instances sized for peak demand that never materialized, and resources nobody's revisited since the day they were deployed.
From there, I apply a mix of native tooling and habits: right-sizing based on actual utilization data rather than guesses, scheduling non-production resources to stop outside business hours, committing to reservations where usage is predictable, and reviewing spend regularly instead of after a bill spikes.
None of this requires exotic tooling; AWS and Azure both provide the cost visibility and automation required. I use them consistently and tie every cost decision back to real usage data instead of intuition, reducing costs without sacrificing reliability or performance.
Selected work
Examples from enterprise production environments I've led. Client names are kept private.
Move .NET services to Docker on ECS with autoscaling
- Problem
- .NET services ran on Linux EC2 instances sized for peak traffic around the clock, and every rollout meant updating servers one at a time.
- What I did
- Containerized each service with Docker, deployed them to Amazon ECS, and added autoscaling based on actual demand.
- Result
- Consistent builds and deploys, no more server-by-server rollouts, and infrastructure costs down about 25% with no application code changes.
How engagements work
Every engagement starts with a free, no-obligation conversation. Project work is $150/hour with scope agreed up front, or ongoing care as a monthly managed service.
- 1
Discovery
What you run today, where it hurts, and what “done” looks like.
- 2
Plan
A written roadmap: options, sequence, and what I would touch first.
- 3
Build
Infrastructure, automation, and security — as code, in your accounts.
- 4
Support
Monitor, patch, and keep changing it as the workload changes.
Common questions
Who will I be working with?
Me, Shane Schlabach. The person on the first call is the person doing the work. There are no account managers and no handoffs to junior staff.
How much does it cost?
Project work is $150/hour, with scope and a plan agreed before work starts. Managed service starts at $2,000/month and is scoped after a review of your environment.
Do you work with companies outside Ohio?
Yes. I'm based in Cincinnati, Ohio and work remotely with teams across the United States.
Who owns the code and documentation?
You do. Everything is built in your own AWS or Azure accounts and source control, with handoff documentation so your team can run it without me.
How do we get started?
Use the form below to send a few sentences about where things stand. I reply within one business day, and the first conversation is free with no obligation.