About

I connect customer decisions, commercial execution, and technical context.

My best work sits where a customer decision, a complex product, and several internal teams meet. I bring structure to discovery, translate what matters, and keep the commercial next step clear.

Point of view

Technical depth matters when it improves the quality of a customer decision.

I am based in Scottsdale, Arizona, and have worked across entrepreneurship, complex transactions, web infrastructure, and B2B services. The industries changed; the core work did not: understand what someone is trying to decide, identify the constraint, and keep the evidence and next action clear.

That is also how I approach technical products. I start with the user and decision, then work backward into requirements, architecture, controls, validation, and communication. The result should be useful to a practitioner and legible to the person responsible for the outcome.

Professional strengths

What I bring to customer-facing technical work.

Customer decisions

Turn discovery, market context, and competing priorities into a concrete evaluation and next step.

Technical translation

Turn technical findings, controls, and tradeoffs into language each stakeholder can use.

Operating discipline

Carry context across sales, product, technical, and delivery handoffs without losing the customer problem.

Working principles

Make the decision more honest and more usable.

Name the decision. Requirements become useful when the decision, owner, and consequence are clear.
Ground the recommendation. Connect the proposed action to the customer need, operating context, and relevant facts.
Plan the handoff. Authority, privacy, human review, and failure modes belong in the operating design.
Make the next step explicit. Name the owner, timing, dependency, and decision that moves the work forward.