Digital Business Transformation: From Strategy to P&L

The digital channel grows, but profit does not

Online revenue increases, but traffic, discounts, logistics, and service costs rise with it. The team manages digital-channel metrics without seeing the contribution to gross and operating profit.

Online and retail compete

Retail, the website, app, marketplaces, and contact center protect their own metrics. Meanwhile, the customer moves through several touchpoints, while the company pays twice for demand and argues over attribution.

The product plan is disconnected from strategy

The backlog is built from local requests by individual functions. There are many initiatives, but it is unclear which business problem each one solves, what effect to expect, or why it should be done now.

Data exists, but decisions do not

Reports disagree, manual compilation takes days, and metrics are not linked to actions. Executives debate whether the numbers are correct instead of choosing a decision and controlling the outcome.

Operations constrain customer experience

The promise in the interface does not match availability, picking speed, delivery, or service performance. Conversion is constrained by the business’s real ability to fulfill the order, rather than by button design.

Technology develops without an owner of the outcome

IT is accountable for launching the system and the business for requirements, but no one owns the change in P&L or the process after release. The project formally closes, yet the new way of working never takes hold.

1. P&L and the growth arena

First define where the company creates value and which financial metric will measure the change. It may be gross-profit growth, lower cost to serve, faster inventory turnover, higher product availability, or customer-base growth. This choice becomes the filter for the entire initiative portfolio.

2. Customer and channels

Consider the entire customer journey, from need and choice through order receipt, service, and repeat purchase. Retail, e-commerce, the app, CRM, marketplaces, and the contact center share one economic model instead of competing local goals.

3. Products and processes

Change the digital product together with the process behind its interface. Product pages, checkout, service booking, and delivery status must connect with assortment, inventory, the OMS, logistics, and operational accountability.

4. Data, technology, and AI

Data must support a specific decision, and technology must support a durable process. End-to-end analytics, personalization, AI assistants, and automation are assessed by business impact, data quality, the cost of error, and their ability to fit into daily work.

5. Organization and management

The target model defines owners, decision rights, KPIs, and the management cadence. Without this, the new system remains a collection of projects: functions continue working toward old goals, and cross-functional problems have no single owner.

1. Establish the baseline

Define P&L, customer and operational metrics, process constraints, data quality, and initiatives already under way. Separate symptoms from causes and agree on a single baseline for the metrics.

2. Design the target model

Describe how the customer journey should work, which decisions are made at each level, what changes in products and operations, which data is needed, and who owns the overall outcome.

3. Build the initiative portfolio

Give every initiative an impact hypothesis, effort estimate, dependencies, owner, and metric. The portfolio provides one management language for comparing a product enhancement, process change, marketing mechanism, and technology project.

4. Set the sequence

Quick wins should not create new debt, and foundational projects should not block improvements for a year. Connect the first 90-day plan with a 12–24-month horizon, accounting for data, integrations, people, and operational readiness.

5. Manage the impact

A regular cadence surfaces deviations, decisions, and the actual contribution of initiatives. If a hypothesis is not validated, adjust or close it. If the effect is achieved, embed the new practice in the process, KPIs, and accountability.

ORTEKA

An omnichannel P&L model connected e-commerce, retail, CRM, the contact center, UX, mobile products, and analytics. The e-commerce share grew from 14% → 22%+, gross profit increased by +24.8%, and the validated impact of the UX, traffic, mobile-product, and CRM portfolio reached RUB +165 million.

ORTEKA case: omnichannel sales and P&L

SUNLIGHT

Digital front ends were connected with the OMS, SLAs, delivery, content, and service. E-commerce grew from RUB 5.6 billion → RUB 13 billion, while order picking and confirmation accelerated from 4–6 hours to 30–60 minutes.

SUNLIGHT case: digital growth through operational speed

Kenguru

The mobile product, CRM, stylists’ personalized service, and AI were brought into a single sales model. E-commerce grew by x2+, app revenue increased by +75%, while product and AI personalization generated RUB +13 million in additional monthly revenue.

Kenguru case: app, CRM, and AI

Tanuki

The OMS, SLAs, operator interfaces, courier app, and restaurant incentives became a single order-and-delivery framework. The share of orders delivered on time increased by +15 pp, while online GMV grew +10% year over year.

Tanuki case: digital sales and operations

Where should digital transformation start?

Start with the business objective and the metric baseline. Understand where the company is losing growth or profit, which customer and operational gap drives the problem, and how the outcome will be measured. Select a platform or contractor only after that.

How is transformation different from digitization?

Digitization moves an existing operation into a digital format. Transformation changes the model itself: the customer journey, process, product, decision, accountability, and economics. Sometimes digitization is enough; not every task needs to become a large program.

Who should own the outcome?

The owner should be an executive capable of managing an end-to-end business outcome. IT, product, marketing, and operations own their respective parts, but the overall result requires a role with the authority to change priorities and resolve cross-functional conflicts.

How do you calculate the economic impact?

Before launch, establish the baseline and the mechanism of impact: incremental revenue, gross profit, cost reduction, faster turnover, or lower losses. Separate the effect from seasonality, overall business trends, and concurrent initiatives as far as the data allows.

Is a separate digital strategy needed?

It is useful when it translates business choices into a target model, initiative portfolio, and execution sequence. It should not sit alongside corporate strategy; its purpose is to show how products, data, and technology change the way shared goals are achieved.

Why do programs stall after strategy?

Often, outcome owners have not been appointed, KPIs have not changed, operational dependencies are underestimated, and there is no management cadence. Target-model design and the start of execution should therefore belong to one program rather than two disconnected phases.