Open banking and data access
What 1033 actually requires, and what it costs to comply well rather than minimally. Consent, permissioning, API standards, and the gap between shipping an endpoint and running a data sharing program.
Advisory
I spent over four years at Akoya, where I owned product strategy and commercialization and helped grow the data access network from nothing to billions of requests per month and seven figures in revenue. Before that, five years in consulting with banks on open banking and digital transformation.
I take on a small amount of advisory work. If you're working on something here and want a second opinion, send me a note.
What 1033 actually requires, and what it costs to comply well rather than minimally. Consent, permissioning, API standards, and the gap between shipping an endpoint and running a data sharing program.
Account tokenization, account verification, and pay by bank. I owned a tokenization product and spent a few years on the industry side of it (FDX, Nacha), so I know the build and the politics of getting a scheme adopted.
Businesses that only work if both sides show up: institutions on one side, fintechs on the other. Participant incentives, governance, standards, and the chicken and egg problem of the first two years.
Pricing and packaging, roadmap and prioritization. Also the product function itself: hiring product managers, growing them, and putting a discovery process in place that people actually follow.
Most of my work has been with banks, credit unions, fintechs, and data aggregators.
A readiness review, a strategy, a market assessment. Scoped up front, with something concrete at the end.
Regular calls, a second read on work in progress, and questions as they come up. Useful when the problem is continuous rather than a one off.
A longer horizon and a lighter touch, usually with a founding team.
Email is the fastest way to reach me. A sentence or two about what you are working on is plenty to start.
Start a conversation