Introduction: The cost-centre trap
Open with the observation that in most mid-market retail businesses, the technology function reports into operations or finance, is measured on cost and uptime, and is the last team consulted on strategic decisions. Explain why this operating model made sense historically but is now actively holding retailers back in a digitally driven market.
Frame the article as a practical argument for a different model, not a theoretical one.
Why most retail businesses treat technology as a cost centre
The historical context
Explain how retail technology functions evolved from IT departments managing POS systems and back-office infrastructure. Cover how this legacy shaped reporting lines, budgeting models, and the perception of technology as operational plumbing rather than commercial capability.
The self-fulfilling prophecy
Describe the cycle: technology is seen as overhead, so it is underfunded. Underfunding leads to poor delivery and mounting technical debt. Poor outcomes reinforce the view that technology is a cost, not a driver of value. Show how this cycle persists even when executives intellectually agree that digital matters.
The symptoms in practice
List observable indicators that a retailer is stuck in the cost-centre model: technology leaders absent from board meetings, project-based budgeting with no persistent investment, engineering measured on tickets closed rather than outcomes delivered, and a backlog that grows faster than it shrinks.
The product-thinking shift
What product-oriented technology means in retail
Define the model clearly: technology teams organised around business capabilities (customer experience, fulfilment, merchandising, data) rather than around systems or projects. Teams own a domain, have a persistent roadmap, and are accountable for commercial outcomes.
From projects to products
Explain the practical difference between project-based and product-based delivery. Cover how project-based models create start-stop cycles, knowledge loss, and misaligned incentives, while product-based models build compounding knowledge and continuous improvement.
Technology as enabler, not support function
Articulate the core mindset shift: technology exists to create commercial advantage, not to keep the lights on. Cover what this looks like in practice: technology leaders contributing to commercial strategy, engineering teams prototyping new capabilities proactively, and technical feasibility shaping business decisions rather than following them.
What a modern retail tech operating model looks like
Organisational structure
Describe a practical structure for a mid-market retailer: a small, senior technology leadership team (CTO or VP Engineering, plus leads for platform, data, and delivery), product-aligned squads that include engineering and business stakeholders, and a thin layer of shared services for infrastructure and security.
Governance and prioritisation
Cover how decisions get made: a technology investment committee with commercial representation, quarterly planning aligned to business objectives, and a transparent prioritisation framework that balances innovation, maintenance, and risk reduction.
Metrics that matter
Propose a balanced scorecard that includes commercial outcomes (revenue influenced, conversion impact, operational efficiency), delivery health (velocity, cycle time, deployment frequency), and platform health (technical debt ratio, incident frequency, integration reliability).
Embedding technology in commercial decision-making
The CTO at the leadership table
Argue that the technology leader must be part of the executive team with a direct line to the CEO, not buried under operations or finance. Cover what this enables: earlier input on strategic decisions, better resource allocation, and a technology perspective in M&A and partnership discussions.
Joint planning and shared accountability
Describe how technology and commercial teams should plan together, with shared OKRs or KPIs that prevent the “throw it over the wall” dynamic. Provide a practical example of how a merchandising initiative and a technology capability investment can be planned as a single programme.
Commercial literacy for technology leaders
Make the case that technology leaders in retail need to understand margin, customer lifetime value, inventory economics, and channel profitability. This commercial literacy is what earns a seat at the table and ensures technology investment is directed at genuine business value.
Capability building vs outsourcing
What to own internally
Identify the capabilities that should be built internally: technology strategy, architecture decisions, vendor management, data ownership, and the core product management function. Argue that these are strategic assets that cannot be effectively outsourced.
What to outsource and how
Cover legitimate outsourcing use cases: implementation projects, specialist skills for time-bound needs, managed infrastructure services, and development capacity for peak demand. Emphasise the importance of retaining control of direction and quality.
The partner dependency risk
Warn about the risk of outsourcing too much to a single systems integrator or agency. Describe the pattern where the partner becomes the de facto technology function, creating dependency, knowledge asymmetry, and escalating costs.
Making the transition: a practical roadmap
Start with the narrative
Explain that the first step is not restructuring but building the case for change. This means framing technology investment in commercial terms that resonate with the board and CEO.
Quick wins: embed before you restructure
Suggest low-friction starting points: invite the CTO to board meetings, co-locate a technology lead with the commercial team, introduce outcome-based metrics for one initiative. These create evidence before asking for structural change.
The structural shift
Outline a phased approach to reorganising: define product domains, assign ownership, shift from project to product budgeting, and build the governance framework. Acknowledge that this takes 12 to 18 months to fully embed.
Conclusion: This is a leadership challenge, not a technology one
Reinforce that the operating model shift requires executive sponsorship and cannot be driven by the technology function alone. Encourage technology leaders to build the commercial case, start with small demonstrations of value, and recognise that changing how a business thinks about technology is harder than changing the technology itself.
What to read next
If you found this useful, these related pieces go deeper on specific aspects:
- Standardising technology across a PE portfolio applies the operating model thinking to multi-company contexts where portfolio-level governance is also a consideration.
- What usually goes wrong in retail technology transformation covers the execution risks that emerge when the operating model is not aligned with the transformation ambition.
- What a Fractional CTO actually does explores one practical model for embedding senior technology leadership without the overhead of a full-time hire.
Next steps
If you are rethinking how technology is structured and led in your retail business, get in touch or review the services to understand how an advisory engagement might help.
What to read next
- What a fractional CTO actually does (and when you need one) — The operating model shift described here often starts with bringing in senior technology leadership on a flexible basis.
- What usually goes wrong in retail technology transformation — Most retail transformation failures trace back to operating model problems, not technology choices.
- Standardising technology across a PE portfolio: where to start — How the product-led model scales across a portfolio context where standardisation is the goal.