Hello Medium, I’m the Guy Who Built the Stuff You Never See

Let me start with a confession: I’ve spent 27 years in enterprise technology, and almost nothing I built has my name on it.

That’s not a complaint. It’s the nature of the work. I build the systems behind the systems, the invisible infrastructure that keeps real products running at global scale. When your connected car quietly downloads an update overnight, or a telemetry platform decides your vehicle needs attention before you do, somewhere in that chain is the kind of plumbing I’ve spent my career obsessing over. Nobody claps for plumbing. But when it breaks, everybody notices.

So this is my first post on Medium, and I figured the polite thing to do is introduce myself before I start having opinions in public.

The short version of a long story

I spent 13+ years at Ford Motor Company, eventually as a Senior Director, working on some of the most complex mobility platforms on the planet. Software-defined vehicles, where I led global product teams across 24 large-scale initiatives. Connected ecosystems powering 18 million+ vehicles. Autonomous systems. Marketplaces, telemetry, cloud-native architectures, the whole buffet.

Some numbers from that chapter, because engineers love receipts: we accelerated feature delivery by 30%, cut system latency by 85%, and I helped secure $150M+ to build next-generation software-defined vehicle platforms. Along the way I picked up 18 U.S. patents in distributed systems and connectivity.

Here’s what those numbers don’t tell you: how many times I watched brilliant technology die in a conference room.

Not because it didn’t work. Because it didn’t fit. The demo dazzled, the pilot impressed, and then it hit the messy reality of legacy systems, skeptical teams, and workflows that had calcified over decades. I learned, sometimes painfully, that building the system is the easy half. Making it real, usable, and actually adopted is where careers go to be humbled.

That lesson changed my trajectory. I went back to school for an Executive MBA at Ross (University of Michigan) to learn to think in markets and strategy, not just architectures. I took a CTO role and got a crash course in operating with ambiguity, speed, and a budget that always felt one meeting away from disappearing. I wrote a book, Empowering Enterprises with Generative AI, mostly because I kept having the same conversation with executive after executive and figured I should just write it down.

And then, in late 2025, I did the thing my Ford-trained risk instincts screamed against. I left a comfortable seat to start a company.

What I’m building now

The company is 2nd Brain Labs, and it exists because of one belief I can’t shake:

The future won’t belong to whoever has the most data. It will belong to whoever can activate it most intelligently in their enterprise.

Every enterprise I’ve ever worked with is sitting on decades of accumulated knowledge. Codebases, APIs, documentation, workflows, tribal wisdom trapped in the heads of engineers who are three years from retirement. Then generative AI showed up, and everyone rushed to bolt a chatbot onto the front door while the actual intelligence of the company stayed locked in the basement.

Our flagship product is Synapse, an Enterprise Context Engine. In plain English: Synapse makes your enterprise systems legible to AI. It takes your existing codebases and APIs, the ones written before “prompt” was a noun anyone said out loud, and makes them AI-ready through the Model Context Protocol (MCP) so your team can focus their energy on building agents to solve real business problems and not worry about mundane task of understanding how legacy codebases and APIs expose their knowledge. And it does this in minutes, not the multi-year “digital transformation” death march everyone has learned to dread.

Think of it like hiring a translator for a brilliant employee who only speaks a language nobody else in the building understands. The knowledge was always there. Now the rest of the company, and its AI, can finally talk to it.

We’re already working with Fortune 500 companies in automotive and healthcare, and we’ve built an engineering team in Hyderabad, India that I’m unreasonably proud of. The commute between Michigan and Hyderabad is brutal. The energy on the other end makes it worth it.

Here’s the thing I believe most strongly, the hill I’ll write many future posts on: AI isn’t a feature. It isn’t a layer you sprinkle on top of the org chart like parmesan. Done right, it becomes a second brain for the enterprise, one that changes how value gets created in the first place. The companies that win won’t be the ones with the flashiest demos. They’ll be the ones that integrate deepest.

Why I’m here, and what I’m asking

I’ve read Medium for years. I’ve just never contributed, which makes me the guy who shows up to the potluck empty-handed and eats everything. Time to fix that.

My plan is to write about what I’m actually living: the unglamorous middle of enterprise AI adoption, lessons from two decades of large-scale systems, and the honest, occasionally embarrassing experience of going from corporate executive to first-time founder in my late 40s. Spoiler: the founder learning curve does not care about your patents.

But I’m new here, and I know it. So to the veterans of this platform, I’d genuinely love your guidance:

• What do you wish someone had told you before your first ten posts?
• What makes you actually follow a writer here, versus read once and move on?
• And what mistakes should a recovering corporate executive watch out for? (Besides opening with a slide deck. I’ve been warned.)

Drop a comment, or just say hello. I’ll respond to every one.

If you’re building the future of your organization, investing in it, or simply curious about what happens when AI meets 30-year-old enterprise systems, stick around. I promise stories from the trenches, not theory from the balcony.

Thanks for reading. See you in the next one.