Built & sold two companies. Led four transformations. 35 years at the intersection of technology and business value. Board director. Writing at https://xitter.cf/t.co/FSi15YxDGW
Joined May 2024
- Tweets4.6K
- Following69
- Followers3K
- Likes2.3K
Pinned Tweet
I’m exploring my next executive leadership opportunity.
I’ve spent my career building, scaling, and transforming technology businesses, with experience across technology services, enterprise platforms, fintech, consulting, and blockchain.
I’m looking for the right CEO, COO, President, or senior operating role where I can help a company accelerate growth, improve execution, and create enterprise value.
A little more about me in the video below.
If you know a company that could use this kind of leadership, I’d welcome an introduction.
Growth that burns your margin isn't a strategy. It's a subsidy.
We ran four straight years of 50%+ growth with 15%+ EBITDA. Profit didn't slow growth down. It paid for it.
Grow first and fix margins later, or be profitable from day one?
AI doesn’t remove the need for senior judgment. It concentrates it.
Two or three people who can audit output, own architecture, and make the hard calls now outproduce what used to take a larger team. The leverage is real.
The failure mode is pretending the judgment part is optional once the code is generated. It isn’t. Smaller teams only work when the remaining humans are higher-bar.
Your company shouldn’t collapse if one person quits.
AI lets solopreneurs run development, accounting, marketing, sales, and support. Real leverage.
Most still aren’t built to scale. You need subject-matter experts who can direct the AI and make judgment calls. A smaller team works. Zero team usually doesn’t—once you’re past shipping the idea.
When everything runs through one person + AI, you’re one resignation away from major disruption.
Lean is smart. 100% reliance on one person is a risk most people aren’t pricing in.
Wesley Crook retweeted
AI is compressing software engineering teams everywhere. Five engineers used to be the norm — now two or three ship the same output. But the people winning aren't the best prompt writers. They're the ones who can audit AI code, catch what it misses, and own the architecture end to end. Smaller teams. Higher bar. The leverage is real. The judgment is still human.
wescrook.com
AI is compressing software engineering teams everywhere. Five engineers used to be the norm — now two or three ship the same output. But the people winning aren't the best prompt writers. They're the ones who can audit AI code, catch what it misses, and own the architecture end to end. Smaller teams. Higher bar. The leverage is real. The judgment is still human.
wescrook.com
Wesley Crook retweeted
I’m exploring my next executive leadership opportunity.
I’ve spent my career building, scaling, and transforming technology businesses, with experience across technology services, enterprise platforms, fintech, consulting, and blockchain.
I’m looking for the right CEO, COO, President, or senior operating role where I can help a company accelerate growth, improve execution, and create enterprise value.
A little more about me in the video below.
If you know a company that could use this kind of leadership, I’d welcome an introduction.
I've sold two companies. The first one surprised me. The second one didn't.
The difference wasn't luck or timing. It was understanding that if the clients call you, the team can't decide without you, and the process lives in your head - an acquirer isn't buying a business. They're buying a job. And they'll price it that way.
Link 🧵 👇
This is where tokenization starts becoming more than just an asset story.
Cross-border settlement has always been slowed down by coordination across institutions, currencies, and jurisdictions. Atomic settlement changes that equation by reducing counterparty risk and removing a lot of the operational friction in between.
What stands out here is the focus on interoperability and predictable execution across multiple participants.
As more financial infrastructure moves on-chain, systems that can coordinate reliably at scale become increasingly important.
Good read from The Block:
theblock.co/post/402846/bis-…
As systems get more complex any design flaws they have tend to become magnified.
Great points by Aaron in this clip.
A pattern Aaron Contorer talked about recently:
teams move quickly to capture market demand, prove traction, and get products into users’ hands.
Then the system grows more complex underneath than anyone originally expected.
Engineering teams feel maxed out.
Business teams feel like delivery keeps slipping.
The gap between what was promised and what the system can realistically support starts getting wider.
As more products move into production environments, that tension is becoming increasingly common across the industry.
Canton is focused on a part of the market that’s becoming increasingly important: systems that can coordinate securely and reliably across multiple participants.
That becomes a very different engineering problem than simply launching an application.
Excited for us to be joining the @CantonFdn
FP Block has joined the @CantonFdn.
Canton is focused on enabling secure, interoperable infrastructure for multi-party systems, especially in environments where privacy, coordination, and consistency are critical.
That aligns closely with the kind of systems we spend our time building.
As more workflows move on-chain, the challenge becomes less about launching products and more about making them operate reliably across participants and environments.
Consensus made one thing very clear:
The conversation is shifting from speculation to infrastructure, reliability, and systems that can actually operate at scale.
A real pleasure to have @real_digidavid on our panel during our side-event at @consensus2026
If you don't know about @gosodax yet they're worth checking out
One of the challenges with multichain applications is that liquidity is fragmented across networks.
At our @Consensus2026 side-event, @real_digidavid from @gosodax broke down how that gets handled at the infrastructure layer so applications can stay focused on what they’re actually building.
Instead of managing complexity across chains, the system routes across 18 networks to access liquidity and execute trades.
A good example of where abstraction starts to matter as systems scale.
Most teams don’t want to rebuild core infrastructure over and over.
They want something they can trust, integrate with, and build on top of long term.
We’ve seen what happens when teams chase chains and have to rebuild when things change.
That’s a big part of why we built Kolme.
Great interview with @DogecoinZack from @GenzioCo at @consensus2026
Well worth a listen if you're building something that you need to get production ready.
During @consensus2026, @DogeCoinZack caught up with @WesCrook
A lot of the discussion touched on where things are actually heading as systems move beyond early traction and into environments where consistency, coordination, and long-term reliability start to matter more.
That shift is showing up across the industry right now, especially as more teams focus on building systems that can operate at scale, not just get to market.
Enterprise adoption comes down to one thing: predictability.
Knowing what’s on your chain, who’s interacting with it, and how it behaves under real conditions.
That’s still a gap across most ecosystems today.
It’s also one of the reasons we built Kolme. Systems need to be understandable, controllable, and reliable before enterprises fully commit.
Curious to learn what other teams are seeing as Institutions and Enterprise starts to enter the space more.
The industry is entering a phase where reliability is becoming a much bigger part of the conversation, especially as Enterprise makes its entry.
More teams are thinking about:
▶️ consistency under real usage
▶️ coordination across systems
▶️ operational scale
▶️ long-term maintainability
What challenges is your team running into most as systems mature?
