Adobe HD Supply

Prepared for HD Supply · November 2026

The Business Case for Connected Insights

A transparent business case built on HD Supply’s operating inputs. It starts from the improvement you would need to see, not the improvement we hope you get.

Financial scenarios are illustrative and should be validated with HD Supply Finance using agreed baselines, contribution rates, and incrementality methods.

01 · The short version

A very small improvement covers the cost

HD Supply’s digital business is large enough that the annual Customer Journey Analytics (CJA) investment is covered by about $1 of extra revenue for every $7,800 of existing digital revenue. Everything that follows shows how we got there, and what still needs your validation.

0.013%Break-even hurdleImprovement on the $3.8B digital revenue baseline needed to cover the annual investment
199%Three-year ROIConservative case, modeled, not guaranteed
$581KThree-year net benefit$874K benefit less $292,680 investment
~7 mo.Illustrative paybackInside Year 1, assuming benefit builds evenly

What the model assumes

A 0.05% measurable improvement on a provisional $3.8 billion digital revenue baseline, a 20% contribution rate, and benefit that ramps 50% / 80% / 100% over three years. These are deliberately conservative planning assumptions, not predictions about HD Supply’s performance.

What is checked and what is not

The arithmetic has been validated. The business inputs have not yet been approved by HD Supply Finance: the revenue baseline, contribution rate, improvement assumption, ramp, and the way incremental value will be measured. The right conclusion is that the economics justify moving to validation, not that the outcome is guaranteed.

02 · Why this matters to HD Supply

The buying journey doesn’t stay in one system

A buyer may respond to marketing, research products on the website, sign in to a business account, move into a PunchOut or e-procurement platform, and finish the order in a separate transaction system. Web analytics sees the first part. The transaction system sees the last part. Today, those are not always analyzed as one journey.

  1. MarketingCampaigns and media
  2. Digital researchWebsite and product browsing
  3. Authenticated buyerBusiness account sign-in
  4. Procurement / PunchOutWhere visibility is often lost
  5. TransactionOrder completed in a separate system

Connect outcomes

Link web activity to procurement and transaction outcomes.

Analyze at scale

Look at journeys for the individual buyer and for the whole business account.

Find opportunity

Identify friction, commercial influence, growth signals, and risk.

What it depends on

CJA does not connect everything automatically. It needs reliable person, account, procurement, and transaction identifiers across environments, with governed data definitions and validation. Confirming those is part of the next steps. The value is not simply having more data in one place; it comes from making a better decision, acting on it, and measuring the result.

Five places connected insight can create value

Digital commerce

Find friction and opportunity across a large existing digital business. Because the revenue base is significant, even a small measurable improvement can be meaningful economic value.

  • Which digital experiences contribute to downstream orders?
  • Where do customers hit friction between research and purchase?
$3.8BProvisional annual digital revenue baseline, the base for the primary financial case
We do not add these five together

Account growth, repeat purchasing, marketing influence, and e-procurement may all show up in the same digital revenue. The primary financial case therefore uses one consolidated digital-commerce improvement so no value is counted twice.

03 · The financial case

From a $3.8 billion base to $380,000 a year

The conservative case is the primary decision scenario. Each step is one multiplication, so every number can be checked and replaced with HD Supply’s own.

Start
$3.8B
Provisional annual digital revenue baseline
× improvement
0.05%
About $1 for every $2,000 of existing digital revenue
= revenue
$1.9M
Modeled incremental revenue (not profit)
× contribution
20%
Illustrative: 20¢ of each added dollar is economic value
= benefit
$380K
Modeled annual contribution benefit at full realization

Why not use the $1.9M?

Incremental revenue is revenue above what HD Supply would otherwise have produced. Generating, serving, and fulfilling it costs money, so counting all $1.9M would overstate the value. The $380,000 is the figure used in the ROI.

Both assumptions are placeholders for your numbers

The 0.05% and 20% are illustrative, not claims about HD Supply’s performance or profitability. HD Supply Finance should confirm the baseline and replace the 20% with the contribution rate, gross margin, or other measure you use for incremental revenue.

Value builds over time

Connecting data, building capability, driving adoption, changing decisions, and measuring results all take time, so $380K is not multiplied by three. The model realizes 50% of it in Year 1, 80% in Year 2, and 100% in Year 3.

Year 1

50% realization
$380K × 50% = $190K
Benefit
$190K
Investment
$97.6K
95%
cumulative ROI
$92,440 net

Through Year 2

80% realization
$380K × 80% = $304K
Benefit
$494K
Investment
$195.1K
153%
cumulative ROI
$298,880 net

Through Year 3

100% realization
$380K × 100% = $380K
Benefit
$874K
Investment
$292.7K
199%
cumulative ROI
$581,320 net

Bars show cumulative figures. ROI = cumulative net benefit ÷ cumulative investment. For example, $581,320 ÷ $292,680 ≈ 199%. These are modeled projections, not guaranteed outcomes; actual value depends on implementation, data readiness, adoption, business actions, and measured incremental improvement.

Show the full year-by-year table
PeriodBenefit that yearCumulative benefitCumulative investmentCumulative net benefitCumulative ROI
Year 1$190K$190K$97,560$92,44095%
Through Year 2$304K$494K$195,120$298,880153%
Through Year 3$380K$874K$292,680$581,320199%

04 · Investment and Adobe’s contribution

Recurring cost and one-time support, kept separate

The recurring investment is judged against the recurring benefit. Adobe’s implementation support lowers the cost and risk of getting started, but it is never counted as ongoing business benefit.

$97,560

Incremental annual CJA investment

The recurring cost evaluated against the recurring benefit.

$292,680

Three-year investment in the model

Three full annual periods ($97,560 × 3). No ROI credit is taken for the 90-day billing transition, which keeps the cost treatment conservative.

~$220K

Adobe implementation support at no additional charge

One-time transition support. It reduces upfront cost and risk, and is not counted in ROI.

How Adobe lowers the cost and risk of the transition

  • A 90-day transition period before CJA billing begins
  • Adobe Analytics stays available throughout the transition
  • Increased Analytics transition capacity and a waiver of pending overages
  • Parallel validation before migration, so numbers can be compared side by side
Why it matters

The ROI case is designed to stand on the recurring economics alone. The $220K of support is upside to the risk profile, not a number in the return.

05 · The break-even hurdle

Work backward from the cost

The 199% ROI shows what the conservative assumptions produce. The more decision-useful question is the reverse: how much improvement is needed just to cover the annual cost? This does not say CJA automatically creates that improvement. It says how high the bar is.

Digital commerce

Against the $3.8B baseline

$97,560 ÷ 20% = $487,800 of incremental revenue needed.

$487,800 ÷ $3.8B ≈

0.013%

Compare with the 0.05% used in the conservative case.

E-procurement, as a stand-alone test

Against the $764M baseline

The same $487,800 of incremental revenue needed.

$487,800 ÷ $764M ≈

0.064%

Not a forecast. A way to see the hurdle inside one specific, relevant part of the business.

Why e-procurement is the natural place to prove it

It is a commercially important journey that spans several environments: the digital experience holds the signals of intent, interest, and friction, and the procurement system holds the final order. When they cannot be analyzed together, it is hard to see how the whole journey influenced the outcome.

Questions a connected view can answer

  • Which digital experiences precede procurement orders?
  • Where do buyers hit friction between the digital and procurement environments?
  • How does marketing engagement contribute to e-procurement revenue?
  • Which journey improvements lead to measurable procurement results?
No double-counting

E-procurement is already part of the $3.8 billion digital base, so it is used here to illustrate where improvement could be found and measured. It is not added on top of the three-year ROI.

06 · Test the assumptions

Change the inputs and watch the result move

Use the sliders to try HD Supply’s own baseline, improvement, and contribution rate. The 50% / 80% / 100% ramp and the $97,560 annual investment stay fixed. Nothing you enter leaves this page.

Provisional. Finance to confirm.
Conservative case: 0.05%
Conservative case: 20%. Replace with Finance’s measure.
Modeled incremental revenue (per year)$1.90M
Annual contribution benefit at full realization$380K
Three-year benefit (50% / 80% / 100%)$874K
Three-year net benefit (after $292,680)$581K
Three-year ROI199%
Break-even improvement for annual cost0.013%

Three reference scenarios: sensitivities, not forecasts

The scenarios are mutually exclusive views of the same digital-commerce lever. They should not be added together or presented as predictions.

ScenarioCore assumptionAnnual contribution3-yr net benefit3-yr ROI
Conservative (primary)0.05% revenue; 20% contribution$380K$581K~199%
Base sensitivity0.10% revenue; 30% contribution$1.14M$2.33M~796%
Upside sensitivity0.25% revenue; 30% contribution$2.85M$6.26M~2,140%

The larger outputs show how much the result depends on the assumptions. They are not expected outcomes.

07 · From modeled value to measured value

How we will know the value is real

CJA supplies the analysis and measurement foundation. Economic value is created only when a connected insight leads to a better decision and that decision produces a measurable outcome.

Identify the opportunity

Use connected journey analysis to find friction, commercial influence, growth or risk signals.

Take a business action

Change an experience, audience, marketing decision, procurement journey, or account strategy.

Measure the outcome

Track KPIs such as conversion, incremental revenue, contribution, procurement activity, repeat purchase, account growth, and ROAS.

Validate incremental value

Observed improvement is not proof of cause. Use a credible comparison: a controlled experiment, holdout, matched group, geographic test, or another method Finance approves.

Guardrails that keep the case credible

  • Revenue is not treated as profit. A Finance-approved contribution measure is applied.
  • One-time support and recurring benefit stay separate.
  • Overlapping outcomes are not counted twice.
  • Reallocating media spend is not automatically counted as savings.
  • The model is recalculated whenever an input changes.

Inputs HD Supply Finance should confirm

$3.8B digital revenue baseline
$764M e-procurement revenue baseline
Contribution rate on incremental revenue
0.05% improvement assumption
50% / 80% / 100% realization ramp
Recurring CJA investment
Method for validating incremental value

For each: business definition, system of record, included population and channels, reporting period, owner, and approved value.

Why some operating numbers don’t reconcile, and how we handle it

The operating metrics came from different source systems, populations, channels, or periods. For example, 7.06M digital orders × a $485 average order value is about $3.42B, not $3.8B, and 2.80M e-procurement orders × $485 is about $1.36B, versus a reported $764M.

Rather than force the numbers to agree, we keep them as separate planning inputs. The formulas are valid on the stated inputs, but the $3.8B baseline should be confirmed independently with Finance, and the ROI recalculated if it changes.

08 · Q&A

Is this an Adobe ROI benchmark?
No. The model uses HD Supply’s operating inputs and clearly labeled illustrative assumptions. The final case should use HD Supply-approved baselines, margins, and benefit-recognition rules.
Is Adobe committing to this return?
No. This is a modeled decision case with a measurement plan. Actual value has to be demonstrated through implementation, adoption, business actions, and agreed measurement.
Have the numbers been validated?
The arithmetic has. The business inputs still need validation by the right HD Supply owners, especially Finance.
Which number matters most?
The roughly 0.013% annual break-even hurdle. It shows how small the improvement needs to be for the annual investment to pay for itself, without relying on a forecast.
Does CJA automatically connect everything?
No. Common identifiers, governed definitions, and reliable data feeds are implementation prerequisites.
How is this different from web analytics?
Web analytics is strongest inside the digital experience. CJA is designed to analyze journeys across channels, identities, accounts, procurement activity, and transactions over time.
Why not add up all five value levers?
Doing so could count the same revenue more than once. A lever should be added separately only if it has a distinct population, outcome, time period, and validation method.
Why isn’t the $220K of implementation support in the ROI?
Counting it as recurring benefit would overstate sustainable value. It is shown separately as one-time support that reduces upfront cost and risk.
Will CJA prove the ROI by itself?
No. CJA provides the analysis and measurement foundation. Proving incremental value requires a business action and an agreed comparison method. We suggest starting with e-procurement and one or two other journeys where identity is feasible, an action can be taken, and the KPI can be observed within the implementation timeline.
Does the data mismatch invalidate the case?
It doesn’t invalidate the method, but it keeps the output provisional until the baseline is confirmed. Mapping each metric to its system of record, scope, and period is the correct step, and it avoids false precision.