Latest / Startup Stories with Fexingo: Conversations About Founders, Funding, and Building Companies from Zero / How Plaid Built the Financial Data Rails of the Internet
Transcript
- Lucas: In early 2013, two software engineers in New York were trying to build a personal finance app called Tally. They wanted it to automatically pull in a user's bank transactions and balances so you could see your whole financial life in one place. And they hit a wall almost immediately. Luna: The bank data problem. I've heard this story before, but it's worth repeating because it's so absurd in hindsight. Lucas: Right. To connect to a bank, you needed a data feed — and those feeds were exclusively sold to large institutions like Intuit or Yodlee. Even if you got access, each bank had its own proprietary format, its own security protocols. The whole system was built for the 1990s. So Zach Perret and William Hockey — the co-founders — realised the app they were building was never going to work unless someone fixed the underlying pipes. Luna: So they pivoted from building the consumer product to building the infrastructure. That's the classic 'pick and shovel' play in fintech. Lucas: Exactly. They renamed the company Plaid, joined Y Combinator in the summer of 2013, and started building what they called 'the Plaid API' — a single integration point that any developer could use to connect to hundreds of financial institutions. The early days were incredibly manual. They literally screen-scraped bank websites, reverse-engineering the HTML so their system could log in and pull data. It was fragile, but it worked. Luna: Screen-scraping has this reputation as a hack, but for years it was the only way to get real-time data from banks that refused to open APIs. It's ugly, but it solved the problem. Lucas: And it got them their first customers. By 2014, Plaid had signed on about a dozen fintech startups. The big break came when Venmo — already exploding in popularity — decided to use Plaid as its primary bank-connection layer. That single partnership gave Plaid massive credibility. If Venmo trusts you with its users' bank credentials, you're probably legitimate. Luna: That's the network effect of developer adoption. Once a few key players like Venmo and Coinbase and Robinhood use Plaid, every other fintech startup feels like they have to use it too. It becomes the default. Lucas: And that's exactly what happened. By 2018, Plaid was connected to over 11,000 financial institutions and powering apps used by roughly one in five Americans with a bank account. The company raised money at a $2.65 billion valuation that year. And then in early 2020, Visa announced it would acquire Plaid for $5.3 billion — a massive exit for a seven-year-old startup. Luna: And then the Department of Justice sued to block the acquisition on antitrust grounds, arguing that Plaid was a potential competitor to Visa's own debit card network. The deal collapsed in early 2021. Lucas: It was a gut punch for the company. They had been preparing for life inside Visa for almost a year. Suddenly they were independent again, facing a regulatory environment that was now openly skeptical of big tech and fintech consolidation. But here's the thing — Plaid didn't just survive. It used that moment to refocus. Luna: I remember reading that after the deal fell apart, they raised a new round at a $13.4 billion valuation from investors including Altimeter Capital and Silver Lake. That's higher than the Visa acquisition price. Lucas: Right. The market effectively said, 'You're worth more on your own than Visa was willing to pay.' And since then, Plaid has been quietly expanding beyond just bank connections. They launched Plaid Exchange, which lets banks build their own APIs using Plaid's technology. They acquired Quovo, a data analytics platform for investment accounts. They're now moving into income verification, identity verification, even anti-fraud tools. The thesis is that financial data is the new oil, and Plaid wants to be the refinery. Luna: But that expansion also brings more regulatory scrutiny. The CFPB has been looking at how consumer financial data is shared and used. Plaid is right in the middle of that conversation. Lucas: Absolutely. In 2023, the CFPB proposed a rule under Section 1033 of the Dodd-Frank Act that would require banks to make consumer data accessible via standardized APIs — basically mandating the open banking model that Plaid has been pushing for. It's a double-edged sword. On one hand, it validates Plaid's entire premise. On the other, it could open the door to more competition if banks start building their own compliant APIs. Luna: It's fascinating to watch a company that started by scraping bank websites now be seen as the mature, responsible steward of financial data infrastructure. They've gone from scrappy startup to quasi-public utility in just over a decade. Lucas: And I think that's the real lesson of Plaid's story. It's not just about the technology or the timing — though both were crucial. It's about identifying a foundational problem that everyone else was ignoring because it was too hard and too ugly to solve. Zach and William didn't set out to build a multibillion-dollar company. They set out to make their own failed app work, and in doing so, they accidentally built the rails that the entire fintech ecosystem now runs on. Luna: If these conversations have moved your work forward in some small way — maybe helped you think differently about a problem you're facing, or just given you a good story to tell — that's exactly why we make them. We deliberately don't run ads on these shows. If you want to support that choice, the link is buy me a coffee dot com slash fexingo. Lucas: Yeah, and that support genuinely makes a difference. It means we can keep spending time on deep dives like this one without worrying about sponsors. So if you've gotten value from the show, that's the place to go. Luna: Alright, back to Plaid. One thing I've always wondered — how did they convince the first banks to work with them? Banks are notoriously slow and security-conscious. Lucas: They didn't, at first. The early strategy was to bypass banks entirely and work directly with consumers. Plaid's technology would log in to a bank's online portal using the user's credentials, just like the user would. That's the screen-scraping model. Banks hated it, but they couldn't stop it without blocking their own customers. Luna: So it was a kind of constructive friction. Force the banks to deal with the reality that consumers wanted to share their data, and then offer them a better solution. Lucas: Exactly. Over time, Plaid started building direct API integrations with major banks like JPMorgan Chase and Wells Fargo. Those deals gave Plaid official, sanctioned access — but they also came with strict data-sharing agreements and security audits. It was a gradual process of moving from adversarial to collaborative. Luna: That shift from 'we're scraping your website' to 'we're your trusted partner' is one of the hardest transitions in business. Most companies never make it. Lucas: And Plaid made it in part because they were willing to invest in compliance and security early. They hired former regulators, built a robust privacy team, and published transparency reports. They understood that if they wanted to be the infrastructure for finance, they had to be boring and trustworthy. Luna: Let's talk about the developer experience angle. Plaid is often praised for having great documentation and SDKs. How important was that to their growth? Lucas: Hugely important. In the early days, the technical founders themselves were the customer support team. They would hop on GitHub issues, answer questions on Stack Overflow, and make sure any developer who tried Plaid had a smooth experience. That created a loyal community of advocates who recommended Plaid to other developers. It's the same playbook that Stripe and Twilio used. Luna: It's almost a cliche now — 'build for developers first' — but Plaid is a textbook case of it working. They turned a commodity into a differentiator through sheer execution. Lucas: And that execution is still playing out. Today, Plaid has over 8,000 fintech customers, from startups to public companies like SoFi and Betterment. They process connections for more than 200 million consumer accounts. And they're expanding into Europe and the UK, where open banking regulations are even more advanced. Luna: So what's the next frontier? Where does Plaid go from here? Lucas: I think the big push is into what they call 'financial access' — using data to help people qualify for loans, get paid faster, or prove their income to a landlord. They already have a product called Plaid Income that lets consumers share their payroll data with lenders. And they're experimenting with credit underwriting models that use transaction history instead of traditional credit scores. If they can make that work, they could fundamentally change how credit is distributed. Luna: That's a massive opportunity, but it also puts them in direct competition with the credit bureaus — Equifax, Experian, TransUnion. Those are entrenched, regulated incumbents with a lot of lobbying power. Lucas: Exactly. And Plaid has already faced pushback from big banks who don't want to lose control of customer data. So the next chapter of Plaid's story is going to be as much about politics and regulation as it is about technology. But if the past decade is any guide, they'll find a way to make it work. Luna: It's one of those rare startup stories where the company's success is almost invisible to end users, yet it touches nearly every financial app they use. That's the mark of true infrastructure. Lucas: Yeah, and in many ways, that's the highest compliment you can pay a company. When the infrastructure works perfectly, no one thinks about it. You just open your app and see your balance. And that's what Plaid has spent the last thirteen years making possible.