About

15 years changing how organizations operate.

Every phase of my career has been about the same thing — redesigning how organizations work. AI-native transformation is where that work leads now.

10+Years product management
10+Years delivery & operations
6+Years engineering & architecture
2+Years building with AI
Dan Genduso

The through-line across every engagement has been the same: capabilities. Not tools, not software, not processes in isolation — but the full system that enables an organization to do something it couldn't do before, or do it better. That means people, process, policy, and technology designed together as one thing.

I've built capabilities from scratch, consolidated hundreds of fragmented versions of the same capability across global organizations, and designed the operating model that builds and improves all capabilities continuously. Each phase stacked on the last. None of them went away. That accumulation is what I bring into a room.

Based in

San Francisco, CA

Currently

Available for contract or hire

Building

DiverseCiti and APOLLO1

How I engage

Embedded in your organization, designing and building AI-native capabilities using a structured five-phase process from discovery through delivery

How I got here

My journey.

Each phase added a new layer. None of them went away.

2023 — Present

AI Builder

Building AI-native products and the operating system for building AI-native capabilities as products. APOLLO1 has evolved into the platform through which AI-native capabilities are designed, delivered, and operated. Applying everything from the previous phases — capability design, product engineering, operating model thinking — with AI as the new foundational layer. Also applying this directly to client organizations as a Fractional CAIO.

What I learned

The bottleneck is no longer capability or headcount. It is clarity. With AI, the limiting factor is how well you understand the problem — not how many people you have to work on it. One person with agents and the right depth can lead transformation at a scale that previously required a large team.

2021 — 2023

System Builder

Moved from building individual capabilities to designing the operating model that builds all capabilities continuously — the system that defines how an organization learns, decides, builds, and improves. Designed and implemented product operating models across a global organization, connecting customer learning to capability delivery across functions. This was the shift from building one thing well to designing the system that builds everything well.

What I learned

The organizational operating model is itself a product — and most organizations inherited theirs without ever designing it intentionally. When you treat it as something to be built and continuously improved, the organization's ability to deliver compounds over time.

2018 — 2021

Product Builder

Learned to code. Shifted from building capabilities inside organizations to building my own products end-to-end — architecture, engineering, deployment. Started APOLLO1. Closed the gap between knowing what to build and being able to build it myself. This phase was about becoming a complete builder: someone who could own the full technical stack, not just the strategy and design.

What I learned

Understanding how something gets built fundamentally changes how you think about what to build. The best product decisions come from people who can see both sides of that line. Start simple, ship, learn, and improve — the loop matters more than the plan.

2012 — 2018

Capability Builder

Grew from contributing to capabilities to owning them end to end. Started with the technical builds — designing and delivering the product and technology dimension of CRM and marketing operations capabilities. Then expanded to own the full capability across all four dimensions: the process design, the policy and governance, the people and change strategy, and the technology. Running the full 5 Ds — Discover, Diagnose, Define, Design, Deliver — to redesign capabilities from the ground up rather than just improving what existed.

What I learned

A capability is not a tool, a role, or a process in isolation. It is a system built across all four dimensions — people, process, policy, and technology — and change only sticks when all four move together. You can't fix the technology without fixing the process. You can't fix the process without addressing the governance and the people around it.

2010 — 2012

Capability Specialist

Started in CRM and marketing operations — specialized capability domains that required working across people, process, and technology simultaneously. The work included process design, technical implementation, program management, and change management and readiness on the people side. Not yet owning capabilities end to end, but learning what it took to make change stick inside complex organizations through the full arc of a capability build.

What I learned

Organizations resist change not because people are opposed to improvement but because change that touches only one dimension — just the technology, just the process — doesn't hold. The work that sticks is the work that accounts for how people actually experience the change.