When the Case Won’t Close: A Critical Autopsy of Digital Transformation Between Giants and Startups

The crime scene: the user in the middle of the room

A bank boasts at a press conference about its new “100% digital” app. Two weeks later, call center volume is up 25% because customers can’t figure out how to make a simple international transfer.

Later that same month, a fintech proud of its 30‑second onboarding celebrates its “hypergrowth” on LinkedIn. In the risk committee, with no photos and no hashtags, someone shows an uncomfortable slide: delinquency among new digital customers is three times higher than in the traditional portfolio.

Same city, different hospital: the CEO inaugurates a brand‑new telemedicine solution. The campaign talks about the “patient at the center”; doctors talk about “yet another screen” and older patients keep calling on the phone because they don’t understand the portal.

If you look at the headlines, it seems we are witnessing an epic duel: giants versus startups, dinosaurs versus agile mammals. If you look at the real data on adoption, profitability and satisfaction, the scene looks more like a coroner’s file: lots of scars, lots of noise… and a “user value” that often appears dead in the middle of the room.

As a dissenting scientist, my task today is not to applaud the narrative of disruption, but to treat this comparison for what it is: an autopsy. Not of who is “more innovative”, but of who is actually creating sustainable value and who is just putting makeup on the corpse.

The origin of the wound: how we got to this case file

Sources agree on the superficial: digital transformation has reshaped the business landscape. Startups have exploited agility, cloud‑native technology and user obsession; incumbents have tried to defend their position with resources, brand strength, and favorable regulation.

Some facts almost everyone accepts:

• Traditional companies were born in analog environments, with physical processes, heavy hierarchies, and business models designed for stability, not for constant pivots.
• Startups operate on generally technological models, funded by venture capital, with high tolerance for failure and a focus on accelerated growth rather than immediate profit.
• According to widely cited analyses, around 70% of digital transformations fail, often due to cultural resistance and lack of coherent strategy.
• Startups and giants are now active in all key sectors: banking/fintech, retail/e‑commerce, health/healthtech, mobility/platforms, education/edtech.

So far, the standard narrative. The consensus. But a coroner does not stop at the first version of events.

The true origin of the wound is not “the arrival of technology”. It is something more uncomfortable: we have confused digitizing the way we charge with transforming the way we create value. And both incumbents and startups, each in their own way, have taken part in this collective deception.

The invisible conflict: when both sides play the same wrong game

Almost all reports repeat the same framework: incumbents = scale and stability, startups = agility and innovation. What almost no one dares to spell out is the underground conflict: both sides share incentives that are not aligned with the user nor with the sustainability of the system.

Patterns that are rarely named:

• Obsession with growth at any cost: in startups, driven by investor demands; in incumbents, by market pressure and bonuses tied to the short term.
• Digitalization as makeup: many “transformative” projects in large companies are incremental automations of inefficient processes, not deep redesigns.
• User experiences designed to capture data, not to resolve friction: the funnel is optimized, not the life of the person on the other side of the screen.
• Regulation used as a defensive weapon: incumbents use it as a wall; many startups treat it as something that “will be fixed later”. In both cases, the user is exposed.

Looking at banking, retail, health, mobility and education from this forensic angle, what matters is not who is more digital, but who assumes the real cost of transformation:

• Who bears the operational risk when an app fails? The user.
• Who bears the complexity of navigating poorly integrated physical and digital channels? The user.
• Who finances, via fees, commissions or personal data, the unfulfilled promises of innovation? The user.

The crime, therefore, is not “slow incumbents” or “irresponsible startups”. The crime is systemic: a market that rewards digital storytelling over tangible, measurable impact on people’s lives.

With this in mind, let’s open the case files sector by sector.

Case file 1: Financial services – banks vs fintech

a) Business model

• Incumbent banks: live off interest, fees, and large‑scale risk management. High barriers to entry due to regulation and capital requirements. Their historic value: perceived safety and the ability to operate large volumes robustly.
• Fintechs: value propositions focused on accessibility (accounts in minutes), usability (polished apps) and transparent costs. Revenues from fees, card interchange, premium subscriptions, origination fees on loans.

The angle often hidden: many fintechs rely on back‑end banks or regulated providers to operate. “Breaking the banking system” often means “putting a nice interface on the same regulated infrastructure”.

b) Technology

• Banks: legacy systems, old banking cores, layers and layers of middleware. Costly integrations, but with robustness proven over decades of operation.
• Fintechs: cloud‑native architectures, microservices, open APIs, short development cycles. Real capacity to experiment, but also greater fragility if design is rushed.

In the technological crime scene, the trace is clear: banks drag technical debt; fintechs accumulate robustness debt.

c) User experience

• Onboarding: banks with long forms, in‑person visits, heavy KYC. Fintechs with onboarding in minutes using biometrics and online verification.
• Personalization: banks with coarse segmentation; fintechs using transactional data for dynamic offers.
• Trust: surveys usually show higher structural trust in banks (security, deposit protection), versus fintechs seen as convenient but less solid.

Key clue: users often end up duplicating relationships: a “serious” bank for salary and savings, and a fintech for daily payments. The promise of full replacement rarely materializes.

Case file 2: Retail and consumer – physical store vs e‑commerce/D2C marketplaces

a) Business model

• Traditional retail: physical stores, margins constrained by rent, staff, and in‑store inventory. Value: physical experience, immediacy, local trust.
• E‑commerce / D2C: direct online sales, lower physical fixed costs but high variable costs in digital marketing, logistics and returns.

The dominant narrative talks about a “cost advantage” for D2C. Real data often show margins eroded by rising CAC and high return rates.

b) Technology

• Retailers: POS systems, ERPs, inventories often disconnected from the online channel. Partial digitalization (for example, poorly integrated click & collect).
• E‑commerce startups: cloud platforms, advanced inventory analytics, dynamic pricing, automated marketing.

The blind spot: much of that technological sophistication is aimed at securing the sale, not at optimizing the product life cycle or the impact on the user (sizes, quality, sustainability).

c) User experience

• Physical: direct try‑on, human assistance, immediate resolution. Frictions: travel, opening hours, limited stock.
• Digital: extreme convenience, price comparison, recommendations. Frictions: uncertainty about size/quality, delivery times, returns management.

Here the corpse appears in the form of impulsive overconsumption and saturated logistics. Optimized UX has made it easier to buy things the user didn’t need, while traditional retailers, when they digitize poorly, offer the worst of both worlds: physical lines and clunky websites.

Case file 3: Health – hospitals/insurers vs healthtech

a) Business model

• Hospitals and insurers: heavily regulated models, revenues per medical act, policies, agreements with public or private payers.
• Healthtech: specific solutions (telemedicine, appointment management, monitoring, digital medical records) aimed at efficiency, access or experience.

The sugar‑coated story: “technology empowers the patient”. The awkward fact: in many systems, billing is still tied to in‑person acts, which disincentivizes full adoption of digital models.

b) Technology

• Traditionals: legacy systems, fragmented medical records, little interoperability.
• Startups: diagnostic AI, tracking apps, teleconsultation platforms.

But the scene no one wants in the official photo is this: a doctor jumping between three different systems, a patient portal, an insurer app and an internal hospital system. The promise of integration serves the provider more than the professional or the patient.

c) User experience

• Patient in the traditional system: calls, waits, repeated forms.
• Patient in healthtech: in theory, fast access to appointments and results. In practice, fragmented apps, privacy concerns, and inequality in digital access.

The crime here is clear: technology without redesigning the incentive model. Neither incumbents nor startups can fix the system if payment remains tied to inefficiency.

Case file 4: Mobility and transport – traditional operators vs platforms

a) Business model

• Traditional operators: public transport, regulated taxis, bus or train companies. Revenues from tickets, service contracts.
• Mobility platforms: aggregation of demand and supply (drivers, vehicles), commissions per ride, dynamic pricing.

It was sold as the “democratization of transport”. What we have, in many cities, is a shift of risk onto drivers and increased traffic in already saturated areas.

b) Technology

• Traditionals: ticketing systems, route planning, increasingly digitized but with inertia.
• Platforms: matching algorithms, route optimization, user apps with real‑time tracking.

The ignored side of the algorithm: it is optimized to minimize idle time… not necessarily to optimize urban sustainability or service equity.

c) User experience

• Public transport: low cost, fixed schedules, often crowded, but essential.
• Platforms: shorter wait times, door‑to‑door convenience, better UX.

The autopsy shows a user satisfied in the short term, but an urban system paying the bill: congestion, precarious work, environmental footprint.

Case file 5: Education – traditional institutions vs edtech

a) Business model

• Universities/schools: revenues from tuition, public or private funding, academic reputation as the main asset.
• Edtech: online courses, subscription models, intensive bootcamps, on‑demand content.

The promise was “breaking down access barriers”. But a cold analysis shows that much of edtech supply is concentrated in segments with high purchasing power and good connectivity, not among those excluded from the traditional education system.

b) Technology

• Institutions: virtual campuses, basic LMS, videoconferencing added to classes designed for in‑person delivery.
• Startups: intuitive platforms, adaptive learning, progress analytics.

However, most solutions have limited themselves to moving content online, not redesigning skills, assessment or credentials at a systemic level.

c) User experience

• Traditional student: rich experiences in human interaction, but little flexibility and rigid curricula.
• Edtech student: flexibility, modularity, self‑paced learning… and risk of isolation, dropout, and credentials of uneven value.

In this file, the user appears split: grateful for the flexibility, but lost in a sea of offerings that are hard to assess.

The hidden pattern: structured comparison of the sides

Here is where the autopsy must become cold and tabular. Opinion is not enough; we have to contrast.

Table 1 – Structural scorecard: incumbents vs startups

This table is well known; almost nobody disputes it. But we still need another one: the one that evaluates who is really creating net value for the system, not just for their own balance sheets.

Table 2 – Who wins, who loses, and where value goes missing

The fundamental forensic finding: neither incumbents nor startups, by themselves, are optimized to maximize systemic value. Their strengths are complementary, but their incentives clash.

Evidence and clues that reports gloss over

Reviewing the literature and data, uncomfortable constants appear:

• Most corporate digital transformations fail or remain superficial. Cultural resistance and lack of clear strategy are recurring causes.
• Many digital startups use advanced technology (AI, big data, SaaS) to optimize acquisition and retention, but rarely to question the underlying economic model.
• Digitalizing the user experience, without process redesign, creates a paradox: attractive interfaces on top of slow or inefficient services.
• In regulated sectors (finance, health), startups end up depending on incumbents’ infrastructure and licenses, which limits the real scope of their disruption.
• The rise of the SaaS model has allowed many traditional companies to outsource critical infrastructure, but without addressing the root problem: processes designed for paper, not for data.

These clues point to a pattern: we confuse development speed with depth of change. We ship apps faster, but we question the value contract with the user very little.

The strategic shift: changing the object of the experiment

If we accept that the “crime” is not who wins market share, but where systemic value is lost, the strategic shift cannot be reduced to copying the other side’s tactics.

The right question is not: “How can we be as agile as a startup?” or “How can we scale like an incumbent?”. The forensic question is: how do we rebuild the system so the user stops being the body in the middle of the room?

For incumbents: rewriting the internal report

1. From digitizing channels to redesigning the business model
   An app is not enough. You must rethink how value is generated and captured:

   • Review fees, commissions and incentive structures that penalize digital vs. physical use.
   • Align revenues with real outcomes for the user (e.g. effective health, applicable education, sound finances).

2. Turn technical debt into a controlled lab

   • Gradually liberate the core via modular architecture, APIs, and extracting functionalities to modern layers.
   • Set robustness and resilience metrics as clear as UX and NPS metrics.

3. Put data at the service of the user, not just the organization

   • Design client dashboards that help them understand and manage their situation (financial, health, educational), not just to sell them more.

4. Culture: change the question in committees
   Fewer “What is our competition doing?” and more “What specific user friction did we eliminate this quarter?”

For startups: stopping the fever before it becomes sepsis

1. Distinguish growth from model health

   • Don’t treat product‑market fit as pure usage metrics; include net value for the user (healthy retention, not impulsive; reduction of time or anxiety; real impact).

2. Take regulation seriously from day one

   • See regulation as system boundary design, not an obstacle to dodge. Build compliance as a competitive advantage.

3. Architecture with a longevity view

   • Design systems not only to “move fast” but to coexist for years with critical infrastructures (banks, hospitals, governments).

4. Radical transparency with users and investors

   • Explain where the real risks lie, where cross‑subsidies are, and the side effects of the model (e.g. in mobility or education).

For regulators and investors: changing the lenses

1. Regulate models, not just entities

   • Look at where real risk concentrates (data, leverage, tech dependency) rather than just who holds the license.

2. Reward systemic‑value indicators

   • Instead of glorifying valuations and funding rounds, value projects for resilience, inclusiveness and price‑cost alignment.

3. Promote sandboxes that force collaboration

   • Regulated spaces where incumbents and startups must co‑design solutions, sharing responsibility and traceability of results.

Convergence scenarios: when the ideal suspect is a hybrid

Hybridization already exists, but it is often poorly described. It’s not just “banks investing in fintech” or “retailers opening e‑commerce”. What matters is how risk, data control and user experience are distributed.

Here are four useful archetypes for analyzing these pacts.

1. The “brain in the shadows” (deep white‑label)

• Description: the startup provides technology and UX, but hides behind the incumbent’s brand. The user barely knows it exists.
• Value: the incumbent modernizes without altering its identity; the startup scales fast by leveraging the customer base.
• Risks: little visibility and extreme dependency for the startup; temptation for the incumbent to postpone refactoring its core.

2. The “commercial Frankenstein” (poorly orchestrated B2B2C)

• Description: the end user sees two brands, two apps or two poorly stitched processes (e.g. insurer + telemedicine platform with redundant steps).
• Value: fast time‑to‑market, shared costs.
• Risks: fragmented experience, higher error probability, user flight to more coherent options.

3. The “shared lab” (purpose‑specific joint venture)

• Description: incumbent and startup create a joint entity to attack a specific segment or problem.
• Value: governance, risk sharing and metrics can be designed from scratch. Good ground to test pay‑for‑results models.
• Risks: cultural clashes, corporate timelines that suffocate startup speed.

4. The “orchestrated ecosystem” (multi‑actor platforms with clear rules)

• Description: an actor—not always the incumbent—designs an open platform with APIs, data standards and transparent rules of the game. Startups and incumbents provide modular services.
• Value: maximum flexibility for the user, ability to switch providers without redoing the whole journey.
• Risks: high governance complexity, constant tension between openness and rent capture.

In all these archetypes, the forensic criterion must be the same: who assumes which responsibility when something fails, and who keeps which data when everything goes well?

Field manual: actionable recommendations by actor type

For traditional companies (incumbents)

1. Define an explicit thesis on what NOT to compete on with startups
   Accept you shouldn’t replicate every new app; focus on what your scale and license let you do better.

2. Map user frictions before investing in technology
   Every euro in digital should be traced to a specific user problem, not to a tech fad.

3. Adopt an ecosystem portfolio model

   • White‑label for tactical speed.
   • Joint ventures for strategic bets.
   • Open APIs to attract external innovation.

4. Reform data governance

   • Include ethical committees with external participants.
   • Publish clear data‑use principles and effective opt‑out mechanisms.

5. Incentivize internal collaboration with startups

   • Business objectives tied to co‑creation initiatives, not just legacy efficiency.

For startups

1. Integrate regulation and compliance into product design
   Avoid models that depend on “staying ahead of the regulator”. They are time bombs.

2. Choose asymmetric battles

   • Attack niches where incumbent scale is not a direct advantage (e.g. underserved segments, niche processes).

3. Measure success beyond growth

   • Include metrics of user well‑being, total cost of ownership, relationship sustainability.

4. Design for integration, not just acquisition

   • Clean APIs, open standards, documentation tailored to real corporate teams.

5. Build brand on transparency, not just on design

   • Communicate service limits, risks and tech dependencies. Users value honesty more than fictional perfection.

For mixed alliances (incumbent + startup)

1. Agree on success metrics first, then sign the commercial contract

   • Define from the start what success means for the user, not just for each party.

2. Map end‑to‑end responsibilities

   • Who answers to the user if something breaks? Who handles support? Who can touch which data, and for what?

3. Set review cycles based on real usage data

   • Fewer “project follow‑up” committees and more analysis of session recordings, resolution times, error rates.

4. Design clean exits

   • The user must not be trapped in the middle of a contractual war if the alliance breaks down.

The full scene: from who wins to what is worth winning

The popular narrative talks about a silent war for the customer between giants and startups. The coroner who looks coolly at the data sees something else: a much quieter war over the meaning of the word “value”.

If value means only capturing more revenue or more data, digital transformation will keep creating shiny platforms on top of exhausted systems, users saturated with options, and institutions unable to sustain their own promises.

If value starts to be measured in real friction reduction, service robustness, inclusion and transparency, the map changes: incumbents and startups stop being opposing sides and become pieces of a system that needs redesign.

The paradigm shift I propose is simple and radical:

• From disruption as a goal to coherence as the central metric.
• From the user as “target” to the user as co‑owner of data, process and, in part, service design.
• From technology as a competitive weapon to technology as a testable hypothesis of systemic improvement.

Until we start writing earnings reports in those terms, we will keep arguing over who wins market share while the truly harmed party—users’ time, attention and trust—lies stretched out in the middle of the room.

Next time you read a headline about a startup’s latest multi‑million round or yet another transformation program at a giant, don’t ask “How much will they grow?” Ask: “What corpse have they actually brought back to life?”

References

1. ticnegocios.camaravalencia.com. "Startup vs Empresa tradicional: diferencias clave y conceptos básicos". Cámara Valencia, TicNegocios.
2. yuzz.org. "¿Qué diferencia hay entre una empresa y una startup?".
3. blogs-es.vorecol.com. "Cómo están las startups redefiniendo los modelos de negocio tradicionales en la era digital".
4. udax.edu.mx. "Transformando el futuro: innovaciones en modelos de negocio".
5. elpais.com. "Software por suscripción: un nuevo modelo más ágil y barato".
6. powerplan.es. "Transformación digital y modelos de negocio innovadores en la experiencia del cliente".
7. dle.rae.es. "Introducción". Diccionario de la lengua española.
8. definicion.edu.lat. "Introducción" – Concepto y uso.
9. es.wikipedia.org. "Introducción (música)".
10. en.wikipedia.org. "La Introducción" (album by Carlos & Alejandra).