When a Client Says "Redesign"

A founder comes in with a request: we need a redesign.

Something isn't working. Conversions are low. Investors don't get the product. Users leave after the first screen.

But "redesign" is not a diagnosis. It's a symptom.

Because the problem is almost never the visuals. Not the colors. Not the button placement or the outdated font.

The problem is that the product isn't saying the right thing. Or it's saying the right thing to the wrong people. Or it's saying everything at once and landing nowhere.

In that case, a redesign isn't an interface update. It's surgery on meaning.

Before

After

What's Actually Broken

80% of projects that come to us as "redesigns" are not problems of form. They're problems of content.

The positioning is blurry. Features are described in developer language, not user language. The first screen talks about the product instead of talking about the problem it solves.

The user arrives. Reads. Doesn't understand why this is for them. Leaves.

A new font gets added. An animation. It looks better. The user arrives again. Reads. Doesn't understand why this is for them. Leaves, but now it looks nice.

The problem isn't solved. Just repackaged.

That's not a redesign. That's polish. And polish doesn't heal anything.

Our First Step Is Not Figma or Framer

Before opening any editor, one thing needs to be clear: what is this product being built for right now.

The goal of increasing conversions is one logic. The goal of attracting investors in three months is completely different. Entering a new market is a third.

These are not the same. And the design for each of these goals will be different. Not stylistically but structurally.

So the first conversation is not about moodboards or references. It's about the founder's goals. About who is making the decision on the other side of the screen. About what that person needs to understand, feel, and do after seeing the product.

Only then does it become clear what's actually broken. And what actually needs to change.

80% of Success Is Analysis

Redesign without analysis is intuition. Sometimes it works. Usually not.

We look at competitors. Not to copy them but to understand the context the product lives in. How it looks next to them. Where it gets lost. Where it can win.

We look at how the product describes itself. What words it uses. How well those words match what actually matters to the audience.

We look at structure. What comes first, what comes second, what logic sits behind that. Often the most important thing is buried halfway down the page. And the first screen is occupied by something that looks good but doesn't work.

Only after this does it become clear what to pull out by the root. And what to keep.

Redesign Is Surgery, Not Polish

Polish makes a product look better. Surgery makes it work.

These are different things. And an honest conversation with a client starts exactly there.

We don't come to make things look nice on top of what already exists. We come to understand what isn't working and remove it. Even if that's uncomfortable. Even if it means rewriting everything the founder spent six months building.

Because new colors don't change the logic. And the logic is the product.

Redesign is not about the page. It's about what the page says.

And if that's broken, you pull it out by the root.