RUNWAY SERIES : Everyday Finance, Rewired.

Olive Capital (hosted by Raph Grieco)

Runway Series, by Olive Capital (https://olivecapital.vc), explores since 2019 the same curiosity that has always shaped this show, the stuff changing underneath finance, product, and the way people build and finance tech innovation. The next generation of great consumer finance companies, the ones that could become the Revoluts of the next decade, are being built right now, during this shaky technological shift. We explore: invisible rails, the agentic economy, trustless privacy, and everyday money.

  1. 1d ago

    [Rails Report #4] ERC-8004 and modular agentic verification, explained simply

    Today for "Rails Report #4": -- When people talk about AI agents, they usually focus on what the agent can do. Can it plan? Can it execute? Can it make decisions? Can it complete a task end to end? But once agents start interacting with real-world systems, another question becomes just as important: how do we know what, or who, we are trusting? That is where modular verification matters. ERC- 8004, in simple terms, points toward a more structured way for agents and systems to prove things about themselves. Instead of relying on vague assumptions or one-off integrations, the idea is to create a modular layer where identity, capabilities, permissions, and verification can be checked more cleanly. Why does that matter? Because agents are only useful if they can operate in environments where other systems are willing to trust them enough to let them act. If an agent is going to move value, access services, trigger workflows, or interact with financial rails, then the system around it needs some way to verify that it is legitimate, authorized, and behaving within bounds. Today, that kind of trust is often handled manually, or through fragmented point solutions. One platform does one check. Another platform does another. A third layer tries to enforce policy. It works, but it is brittle. Modular agentic verification is interesting because it suggests a more composable future. Instead of forcing every application to reinvent trust from scratch, you can build a shared framework where different components handle different parts of the verification problem. That could mean proving an agent’s identity. It could mean checking what permissions it has. It could mean validating that it is allowed to perform a specific action. And it could mean making those checks interoperable across systems. The big picture is simple: as agents become more capable, verification becomes more important. Without verification, agents are just software that can act. With verification, they become software that can act inside systems that care about trust, compliance, and accountability. So when we talk about ERC-8004 and modular agentic verification, we are really talking about the plumbing that makes autonomous systems usable in the real world. Not just smarter agents, but trustworthy ones. And once that layer exists, a lot of what comes next in finance, infrastructure, and automated workflows becomes much easier to imagine. -- The podcasts are authored, edited and produced by Raph Grieco (⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠raphael-grieco.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠olivecapital.vc⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠).

    [Rails Report #4] ERC-8004 and modular agentic verification, explained simply
  2. Jul 21

    [Rails Report #3] Why stablecoins win where crypto UX loses

    Today for "Rails Report #3": -- Stablecoins win where crypto UX loses, because they solve a problem users actually care about: moving value without making them think about the machinery underneath. That sounds simple, but it is the core issue. A lot of crypto products have been built around interesting technology first, and usable experience second... The result is often a system that works for experts, but still feels awkward for everyone else. Stablecoins are different. They are useful because they sit closer to the behavior people already understand. They can feel like money, move like money, and settle faster than traditional rails, without asking the user to become a crypto native. That matters because most users do not want to manage wallets, seed phrases, chains, bridges, gas, or technical jargon. They want speed, clarity, and confidence. If a product creates too much cognitive load, the underlying innovation does not matter. The user leaves before they ever benefit from it. Stablecoins succeed because they reduce that load. They make payments easier to reason about. They make transfers more predictable. They make cross-border movement cleaner. And they can be embedded into products in a way that feels operational rather than ideological. That is where crypto UX often loses. Not in the technology, but in the interface. Not in the ambition, but in the translation from protocol to product. The best stablecoin experiences do not advertise themselves as crypto. They behave like better financial infrastructure. They hide complexity, shorten the path to completion, and let users focus on the outcome instead of the mechanism. And that is the deeper lesson. In finance, the winning product is rarely the one with the most sophisticated back end. It is the one that turns that sophistication into something people can actually trust, use, and repeat. Stablecoins win where crypto UX loses because they make value movement feel normal. And in consumer products, normal is powerful. -- The podcasts are authored, edited and produced by Raph Grieco (⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠raphael-grieco.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠olivecapital.vc⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠).

    [Rails Report #3] Why stablecoins win where crypto UX loses
  3. Jul 14

    [Everyday Money #2] The spending pattern shift between Gen Z and Millennials: what it means for product

    Today for "Everyday Money #2": -- One of the most useful things a fintech builder can understand is not just what people spend money on, but how their spending behavior changes across generations. Gen Z and Millennials both grew up with digital products, but they do not behave the same way. Their expectations around money, trust, convenience, and identity are different in ways that matter a lot for product design. Millennials came of age during the rise of smartphones, neobanks, subscriptions, and digital-first consumer habits. They are often more comfortable with structured financial tools, planning, and products that help them organize complexity. Many of them have already built routines around budgeting apps, payment apps, and account consolidation. Gen Z is different. They are even more fluid, more mobile, and more selective about the products they keep. They are less attached to traditional financial institutions, more sensitive to design and social proof, and often more willing to experiment with new tools, but also quicker to abandon anything that feels slow, opaque, or generic. That shift matters because spending is not only about income. It is about interface. It is about how people feel when they open an app, how quickly they get value, and whether the product fits into their real behavior instead of asking them to change it. For product teams, this creates a few important implications. First, the user journey has to feel lighter. Gen Z often responds better to products that are simple, visually clear, and immediate. They do not want to do extra work to understand the value. Second, trust has to be earned quickly. Both generations care about safety, but younger users are often more skeptical of institutions and more influenced by peer signals, transparency, and product experience. Third, financial products need to reflect how people actually live. That means supporting variable income, flexible spending, social payments, short planning cycles, and increasingly fragmented financial lives. There is also a deeper shift happening underneath all of this. Millennials often think in terms of optimization. Gen Z often thinks in terms of access, flexibility, and identity. One generation wants better tools. The other wants tools that feel native to how they already operate. That difference is easy to miss, but it can shape everything from onboarding to retention to monetization. If you build consumer finance products today, the question is no longer just how to serve “young users.” The question is which behaviors are changing, which expectations are becoming permanent, and which assumptions about money management are already outdated. Because the spending pattern shift is not just about age. It is a signal about what the next generation of financial products has to feel like in order to matter. -- The podcasts are authored, edited and produced by Raph Grieco (⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠raphael-grieco.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠olivecapital.vc⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠).

    [Everyday Money #2] The spending pattern shift between Gen Z and Millennials: what it means for product
  4. Jul 7

    [Everyday Money #1] The psychology of the "super wallet": what makes users consolidate their finances in one app

    Today for "Everyday Money #1": -- One of the most interesting questions in consumer fintech is not how to get someone to download an app. It is how to get them to trust one app with more and more of their financial life. That is the psychology behind the super wallet. At first, people are cautious. They may use one app for payments, another for savings, another for investing, and another for budgeting. That fragmentation feels safe because it limits exposure. But over time, if one product proves consistently useful, fast, and reliable, users start consolidating. And that is more than just a product decision, it is a psychological one. People consolidate finances in one app when the app reduces mental load. When it makes money feel more organized. When it turns a scattered financial life into something clearer and easier to manage. Convenience matters, but so does confidence. The user has to believe that the app is not just good at one task, but good at being a system they can come back to. There are a few forces behind that behavior. One is habit. The more often a product becomes part of a daily or weekly routine, the harder it is to replace. Another is visibility. If users can see their balances, transactions, goals, and activity in one place, the app becomes a kind of financial control center. And another is trust. Once people feel that a product is stable, transparent, and useful across multiple use cases, they stop thinking of it as a feature and start thinking of it as an account. That is what makes the super wallet so powerful. It is more than just aggregation for its own sake, it is the gradual collapse of financial fragmentation into a single interface that users actually want to keep using. In the end, consolidation happens when the product is useful enough to start replacing a set of decisions with a single habit. -- The podcasts are authored, edited and produced by Raph Grieco (⁠⁠⁠⁠⁠⁠⁠⁠⁠raphael-grieco.com⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠olivecapital.vc⁠⁠⁠⁠⁠⁠⁠⁠⁠).

    [Everyday Money #1] The psychology of the "super wallet": what makes users consolidate their finances in one app
  5. Jun 30

    [Agent Dispatch #1] MCP as a financial interface layer

    Today for "Agent Dispatch#1": -- When people talk about the future of software, they often focus on what the model can do. But the real shift may be in how that intelligence connects to the systems around it. That is where an MCP (Model Context Protocol) becomes interesting. At a high level, MCP is about giving software a structured way to access tools, data, and external services. In a financial context, that starts to look less like a technical protocol and more like a new interface layer, one that lets agents interact with wallets, accounts, payments, portfolio data, and other financial actions in a more standardized way. That matters because finance has always been fragmented. Every institution, product, and workflow has its own rules, formats, and integrations. Humans can deal with that fragmentation by clicking, logging in, switching screens, and making judgment calls. Software agents need something cleaner. MCP could help provide that cleaner layer. Instead of building one-off integrations for every financial action, builders can think in terms of a shared interface between agents and financial systems. That opens the door to more composable workflows, more automation, and eventually, more autonomous financial behavior. The bigger idea is not that MCP replaces the stack underneath. It is that it creates a more usable front door for intelligence to interact with finance. And if that works, it changes more than convenience. It changes how financial products are built, how agents operate, and how value moves through the system. That is why MCP as a financial interface layer is worth paying attention to. It may end up being one of the quiet infrastructure shifts that makes the next generation of finance feel much more usable. -- The podcasts are authored, edited and produced by Raph Grieco (⁠⁠⁠⁠⁠⁠⁠⁠raphael-grieco.com⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠olivecapital.vc⁠⁠⁠⁠⁠⁠⁠⁠).

    [Agent Dispatch #1] MCP as a financial interface layer
  6. Jun 23

    [Rails Report #2] Why x402 micropayments matter more than most people realize

    Today for "Rails Report #2": -- Most people hear the word micropayments and think of something niche, maybe even a little technical. But I think x402 matters because it points to a much bigger shift in how the internet can work. For years, digital products have been built around subscriptions, ads, or free trials. Those models are familiar, but they are also clumsy. They force everything into a few blunt pricing structures, even when the value being delivered is small, instant, and highly specific. x402 is interesting because it makes it easier to imagine a world where value can move as fluidly as information does. Instead of asking users to commit to a full subscription or a large upfront payment, you can pay for exactly what you use, at the moment you use it. That sounds small, yet it is not. If the economics of the internet become more granular, then entire product categories can change. APIs can be priced more precisely. AI agents can pay for services on demand. Content, compute, and software can be unlocked in smaller, cleaner transactions. And builders can design products around actual usage instead of arbitrary packaging. That is why x402 matters more than most people realize. It is more than just a payment mechanism, it is a design primitive for a different internet economy, one where the cost of moving value becomes low enough to match the speed and scale of digital interaction. And once that becomes normal, a lot of what we think of as “how the internet monetizes” starts to look outdated. -- The podcasts are authored, edited and produced by Raph Grieco (⁠⁠⁠⁠⁠⁠⁠⁠raphael-grieco.com⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠olivecapital.vc⁠⁠⁠⁠⁠⁠⁠⁠).

    [Rails Report #2] Why x402 micropayments matter more than most people realize
  7. Jun 16

    [Disclosure #1] Why "programmable confidentiality" beats privacy regulation

    Today in "Disclosure #1": -- Privacy regulation matters. It creates boundaries, sets expectations, and forces companies to take data handling seriously. But regulation alone is not enough. The reason is simple: regulation tells companies what they are allowed to do. Programmable confidentiality changes what the system can do by default. That distinction matters. In a traditional model, privacy is often bolted on after the fact. Data gets collected, stored, shared, and then protected through policy, legal language, and access controls. The user is asked to trust that the right safeguards are in place. Programmable confidentiality flips that model. It makes selective disclosure, constrained access, and controlled visibility part of the architecture itself. Instead of saying, “we promise to protect your data,” the product is designed so only the minimum necessary information is ever revealed in the first place. That is a much stronger foundation. It is stronger because it reduces risk before it starts. It is stronger because it scales better than manual enforcement. And it is stronger because it gives users and businesses a clearer, more precise way to interact: share what is needed, hide what is not. Privacy regulation is still essential. But it is a floor, not a product experience. The real shift happens when confidentiality becomes programmable, when privacy is no longer just a legal obligation, but a native property of the system. That is why programmable confidentiality beats privacy regulation. Not because regulation is unimportant, but because architecture is more durable than policy. -- The podcasts are authored, edited and produced by Raph Grieco (⁠⁠⁠⁠⁠⁠⁠⁠raphael-grieco.com⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠olivecapital.vc⁠⁠⁠⁠⁠⁠⁠⁠).

    [Disclosure #1] Why "programmable confidentiality" beats privacy regulation
  8. Jun 9

    [Rails Report #1] What "invisible rails" actually means for a consumer finance app builder

    Today for "Rails Report #1", I want to unpack a phrase that gets used a lot, but still means different things depending on who you ask: "invisible rails". -- For a consumer app builder, invisible rails are the infrastructure layers that sit underneath the product experience and make everything feel effortless. The user does not need to think about settlement, custody, payments routing, identity checks, or reconciliation. They just open the app, move money, make a decision, or complete a workflow, and the system handles the complexity in the background. That matters because consumer products win when friction disappears. The best products do not ask people to understand the machinery. They make the machinery disappear. In finance, that has become even more important. The old stack was built around visible institutions, visible intermediaries, and very visible friction. The next stack is different. It is faster, more modular, more programmable, and increasingly embedded inside products that do not even look like financial services at first glance. For a builder, this changes the game in three ways: First, you can design for behavior instead of infrastructure constraints. You are no longer forced to make the user adapt to the back end.Second, you can move from one large product to many small actions. Payments, savings, investing, FX, identity, and settlement can all become moments inside a broader experience rather than separate destinations. Third, you can create trust without exposing complexity. The user does not need to see every rail to feel that the system is reliable, secure, and instant. That is what invisible rails really mean. Not just better technology, but a different product philosophy: hide the plumbing, improve the experience, and let the user focus on the outcome. If you build in consumer finance today, that is probably one of the biggest shifts to understand. -- The podcasts are authored, edited and produced by Raph Grieco (⁠⁠⁠⁠⁠⁠⁠raphael-grieco.com⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠olivecapital.vc⁠⁠⁠⁠⁠⁠⁠).

    [Rails Report #1] What "invisible rails" actually means for a consumer finance app builder

Trailers

5
out of 5
4 Ratings

About

Runway Series, by Olive Capital (https://olivecapital.vc), explores since 2019 the same curiosity that has always shaped this show, the stuff changing underneath finance, product, and the way people build and finance tech innovation. The next generation of great consumer finance companies, the ones that could become the Revoluts of the next decade, are being built right now, during this shaky technological shift. We explore: invisible rails, the agentic economy, trustless privacy, and everyday money.