I've sat in rooms full of sharp, experienced leaders generating enormous activity — refining requirements, commissioning analysis, building roadmaps — while something essential went unspoken.
Direction was implied. Tradeoffs were softened. And motion started masquerading as progress.
I work with fintech founders and executive teams navigating regulatory pressure, platform complexity, and AI acceleration — bringing structure to environments where confusion compounds cost.
In high-stakes product environments, complexity creates a specific kind of drift. Stakeholders multiply. Constraints layer. AI accelerates what teams can build. Detail expands in every direction.
But without a clearly defined aim, signal gets buried in noise. Organizations respond by producing more — more analysis, more alignment meetings, more roadmap iterations — without confronting the core tension: nobody has articulated what they're actually building toward.
Most strategic inertia isn't caused by external constraints. It's caused by avoided decisions — the accumulated weight of tradeoffs no one was willing to name.
I've watched this pattern consume years inside institutions. An initiative that clearly lacked a coherent product vision ran for twelve months — expanding requirements, generating analysis, producing motion — until a senior leader finally asked the simplest question: "Why would we build this if we don't have a vision for what it plugs into?" The work was deprioritized in a week.
The data to make that call existed on month one. What was missing wasn't information. It was willingness to decide.
I've built more with AI tools in one quarter than was possible in years. That's not a talking point — I built a complex vertical SaaS platform in 48 hours over a holiday break, and I run a multi-agent system on two Mac Minis that handles real operational work daily.
When execution becomes cheap, unclear thinking gets expensive fast. I learned this firsthand: in my first agentic build, I omitted authentication. The agents didn't fail — they did exactly what I told them to do. The failure was ambiguity in my intent. That structural gap cascaded through the entire system.
AI is compressing timelines. Code is cheaper. Prototypes are instant. But the ability to decide — to articulate aim, accept tradeoffs, and commit under incomplete information — is not accelerating at the same rate. More data doesn't automatically produce better judgment. In many organizations, additional analysis becomes a substitute for courage.
When building is easy, knowing what to build matters more than ever.
Early-stage startups. Fortune 100 institutions. Scrappy founding teams and complex enterprise machines. The failure modes are different. The clarity problems are the same.
Architected cross-border payment capabilities, unlocking $3M in new commercial revenue in year one.
Led product strategy for commercial card platforms at a top-4 U.S. bank — mobile wallet, receipt capture, card management.
Designed rules infrastructure enabling configurable business logic at scale — architecture that became a platform capability.
Navigated regional regulatory requirements during technology platform migrations across multiple international markets.
Took a functional MVP and helped transform it into a world-class financing platform unlike anything else in the market.
Built and operate a multi-agent AI system handling real workflows: communications, operations, podcast production, monitoring.
Decisive alignment, built to last.
4–6 weeks. Structured. End-state driven. The discipline is design thinking applied at the executive level: start with the end, back into current reality, define what must be true, then build the system that sustains decisive leadership.
You don't get advice. You get a decision-grade artifact your team can operate from after I'm gone.
What are we actually aiming at? What changes for the user? For the business? What becomes true if we succeed? No features. No roadmap. Just the target.
Where are we actually? What constraints are real versus assumed? Where is analysis masking uncertainty? Where is inertia compounding? Diagnosis without ego.
If the end state is X, what capabilities must exist? What tradeoffs must be accepted? What risk posture? What incentives must change? Alignment forms — or fractures — here.
A clearly articulated aim. Explicit tradeoffs. Prioritization logic. A roadmap anchored to outcomes. A leadership narrative. A reusable decision framework that survives after I'm gone.
I also work with teams through executive intensives (1–2 day workshops for urgent alignment needs) and selective ongoing advisory for teams that want continued strategic partnership.
Credibility comes from building. Here's what I'm actively working on.
A coworking space on South Boulevard in Charlotte. Home to builders, founders, and the local AI community. Where OpenClaw Community Night drew 120+ people to watch five builders demo live agent systems.
A self-hosted multi-agent system running on two Mac Minis at Tabbris. Alfred — the primary agent — handles communications, monitors channels, manages operations, and runs podcast production pipelines. Real infrastructure, not a demo.
A podcast about what's actually working with AI, what's not, and what happens next. The good, the bad, the ugly of building with these tools. No polish. That's the point.
Organizing events for people building real AI systems in Charlotte. Not theory — demos, workflows, use cases. Builders experimenting in public, learning by doing.
On systems, leadership, AI, and the human work underneath all of it.
Once execution stopped being the constraint, the real bottleneck came into focus. On ambiguity as the most dangerous thing in the system.
A 48-hour build of a vertical SaaS platform. Not a concept deck — a functioning system with real data models, real workflows, and real lessons about intent.
Entrepreneurs are 50% more likely to report mental health conditions. On killing "fake it till you make it," building identity outside work, and vulnerability as a muscle.
On nonlinear paths, entrepreneurial roller coasters, and 3,796 days clean from an eight-year opioid addiction. The journey was far from linear — and I wouldn't change any of it.
Leadership isn't about standing in the spotlight. On what rugby, humility, and failing your team teaches you about leading.
I was supposed to go to law school. I ended up bartending with a startup founder instead and never looked back. Since then I've been fired for being disruptive to the status quo. I've worked for sweat equity with no salary. I pitched to take over a company from its own founder. I started an impact investing tech company that got tremendous feedback from users and failed to raise money in a risk-averse city.
I also spent nearly eight years on a carousel of opioid addiction after a devastating rugby injury in college. I had a seizure in the office. That was the moment I realized something had to change. It's been 3,796 days since I last took an opioid painkiller. I'll hit 4,000 days sober on October 13, 2026 — my ninth wedding anniversary.
Recovery taught me more about systems than any business book. Addiction is, at its core, an incentive design problem — where short-term signals overwhelm long-term aims. Getting clean required the same discipline I now bring to organizations: name the real problem, stop rationalizing drift, and commit to a direction even when the data is incomplete.
I've watched teams spend years building without asking what they were building toward. I've done the same thing in my own life. The cost is the same in both cases — time you don't get back, spent on motion that felt productive but wasn't anchored to anything real.
The leaders I work best with share something in common: they're willing to confront uncomfortable truths about their organizations, their incentives, and sometimes about themselves. That's not weakness. That's where alignment actually begins.
If you already feel the noise and sense the inertia, the question is whether you're ready to interrupt it.