Start with an outcome, not a staffing package.

Best when

• A promising idea with unresolved scope
• A product decision crossing business, experience, and technology
• A team preparing for an MVP or larger investment

Focus

Reduce the most consequential uncertainty before committing to a build plan.

Working shape

A collaborative sequence of context review, stakeholder working sessions, user and workflow framing, assumption mapping, and solution exploration. Exact duration and participation depend on the decision in scope.

Typical outputs

• Opportunity and constraint framing
• Assumption and evidence map
• Critical value path
• Prototype or technical spike plan where useful
• Recommended decision sequence

Best when

• Founders who need an experienced product counterpart
• Growing teams formalizing product discovery and prioritization
• Businesses aligning product, commercial, and technical decisions

Focus

Turn product judgment into a repeatable system of choices, evidence, and accountable follow-through.

Working shape

A focused leadership cadence covering product thesis, discovery, prioritization, roadmap direction, metrics, team coaching, and the decisions that need senior product ownership.

Typical outputs

• Product thesis and strategic choice set
• Opportunity and prioritization framework
• Outcome-led roadmap direction
• Product metrics and review cadence
• Product team coaching and leadership support

Best when

• Founders testing a product thesis
• Teams turning a manual service into a product
• Businesses seeking evidence before a broader roadmap

Focus

Create an observable product release around the next important business and product decision.

Working shape

A staged engagement spanning definition, prototype, production engineering, and release preparation. Scope is bounded by the evidence the product needs to create, not by a standard feature package.

Typical outputs

• MVP decision and scope brief
• Experience prototype
• Architecture and delivery plan
• Production implementation
• Instrumentation and post-release review plan

Best when

• Teams needing sustained product, design, and engineering capacity
• A product area with an evolving roadmap
• Organizations that want one connected external delivery unit

Focus

Maintain product coherence and delivery momentum across a continuing stream of decisions.

Working shape

A stable core team with agreed ownership, planning cadence, quality signals, and interfaces to internal stakeholders. Composition adjusts to the product area and existing team capability.

Typical outputs

• Product and technical leadership
• Experience design
• Software engineering
• Quality and release practices
• Visible decision and delivery cadence

Best when

• A defined AI opportunity that must move beyond a demo
• A product adding grounded or tool-using behavior
• An operation introducing human-reviewed AI assistance

Focus

Prove useful behavior and its operating controls before expanding autonomy or scope.

Working shape

Use-case and risk framing followed by a context, workflow, evaluation, interface, and production integration track. The engagement boundary reflects consequence, data access, and technical uncertainty.

Typical outputs

• AI job and risk brief
• Context, tool, and permission design
• Evaluation scenarios
• Human review and recovery flow
• Production implementation and observability

Best when

• Founders without a permanent technical executive
• Teams facing a sequence of connected technical choices
• Businesses that need independent technical decision support

Focus

Create a durable technical decision system rather than a stream of disconnected recommendations.

Working shape

A recurring leadership cadence with defined decision ownership, access to relevant product and technical context, and focused work between reviews. The role complements rather than obscures internal accountability.

Typical outputs

• Technical landscape and risk review
• Architecture decision support
• Delivery and quality guidance
• Team or vendor evaluation
• Decision records and leadership cadence

Best when

• Products moving from launch into sustained learning
• Teams addressing reliability and product improvements together
• Organizations evolving a system without losing architectural clarity

Focus

Use production evidence to guide improvements while preserving system health and delivery capacity.

Working shape

A recurring product and engineering cadence covering observation, prioritization, design, implementation, release, and review. Capacity and responsibilities are agreed around the product's needs.

Typical outputs

• Product signal review
• Evolution roadmap
• Experience and feature delivery
• Reliability and architecture work
• Release learning reviews