An approach built around decisions, not deliverables.
Engagements begin with a decision already in motion. The work rarely fits neatly inside a functional boundary, because the questions are too consequential to delegate and too cross-functional to assign to a single department.
- 01
Category strategy
Where the company is actually competing, what it is competing for, and what has to be true about the rest of the business for that position to hold. Most execution problems begin as positioning problems.
- Category framing & narrative
- Competitive position under stress
- Build / buy / partner choices
- 02
Operating models
How partnerships, product, sales, and customer success are wired together, and how decisions move between them. Strategy succeeds or fails in the operating model.
- Org design across functions
- Decision rights & accountability
- Cadence: planning, QBR, board
- 03
Partner ecosystems
An ecosystem is the cumulative result of a small set of decisions repeated for years: which partners to invest in, which integrations to deepen, which standards to adopt. Durable ecosystems are designed through repeated decisions, not accumulated by accident.
- Ecosystem thesis & whitespace
- ISV & platform program design
- Integration roadmap & sequencing
- 04
Commercial architecture
Pricing, packaging, partner economics, and incentive design treated as one system rather than four. When they drift, partner motions stall and direct sellers stop trusting the model. Aligning them is usually the unlock.
- Pricing & packaging review
- Partner economics & comp
- Co-sell incentives end-to-end
- 05
AI governance
Inside enterprise software, AI is less a feature question than a governance question — data rights, customer trust, internal accountability, and what the company will and will not ship. Companies that settle these questions early build different products and sell them differently.
- Data & customer-trust posture
- Internal review & accountability
- Partner & model-vendor strategy
- 06
Commercial Strategy
Commercial strategy brings pricing, go-to-market, partnerships, and operating decisions into a single system. Growth rarely stalls because people work too little. It stalls because the commercial model asks different parts of the business to optimize for different outcomes.
- Go-to-market architecture
- Revenue model & incentives
- Platform & alliance strategy
Every engagement begins with an executive decision that has become impossible to postpone.
Sometimes the question is strategic. Sometimes organizational. More often, it sits between functions where no single executive owns the answer.
The objective is not another presentation. It is a decision the business can defend and execute.
- What does an engagement actually look like?
- Engagements begin with a decision already in motion, usually one that sits between functions and cannot be cleanly delegated. The work is led personally and structured around the decision rather than a fixed deliverable list. Output is typically a short document, a working session with the leadership team, and a follow-on conversation a few weeks later.
- How long do most engagements run?
- Most mandates run six to twelve weeks. A small number continue as quiet, ongoing advisory once the initial decision has been made and execution is underway.
- Do you deliver implementation, or only strategy?
- The objective is a decision the business can defend and execute, not another presentation. Implementation stays with the operating team, but the engagement is designed so the path from decision to execution is explicit and owned inside the company.
- Which questions trigger an engagement?
- Category strategy resets, partner ecosystem rebuilds, operating model and decision-rights work, commercial architecture (pricing, packaging, partner economics), and AI governance inside enterprise software. The common thread is a question too consequential to delegate and too cross-functional to assign to a single department.