Inside the problem. Not above it.
Stephen Diesel
I've built inside early-stage companies and fund-backed organizations where the operating and product function either didn't exist yet or had never been deliberately designed. Regulated financial infrastructure, blockchain ecosystems, institutional platforms. The context varies. The work is the same.
The work I do sits across technical systems, organizational structure, and how people actually work together under pressure. Most operators specialize in one. The problems that stall early-stage companies usually span all three. So does the fix.
This work is underserved.
Most companies either outsource the decisions entirely or add headcount and hope.
Neither transforms how the organization actually works.
I do this work because I've seen what capable teams look like when the structure finally matches what they're able to do.
Prior Work
Vaulta Foundation was built as a funding arm for an open-source blockchain ecosystem. Then came a pivotal decision: become a product development organization. Take direct ownership of the protocol. Build rather than fund.
The decision was clear. What came with it was not. Everyone knew the direction had changed. Nobody knew how to move in it. Meetings multiplied. Decisions stalled. The gap between ambition and execution was widening every week.
I came in as the first product function. No delivery model, no decision framework, no way to sequence what the organization needed to build. I built all of that while the org was already in motion. By the time the engagement closed, they could execute on what they'd decided to do. They couldn't before.
Jenius Bank was being built by people who were genuinely excellent at traditional banking and had never built a net-new digital product before. That distinction matters more than it sounds. Traditional banking optimizes existing products. Zero-to-one requires something structurally different: a process for figuring out what to build, a tolerance for ambiguity before information is complete, a way of making decisions the organization hadn't been built to make.
I came in early and worked across the actual product: deposits onboarding, financial wellness, platform architecture decisions. But the harder work was navigating between teams that had never built together before. Product, fraud, risk, compliance. Each operating with their own priorities and no shared process for making decisions across them.
I shaped the function before execution began: the discovery model, how stakeholders navigated decisions together, the hiring architecture as the team scaled. The measure of the engagement was whether they needed me at the end. They didn't.
Ozmo had built a real business on mobile device support. Their research process had also been built for a world that no longer described their market. Business phones and smart devices require a different approach. Physical properties matter, and the information you need is rarely captured directly. But the more fundamental problem was organizational: the people who understood those devices best, the CSRs servicing them daily, had no input into how the product got built.
The fix wasn't a new process. It was redesigning who had access to what decisions. Direct CSR interviews, structured data aggregation, documentation that captured what a call log couldn't. The operating model changed before the product did.
The result opened a new business line with Verizon, their largest enterprise client. The patterns that win one market are often the ones that miss the next. Fixing that is an operating design problem.