A New Phase Begins

I've spent years building tech startups and, at various points, pitching them to banks. Now I'm on the other side of that table, working as CTO of a community bank. The view is different from here, and I want to share what I'm learning along the way.

The curiosity that brought me here goes back to 2008. Cell phones were everywhere but smartphones were still new. Texting had become the universal way to communicate, but sending money was still surprisingly hard. I remember trying to split a bill with friends, the usual chaos of cash and IOUs, when a text message came through. The contrast hit me. Why was texting so easy and sending money so difficult?

That question led to XipWire, a platform I built to let people send money via text message. The vision was to partner with banks and offer the service to their clients. I spent months pitching the idea, sitting in conference rooms trying to convince bankers that mobile payments were the future. They looked at me like I had three heads.

The rejection stuck with me, but not in the way you might think. I wasn't bitter about the banks saying no. I was curious about why they said no. What were they seeing that I wasn't? What structural issues, regulatory constraints, or technical limitations made them hesitate? From my side of the table I saw resistance. I wanted to understand what the conversation looked like from theirs.

A few years and a couple of other companies later, the opportunity to actually find out came up, the chance to take on a community bank's technology and data challenges directly. That was a compelling combination because it was exactly the kind of problem I'd been working on from the outside for years. Now I get to work on it from the inside.

What I Expect to Find

Community banks have a reputation for legacy technology, and that reputation has a basis. Decades of vendor decisions, regulatory shifts, and growth tend to produce data spread across systems that were built independently, at different times, by different vendors, for different purposes. Plenty of data exists. The challenge is that it sits in places that were never designed to work together.

That kind of fragmentation is not new to me. It is the standard pattern at any institution that has been around long enough to accumulate systems. What is new is the regulatory context that shapes every technology decision. Banking is its own world, with its own language, and a lot of history I am going to spend time learning.

The Thread I Want to Pull

The opportunity I am most interested in is what becomes possible when the data finally comes together in one place. Better client experience, faster credit decisions, sharper fraud detection, more thoughtful operational choices. The patterns that data unlocks are familiar from other industries. The question is how those patterns translate inside a regulated business where pace, governance, and trust matter more than they do in a typical tech context.

I don't have the answers yet. I am going to write about what I learn along the way. The economics of how banks actually make money. The regulatory environment that shapes every decision. The technology that runs under the hood. The data work that I think can change what a community bank is capable of when done well.

If you are in tech and curious about banking, or a banker wondering what an outsider sees, I hope you find something useful here. The connecting thread is the belief that data and automation, applied carefully and in collaboration with regulators, can make community banking work better for clients and for the people who serve them.