saasups maps every dependency, scores every application against the 7 R's, and produces an executable AWS roadmap with a FinOps cost model attached — before a single ticket is written.
All figures, profiles, and cost models on this page are illustrative examples of saasups outputs. They are not actual customer results.
modelled EC2 cost reduction (target architecture vs. current)
Illustrative
0
writes to source systems — read-only discovery
Illustrative
0
days from first scan to board-ready roadmap
Illustrative
Example engagements
Three sectors. Three estates. One consistent output.
The profiles below illustrate the range of estates saasups is built for. All data is illustrative.
Global insurerIllustrative
A global insurer running 280+ on-prem .NET and Java applications across three legacy data centres
Situation
Eight years of acquisitions left the estate with no authoritative dependency map. Three previous lift-and-shift attempts had stalled at the discovery phase — teams could not agree on which applications shared databases or services.
What saasups mapped
280 applications catalogued and dependency-linked
Every shared database, message broker, and API endpoint surface-mapped
7 R's score assigned to each application (Rehost / Replatform / Refactor / Rearchitect / Rebuild / Replace / Retire)
After (modelled)£2.6 M/yr modelled AWS target-architecture cost — 38% reduction
Deliverable
Scored estate, cost model, and a wave-sequenced roadmap ready for engineering sprint planning
Fortune-500 manufacturerIllustrative
A Fortune-500 manufacturer with an ERP-anchored estate spread across 14 subsidiaries
Situation
A board mandate required 60% of workloads to run on AWS within 36 months. The central architecture team had no single view of the application estate across subsidiaries — each BU maintained its own CMDB with different taxonomies.
What saasups mapped
14 subsidiary inventories consolidated into a single scored estate
SAP and Oracle dependencies modelled against AWS-native and managed alternatives
FinOps model built per wave: reserved-instance coverage, savings-plan recommendations, right-sizing targets
Before$11.4 M/yr across on-prem and co-location (blended)
→
After (modelled)$7.1 M/yr modelled AWS steady-state — 38% reduction, RI-adjusted
Deliverable
Executable 36-month roadmap, wave-sequenced, with each wave's cost delta pre-calculated
Healthcare SaaS platformIllustrative
A healthcare SaaS platform managing PHI workloads across a mixed AWS + private-cloud estate
Situation
Rapid growth meant new microservices were deployed faster than the architecture team could document them. A compliance audit flagged undocumented data flows as a risk. Engineering leadership needed a current-state architecture — not a 12-month consulting engagement.
What saasups mapped
190 microservices and 34 data stores dependency-mapped in 48 hours
PHI data-flow paths identified and tagged against HIPAA boundary requirements
Before$2.9 M/yr AWS spend (over-provisioned, high inter-AZ traffic, no RI coverage)
→
After (modelled)$1.95 M/yr modelled optimised spend — 33% reduction with RI and right-sizing
Deliverable
Compliance-annotated dependency map, scored estate, and a prioritised refactor backlog
Before / After
What the cost model produces
Every saasups engagement outputs a FinOps cost model comparing your current-state run cost against the target architecture. Figures are pre-calculated per wave — not a back-of-envelope estimate.
Figures below are illustrative outputs from a saasups cost model, not actual customer data.
Illustrative. Actual savings depend on estate composition and commitment terms.
In their words
What engineering leaders say about the output.
Role-attributed illustrative quotes. Not actual customer testimonials.
"
We had spent six months trying to build our own dependency map in Confluence. saasups produced a scored estate in 36 hours. That is not a small difference — that is a different class of tool.
VP Engineering, enterprise insurer (illustrative)
"
The board asked for a FinOps-grounded roadmap, not a technology wish list. The cost model gave us the language to have that conversation. Every wave had a cost delta attached.
Director of Cloud Architecture, Fortune-500 manufacturer (illustrative)
"
What impressed the compliance team was that the dependency map was generated read-only. No agents, no writes, no change windows. Discovery without risk.
CTO, healthcare SaaS platform (illustrative)
See your modernization path mapped — talk to a saasups architect