How to Ruin a Value Chain in 5 Steps

A practical manual for banks, hospitals, retailers and very cool apps

The fastest way to destroy value in an organization is to not understand how your value chain is structured or how your neighbor is reconfiguring theirs. Today that comparison is almost always: incumbents vs startups.

In this analysis we’ll contrast, link by link in the value chain (acquisition, production/service, distribution, support, monetization), how the following operate:

• Banks vs fintech
• Hospitals/insurers vs healthtech
• Physical retail vs e‑commerce / marketplaces
• Traditional mobility/logistics vs digital platforms

And we’ll do it across three overlapping layers:

1. Business model
2. Technology
3. User experience (UX)

1. Reading framework: the value chain, “incumbent vs startup” edition

To ground the analysis, think of each business as a chain of 5 links:

1. Acquisition: how you attract and convert customers (marketing, sales, channels).
2. Production/service: how you generate the core product/service.
3. Distribution: how you deliver that product/service (physical/digital channels, logistics).
4. Support: how you manage incidents, after‑sales, service.
5. Monetization: how you charge, pricing, recurrence, cross‑sell, etc.

In each link, we’ll look at:

• Incumbent:

  • Typical business model
  • Classic technology stack
  • User experience

• Disruptive startup:

  • Emerging model
  • Technology
  • UX and digital product

• Structured comparison:

  • Advantages / disadvantages
  • What is being “hybridized”

2. Banking vs Fintech

2.1 Traditional bank archetype

Business model

• Revenues:
  • Net interest margin (deposits vs loans).
  • Service fees (cards, accounts, transfers, FX).
  • Investment banking, insurance, asset management (depending on the bank).
• Costs:
  • Branch network, headquarters, staff.
  • Legacy systems, regulatory compliance, risk and regulatory capital.
• Vertical integration: high. From acquisition to back‑office, almost everything is in‑house.
• Physical vs digital assets: heavy weight in real estate, ATMs, branches; very heavy, non‑modular core systems.
• Scalability:
  • Geographic scale‑up is expensive.
  • Scaling products is slow (internal approval cycles, regulators).
• Governance and decision‑making:
  • Hierarchical, with multiple risk, compliance, product committees.
  • Long time horizon, focus on stability and solvency.

Technology

• Architecture:
  • Monolithic banking core, with integration layers around it (ESB, middleware).
  • Releases a few times a year.
• Cloud:
  • Gradual adoption, often hybrid (on‑prem + cloud).
  • Resistance due to regulatory and perceived security issues.
• Data and analytics:
  • Classic BI (regulatory reporting, internal dashboards).
  • Statistical credit risk models, but limited use of real‑time ML.
• Automation:
  • Heavy processes in paper / PDFs / RPA on top of legacy systems.
• Integrations:
  • Internal APIs; few public APIs (though PSD2/Open Banking in Europe and elsewhere is changing this).
• Cybersecurity and compliance:
  • Very robust, but also a source of friction.
  • Large compliance, audit, legal teams.

User experience

• Journeys:
  • Slow onboarding (branch visit, wet signatures, in‑person KYC).
  • Products designed from a risk perspective, not from the user’s perspective.
• Omnichannel:
  • Web, app, branch, call center… but with silos and inconsistent experiences.
• Personalization:
  • Basic segmentation (mass, affluent, private).
• Friction:
  • Long forms, manual processes, hours of waiting for certain procedures.
• Response times:
  • Loans and complex products: days or weeks.
• Feedback:
  • Periodic surveys (NPS), complaints through formal channels; little “fast cycle”.

2.2 Fintech archetype

Business model

• Revenues:
  • Interchange fees, premium subscriptions (neobanks), per‑transaction fees (payments, remittances).
  • Banking as a service, specialized lending, buy now pay later, aggregators.
• Costs:
  • Small team, cloud infra, digital marketing.
  • Usually no physical network; lower initial regulatory cost (operate as agents, e‑money, etc.).
• Vertical integration:
  • Varies: from full‑stack (Nubank) to “front‑end” on top of banks/partners.
• Physical vs digital assets: almost entirely digital; focus on product IP, data, brand.
• Scalability:
  • Very high in digital channels: a well‑designed product can be replicated globally with regulatory adaptations.
• Governance:
  • Founders with strong decision power.
  • Lightweight committees, fast iteration; VC pressure for growth.

Technology

• Architecture:
  • Microservices, APIs first.
  • Cloud infrastructure from day one.
• Data and analytics:
  • Intensive use of transactional and alternative data (app behavior, networks, telco).
  • ML in scoring, fraud prevention, personalization.
• Automation:
  • Natively digital processes (digital KYC, onboarding in minutes, e‑signature).
• Integrations:
  • Open APIs with merchants, platforms, aggregators.
• Cybersecurity and compliance:
  • “By design” in many cases, but less maturity in formal processes than banks.

User experience

• Journeys:
  • Designed “mobile first”. Account opening in minutes, instant virtual card.
• Omnichannel:
  • Very strong in digital (app/web); human support via chat/WhatsApp, almost no physical presence.
• Personalization:
  • Behavior‑based offers, smart alerts and notifications.
• Friction:
  • Minimal in onboarding and frequent use; huge focus on reducing clicks and screens.
• Response times:
  • Authorizations in seconds; credit decisions in minutes.
• Feedback:
  • Product iteration based on real usage, A/B testing, cohort analytics.

2.3 Synthetic comparison: banking vs fintech

Dimension             | Traditional bank                     | Fintech
--------------------- | ------------------------------------ | ----------------------------------------
Revenues              | Intermediation + broad fees          | Specific fees, subscription, BaaS
Costs                 | High physical & regulatory CAPEX     | Higher variable OPEX, low physical infra
Technology            | Monolithic, on‑prem core             | Microservices, cloud, APIs
Data                  | BI and statistical models            | Real‑time ML, alternative data
Onboarding            | Slow, in‑person or semi‑in‑person    | 100% digital, minutes
Regulation            | Very strong, established framework   | In transition, sandbox in some countries
Trust                 | High due to brand and age            | Wins on UX; must build reputation
Innovation            | Gradual, at regulatory pace          | Fast, with risk of “moving too fast”

Hybridization in banking

• Banks copying fintech:
  • “Smart” branches, redesigned apps, digital KYC, open APIs (open banking).
  • Innovation labs, hackathons, agile squads.
• Fintech copying banks:
  • Apply for full licenses (Nubank, Revolut) and adopt robust risk and compliance structures.
  • Start to look like banks in reporting, capital and supervisor relations.

3. Healthcare vs Healthtech

3.1 Traditional hospital / insurer archetype

Business model

• Revenues:
  • Fee‑for‑service, DRGs (episode‑based payments), insurance premiums.
• Costs:
  • Hospital infrastructure, equipment, healthcare personnel.
  • Fragmented systems, administrative and authorization costs.
• Vertical integration:
  • Many hospitals integrate diagnosis, treatment and sometimes insurance.
• Physical vs digital assets:
  • Overwhelming dominance of physical assets, not easily replicable.
• Scalability:
  • Limited by physical capacity and availability of professionals.
• Governance:
  • Strong influence from doctors, unions, regulators, insurers.
  • Slow decision‑making, highly constrained by regulation and ethics.

Technology

• Architecture:
  • Hospital Information Systems / EMRs monolithic, often on‑prem.
• Cloud:
  • Gradual adoption; privacy concerns (HIPAA, GDPR, etc.).
• Data:
  • Lots of clinical data underused; reporting focused on compliance and billing.
• Automation:
  • Very uneven; large part of the flow is still paper + calls + fax in some countries.
• Integrations:
  • Closed systems, limited interoperability (HL7, FHIR slowly adopted).
• Cybersecurity and compliance:
  • Extremely sensitive yet frequent breaches; old systems are hard to patch.

User experience (patient)

• Journeys:
  • Appointment, waiting, consultation, tests, more waiting, results on paper.
• Omnichannel:
  • Phone + in‑person; web portals not very user‑friendly.
• Personalization:
  • Limited; except in premium private medicine or specific chronic programs.
• Friction:
  • High: waiting times, repeated data entry, lost results, cross authorizations.
• Feedback:
  • Occasional satisfaction surveys, formal complaints.

3.2 Healthtech archetype

Business model

• Revenues:
  • Telemedicine (per consult, subscription), SaaS for clinics, connected devices, management platforms.
  • B2B2C models (insurer + employee/patient).
• Costs:
  • Software development, regulatory compliance (for medical devices, trials), cloud infrastructure.
• Vertical integration:
  • From purely digital platforms to full‑stack (virtual hospitals, owned clinics).
• Physical vs digital assets:
  • Mainly digital; when physical, usually lightweight (wearables, remote diagnostic kits).
• Scalability:
  • High in digital services (teleconsultation, remote monitoring).
• Governance:
  • Tech founders + doctors; strong tension between fast iteration and clinical/regulatory validation.

Technology

• Architecture:
  • Cloud‑native, microservices; clinical record and device data lakes.
• Data and AI:
  • Clinical decision support algorithms, automated triage, anomaly detection in imaging, etc.
• Automation:
  • Automatic reminders, adherence tracking, wearable integration.
• Integrations:
  • APIs with hospital EMRs, insurers, pharmacies (where the system allows it).
• Cybersecurity and compliance:
  • Security by design, end‑to‑end encryption, granular access controls.

User experience (patient)

• Journeys:
  • Digital onboarding, instant appointment, video or chat consult, e‑prescription.
• Omnichannel:
  • App, web, sometimes kiosks in pharmacies or companies.
• Personalization:
  • Tailored care plans (diabetes, COPD), personalized reminders.
• Friction:
  • Low for mild/moderate conditions; still hard in complex cases requiring physical coordination.
• Feedback:
  • Marketplace‑style ratings (doctor, care quality), real‑time NPS.

3.3 Synthetic comparison: healthcare vs healthtech

Dimension             | Traditional hospital/insurer         | Healthtech
--------------------- | ------------------------------------ | ----------------------------------------------
Revenues              | Fee‑for‑service, premiums            | Subscription, telemedicine, B2B2C, SaaS
Costs                 | Physical infra, personnel            | Software dev, cloud, regulatory
Technology            | Monolithic EMR, on‑prem              | Cloud, microservices, FHIR/HL7 integrations
Data & AI             | Reporting, limited advanced use      | Decision support, triage, remote monitoring
Experience            | Clinical‑centric, low UX focus       | User‑centric, telemedicine and self‑service
Regulation            | Very strong, stable tradition        | Growing; medical device classification, etc.
Trust                 | High due to medical authority        | Wins in access/speed; must prove safety & rigor
Innovation            | Slow, constrained by clinical        | Faster, but limited by evidence and regulation

Hybridization in healthcare

• Hospitals copying healthtech:
  • Patient portals, apps for results, teleconsultation.
  • Innovation teams, partnerships with startups for remote monitoring.
• Healthtech copying hospitals:
  • Chief Medical Officers, ethics committees, clinical trials, certifications (FDA, CE).
  • Heavier but necessary quality processes to scale with credibility.

4. Physical retail vs e‑commerce / marketplaces

4.1 Traditional retailer archetype

Business model

• Revenues:
  • Margin on products sold (buy from wholesalers/manufacturers and resell).
  • Secondary revenues: shelf‑space rental, private labels.
• Costs:
  • Store rent/ownership, inventory, supply logistics, store staff.
• Vertical integration:
  • Varies: from pure distributors to integration with private labels, logistics and even manufacturing.
• Physical vs digital assets:
  • Very focused on physical stores, warehousing and traditional logistics.
• Scalability:
  • Opening new stores, very capital‑intensive.
• Governance:
  • Long planning cycles (seasons, collections), centralized decisions.

Technology

• Architecture:
  • Monolithic ERPs, in‑store POS systems, inventory not fully integrated in real time.
• Cloud:
  • Partial (CRM, marketing), but much of the core still on‑prem.
• Data:
  • Focus on historical sales, turnover, margins; limited use of advanced predictive analytics.
• Automation:
  • Semi‑automatic replenishment; back‑office RPA; automated warehouses only in leaders.
• Integrations:
  • Closed systems; hard integration with marketplaces or external partners.

User experience

• Journeys:
  • Discovery in store, in‑person purchase, paper receipt.
• Omnichannel:
  • Web or app as “catalogue”; BOPIS (buy online, pick up in store) still maturing unevenly.
• Personalization:
  • Points‑based loyalty programs; mass campaigns.
• Friction:
  • Travel to store, queues, locally limited stock.
• Feedback:
  • Occasional surveys, suggestion box, calls to customer service.

4.2 E‑commerce / marketplace archetype

Business model

• Revenues:
  • Margin on owned sales + third‑party commissions (marketplace).
  • Advertising, logistics services, subscriptions (Amazon Prime), data.
• Costs:
  • Tech infrastructure, fulfilment centers, digital marketing, last mile (owned or outsourced).
• Vertical integration:
  • From pure marketplaces to Amazon‑type models (own logistics, private labels, financial services).
• Physical vs digital assets:
  • Fewer stores, more fulfilment centers; central value in platform and data.
• Scalability:
  • Very high: adding sellers/products is cheap; limits lie in logistics and CAC.
• Governance:
  • Driven by daily metrics (conversions, churn), continuous experimentation.

Technology

• Architecture:
  • Microservices; recommendation engines, dynamic pricing systems.
• Cloud:
  • Full cloud or optimized hybrid; intensive use of CDNs and auto‑scaling.
• Data and AI:
  • Recommenders, segmentation, demand prediction, fraud detection.
• Automation:
  • Robotic operations in leading logistics (Amazon, Alibaba), self‑service processes for sellers.
• Integrations:
  • APIs for sellers, logistics partners, payment gateways, etc.

User experience

• Journeys:
  • Search, recommendation, purchase in minutes, delivery in 24–48 hours or same day.
• Omnichannel:
  • 100% digital, pickup points, lockers, some support stores.
• Personalization:
  • Very high: recommendations by history, behavior, context.
• Friction:
  • Low, except for returns in some countries or segments.
• Feedback:
  • Product/seller ratings, reviews, transactional NPS.

4.3 Synthetic comparison: retail vs e‑commerce

Dimension             | Physical retail                      | E‑commerce / Marketplace
--------------------- | ------------------------------------ | --------------------------------------------
Revenues              | Resale margin                        | Margin + commissions + ads + logistics
Costs                 | Stores, inventory, staff             | Fulfilment centers, tech, last mile
Technology            | Monolithic ERP/POS                   | Cloud platform, microservices, recommender
Experience            | Store visit‑centric                  | Convenience‑ and speed‑centric
Omnichannel           | In transition                        | Natively digital, integrates logistics & payments
Regulation            | Less intense                         | Growing (competition, tax, data)
Trust                 | Physical presence gives security     | Based on brand, reviews, return policies
Innovation            | Cyclical (collections)               | Continuous (features, logistics, pricing)

Hybridization in retail

• Retailers copying e‑commerce:
  • Own marketplaces (Carrefour, Walmart), apps, click & collect, digital cards.
  • Use of data for assortment and dynamic pricing.
• E‑commerce copying retailers:
  • Physical “showroom” stores (Amazon Fresh, Amazon Go, Warby Parker).
  • In‑person experiences for complex products.

5. Traditional mobility / logistics vs digital platforms

5.1 Traditional operator archetype (taxis, transport, classic logistics)

Business model

• Revenues:
  • Regulated fares (taxis), B2B logistics contracts, per‑shipment fees.
• Costs:
  • Owned vehicles or licenses, warehouses, fuel, drivers/operators.
• Vertical integration:
  • From pure carriers to integrated operators (warehousing + transport + customs).
• Physical vs digital assets:
  • Very asset‑intensive.
• Scalability:
  • Grow fleet, routes, warehouses; relatively slow growth.
• Governance:
  • Traditional structures, often guild‑based (taxis, trucking).

Technology

• Architecture:
  • Traditional fleet and warehouse management systems, on‑prem.
• Data:
  • Focus on operational tracking (basic tracking), static route planning.
• Automation:
  • Low to medium; advanced WMS only in large operators.
• Integrations:
  • Few APIs; communication with clients via EDI, email, phone.

User experience

• Taxis / urban transport:
  • Physical stands, phone calls, little transparency on price/time.
• B2B logistics:
  • Limited tracking, communication via email/calls, poor real‑time visibility.
• Friction:
  • High uncertainty, little information, manual processes.

5.2 Digital mobility / logistics platform archetype

Business model

• Revenues:
  • Commission per trip/shipment (Uber, Cabify, Didi, Glovo), B2B subscriptions (logistics SaaS).
• Costs:
  • Platform development, marketing, driver/courier incentives.
• Vertical integration:
  • Platform model (third‑party assets) vs full‑stack (own fleet, dark stores, etc.).
• Physical vs digital assets:
  • Low owned assets (pure platforms); value in matching algorithms and user network.
• Scalability:
  • Very high: more users/drivers create network effects.
• Governance:
  • “Tech” culture, data‑driven decisions, continuous iteration of prices and promotions.

Technology

• Architecture:
  • Microservices, real‑time, maps, trip‑assignment and route‑optimization algorithms.
• Cloud:
  • 100% cloud, highly elastic.
• Data and AI:
  • Demand prediction, surge pricing, ETAs, fraud detection.
• Automation:
  • Automatic driver‑passenger matching, dynamic routing, automatic billing.
• Integrations:
  • APIs with merchants, restaurants, e‑commerce, B2B customers’ ERPs.

User experience

• Urban mobility:
  • Booking via app, map visualization, price estimate, automatic payment, driver rating.
• Logistics / last mile:
  • Real‑time tracking, delivery windows, notifications.
• Friction:
  • Minimal in contracting and payment; service/safety debates depending on city.
• Feedback:
  • Reputation system, instant reviews.

5.3 Synthetic comparison: mobility/logistics

Dimension             | Traditional operator                 | Digital platform
--------------------- | ------------------------------------ | ------------------------------------------
Revenues              | Regulated fares / B2B contracts      | Commissions, SaaS, platform services
Costs                 | Fleet, warehouses, staff             | Tech, network incentives, some owned assets
Technology            | Basic fleet/warehouse systems        | Cloud platform, geolocation, real time
Experience            | Manual, low transparency             | App, tracking, visible price
Regulation            | Historically regulated (taxis, etc.) | Contested (labor, tax, competition)
Trust                 | Based on local notoriety             | Based on platform reputation and ratings
Innovation            | Low‑to‑moderate                      | High, fast iteration of model & features

Hybridization in mobility/logistics

• Traditionals copying platforms:
  • Taxi apps (Free Now, MyTaxi), tracking portals in logistics, dynamic pricing.
• Startups copying traditionals:
  • Own fleets (dark kitchens, dark stores, micro‑fulfilment) to guarantee service.
  • Deals with regulators, adoption of labor agreements and safety standards.

6. The three layers across the value chain

To stay oriented, it helps to see what changes by layer across the whole value chain.

6.1 Layer 1: Business model

• Incumbents:

  • Advantages:
    • Diversified, established revenue streams.
    • Access to cheaper capital, brand and customer base.
    • Better management of regulation and systemic risks.
  • Disadvantages:
    • Very high fixed costs; heavy structures.
    • Hard to experiment with models that cannibalize the current business.

• Startups:

  • Advantages:
    • Focused on a value‑chain niche with clear value propositions.
    • More flexibility to test pricing, bundles, subscription models.
  • Disadvantages: