10%
AWS bill cut immediately upon integration
< 1 week
From kickoff to live savings
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 just integrated, and we started seeing savings right away. It was pretty surprising and pretty cool that we just integrated and literally 10% of the bill is cut. I don't know how it does that, I already see that on EC2, our bill is less."

Daniel Grek
CTO
SalesForge builds six interconnected sales tools covering everything from email infrastructure to multichannel outreach. The 45-person team runs all six products on AWS with a single DevOps engineer managing infrastructure. As they expand into data science and machine learning, keeping cloud costs predictable has become a priority.
Industry
Sales Technology Platform
Integrations

Location
Tallinn, Estonia
Pump services
Pump View
Use Case 1
Instant Savings Without the Reserved Instance Gamble
For most startups on AWS, meaningful cost savings require locking into reserved instances for one to three years. SalesForge couldn't make that bet. Their infrastructure spans six products, workloads are still maturing, and predicting capacity needs two years out wasn't feasible.
Pump Save eliminated that trade-off entirely. When SalesForge integrated, savings showed up immediately: a 10% reduction on their AWS bill with no manual configuration and no DevOps time invested. The integration itself was handled using Pump's pre-built CloudFormation stacks, and the whole process took less than a week from kickoff to live savings. Daniel described the experience as "pretty magical," with savings happening on autopilot without requiring engineering attention.
As SalesForge's workloads stabilize, the team plans to layer in Pump's reserved instance recommendations to compound those savings further.
Use Case 2
The CEO Stays Informed Without Opening Another Tool
At SalesForge, not everyone managing cloud costs wants to (or needs to) log into a dashboard. Their CEO stays informed through savings reports delivered directly to Slack, without ever opening the Pump platform. For the DevOps engineer who does use the dashboard day to day, the interface is self-explanatory and requires no learning curve.
This Slack-first approach fits how a 45-person startup actually operates. The DevOps team monitors savings and checks recommendations in the Pump dashboard when they need to go deeper. Leadership gets the headlines in Slack. No one has to context-switch into another tool to stay informed about cloud spend.
The team also has a dedicated Slack channel with the Pump support team, which Daniel called out as a major differentiator from other solutions they evaluated. Any question gets answered quickly, even though the platform itself rarely requires it.
Use Case 3
A Self-Service Dashboard That Doesn't Need a Learning Curve
With only one DevOps engineer and six products running on AWS, SalesForge needed cost visibility that didn't require a dedicated analyst to interpret. The Pump View dashboard gave them exactly that: a single view of spend across all six products, with optimization recommendations built in.
Daniel noted that the dashboard is "very self-explanatory," meaning their DevOps engineer can check savings, review reserved instance suggestions, and monitor spend trends without scheduling walkthroughs or reading documentation. As SalesForge grows its DevOps team, the dashboard is ready for more users without any additional setup. The team plans to activate Pump's budget alerts and anomaly detection next, adding proactive cost monitoring to the visibility they already have.
"Without us investing much time there, it's pretty magical that it just does the savings."
-- Daniel Grek, CTO
Pump’s impact
Since integrating Pump, SalesForge has seen an immediate 10% reduction in their AWS bill, without any manual optimization work from their engineering team. The onboarding process took less than a week using Pump's CloudFormation stacks, and their solo DevOps engineer didn't need to step away from core infrastructure responsibilities to get it running.
Beyond the cost reduction, Pump changed how SalesForge manages cloud spend visibility across the company. The CEO now tracks savings through Slack reports without logging into any platform. The DevOps engineer has a clear, self-service dashboard for monitoring costs and reviewing optimization recommendations, without it becoming another full-time responsibility.
SalesForge plans to act on Pump's reserved instance recommendations as their workloads mature and stabilize. Daniel also flagged interest in automated infrastructure optimization, specifically AI-driven rightsizing for EC2 and RDS, similar to what they've seen from tools like PGAnalyze on their Postgres databases. The team is also planning to set up Pump's budget alerts and anomaly detection to build proactive cost monitoring into their existing workflows.
