When Friction Wins: Why Traditional Industry Still Survives the Startup Revolution

The Hook: when the “Continue with Google” button doesn’t make payroll

Picture a Monday morning meeting.

On one side of the table, the CEO of an 80‑year‑old bank. Solid balance sheet, controlled risk, an oversized legal team, and systems nobody dares to touch without lighting candles first.

On the other side, the founder of a neobank bragging in her pitch: “3‑minute onboarding, sky‑high NPS, 500,000 users in 18 months.”

When the slides go dark, the uncomfortable question isn’t who has the better app.

The real question is: who is still alive, regulated, and profitable if tomorrow the venture capital market freezes for three years?

That’s what this piece is about. Not celebrating unicorns or romanticizing marble buildings, but comparing –sector by sector– how business models, technology, and user experience actually work in traditional industry and the startup ecosystem… and what the hell each side should copy from the other without destroying what already works.

The genesis: how we ended up in this fake “old vs new”

You already know the standard narrative: traditional industry is slow, bureaucratic, a slave to legacy systems, while startups are agile, digital, and user‑centric.

There’s some truth to that. But the contrast usually ignores three basic facts you can see in banking, retail, healthcare, and mobility:

1. Traditional companies are designed to survive full economic cycles.
   Hierarchical structures, standardized processes, prudent balance sheets, local presence, and strict regulation aren’t design flaws; they’re part of the survival mechanism.

2. Startups are designed to explore, not to stabilize.
   They live in uncertainty, burn capital to buy time, and validate value propositions through constant experimentation. Their favorite metrics (users, monthly growth, engagement) are not those of a mature business.

3. The venture capital ecosystem assumes most will die.
   Volatility is a feature, not a bug: a few wins make up for the graveyard of “disruptive” products nobody uses.

From there, the myth is built: new equals better, old equals doomed. The real comparative picture of business models, technology, and UX is far less romantic.

The general comparative framework: what exactly are we comparing?

Before going sector by sector, let’s put the pieces on the table.

What we call “traditional industry”

• Established organizations in existing markets (banking, supermarkets, clinics, taxis, etc.).
• Proven business models focused on sustained profitability and resilience.
• Hierarchical structures, standardized processes, heavy regulatory load.
• Funding based on equity, reasonable debt, and organic growth.

What we call the “startup ecosystem”

• Emerging companies focused on innovating business models, products, or services.
• High uncertainty, continuous iteration, search for global scalability.
• Funding dependent on investors who accept high portfolio mortality.
• Focus on traction, network effects, and accelerated growth, often over early profitability.

The three axes of contrast

1. Business model
   How they make money (revenue sources, cost structure, CAPEX vs OPEX), what they sacrifice to grow, and what they consider “success.”

2. Technology
   Infrastructure (legacy on‑premise vs cloud‑native, monoliths vs microservices), pace of change, security, vendor dependency.

3. User experience (UX)
   What it feels like to interact with each: branches, paperwork, and opening hours vs mobile‑first, self‑service, and design measured by NPS, conversion, and churn.

Sector‑by‑sector comparison: banking, retail, healthcare, and mobility

1. Banking vs fintech: solvency versus pretty screens

a) Business model

Traditional banks

• Revenue:
  • Interest from loans and credit.
  • Fees on accounts, cards, transfers, FX, etc.
  • Investment services, insurance, and corporate banking.
• Costs:
  • Branch network, staff, ATMs, regulatory and compliance services.
  • Risk systems, auditing, locked‑up regulatory capital.
• Regulation:
  • Strict supervision, capital requirements, AML rules, consumer protection.
• Growth logic:
  • Priority: stability and recurring profitability.
  • High CAPEX in physical and technological infrastructure.

Typical neobanks and fintechs

• Revenue:
  • Interchange fees from card payments.
  • Premium subscriptions (accounts with extra perks).
  • Commissions on third‑party products (insurance, investments) offered via marketplace.
• Costs:
  • Cloud infrastructure, product/tech teams, acquisition marketing.
  • Lower spending on branches, but dependence on third parties (banking‑as‑a‑service, core providers).
• Regulation:
  • Sometimes operate with limited licenses or by piggybacking on regulated banks.
• Growth logic:
  • Priority: growth in user base and transaction volume.
  • Low or no profitability tolerated in the early years.

Key difference: the bank stares at the balance sheet, the regulator, and systemic risk; the fintech stares at the acquisition funnel and monthly churn.

Concrete example: opening an account. A universal bank assumes a high acquisition cost per customer but expects them to stay for years, take a mortgage, a card, insurance. A neobank aims to open hundreds of thousands of accounts quickly, knowing a sizable share will remain almost inactive.

b) Technology

• Traditional banks:

  • Core banking systems on on‑prem mainframes.
  • Monolithic ERPs, long release cycles.
  • Extreme focus on security, traceability, and compliance.

• Fintech / neobanks:

  • Cloud‑native architecture, microservices, open APIs.
  • Fast iteration, feature flags, frequent deployments.
  • Heavy use of data for alternative scoring, personalization, automation.

Advantages and disadvantages

c) User experience (UX)

• Traditional bank:

  • Opening an account: in‑person appointments, wet signatures, fragmented processes.
  • Limited opening hours, opaque language, products designed from the balance sheet, not the user.

• Neobank:

  • Fully digital onboarding in minutes, ID verification via photo and video.
  • Mobile‑first app, real‑time notifications, spend categorization.
  • Continuous iteration based on metrics: signup conversion, recurring use, NPS.

Impact: neobanks win in acquisition among digital and younger segments; banks defend with brand trust, product breadth, and physical presence in critical moments (mortgages, serious payment issues, legal claims).

2. Retail vs e‑commerce and quick commerce: supermarket aisle vs infinite scroll

a) Business model

Traditional supermarkets

• Revenue:
  • Margin on in‑store product sales.
  • Deals with suppliers (promos, shelf positioning, private labels).
• Costs:
  • Store rent and operation, staff, limited last‑mile logistics.
• Regulation:
  • Health, labor, and competition rules; less prudential pressure than banking.
• Growth logic:
  • Expansion via new store openings and range optimization.
  • Store‑level profitability as a key metric.

E‑commerce and quick commerce

• Revenue:
  • Margin on online product sales.
  • Marketplace commissions on third‑party brands.
  • Delivery fees (subscriptions like “unlimited shipping”).
• Costs:
  • Fulfilment centers, dark stores, heavy last‑mile logistics.
  • Digital marketing, tech, remote customer service.
• Growth logic:
  • Priority: digital market share, purchase frequency, basket size.
  • Highly variable OPEX tied to order volume.

Uncomfortable truth: many quick‑commerce models have learned that 10‑15 minute delivery looks great in PowerPoint but kills margin in practice.

b) Technology

• Traditional retail:

  • Monolithic ERPs, inventory systems often disconnected from online.
  • Slow upgrade cycles; lots of batch, little real‑time.

• E‑commerce / quick commerce:

  • Cloud platforms, microservices for catalog, payments, logistics.
  • Automated picking, route optimization, dynamic pricing.
  • Data‑driven demand forecasting and promo tuning.

c) UX

• Physical supermarket:

  • Visit‑centered experience: get there, search for products, queue.
  • Hard‑to‑replicate advantage: you can see, touch, physically compare.

• E‑commerce / quick commerce:

  • Filtered search, recommendations, purchase history, one‑click repeat orders.
  • Asynchronous shopping, anytime, anywhere.

Compared journey: the monthly big shop

• Traditional: one 60–90 minute visit, physical friction but “all done at once.”
• Startup: several small purchases during the week; great convenience but possible notification fatigue and a sense of scattered spending.

Impact: startups win on convenience and digital personalization; incumbents hold ground with economies of scale and better margins in well‑run physical stores.

3. Healthcare vs healthtech: waiting room vs waiting room… virtual

a) Business model

Traditional clinics and hospitals

• Revenue:
  • In‑person consultations, surgeries, diagnostic tests.
  • Insurance reimbursements, out‑of‑pocket payments.
• Costs:
  • Physical infrastructure, medical equipment, healthcare staff.
• Regulation:
  • Extremely strict: health standards, medical data protection, professional liability.
• Growth logic:
  • Increasing capacity (more beds, more specialties).
  • Profitability tightly linked to occupancy and payer contracts.

Telemedicine platforms and healthtech

• Revenue:
  • Pay‑per‑use online consultations.
  • Subscription models (employers, insurers) for medical access.
  • B2B services: medical record systems, population analytics, etc.
• Costs:
  • Tech development, regulatory compliance, acquiring users/professionals.
• Growth logic:
  • Rapid geographic scaling (no physical clinics).
  • Strong pressure to show real engagement, not just app downloads.

b) Technology

• Traditional clinics:

  • Patient management systems (HIS) often old and closed.
  • Complex integrations between departments (lab, radiology, pharmacy).

• Healthtech:

  • Cloud‑based electronic health records, API‑based interoperability.
  • Use of AI for triage, reminders, treatment adherence.
  • Population analytics for prevention and program design.

c) UX

• Traditional model:

  • Booking by phone in limited hours.
  • Waiting room, repeated paperwork, little transparency on prices and times.

• Telemedicine:

  • Booking via app, reminders, video calls from home.
  • Access to records, e‑prescriptions, asynchronous messaging with doctors.

Comparing the “book an appointment” journey:

• Traditional: call, wait, haggle over time slots, arrive early, wait again.
• Startup: pick a time slot in an app, get notified, connect from your phone.

The catch: the digital experience is clearly better for minor issues or follow‑up. But for complex conditions, emergencies, or delicate diagnoses, physical infrastructure and institutional reputation matter more than any UX.

4. Mobility: traditional taxi vs a screen with dynamic pricing

a) Business model

Traditional taxis

• Revenue:
  • Regulated per‑ride fares.
• Costs:
  • Licenses, vehicle maintenance, insurance, fuel.
• Regulation:
  • Very high; limited number of licenses, fares set by authority.
• Growth logic:
  • Designed stagnation: the market is regulated to avoid oversupply.

Ride‑hailing apps

• Revenue:
  • Commission on each ride (percentage of user fare).
• Costs:
  • Tech development, marketing, support, fare subsidies in growth phases.
• Growth logic:
  • Maximize supply‑demand density, network effects, geographic expansion.

b) Technology

• Traditional taxis:

  • Call centers, radios, basic dispatch systems.

• Ride‑hailing apps:

  • Cloud platforms, geolocation, optimized driver‑passenger matching.
  • Dynamic pricing algorithms based on supply and demand.

c) UX

• Traditional taxi:

  • Hail on the street or call dispatch.
  • Uncertainty on arrival time and final cost (even if the tariff is regulated).

• Ride‑hailing app:

  • Booking with defined origin/destination, estimated price, live tracking.
  • Automatic payment, two‑way rating.

Impact: the startup offers control and predictability. Traditional industry defends its turf via regulation and, in some cases, the trust that the service won’t “disappear” if an algorithm decides the area isn’t profitable.

The invisible conflict: the hidden cost of choosing speed over robustness

Behind all these comparisons there’s an awkward pattern almost nobody mentions at innovation events:

• Traditional industry buys robustness by sacrificing speed.
  It builds redundant processes, control layers, and heavy systems because its explicit mission is not to collapse when things go wrong.

• Startups buy speed by sacrificing redundancy.
  They accept operational issues, partial failures, and radical pivots because their mission is to find something that works before the cash runs out.

Practical consequence:

• In expansionary cycles with abundant capital, the “startup” narrative looks unbeatable.
• When the cycle turns, solid balance sheets, liquidity, and established logistics networks start looking like a good idea again.

It’s not that one model is good and the other bad. Each is optimized for a different type of risk.

Evidence and insights: who actually wins what

Across the sectors, a clear cross‑cutting pattern emerges.

The unvarnished scorecard

The expected winners aren’t always who you think:

• In banking, UX and tech favor fintech, but real power remains with those who issue licenses, manage systemic risk, and understand credit cycles.
• In retail, the 15‑minute delivery promise raised the bar, but unit economics have forced many quick‑commerce players to scale back and resemble classic retailers… with decent apps.
• In healthcare, telemedicine improves access, but nobody wants major surgery in a “100% digital hospital.” Bricks still matter.
• In mobility, apps win the customer’s mind, but regulation decides who survives.

Cross‑sector patterns and trade‑offs few want to own

How startups challenge incumbents

1. On business model:

   • Blowing up traditional revenue sources with transparent pricing, subscriptions, marketplaces, and freemium.
   • Shifting focus from “product” to “ongoing service” measured by recurring use.

2. On technology:

   • Building on cloud, APIs, and automation to cut time‑to‑market.
   • Measuring everything to make data‑driven decisions.

3. On UX:

   • Redesigning the full journey: onboarding, use, support, offboarding.
   • Stripping out paper, schedules, and unnecessary friction.

The inevitable trade‑offs

• Speed vs robustness:

  • Startups: launch in weeks, fix live.
  • Incumbents: take months or years, but what they launch tends to survive long regulatory and operational cycles.

• Innovation vs regulatory compliance:

  • Startups: play at the edges of regulation, sometimes until regulators notice.
  • Incumbents: can’t risk sanctions that threaten their license.

• Niche vs mass coverage:

  • Startups: attack ignored or underserved segments.
  • Incumbents: need products that scale to thousands or millions of customers.

• Superior digital UX vs brand trust:

  • Startups: slick UX, but young brands with no crisis track record.
  • Incumbents: poor UX, but accumulated reputation and often implicit regulatory backing.

Regulation as a tilted playing field

In every sector, regulation works unevenly:

• In the short term it seems to punish incumbents (more requirements, more audits).
• In the long term it becomes a defensive moat: not everyone can meet the capital, control, and reporting standards.

The startups that survive end up, paradoxically, trying to look more like incumbents in how they deal with regulators.

Convergence strategies and scenarios: both sides are copying each other

How incumbents are reacting

They’re not just watching their millennial customers being stolen. They’re doing multiple things at once:

• Innovation labs and digital hubs: semi‑shielded spaces to experiment with new products and UX.
• Corporate venture capital: investing in startups as cheap options on the future.
• Selective acquisitions: buying tech and teams that have shown product‑market fit.
• Gradual tech modernization: moving parts of the stack to the cloud, breaking monoliths into modules, opening APIs (e.g. open banking).
• Strategic alliances: handing the UX layer to startups while retaining regulated infrastructure (banking‑as‑a‑service, white‑label in healthcare, etc.).

How startups are being forced to grow up

The infinite‑growth party ends at some point, and surviving startups begin to:

• Chase real profitability: fix unit economics, cut subsidies, prioritize profitable cohorts.
• Professionalize operations: processes, governance, serious risk planning.
• Take compliance seriously: invest in legal, compliance, security, certifications.
• Diversify products: move from a single hero service to broader portfolios.

Win‑win collaboration models

Here’s where there’s real value beyond the endless war narrative.

• White‑label: startup provides UX and digital layer; incumbent provides license, heavy ops, and balance sheet.
• Co‑branding: leverage incumbent trust and startup freshness in joint offers.
• Infrastructure‑as‑a‑service: banks, retailers, or hospitals open their infrastructure for startups to build on.
• Open banking and APIs: let third parties (with consent) access data and capabilities to create new services.
• Marketplaces and platforms: incumbents become aggregators of startup products, and vice versa.

Decision frameworks: what each side should copy without self‑sabotage

For traditional‑industry executives

Practical framework by dimension

1. Business model

   • Hard questions:
     • Which part of my revenue comes from friction customers hate? (opaque fees, unnecessary processes).
     • Can I turn one‑off products into recurring services?
   • Actions:
     • Map revenue from friction vs real perceived value.
     • Run pilots with subscription or hybrid models without touching the core base all at once.

2. Technology

   • Questions:
     • Which legacy systems are true defensive moats and which are just dead weight?
     • Where do I need extreme resilience and where can I afford to experiment in the cloud?
   • Actions:
     • Prioritize decommissioning systems that don’t offer competitive advantage.
     • Build an API layer that isolates the legacy core and lets you iterate on the edge.

3. UX

   • Questions:
     • Where in the journey does the customer suffer unnecessarily?
     • What experience metrics do I track beyond occasional satisfaction surveys?
   • Actions:
     • Redesign 2–3 critical journeys (onboarding, complaints, cancellation) with mixed business‑tech‑legal teams.
     • Implement continuous metrics: transactional NPS, cycle times, abandonment per step.

For startup founders

Flip side: not everything “corporate” is a disease.

1. Business model

   • Questions:
     • Do my unit economics work without infinite subsidies?
     • How much of my proposition depends on permissive regulations that can change?
   • Actions:
     • Build cash scenarios without new rounds; identify a rough break‑even point.
     • Design revenue streams that don’t rely solely on endless growth (B2B services, recurring fees, etc.).

2. Technology

   • Questions:
     • Am I building an architecture so sophisticated it buries me in cost and operational overhead?
     • Which tech decisions increase my dependency on specific vendors?
   • Actions:
     • Simplify: use microservices where they truly add agility, but don’t turn everything into an unmanageable puzzle.
     • Have exit or mitigation strategies for key vendors.

3. UX

   • Questions:
     • Am I over‑optimizing onboarding and under‑investing in support and problem resolution?
     • Does the promise I make to users hold up for years, or just for early‑adopter enthusiasm?
   • Actions:
     • Design end‑to‑end journeys including failure handling (payment errors, incidents, returns).
     • Include service stability in success metrics, not just initial conversion.

How sustainable advantages are distributed

• Traditional industry:

  • Sustainable strengths in:
    • Relationships with regulators and ability to comply with complex rules.
    • Strong balance sheets, cheap funding, logistics networks, physical infrastructure.
    • Accumulated brand trust.
  • Risk: mistaking that for a permanent shield.

• Startups:

  • Sustainable strengths in:
    • Exploration capacity: finding new combinations of business model + tech + UX.
    • Speed to iterate, kill bad ideas, and exploit good ones before others.
  • Risk: ignoring that if they want to live 10 years, they’ll have to adopt part of the corporate DNA they love to criticize.

The awkward big picture: not a war, a slow merger

Looking 5–10 years out, the honest question isn’t who will “win”: traditional industry or startups.

The useful question is: who can steal what actually works from the other side, ego aside?

• We’ll see banks that look like tech platforms with a banking license behind them.
• We’ll see health startups with compliance structures boring enough to impress any public hospital.
• We’ll see retailers using their stores as logistics nodes powering third‑party apps.
• We’ll see mobility platforms regulated almost like public services.

The balance of power won’t be decided solely by who has the best app or the most branches. It’ll be decided by:

1. Who better understands which friction is unnecessary and which is a safety mechanism.
2. Who knows when to sacrifice speed for credibility and when to do the opposite.
3. Who dares to question their own success model before the market does it for them.

Traditional industry isn’t dead; startups aren’t a universal answer. The real game is more boring and harder:

• dismantling myths,
• making asymmetric decisions,
• and building models that can survive when the hype, the funding round, and the slide deck are gone.

If after reading this you still think your company “just needs an app” or “just needs one more round,” then you’ve missed the uncomfortable part.

References

1. Comparative analysis of traditional industry vs startup ecosystem: definitions, organization, and economic resilience (context provided in the prompt).
2. Description of business models, technology, and UX in banking vs neobanking, retail vs quick commerce, traditional healthcare vs telemedicine, and taxis vs ride‑hailing (context provided in the prompt).
3. Study of comparative frameworks applied to regulated sectors and organizational practices, including examples from education and construction (context provided in the prompt).
4. Formal definitions and types of definitions according to the Real Academia Española and lexicographic sources (context provided in the prompt).