All case studies
How ICANotes unified FinOps, security, and compliance in one platform with Pump
$109K+
Saved on AWS spend
101
Security findings tracked across 4 frameworks
19
Cost reports created in Pump View
Boost your global cloud visibility and control with Pump. Share your email for details!
By submitting your email, you agree to opt in to marketing emails.
Overview
"We were already paying Amazon for compliance checking separately. We were able to cut that by using Pump directly, on top of the dashboards, anomaly detections, and cost optimization. That was initial cost savings we wouldn't have if we weren't with Pump."
Logan Hansen
IT Director
ICANotes builds electronic health record software purpose-built for behavioral health, used by thousands of mental health professionals across the US. The medium-sized company is 100% remote and runs virtually its entire infrastructure on AWS, with lean IT and DevOps teams managing everything from employee workstations to HIPAA-compliant production environments. With cloud spend touching every part of the business, from development to remote workspaces to security operations, having clear cost visibility and automated optimization is critical.
Industry
Behavioral Health Software
Integrations
Location
Annapolis, MD
Pump services
Use Case 1
Replacing a FinOps Tool with a Platform That Pays for Itself
ICANotes was spending over $5,000 per month on a dedicated FinOps platform that provided cost visibility, savings recommendations, and monitoring. When the team evaluated Pump, the math was straightforward: Pump Save would handle their commitment optimization, Pump View would replace the cost visibility and reporting their previous vendor provided, and Pump Secure would replace the AWS Security Hub compliance checks they were paying for separately. Instead of paying for three overlapping products, ICANotes consolidated into one platform at no additional cost.
Logan and his team now use Pump's recommendations to guide their Reserved Instance and Savings Plan decisions, coordinating directly with the Pump team whenever a major infrastructure change is on the horizon. When ICANotes was in the middle of migrating workloads from Windows to Linux, a project where mistimed commitments could mean paying double, Pump helped them sequence the moves so cost optimization stayed aligned with the technical migration. Logan described the value simply: "It was really useful to have Pump there to say, you guys are doing the right thing. Here's what you need to make sure is done before you schedule these moves."
[Screenshot: Pump View dashboard showing cost monitoring and anomaly detection]
Use Case 2
HIPAA Compliance Checking Without the Extra Line Item
As a behavioral health company handling protected health information, ICANotes has to maintain HIPAA compliance across their entire AWS environment. Before Pump, they were using AWS Security Hub for compliance scoring and framework checks, a service that came with its own cost. Pump Secure replaced that functionality directly. Logan now uses the compliance dashboards in Pump to monitor their HIPAA posture, export compliance reports for customer audits, and track which checks need attention from his security team.
For Logan, who also manages security operations alongside IT, FinOps, and even some DevOps, having compliance visibility inside the same platform where he manages cost optimization means one fewer product to context-switch into. When a customer asks for a compliance audit, the data is already in Pump rather than in a separate AWS console.
"I really like that feature. We already paid for a feature similar to that with Amazon. We were able to cut that by using Pump directly. That was initial cost savings that we wouldn't have if we weren't with Pump."
-- Logan Hansen, IT Director
Use Case 3
Timing Commitments Around Infrastructure Migrations, Not Guesswork
ICANotes doesn't treat commitment decisions as a set-it-and-forget-it exercise. The team has historically stuck with one-year, no-upfront commitments on EC2 because Reserved Instances could be resold if plans changed. But as their infrastructure evolves, with workloads shifting from Windows to Linux and future migrations planned from EC2 to ECS and Fargate, every commitment carries real risk if the timing is wrong.
Logan uses Pump software and team as a strategic checkpoint before making those calls. When ICANotes was mid-migration from Windows to Linux, Logan and his team coordinated directly with the Pump team to make sure they weren't locking into commitments on instances that were about to be decommissioned. Now, as they look at RDS and MemoryDB, where commitments can't be resold, they're evaluating whether partial or full upfront terms make sense for stronger savings. Rather than making those decisions in a vacuum, Logan pressure-tests them with the Pump team first: "Here's what we're thinking. Is this a bad idea, terrible idea? Is it a great idea?"
"It was really useful to have Pump there to say, you guys are doing the right thing. Here's what you need to make sure is done before you schedule these moves. I think it made a considerable difference for us to be able to get those projects completed."
-- Logan Hansen, IT Director
Pump’s impact
The most immediate impact for ICANotes was eliminating roughly $60,000 or more in annual costs from their previous FinOps vendor alone. By replacing that platform ($5-6K/month) and AWS Security Hub with Pump's Save, View, and Secure products, Logan's team consolidated three separate vendor relationships into one. The savings were realized before Pump even started optimizing their AWS commitments.
Beyond the consolidation, Pump changed how ICANotes approaches infrastructure decisions. Logan now treats Pump as an extension of his lean team, using commitment recommendations and anomaly detection to stay ahead of cost changes instead of reacting to them. When major projects come up, like migrating from Windows to Linux or planning a future move from EC2 to ECS and Fargate, Logan coordinates with the Pump team to make sure commitment timing aligns with the technical roadmap. The team also uses Pump View to tag and categorize spend by purpose, separating employee workspace costs from production infrastructure costs so the finance team sees clean reporting.
Looking ahead, ICANotes is planning several infrastructure shifts that will deepen their use of Pump. They're evaluating moves from EC2 to ECS and Fargate for better redundancy and reduced management overhead, and they're considering shifting from one-year no-upfront commitments to partial or full upfront terms on RDS and MemoryDB to capture stronger savings. Logan also plans to install CloudWatch agents for memory metrics on key instances so the team can act on Pump's rightsizing recommendations with full confidence.