RUNWAY SERIES : Everyday Finance, Rewired.

Today for "Agent Dispatch #3":
--
Tax settlement is one of those parts of the economy that most people never think about, but every business feels it. It is usually slow, operationally heavy, and buried inside systems that were not designed for real-time movement. That is starting to change.
When B2B tax settlement becomes autonomous, the entire workflow shifts from manual coordination to embedded execution. Instead of teams chasing invoices, reconciling records, and waiting for periodic processing cycles, the system itself can calculate, validate, and settle obligations as transactions happen. That is a much bigger change than it sounds like.
Because tax is not just an accounting issue. It is part of how trust, compliance, and cash flow work inside businesses. If settlement becomes autonomous, then companies can reduce friction, lower operational overhead, and move faster without having to keep so much human effort tied up in repetitive back-office work.

--
The podcasts are authored, edited and produced by Raph Grieco (⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠raphael-grieco.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠olivecapital.vc⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠).

Today for "Agent Dispatch #2":
--
Portfolio management has always been about making sense of complexity. You take a large universe of assets, filter for relevance, monitor risk, and try to stay aligned with a goal. That process has traditionally required a lot of manual judgment, a lot of research, and a lot of ongoing maintenance. Agentic indexes change that structure.
At a basic level, an index is a way to group assets around a thesis, a strategy, or a rule set. But once you introduce agentic systems, the index stops being a static container and starts becoming something more dynamic. It can adapt, update, monitor, and even act on its own logic in response to new information. That is a significant shift.
Instead of treating portfolio construction as a one-time allocation decision, agentic indexes make it possible to think of the portfolio as a living system. One that can ingest signals, adjust exposure, rebalance according to constraints, and reflect a more continuous view of the market. This matters because most investors do not have the time, bandwidth, or infrastructure to track every relevant variable manually. In practice, they rely on summaries, dashboards, and periodic reviews.
Agentic indexes introduce a different model: one where intelligence is embedded directly into the structure of the portfolio itself. That can change several things at once. It can make thematic exposure more precise. It can reduce the lag between signal and action. It can help users express a thesis in a more automated and repeatable way. And it can make portfolio management feel less like a series of disconnected decisions and more like a governed process.
There is also an important behavioral angle here. People often struggle not because they lack conviction, but because they lack a mechanism that turns conviction into action. Agentic indexes can help bridge that gap.
--
[ More in the episode ]
--
The podcasts are authored, edited and produced by Raph Grieco (⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠raphael-grieco.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠olivecapital.vc⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠).

Today for "Everyday Money #3":
--
There is a quality that the best financial products have that is hard to name but easy to feel. You open the app, and it already seems to understand what you need. The information is in the right place. The action you want to take is one step away. Nothing feels out of order.
That quality is what I would call financial intuition in product design.
It is not about features. Most financial products have enough features. It is not about data either. Most apps show users plenty of numbers. Financial intuition is something more subtle. It is the ability of a product to anticipate behavior, reduce friction at the right moments, and present complexity in a way that feels manageable rather than overwhelming.
And it is genuinely difficult to build.
Part of the reason it is difficult is that financial behavior is deeply personal. Two users with identical incomes can have completely different relationships with money. One wants control and visibility. Another wants simplicity and automation. One checks their balance every day. Another wants the product to handle everything quietly in the background.
A product with financial intuition does not force all of those users into the same experience. It adapts, or at least it creates enough clarity that different users can find their own path without friction.
But there is a more fundamental layer underneath that.
Financial intuition in product design starts with a clear understanding of what the user is actually trying to resolve. Not just the transaction, but the anxiety, the decision, or the goal sitting behind it.
When someone transfers money, they are often managing a commitment. When someone checks their balance, they are often checking a feeling. When someone sets up a savings goal, they are often trying to translate an aspiration into something concrete. The best products understand that financial actions are rarely purely mechanical. They carry emotional weight.
Designing for that weight is what separates good financial products from genuinely trusted ones.
[More in the episode]
--
The podcasts are authored, edited and produced by Raph Grieco (⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠raphael-grieco.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠olivecapital.vc⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠).

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⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠).

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⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠).