Case study/SaaS
AWS costs down 30%+ for a US B2B SaaS platform
unicrew became the programming team for a B2B SaaS platform that had run for over a decade, streamlined how it used AWS and Heroku, and sped up rollouts.
unicrew became the programming team for a US B2B SaaS company whose business platform had been running for over a decade. By streamlining how the platform used AWS and Heroku, unicrew helped bring their AWS costs down by 30% or more. The engagement began under our former Artelogic brand.
- Focus
- SaaS
- Market
United States- Engagement
- Dedicated development team
- Stack
PHP
AWS
Heroku
Outcome at a glance
What this project delivered, in numbers.
- 30%+Lower AWS costsClient-reported, vs. their previous setup
The challenge
The client is a US B2B SaaS company in New York. Their business platform had been live, and fully functioning, for over a decade. What they wanted was a programming team to support overall web development, with one goal stated plainly: faster and safer development.
Our approach
unicrew embedded as the client’s dedicated development team. The scope covered web development, new feature work, and streamlining server usage across PHP, AWS, and Heroku. Three points of contact ran the relationship, a developer, a business manager and a project manager, with day-to-day work running on Jira and WhatsApp.
Changing programming teams on a platform that old is mostly a knowledge problem, and it is the client’s own read on it too: his advice to anyone doing the same is to build conduits that move institutional knowledge into the new team. That is what the transition period was for. unicrew also helped the client scope future projects involving AI.
Streamlining what a platform spends on AWS and Heroku is what our cloud cost and AI-readiness audit is built to find: where a platform is overspending, and what to do about it.
Results
The engagement started in December 2023 and was still running when the client reviewed it. The client reviewed it on Clutch in October 2024, and everything below is his account rather than ours.
- AWS costs came down by 30% or more, after unicrew streamlined how the platform used AWS and Heroku.
- Products were developed and rolled out significantly faster than with the previous service provider.
- A higher rate did not mean a higher bill. Because the work went faster, in the client’s words the team “wound up costing us less or at least the same”.
- Moving onto a new programming team, from a platform that had run for over a decade, was a smooth transition.
Different platform, same shape of work: on a B2B CRM platform unicrew moved the infrastructure to Azure and stayed on afterwards for DevOps. Other clients describe their own engagements, in their own words, on our client reviews page.
“Artelogic does a very good job of delivering and following up on work.”
Patrick W., Founder & President, B2B SaaS Company (USA)
What the client says
Artelogic has enabled us to develop and roll out products significantly faster than our previous service provider. The team has great knowledge of AWS and Heroku, which has helped us streamline and reduce costs. Artelogic has helped us reduce our AWS costs by 30% or more.
04/Technologies
Technologies on this project
Backend
- PHP
Cloud
- AWS
- Heroku
05/Quick answers
The questions behind the project
What did unicrew do for this B2B SaaS platform?
unicrew became the client's programming team, taking on ongoing web development for a US B2B SaaS business whose platform had been live and fully functioning for over a decade. The scope covered new feature development and streamlining server usage across PHP, AWS, and Heroku. In his Clutch review the client credits the team with helping reduce their AWS costs by 30% or more, and with rolling out products significantly faster than their previous service provider. The engagement started in December 2023, under our former Artelogic brand, and was still running at the time of his review.
How did unicrew help cut AWS costs by 30% or more?
By changing how the platform used AWS and Heroku. That is the mechanism the client describes: he credits the team's knowledge of both services with helping them streamline and reduce costs, and puts the reduction at 30% or more. It is one client's environment and one client's result, not a figure we quote in advance, which is why our cloud cost and AI-readiness audit starts by looking at your bill rather than by naming a percentage.
How did unicrew step into a codebase more than a decade old?
Through a transition period, as an embedded dedicated development team rather than a contractor at arm's length. Three points of contact ran the relationship (a developer, a business manager, and a project manager), with day-to-day work running on Jira and WhatsApp. The client's own advice to anyone changing programming teams is to build conduits that move institutional knowledge into the new team, and he describes what happened here as a smooth transition.
Did the higher rate make the engagement more expensive?
Not by the client's account. Patrick W. is direct about it on Clutch: "the pricing was higher than I had hoped", but because the team could work much faster than his previous service provider, "the team wound up costing us less or at least the same". Rate and total cost are two different numbers, and throughput is what separates them.