Letters from the Pass: Urgent Notes on Digital Transformation from a Chef Who Hates Overcooked Strategy

The Order Ticket Is on Fire (The Hook)

Letter 1. Service pass, 2030, 21:37.

You’ve got the entire executive committee seated at table 12.

The CFO complains that margins have halved in five years.
The CMO insists that “young people prefer someone else’s app.”
The CIO swears that “migration to the cloud is at 72%.”

And yet this morning’s numbers are clear: in banking, healthcare, retail, mobility, and education, the same thing is happening as in an overwhelmed kitchen:

• Oven full of old dishes nobody ordered (legacy systems).
• Mise en place duplicated across three different fridges (data silos).
• New apprentices (startups) putting out a short, sharp, winning menu.

You called me at the last minute because you suspect something uncomfortable: maybe you don’t need another presentation on “innovation,” but an honest list of ingredients, cooking times, and food‑poisoning risks.

So I’m going to write to you the way I cook: direct, demanding, and obsessed with balance. Each letter will be a ticket on the pass, a reminder that the future isn’t won with slogans, but with recipes that withstand the heat of real service.

How You Ended Up Cooking with 1987 Recipes (The Genesis)

Letter 2. Walk‑in fridge, 2030, 07:12.

Before you compare sectors, understand your core mistake: you’re still treating digital transformation as if it were changing the tableware, when in reality it’s changing the pantry top to bottom.

For decades, traditional industry worked like a restaurant with a long, structured menu:

• Business models:

  • Consolidated revenue streams, tried and tested, defended by regulation and scale.
  • High fixed costs (branches, hospitals, stores, fleets, campuses) justified by volume and stability.
  • Go‑to‑market based on physical distribution, sales force, and historic brand.

• Technology:

  • Inherited monoliths, hard to touch without taking the whole service down.
  • On‑premise infrastructures designed for robustness, not flexibility.
  • Data as an accounting by‑product, not the key ingredient in the dish.

• User experience:

  • Processes designed around the internal org chart, not the guest.
  • Slow onboarding, extensive documentation, rigid schedules.
  • Faux omnichannel: many channels, but different recipes in each.

Then startups showed up with a different culinary mindset:

• Short, iterative, high‑risk recipes. They perfect one excellent dish before thinking about opening a second dining room.
• Technology as an open kitchen. Anyone on the brigade can see the flame, touch the data, adjust the cooking time.
• Experience as the signature dish. Onboarding in minutes, transparent pricing, mobile‑first as a rule, not an experiment.

Your mistake isn’t failing to look like a startup.

Your mistake is clinging to processes designed for a world where the customer had no alternative delivery option.

The Conflict You Don’t See: It’s Not “Them vs. Us” (The Invisible Conflict)

Letter 3. Cold station, 2030, 11:03.

You’ve been sold the wrong story: incumbents vs. startups, David vs. Goliath, stockpot vs. siphon.

The real tension isn’t between types of companies, but between two kitchen logics:

1. Stability logic:

   • Optimise already‑proven recipes.
   • Minimise variability and health risk (regulation).
   • Prioritise clear, predictable unit economics.

2. Exploration logic:

   • Try new combinations, burn a few sauces.
   • Accept initial losses in exchange for accelerated learning.
   • Bet on new service formats (subscription, marketplace, usage‑based).

You need both if you want a restaurant to last decades. The problem is when:

• Incumbents only cook on the slow flame of stability.
• Startups only work with a blowtorch, ignoring the gas bill.

If you don’t understand this underlying conflict, you’ll make shallow, sector‑by‑sector comparisons and miss the essence: in every market we’ve analysed, the winner is whoever masters the right blend of stability and exploration, not whoever shouts “disruption” the loudest.

Sector Letter 1: Fintech/Banking — Too Many Cooks for a Single Balance Sheet

Letter 4. Stew line, 2030, 09:45.

1.1 Business models: from fixed menu to modular tasting menu

Traditional industry:

• Revenue based on:
  • Interest margins (loans, mortgages).
  • Service fees (accounts, cards, transfers).
  • Bundled, hard‑to‑understand products (tied insurance, opaque conditions).
• Very high fixed costs in branches, systems, and compliance.
• Go‑to‑market: sales force, brand, historic relationships, and protective regulation.

Startup thesis:

• Strip out layers of complexity and distribution cost.
• Attack specific P&L points: payments, consumer credit, remittances, FX, retail investing.
• Monetisation via lower fees, premium subscription, interchange, B2B infrastructure fees.

Archetypes:

• Neobanks: 100% digital accounts and cards, revenue from interchange, FX, subscriptions.
• BNPL: embedded credit at checkout, merchant pricing, shared risk with partners.
• Infrastructure/API: banking‑as‑a‑service, KYC/AML as a service, payment orchestration.

1.2 Technology: from single stove to modular cooking stations

• Incumbents: monolithic core banking, nightly batch runs, lots of point‑to‑point integration, predominantly on‑prem.
• Startups: microservices, public cloud, API‑first, data lakes, ML for alternative scoring.

1.3 User experience: friction as toll vs friction as unforgivable failure

• Onboarding:
  • Traditional bank: days, physical interaction, multiple documents.
  • Fintech: minutes, eKYC, biometrics, guided UX.
• Self‑service: incumbents’ apps are improving, but many critical operations still require a call or visit.
• Personalisation: limited recommendations vs real‑time offer engines.

1.4 Quick scorecard

The missing recipe in almost every bank: use their historical databases with modern architecture and autonomous product teams to experiment in short cycles.

Sector Letter 2: Healthcare/Healthtech — Cooking Under Extreme Sanitary Rules

Letter 5. Hospital kitchen, 2030, 06:58.

2.1 Business models: between clinical menu and health delivery

Traditional industry:

• Revenue from:
  • Medical acts (consultations, surgeries, diagnostics).
  • Hospital stays.
  • Agreements with insurers and public systems.
• Costs dominated by staff, facilities, heavy medical tech.

Startup thesis:

• Shift part of the “in‑room service” to the patient’s home.
• Monetise:
  • Remote monitoring subscriptions.
  • SaaS for clinics (scheduling, medical records, billing).
  • Pay‑per‑use (AI image analysis, pre‑diagnostics).

Archetypes:

• Telemedicine: video‑consultation and medical chat platforms.
• Clinical SaaS: full or modular management (appointments, EMR, billing).
• AI diagnostics: tools for medical imaging, automated triage, population risk.

2.2 Technology: from hanging folders to continuous data flow

• Incumbents: systems fragmented by specialty, poorly interoperable EMRs, in‑house servers due to data sensitivity.
• Startups:
  • Cloud with strong encryption and compliance.
  • APIs to integrate with existing EMRs.
  • AI/ML for risk segmentation, early detection, resource optimisation.

2.3 User experience: patient vs user

• Onboarding:
  • Traditional: multiple forms, repeat data at every centre.
  • Healthtech: unified profiles, accessible histories, apps that accompany before/after the visit.
• Friction: physical waits, little visibility on timing vs digital follow‑up, reminders, results in app.
• Human care: the key isn’t to remove it, but to integrate it with well‑designed self‑service.

2.4 Relative advantages

If you’re a healthcare incumbent, your challenge isn’t to look like a startup, but to cook digital experience without breaking the regulatory cold chain.

Sector Letter 3: Retail/E‑commerce — When the Dining Room Becomes an App

Letter 6. Walking between tables, 2030, 17:22.

3.1 Business models: from aisle to marketplace

Traditional industry:

• Revenue from direct product sales.
• Clear gross margin models, eroded by promotions and overcapacity.
• Costs in rent, inventory, store staff, replenishment logistics.

Startup thesis:

• Become a platform, not just a store.
• Revenue from seller commissions, fulfilment services, data, and onsite ads.

Archetypes:

• Generalist and vertical marketplaces.
• Subscription models: recurring boxes, memberships with benefits.
• Dropshipping and asset‑light: focus on marketing and experience, third parties handle inventory and shipping.

3.2 Technology: from ERP as sole god to a microservices orchestra

• Traditional: POS systems, central ERP, slow integrations, misaligned catalogues between physical and online.
• Startups: modular architectures (headless commerce), recommendation engines, real‑time analytics, cloud‑native.

3.3 User experience: infinite aisle vs precise search

• Onboarding: simple guest checkout vs cumbersome sign‑ups designed more by fraud teams than by product.
• Personalisation: incumbents often limited to newsletters; startups use fine‑grained segmentation, recommendations, dynamic pricing.
• Omnichannel: click & collect, smooth returns, real‑time inventory are the new baseline.

3.4 Scorecard

Your biggest risk here: continuing to optimise aisles when the customer only sees screens.

Sector Letter 4: Mobility/Transport — Delivery Kitchen and Ghost Kitchen

Letter 7. Goods entrance, 2030, 05:50.

4.1 Business models: from licence to algorithm

Traditional industry:

• Taxi firms, public transport operators, logistics companies.
• Revenue from regulated fares or long‑term contracts.
• Costs in fleet, licences, fuel, staff.

Startup thesis:

• Orchestrate existing supply with real‑time algorithms.
• Monetise:
  • Commission per ride.
  • Dynamic pricing.
  • B2B services (last‑mile delivery, fleet management).

Archetypes:

• Ride‑hailing and car‑sharing.
• Micromobility platforms (bikes, scooters).
• Digital last‑mile logistics operators.

4.2 Technology: from control centre to cloud dashboard

• Traditional: static planning systems, phone bookings, fleet ERPs.
• Startups:
  • Mobile apps with geolocation.
  • Real‑time assignment and pricing algorithms.
  • Cloud, event‑driven infrastructure, APIs for third parties.

4.3 User experience: they don’t care about your internal complexity

End users expect:

• Reliable ETA.
• Map tracking.
• Silent, integrated payment.

Incumbents are still often stuck with paper tickets, fragmented information, and reactive customer service.

4.4 Relative advantages

The winning dish in mobility is cooked with regulation at the table, data as base oil, and unit‑economics discipline that many startups still ignore.

Sector Letter 5: Education/Edtech — From Fixed Menu to Personalised Menu

Letter 8. Group‑booking pass, 2030, 15:30.

5.1 Business models: credits vs cohorts

Traditional industry:

• Universities, schools, in‑person academies.
• Revenue from tuition, per‑credit fees, public funding.
• Costs in campuses, teaching staff, admin structures.

Startup thesis:

• Break the “full degree” unit and offer modules, cohorts, bootcamps.
• Models:
  • Subscription (ongoing content access).
  • Pay per course or certification.
  • Revenue‑share (e.g., “pay when you get a job”).

Archetypes:

• Mass and niche course platforms.
• Intensive digital‑skills bootcamps.
• SaaS tools for learning management (LMS).

5.2 Technology: from blackboard to learning graph

• Traditional: basic LMS, videoconferencing bolted onto existing courses, low‑personalisation assessments.
• Startups:
  • Scalable cloud platforms.
  • AI for personalised paths, content recommendations, auto‑grading.
  • Real‑time engagement and performance analytics.

5.3 User experience: captive student vs demanding customer

• Onboarding and use:
  • Incumbents: long admissions processes, heavy bureaucracy.
  • Edtech: instant sign‑up, diagnostic tests, and access within minutes.
• Engagement: static recorded lectures vs live cohorts, moderated forums, practical challenges.

5.4 Scorecard

The key here is alliance: heavyweight degrees + agile, modular experiences with employability metrics.

Cross‑Sector Table: Who Wins What in 2030

Letter 9. Pass whiteboard, 2030, 12:00.

Here’s a cross‑sector view, the equivalent of today’s specials.

The Winners vs. Losers Scorecard (if you don’t fix the recipe)

Evidence, Numbers, and the Hidden Kitchen (Evidence & Insights)

Letter 10. Back‑office behind the kitchen, 2030, 19:10.

You don’t need another report; you need to use data like you use salt: deliberately.

From what you’ve seen in your own business and across sectors, clear patterns emerge:

• Execution speed: Startups ship new features in weeks; many incumbents still work in 6–12‑month cycles. That gap is not anecdotal; it’s a compounded competitive edge.
• Risk management: Incumbents manage commercial risk in validated environments; startups shoulder existential risk (product, market, regulation). That’s why they can experiment more aggressively with pricing, UX flows, and data models.
• Financing: Dependence on venture capital forces startups to prioritise growth over profitability in early years, accepting shaky unit economics in exchange for market share.
• UX/CX metrics: Where startups systematically lead:
  • Time to value: high for incumbents (days, weeks) vs minutes/hours.
  • NPS: when UX is clear and support is fast, the gap can be 20–40 points.
  • Retention: products built for frequent interaction (fintech, edtech, retail) are stickier than services with sporadic, poorly digitised relationships (healthcare, traditional education).

This is the unseen kitchen: you’re not just competing on products; you’re competing on internal metrics that decide what gets cooked and what gets binned.

The Tech Kitchen: Who Uses a Blowtorch and Who Still Uses Charcoal (Technology Dimension)

Letter 11. Utensil storeroom, 2030, 08:20.

Typical incumbent stack vs startup stack

Incumbents:

• Legacy languages and frameworks (COBOL, old‑school Java EE, older .NET).
• Monolithic or heavy SOA architectures.
• Mostly on‑prem due to history, regulation, or perceived cost control.
• Partial automation, manual back‑office processes.
• Point‑to‑point integrations or ESB with bottlenecks.
• Data scattered across many databases, old models, low quality.

Startups:

• Modern languages (Node.js, Go, Python, Kotlin, etc.) and agile frameworks.
• Microservices, containers, Kubernetes, serverless where it makes sense.
• Public or hybrid cloud as the base.
• CI/CD pipelines, frequent deployments.
• Integrations via APIs, webhooks, events.
• Cloud data lakes/warehouses, near real‑time analytics.

Key roles of AI/ML, APIs, low‑code, and events

• AI/ML:
  • Startups use it for scoring, recommendation, fraud detection, clinical triage, learning paths.
  • Incumbents have the volume advantage, but face data‑quality and applied‑talent gaps.
• Open APIs:
  • Fintech: open banking is a clear example of regulation forcing the kitchen open.
  • Retail and mobility: APIs for partners, logistics integrations, catalogues, bookings.
• Low‑code/no‑code:
  • A space where incumbents can move fast if they govern it well: automating internal flows, back office, prototypes.
• Event‑driven architecture:
  • Stop thinking in linear processes and start thinking in real‑time reactions: a payment, a login, a consultation — every event triggers actions.

The real constraint for incumbents isn’t available technology; it’s the courage to encapsulate the monolith instead of rewriting everything at once, and to let new satellite kitchens work on top of it.

UX and Product Design: The Menu the Customer Actually Tastes (User Experience)

Letter 12. Dining room, 2030, 13:05.

Design approach

• Incumbents:

  • Products built around internal processes and compliance.
  • Waterfall development: long specs, big and infrequent releases.
  • Testing limited to technical QA; little real A/B testing with users.

• Startups:

  • User‑centred product, flows stripped to essentials.
  • Agile/lean methods: short cycles, continuous discovery.
  • Constant experimentation: A/B tests, interviews, funnel analysis.

Metrics where startups usually win

• Time to value: first truly useful action in minutes.
• CAC vs LTV: CAC can spike at scale, but the best players design for retention from day one.
• NPS and CSAT: driven by clear pricing, simple onboarding, fast support.

Typical incumbent pain points turned into startup advantages

• Endless forms → Guided, step‑by‑step onboarding with autocomplete.
• Opaque pricing → Simple tariffs, no small print, clear simulators.
• Slow support → In‑app chat, actionable FAQs, well‑designed self‑resolution.

Until you measure friction the way you measure seasoning, you’ll keep serving dishes the customer tolerates but doesn’t recommend.

The Great Reorganisation: Strategic Changes You Can’t Postpone (The Strategic Shift)

Letter 13. Team briefing before service, 2030, 10:00.

Forget “being like a startup.” Your goal is to balance the kitchen.

For incumbents

1. Separate kitchens:

   • Keep a stability kitchen (core, compliance, critical ops).
   • Create an exploration kitchen with its own metrics, free from core bureaucracy.

2. Rethink the business menu:

   • Introduce modular models: subscription, usage‑based, freemium, personalised bundles.
   • Move from closed products to platforms where third parties can cook on top (APIs, marketplaces, ecosystems).

3. Rebuild the brigade:

   • Cross‑functional product teams: business, tech, design, data.
   • Incentives tied to usage and satisfaction metrics, not just short‑term revenue.

4. Pragmatic tech governance:

   • Encapsulate legacy with service layers.
   • Prioritise automation where the customer feels it most (onboarding, support, self‑service).

For startups

1. Cook with a P&L from day one:

   • Understand unit economics by segment, channel, and product.
   • Don’t build a strategy on “the next round will fix it.”

2. Professionalise regulator relations:

   • Bring compliance and legal into product design, not as an end‑stage brake.

3. Pick your battles:

   • Niches where experience is decisive and regulation is manageable.
   • Or infrastructure where you can sell the kitchen to many restaurants.

Incumbent–startup collaboration models

Think of them as shared kitchens with clear risk and reward splits:

1. Commercial deals (reselling/partnering):

   • Incumbent brings distribution and brand.
   • Startup brings specialised digital product.

2. White‑label / embedded:

   • Startup cooks, incumbent serves under its brand.
   • You gain speed without sacrificing customer trust.

3. Corporate Venture Capital (CVC):

   • Minority stakes for early access to innovation.
   • Danger: suffocating the startup with corporate processes.

4. Selective M&A:

   • You buy the recipe and part of the brigade.
   • Key: gentle integration, preserve product culture.

5. Joint ventures / shared labs:

   • Shared kitchens to explore new dishes without risking the core.

In every case, the question isn’t “what do we do together?” but “what new dish can we serve that neither of us could cook alone?”

The Master Blueprint: What’s Really at Stake (The Big Picture)

Letter 14. Last ticket of the night, 2030, 23:58.

The gravest mistake you can make in 2030 is confusing digital activity with a winning recipe.

You’ve seen banks with spectacular apps but pre‑digital risk processes.
You’ve seen health startups with brilliant AI but no solid clinical trials.
You’ve seen retailers with omnichannel in PowerPoint and endless queues in‑store.

What’s at stake isn’t who has more features, but who masters balance:

• Between stability and exploration.
• Between compliance and speed.
• Between experience and profitability.

The 2030 customer doesn’t judge your gastronomy by your storytelling, but by three very simple things:

1. Do you waste less of my time than the others?
2. Do I understand what you’re charging me and why?
3. Do I trust that you’ll still be there when I need you?

Your entire strategy —business models, technology, UX— should answer these three questions as if they were the three base flavours of your kitchen.

If you don’t, someone else will. And as in any good restaurant, the verdict is never delivered in the meeting room, but in the reservation that doesn’t get renewed.

The ticket is in your hand.

Serve better.

References

1. General comparative context of business models, technology, and UX between traditional industry and startups in fintech, healthcare, retail/e‑commerce, mobility, and education, including differences in agility, organisational structures, funding, and risk management.
2. Analysis of the fintech/banking sector: business models based on fees and interest, strong regulatory constraints, emergence of neobanks, BNPL, and infrastructure/API players focused on underserved niches and new data‑driven risk models.
3. Analysis of the healthcare/healthtech sector: traditional systems with manual processes and paper records, healthtechs focused on process digitalisation, telemedicine, SaaS for clinics, and AI‑based diagnostics.
4. Analysis of the retail/e‑commerce sector: incumbents with physical stores and owned inventory, e‑commerce startups with marketplace, subscription, and dropshipping models, highlighting their speed in improving experience.
5. Cross‑sector synthesis on differences in execution speed, funding models, organisational culture, and adoption of technologies such as cloud, data/analytics, AI, and open APIs, as well as the stability/scale advantages of traditional industry vs the agility and UX focus of startups.