Screens are not outcomes

A consumer app founder came to us with 1,500 people hitting his site every day and only 100 converting. He had already talked to a long list of UI designers about it. Every one of them heard "conversion problem" and quoted him a redesign.

That is the standard failure mode of hiring design in this market, and it is worth understanding precisely, because the founder's own words after our first call were that none of those designers thought from the perspective we did, and that this perspective was the thing he actually needed. He didn't need different screens. He needed a different question.

The standard failure mode

Here is how the usual engagement goes. You hire a designer. They ask what pages you need. They produce clean Figma files. The files get implemented. The product looks better. And the number that made you hire them, the deposit rate, the visit-to-trade conversion, the onboarding completion, does not move, because nobody was ever working on it. The designer was paid to produce screens, the screens got produced, and everyone technically did their job. Screens are the deliverable. They were never the goal.

The teams that get burned by this are usually all-engineer teams, which makes sense. Engineers buy design the way they buy components: spec in, artifact out. So they write "we need a landing page, an onboarding flow, a dashboard" and get exactly that. But conversion does not live in any single artifact. It lives in the sequence. Where users come from, what they expect, where they hesitate, which step quietly loses sixty percent of them. A designer who thinks in screens cannot see any of that, and most of the market thinks in screens. Generalist freelancers need to be told word for word what to make. Agencies execute the brief verbatim. Both hand the diagnostic work back to the founder, who is the person least equipped to do it, because he is the one who built the funnel that's leaking.

Diagnose before you design

The reframe is one sentence. Design is not the production of screens. It is the deliberate engineering of a user's path to one outcome, measured. When we start an engagement, the first artifact is not a mockup. It is a diagnosis: where in the flow the 1,400 people go, what they see at the moment they leave, what the product is asking of them that they are not willing to give yet. Sometimes the fix is a redesign. Often it is smaller and stranger. A confusing yes-or-no moment in an intro video. A wallet step sequenced one screen too early. A withdraw function hidden in settings, eroding the trust that funds the next deposit. None of these appear in a screen list. All of them appear in the data and in watching five real users.

Buy outcomes, not artifacts

This also changes how you should buy design. The day-to-day question for the founder above became: here are yesterday's numbers, what do we fix today? That is a different job than "make this page." It needs someone who reads funnels, knows the patterns of this specific market, and treats every design decision as a hypothesis about a metric. When design works that way, it stops being a cost you justify by taste and becomes the cheapest growth lever you have, because the traffic is already there. He was paying for 1,500 visitors a day and keeping 100. The other 1,400 were already bought.

Start with the number

Before you brief anyone on screens, write down the one number the work must move and the date you'll check it. If a designer doesn't ask for that number in the first conversation, they were going to sell you screens. You can get screens anywhere. Outcomes are the scarce thing.