The problem isn't design. It's decision infrastructure.

Fractional product and design leadership for AI-native products that decide, recommend, and automate.

Your team already ships with AI. Raw model capability. Business ambiguity. The product logic nobody has drawn yet. I turn that into systems people can understand, trust, and put to work day to day, so the team can ship without me.

Currently taking one new engagement.

Previously at Meta, Pinterest, and Opendoor.

Why people reach out

You are probably here for one of these problems

Best for seed to Series B AI-native teams. Especially useful when adoption depends on trust, control, workflow, or operational judgment.

Usually someone has already tried the obvious moves. A contract designer, a redesign, a round of onboarding tooltips, and activation still didn't move. A common trigger is concrete: the product works, but every new customer still needs a person in the loop to succeed, and making it self-serve is where trust, legibility, and product decisions all meet.

The Decision Read

Most teams misdiagnose their own problem. Find out what yours is.

Six questions about how your team makes product decisions. That's where every engagement starts, and if it isn't work I do, I'll tell you that too.

Your model works in the demo and stalls in production, and you can't tell where the trust breaks.

You're shipping AI features faster than your team can decide which ones actually matter.

You need senior product and design judgment in the room now, and you're not ready to hire a full-time executive.

Get in touch Free. No signup to run it.

·A fractional product and design leader who sets direction and stays close to execution.

Close enough to the work to back the call, in the room where it gets made.

01 / 06
Reading your situation…
Your read

Send me your read

Leave it with me and I'll reach back out.
Your read and your answers come with it, so when I get back to you, I already know your situation.
The read you're sending

Your answers are sent to Anthropic's API to write the read. I never see them unless you choose to send the read to me. No signup.

Got it. I'll be in touch.
I read every message personally, and I'll come back to you with your read in hand.

Engagement

Who it's for, and what it costs

You're buying the judgment that decides what gets built.

Direction Sprint

Four weeks. Scope fixed up front. $30K.

I map the system, find the load-bearing mechanic, set the direction with its trust model, and leave your team a prototype and a sequence it can carry.

Embedded

Standing product and design direction inside the operating rhythm. $20K/mo.

Best for seed to Series B AI-native teams, especially when adoption depends on trust, control, workflow, or operational judgment.

Advisory

Limited. By invitation following a Sprint.

A standing line for the calls that decide direction, once I already know your system.

I scope the proposal with you in conversation.

The method

I start with the system,
not the screens.
Then I make the moves it needs.

In practice, they run in this order.

01

Map the system

Most of the problem is visible here, and most teams have never drawn it.

02

Find the load-bearing mechanic

Every product lives or dies on one decision. I find the one that carries the weight.

03

Make it legible

A person should understand what to do and why, without being taught.

04

Build the trust layer

AI changes what a person has to believe before they act. Trust has an anatomy: the evidence, the controls, the way back when it's wrong. I design that.

05

Ground it in measurement

If we can't tell whether a decision got better, we shipped decoration.

06

Sequence for compounding

I order the work so each release makes the next one easier. That's what compounds.

About

Hew Suber, MBA

About 17 years building decision-heavy product systems: automation, self-serve, operational modeling, and AI-native products, across Meta, Pinterest, Opendoor, and early-stage companies, including embedded product and design work across a Techstars Atlanta cohort. AI in the workflow by default, not bolted on after.

I pressure-test what's actually buildable against your codebase, and say so early. Range and judgment that keep the roadmap honest, not hours for hire.

Full work history →
Hew Suber

Let's talk

Let's see if the fit is real.

A 30-minute working session is the fastest way to tell. No deck, no pitch. Bring whatever's stuck, and we'll find the one decision the rest is waiting on.

Send a note

Atlanta, GA · Working worldwide

Book a call