Back to Insights

Case study

Managed Cloud Operations Across a Software Holding Company Portfolio on AWS

November 1, 2026

5 min to read

Read summarized version with

About project

Working time:

Since 2025

Industry:

Software holding company

The service:

Managed Services

Overview

The customer is a Canadian software holding company that acquires and operates vertical market software businesses. After each baseline review, Dedicatted brings the acquired company onto a common operating model and runs it under a managed service.

The Challenge

Every acquisition arrived different, and the group could not see risk or spend across its companies.

1. Separate Everything

Each company had its own accounts, billing, tools and security controls.

2. Nobody on Call

Small teams, sometimes reduced after the deal, had no formal on-call.

3. Uneven Protection

Web application firewalls and monitoring existed in some companies and not in others.

4. No Portfolio View

Leadership saw cost and incidents company by company, and only after the fact.

Technology & Approach

We created one onboarding path and one monthly operating model for every company in the portfolio.

Implementation

Acquisition Onboarding
For each company we take stock of accounts, workloads, access, findings and cost, connect the accounts to the group’s organization, apply baseline guardrails, logging, AWS WAF and monitoring, and take over on-call with runbooks for critical systems.

Monthly Operations per Company
Our engineers respond to incidents around the clock, patch and maintain the platform, follow up AWS Security Hub and Amazon GuardDuty findings, and track cost with tagging and showback for that company.

Cost Optimization
Each company gets a monthly review of rightsizing, idle resources and commitment coverage, with savings proposals sized and approved before any change.

Portfolio Governance
The group receives one monthly report across companies covering incidents, security posture, open risks and cost.

Customization & Client Adaptation

The operating model balances one group standard with each product’s own context.

Onboarding Straight After Closing

One company was onboarded in the weeks after its acquisition closed, before its original engineers moved on.

Same Baseline, Local Context

Guardrails are common across the portfolio, while runbooks reflect each product.

Showback per Company

Each company sees its own cost and savings, and the group sees the total.

One Report for Leadership

The operating partner reviews every company on one page each month.

If you find this case interesting, we recommend taking a closer look at

The Results

Several subsidiaries now run on the same security, AWS WAF and monitoring baseline, each has 24/7 on-call that no longer depends on who stayed after the deal, and the group reviews incidents, risk and cost for every company in one monthly report.

Long-Term Value

  • A repeatable path for every future acquisition.
  • Consistent guardrails across the portfolio.
  • Cost per company tracked from the first month.

Business Impact

  • Lower operational risk after each deal.
  • Savings found and approved company by company.
  • Leadership sees the portfolio, not just individual companies.

Contact our experts!


    By submitting this form, you agree with our Terms & Conditions and Privacy Policy.

    File download has started.

    We’ve got your email! We’ll get back to you soon.

    Oops! There was an issue sending your request. Please double-check your email or try again later.

    Oops! Please, provide your business email.