Studio Notes · Behind the build

The website was never the problem

A founder can spend years trying to fix the same website.

The first version feels too small. The second looks polished but sounds like everyone else. The third has stronger visuals, more motion, and a cleaner structure, yet the founder still hesitates before sending someone the link.

At that point, the instinct is to redesign again.

But repeated visual dissatisfaction often points to a decision the website cannot make. If the business has not settled who it is for, what it promises, and why its approach matters, every design becomes a temporary arrangement around an unresolved story.

Why the website gets blamed

The website is where business ambiguity becomes visible.

An offer that feels clear in conversation may become difficult to organize on a page. A founder who can adjust the pitch for every prospect has to choose one message for everyone. Services that grew through opportunity rather than intention suddenly need a hierarchy.

The website exposes all of it.

That exposure can feel like a design problem because the symptoms are visual. The page is too crowded. The headline is vague. The services do not fit into the navigation. The case studies seem disconnected. The call to action feels wrong.

Sometimes those are genuine website problems. More often, they are evidence that the business is asking the page to hold several competing versions of itself.

A construction company wants to look established but approachable, specialized but able to take a broad range of work. A founder with three audiences wants each one to feel like the primary audience. A SaaS business wants to sell the current product while signaling a future platform that does not exist yet.

No layout can resolve a contradiction the company is unwilling to choose between.

The signs of a story problem

A story problem usually follows the business outside the website.

Ask the founder, sales lead, and delivery team what the company does best. If you get three materially different answers, the site is not the original source of confusion.

Look at proposals. If each one describes the company in a new way, the positioning is still being invented deal by deal.

Listen to sales calls. If the founder repeatedly says, “What the website does not really explain is…” pay attention to what follows. That sentence often contains the clearer promise.

Notice how service pages are built. If every capability receives equal weight because no one wants to remove anything, the business has not decided what should lead.

Then look at the revision feedback. Story problems produce comments such as “make it feel more premium,” “it needs more energy,” or “this still does not feel like us.” These reactions are real, but they are too broad to guide design. The team is sensing a mismatch without having language for it.

Chelsey’s question in this situation is: what do you want the right customer to understand, feel, and do after visiting?

If the answer changes depending on the page being discussed, pause the redesign.

The signs of a website problem

Sometimes the story is clear and the website is genuinely failing it.

The company can explain its audience and value consistently, but visitors cannot find the right service. The site is slow on a phone. Forms fail or send inquiries into an inbox no one monitors. Important proof is buried. The content matches the business, but the structure makes it hard to understand.

Gavin looks for failures in the path.

Can the right visitor recognize themselves quickly? Can they move from interest to useful detail without guessing? Does the site collect enough information to support the next step? Does that information reach the right person? Can the team update what changes without rebuilding the page?

A website problem has a more observable shape. People reach a service page and leave. Qualified leads submit incomplete requests. The mobile experience hides key information. A broken connection forces staff to copy form entries by hand. The system does not support the story that the business has already chosen.

In that case, redesigning or rebuilding may be exactly right. The difference is that the work now has a clear brief.

A short diagnosis before you spend

Before commissioning a new site, try explaining the business without discussing design.

Name the primary customer. Describe the situation that brings them to you. State the change you help create. Explain why your way of creating it is meaningfully different. Decide which offer should be easiest to understand and which action the visitor should take next.

If the leadership team cannot agree, begin with the story.

Next, place the agreed story against the current site. Does the homepage communicate the central promise? Does the navigation reflect the way customers think, or the company’s internal departments? Do the examples prove the claim you are making? Does the inquiry path gather the context your team actually needs?

If the story is present but difficult to find, understand, or act on, begin with the website.

The diagnosis can also reveal that you need both. That is common. Positioning may need to be clarified before the website can be restructured around it. The important part is sequence. A build should not begin while the core decisions are still moving underneath it.

What changes when the story is settled

When positioning is clear, the website stops behaving like a collection of pages and starts behaving like a guided decision.

The homepage can lead with one useful idea instead of accommodating every internal stakeholder. The service structure can reflect the work the company wants to grow. Case studies can demonstrate a consistent kind of value, even when the industries differ. Calls to action can match the customer’s readiness instead of defaulting to “contact us.”

Design feedback changes too.

Chelsey can evaluate whether the visual choices create the right expectation. Gavin can determine whether the platform carries that expectation through discovery, inquiry, routing, and follow-up. Both are working from the same promise.

That shared promise does not eliminate iteration. Businesses change, and websites should change with them. But there is a difference between evolving a clear story and repeatedly replacing a site in hopes that a new surface will create clarity.

If you are embarrassed by your website, do not assume the pixels are the cause. Ask whether the company has made the decisions the pixels are being asked to express.

The next redesign should begin only after you know what must remain true when the newness wears off.

← All Studio Notes