Inventing the interfaces for machines that act on their own.

Fractional Chief Design Officer — hands-on — for teams building autonomy, agentic AI, and critical infrastructure. 23 years across Salesforce, Oracle, Uber, PayPal, Samsung, and Nimbus. 24 patents.

Start a conversation See the work

PRODUCTS SHIPPED 0→1
YEARS LEADING DESIGN
PATENTS IN AI, ROBOTICS, INTERFACE
DESIGN ORGS BUILT

EARLY-STAGE

ENTERPRISE BACKGROUND

The hard part was never the model.

Every team building an autonomous system arrives at the same discovery: the intelligence works, and the product still fails. What breaks is the interface — how much a person is asked to trust, how much they can see, and what happens when the system is wrong. That is a design problem. It is the one I solve.

SELECTED WORK

AUTONOMY

Drone Dispatch

Autonomous field operations, designed inside the enterprise. Salesforce.

AI INTERFACES

Generative Canvas

Inventing the agentic interface. The blueprint behind generative patterns now shaping Slack and Salesforce. Salesforce.

STRATEGY

Offerwell

Offerwell — AgentOS

An AI product roadmap, built as an outside operator.

View case study →

NARRATIVE

WhenWeFirst

Early product strategy and the deck that raised on it.

View case study →

APPROACH

How I work as 4 commitments to you...

Design is a multiplier, not a service.

The design function's job is to remove ambiguity so engineering can move faster. If design is a queue you file tickets into, it is costing you velocity instead of adding it. I build it as the function that decides what gets built.

Systems before artifacts.

One beautiful screen is a demo. A system is a company that can ship its tenth screen as well as its first — without me in the room. Everything I build is meant to outlive the engagement.

Three horizons, held at once.

What ships this quarter, what gets designed this year, and what the company is actually for. Most teams work on one of the three. The job is holding all three in the same room and making them agree.

The interface is where trust gets decided.

When a system acts on its own, every design decision is a decision about how much a person should trust it, and when. That is not polish. That is the product.

ENGAGEMENTS

3 ways we start...

Product, design, brand, AI, and the story you tell investors. One person, held at the altitude where those connect.

Audit

TWO WEEKS · FIXED FEE · PRODUCT, DESIGN, BRAND, AI, GTM

A senior read on your product, your design function, and the gap between them. Where the interface asks people to trust the system more than it has earned, where the workflow breaks under real use, and what to build next. You get a written point of view, a prioritized plan, and one artifact showing what good looks like for your product specifically — not a deck of principles. It ends with a recommendation, including the recommendation not to hire me.

90-Day Proof

THREE MONTHS · EMBEDDED

Audit, then build. A working design system, one flagship surface designed and shipped, and the hiring plan for the team that comes after me. Ninety days is long enough to change what a company is capable of, and short enough to see the whole thing from the start.

Fractional Design Leadership

ONGOING · TWO TO THREE DAYS A WEEK

The Chief Design Officer role, held properly, before you are ready to hire one full time. Product direction, design quality, brand, the fundraising narrative, and the recruiting of the design leader who eventually replaces me.

Cash, cash + equity, or equity. I will take the same risk I am asking your team to take.

FAQ

The questions people actually ask.

Most teams do not have a design problem, they have a design leadership problem — no one setting the bar, resolving direction, or deciding what gets built. Your designers usually know what is wrong. I make it possible to fix.

Tell me what you are building.

If it moves, decides, or acts on its own, I want to hear about it. The fastest way in is the two-week audit — but a conversation costs nothing.