Private equity sponsors evaluating an Adobe Commerce portfolio company face a specific TCO question that does not show up in normal platform-selection conversations. The hold period matters. The year-one spend tells the financial diligence story. The year-three spend tells the underlying-business story. The difference between the two is where most surprises live, and getting the model right at acquisition determines how the platform shows up in the value-creation thesis.
This piece is the framework Bemeir’s Adobe Commerce engineering practice uses when supporting PE diligence on a portfolio company running on Adobe Commerce. It is opinionated. Year-one costs are usually inflated by deferred work that should have already happened. Year-three costs are usually closer to the real run rate. Understanding the gap is the diligence work.
What “TCO” includes for Adobe Commerce
A complete TCO model for Adobe Commerce covers seven categories.
Licensing and subscription. For Adobe Commerce Cloud, the annual license fee scales with average daily revenue and is typically the largest single line. For self-hosted Adobe Commerce, the license is included in Magento Open Source but the supporting infrastructure costs land here.
Hosting and infrastructure. Servers, databases, cache, CDN, security. Adobe Commerce Cloud bundles much of this. Self-hosted Adobe Commerce requires explicit infrastructure investment.
Platform maintenance and operations. The retainer or in-house staff that handles patches, monitoring, incident response, and ongoing operational work.
Feature development and customization. The engineering work to build new functionality, integrate with new systems, and adapt the storefront to evolving business needs.
Extensions and third-party tools. The licensing fees for Magento extensions, search providers, personalization tools, and any other commerce-related software.
Integration costs. The ongoing cost of maintaining integrations with ERP, CRM, OMS, PIM, and other systems. Initial integration build typically lives in feature development; ongoing maintenance lives here.
Compliance and security. Audits, penetration tests, PCI DSS validation, and any compliance-related work that the business does annually.
Year-one inflation: where the surprises live
Year-one TCO is almost always higher than the run rate in years two and beyond. The inflation comes from five sources, and PE sponsors should expect each one in diligence.
Deferred maintenance is the most common. The portfolio company has been running on an unsupported Adobe Commerce version, with missed patches, accumulated technical debt, and infrastructure that has not been refreshed in years. Year one spends meaningfully on catching up to a healthy baseline. The cost is real but it is a one-time payment.
Replatform or major upgrade is the second. If the diligence reveals the store needs to migrate from Magento 1, upgrade major versions of Adobe Commerce, or rebuild the storefront on Hyvä or headless, year one carries the bulk of the cost.
Integration rework is the third. ERP integrations, OMS integrations, and other system connections often need attention in year one because they have drifted, broken silently, or were built against versions that are now obsolete.
Security and compliance gaps are the fourth. PCI scope, GDPR readiness, and basic security hygiene work that has been deferred routinely surfaces in year one.
Knowledge transfer and documentation is the fifth. The portfolio company often has no usable documentation of the storefront’s architecture, customizations, or operational patterns. Year one invests in producing the documentation that should already exist.
The composite effect is that year-one TCO can run 1.5 to 2.5 times the year-three run rate for a portfolio company that has been operationally underinvested in. The diligence question is whether the inflation is one-time catch-up or whether it represents structural complexity that will recur.
Year-three run rate: what the actual business costs
By year three, the catch-up work is done. The platform is on a current version. The integrations are stable. The team or agency partner has settled into a cadence. The year-three TCO is the more honest representation of what the platform actually costs to operate.
The components by year three typically look like this for a mid-market Adobe Commerce store doing 50 to 200 million in GMV.
Licensing and subscription: 60,000 to 200,000 dollars annually, depending on revenue tier on Adobe Commerce Cloud.
Hosting and infrastructure: 30,000 to 100,000 dollars annually if not bundled with Cloud, or partially bundled if on Cloud.
Maintenance and operations: 180,000 to 600,000 dollars annually for an agency retainer or equivalent in-house staffing.
Feature development: variable. A business in steady state might spend 150,000 to 500,000 annually. A business with an aggressive storefront roadmap might spend 500,000 to 1,500,000.
Extensions and third-party tools: 30,000 to 120,000 annually, including search, personalization, reviews, loyalty, and other plugins.
Integration costs: 50,000 to 200,000 annually for ongoing maintenance of ERP, OMS, and other integrations.
Compliance and security: 20,000 to 80,000 annually for audits, scans, and remediation.
The total year-three run rate for a mid-market store typically lands between 500,000 and 2,000,000 dollars annually, with the range driven by GMV scale, feature investment intensity, and integration complexity.
The table below summarizes a representative year-1 vs year-3 comparison for a portfolio company that needed meaningful catch-up work at acquisition.
| TCO category | Year 1 | Year 3 | Notes |
|---|---|---|---|
| Licensing and subscription | 150,000 | 150,000 | Stable |
| Hosting and infrastructure | 100,000 | 50,000 | Right-sized after catch-up |
| Maintenance and operations | 400,000 | 300,000 | Reduced after stabilization |
| Feature development | 800,000 | 350,000 | Year 1 includes major upgrade |
| Extensions and third-party | 80,000 | 60,000 | Audit removed redundant tools |
| Integration costs | 250,000 | 100,000 | Year 1 includes ERP rebuild |
| Compliance and security | 90,000 | 40,000 | Year 1 includes initial audits |
| Total | 1,870,000 | 1,050,000 | 44% reduction |
A 40 to 50 percent reduction from year-one to year-three TCO is typical for portfolio companies that needed catch-up work at acquisition. For well-maintained companies, the reduction is smaller because year-one is closer to the run rate.
The diligence questions that matter
When supporting PE diligence on an Adobe Commerce portfolio company, six questions surface the variables that determine the TCO model.
What version of Adobe Commerce is the store running, and is it currently supported? Stores on Magento 1 or on out-of-support Adobe Commerce versions carry mandatory year-one upgrade costs. The Adobe Commerce support lifecycle is the reference.
What is the patch level relative to the latest available release? Stores more than two patches behind carry catch-up costs that include both engineering time and risk premium.
What is the storefront architecture? Hyvä, Luma, headless, or hybrid? Each architecture has a different operational profile and a different forward investment requirement.
What is the integration landscape? How many third-party systems integrate with the store, what is the middleware layer, and what is the documented state of each integration?
What is the documentation state? Specifically, is there a current architectural overview, a runbook library, and a decision log? The absence of these is itself a cost line because year-one will need to produce them.
What is the engineering ownership? In-house team, agency partner, mix? Each model has a different cost structure and a different transition risk profile if the sponsor wants to change vendors.
Value-creation considerations beyond TCO
The TCO model is one input to the investment thesis. Two other inputs matter.
Conversion rate improvement headroom. A store with poor Core Web Vitals, slow checkout, or outdated UX has room to improve mobile conversion by 10 to 30 percent through targeted work. The investment to capture this is part of year-one and year-two feature development. The payoff is measurable revenue lift that improves the exit multiple.
Platform lock-in versus optionality. A store deeply customized on Adobe Commerce is more expensive to migrate later. A store with cleaner architecture and better documentation preserves optionality for the sponsor at exit. Investments in documentation, test coverage, and architectural cleanup pay off at exit even though they do not move year-one revenue.
The Boston Consulting Group commentary on PE value creation in digital and the Bain analysis of digital-driven PE returns cover the broader value-creation patterns. The platform-specific contribution is one piece of the larger thesis.
What we recommend during diligence
Bemeir typically runs a three-day technical due diligence engagement for PE sponsors evaluating an Adobe Commerce portfolio company. The deliverable is a written report covering the seven TCO categories, a year-1 to year-5 cost projection, a risk register with prioritized remediations, and a value-creation analysis identifying the storefront investments most likely to drive multiple expansion.
The cost of the diligence is typically 25,000 to 60,000 dollars. The downstream value is in the rigor of the cost model. Sponsors that skip technical diligence routinely discover six-figure surprises in year one that should have been visible at acquisition.
For sponsors evaluating multiple portfolio companies across Shopify Plus, Shopware, or BigCommerce in addition to Adobe Commerce, the same framework translates with platform-specific adjustments. The TCO categories are the same. The cost ranges differ by platform. The diligence discipline produces the same kind of decision support regardless of stack.
A clean TCO model is the foundation for any value-creation plan that involves the eCommerce platform. The platform is rarely the headline story, but it is usually meaningful in either the cost base or the revenue trajectory. Getting the model right at acquisition lets the sponsor make informed decisions about where to invest and where to leave alone, which is the discipline that drives returns over the hold period.
