Everyone can ship now… but does it make money?


This week I kept coming back to the same thought.

“AI is helping us build faster.”

Cool.

But how much of what we’re building actually makes money?

I saw a clip this week from Jonathan Courtney calling this out directly. Everyone is building. Shipping. Launching. But when you zoom out, a lot of it isn’t translating into real business impact.

And I think I know why.

We’ve collapsed the time it takes to build, but we haven’t improved the quality of the thinking behind it.

So now we’re just shipping more things that feel right.

I see this inside teams all the time.

There’s a moment where everything looks aligned. PM is confident, engineering is already thinking implementation, the flow “makes sense.”

And you’re the only one uncomfortable

Not because something is obviously broken, but because something feels off. The inputs are too clean. The edge cases are missing. The flow assumes a reality that doesn’t exist.

But on the surface, everything looks fine.

So it ships.

And then one of two things happens.

It doesn’t get used. Or it doesn’t drive any real outcome.

No revenue. No adoption. No meaningful change in behavior.

Just more shit in the product.

And the part most people miss is this.

The product itself is only one piece.

If you’re not designing the full system, it’s not an MVP. It’s just a feature.

How does someone even get to this thing?

Is it a VSL funnel? A sales demo? A quiz that segments intent?

What happens after they use it?

Why would they come back? What increases their LTV? What keeps them engaged beyond the first interaction?

That context matters more than the feature.

Because that’s where money is actually made.

AI doesn’t solve that.

It can help you build the thing faster. It doesn’t tell you how the thing fits into acquisition, conversion, and retention.

That still has to be designed.

This is where design actually matters.

Not in making things look clean. Not in shipping faster. But in understanding how what you’re building connects to how users discover it, how they decide to use it, and how it drives revenue or retention over time.

If you don’t have that, you can build all day.

It won’t matter.

And this is also where influence comes from.

Not from big redesigns or calling yourself “strategic.”

From small, clear wins.

You improve one step in the funnel. You increase conversion slightly. You remove friction at the exact moment someone is about to drop off.

Someone sees it and goes, “wait… that actually made a difference.”

And then, “can you look at this too?”

That’s how your surface area grows.

Because now you’re not just designing screens.

You’re helping the product make money.

And that’s the shift.

Anyone can ship now.

But very few people are building systems that actually convert, retain, and compound.

And if you’re not thinking about that…

you’re just building faster ways to stay stuck.

We went deeper on this in this week’s episode.

Why teams are shipping more but winning less

Where AI actually helps (and where it quietly hurts you)

And how to think in systems instead of features

If you care about building things that actually drive outcomes, not just output…

you’ll want to listen to this one.

video preview

Full episode with Co-host: Nick Groeneveld


Talk soon,

Tyler White

Tyler White

Helping designers prove the ROI of their decisions

Each week I share how design decisions actually drive adoption, retention, and revenue — and how to earn your seat at the table without playing politics.

X | LinkedIn | Youtube | Design Table Podcast

600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246


Unsubscribe · Preferences

Tyler White

Every Saturday: real product breakdowns, decision frameworks, and ROI-based thinking for designers who want more leverage (and more money).

Read more from Tyler White
Illustrated podcast thumbnail for The Design Table episode about portfolio presentations, showing a desk scene with bold text and playful visual elements.

Your portfolio is not the presentation There is a specific kind of silence that happens in a portfolio interview. It is not dramatic. Nobody throws a chair. Nobody says, Tyler, this is becoming a crime scene. It is smaller than that. The hiring manager stops nodding. The PM looks at the slide thumbnails instead of the slide you are on. Someone leans back a little. One person is still smiling, but it has the same energy as a flight attendant during turbulence. The work might still be good. The...

Black thumbnail with colorful Figma-style shapes and the text “What’s Left of Your Job?”

Every tool should earn its seat A year and a half ago, I joined CapIntel. This week, I was promoted to Principal Product Designer. Which feels incredible. Not in the “I have ascended into corporate enlightenment” kind of way. More in the “holy shit, I’m trusted to solve bigger problems now” kind of way. And honestly, that trust has changed how I think about design. The more senior I get, the less I care about making beautiful static screens that sit in Figma collecting digital dust. I care...

Laptop open on an airport table while working on product design notes after a Toronto offsite.

You’re doing the work that should’ve been handed off I don’t think most designers are slow. I think we’ve just gotten weirdly good at staying busy with work that doesn’t need us. Not obviously wrong either. The kind that feels responsible and thorough, like you’re doing your job properly. That’s what makes it hard to spot. This hit me after a client call, somewhere between work, travel, and waiting for a flight home from a Toronto offsite. Laptop open at the airport, half a drink beside me,...