The thinking behind the work

How I operate

Systems thinking, pattern recognition, and leadership, grounded in what a team can actually do.

How I operate

People first. A system that works for them.

Nine principles, three connected disciplines. Open any card for the thinking behind it.

People & Leadership

Small teams, enterprise impactHigh standards, high context, high care.

My sharpest work comes from teams that outproduce their headcount. I hire curious generalists, give them clear outcomes, and build the systems that let them move without waiting on a central function. 500+ people led. More than 200 have been promoted to new levels or started their own companies. Leaders eat last: the people closest to the work get context, support, and room to own the result.

Enterprise rigor below the strategyConnect the strategy to the operating discipline.

Full P&L, forecasting, deal desk, CPQ, and quote-to-cash ownership, plus acquisition integration and platform transformation. Operated repeatedly at PE-backed pace and presented directly to boards and sponsors on performance, risk, and the operating plan.

One system, any scaleGive people clear ownership at every scale.

The same architecture works for a lean team launching from zero and for tens of thousands of employees operating at $15B scale: clear ownership, shared instrumentation, operating cadence, and forecasting as a discipline. Scale does not change the design; it adds pods.

Markets & Growth

Orchestration over ownershipMatch supply and demand without erasing what makes either side valuable.

The recurring bet across every marketplace I have built: the orchestration layer that matches supply to demand is the durable asset. REEF, OYO, Booster, and Care Agent create value without forcing either side to surrender its identity. The layer creates the value; identity conversion slows how broadly it can spread.

Partner-led growth, instrumentedMake partner growth part of the revenue system.

Built and ran wholesale, indirect, direct-to-consumer, and capability partnerships across telecom, real estate, healthcare, and clean energy. Shared scorecards, joint forecasting, and deal economics make partner revenue predictable. The channel is part of the operating system, not a side motion bolted on afterward.

Third time through a platform shiftRecognize the pattern, then test what is different.

Career forged in wireless through the voice-to-data, device-to-platform, and one-time-to-recurring transition at $15B scale. The pattern replayed across marketplaces, SaaS, and clean energy. It is running again now in agentic AI infrastructure.

Systems & Execution

Run revenue like a productAlign the team around outcomes, not handoffs.

Federated pods, not a central queue. Each owns one outcome end to end, with a build face that ships the data, automation, agents, and mechanisms, and a run face embedded with the leaders who own the number. Shared instrumentation and fast feedback loops keep the system honest.

Engineering, not storytellingConnect the dots, then validate them with evidence.

Trained as an aeronautical engineer. Systems thinking, inputs and outputs, failure modes, control loops. Revenue is a system with engineerable inputs, not a narrative that needs better framing. MBA and Harvard executive education layered business fluency on top of engineering.

AI-native, deployed and governedUse AI to remove friction, with clear boundaries.

A six-layer architecture for AI-orchestrated GTM: data, intelligence, context, memory, orchestration, and execution, wrapped in observability, governance, and self-learning. Deployed live at $200M+ ARR healthtech. As Executive Chair of an AI Center of Excellence, I also run the tools, experimentation boundaries, and cost discipline behind adoption.

How I connect the dots

From market signal to a team that can act.

Systems thinking shows how the pieces relate. Pattern recognition suggests what might be changing. Data tests the hypothesis. GTM judgment turns it into a decision people can execute.

An interactive view of my operating approach, not a reconstruction of a single engagement. Choose a stage or read the full sequence.

01

Market signal

Keep a pulse on what is changing.

Look across market trends, customer conversations, partner feedback, and social sentiment. A repeated signal is a reason to investigate, not proof on its own.

02

Evidence

Pair the outside view with operating data.

Compare the signal with conversion, retention, customer behavior, and unit economics. Ask what would disprove the pattern before treating it as an opportunity.

03

Opportunity

Find the constraint worth solving.

Connect the market need to a specific point in the revenue system. Distinguish a demand problem from a conversion, value-delivery, or retention problem.

04

Team decision

Give the people closest to the work context.

Agree on the outcome, owner, tradeoffs, and evidence of success. Build shared understanding across marketing, sales, RevOps, enablement, and customer success.

05

Execution

Build the smallest useful operating change.

Combine process, data, and team capabilities. Apply AI where it takes busywork away, with human judgment and clear operating boundaries.

06

Result & learning

Measure the whole system, then adjust.

Watch downstream effects, not just one local metric. Keep what works, revise what does not, and turn the learning into the next decision.

See the documented Bow Tie transformation ↗