What If I Don't Know What I Want My Website to Look Like?

Of all the reasons business owners put off a website project, this is the most common one nobody says out loud: they don't know what they want it to look like. They know their business cold. They can talk about their customers for an hour. But when the designer asks "any thoughts on the design?" — the honest answer is a shrug, and the shrug feels like it's disqualifying.

It isn't. Here's the secret from the designer's side of the table: almost nobody arrives with a visual vision. The people who do are usually the hardest clients — they arrive with someone else's website in their head and spend the project fighting to replicate it. Not knowing what you want isn't a gap in your preparation. It's the normal starting condition, and the design process is built to work exactly from there.

Why "I don't know" is a fine answer

A website's look is not a preference you're born with — it's a conclusion a designer helps you reach from facts you already have. The facts:

Every one of those is something you know cold. The designer's job is to ask the questions that turn business facts into design decisions — which is why a good first conversation is about your customers, not your color preferences. We cover what that conversation should include in what a useful website discovery call should cover.

What you can bring instead of a vision

You don't need to arrive with a design. You can arrive with something better: reactions. Three of them are worth preparing:

Websites you like — in other industries. The fastest way to communicate taste without design vocabulary. Note the feeling, not the features: "this feels calm and expensive," "this feels fun." A restaurant owner pointing at a law firm's site and saying "this — but warmer" has communicated more than a mood board.

Websites you hate, especially in your own industry. Negative examples are just as useful — often more so. "Every plumber site has a stock photo of a guy holding a wrench; I never want that" is a complete design brief in one sentence.

Your own materials. Business cards, the truck wrap, the menu, the signage. You already have a visual identity, even if it's an accidental one — and the website's job may be as simple as agreeing with what your customers already see.

Notice what all three have in common: none require you to know anything about design. They require you to have eyes and opinions, both of which you have.

How the process draws the design out

The reason you don't need a vision is that the project's early phases exist to manufacture one. A typical sequence:

Content and structure first. What pages, what message, what order — before anyone opens a design tool. This is where most of the real decisions live, and it's all words you understand.

Then a rough layout. Gray boxes, placeholder text, no colors. This stage is where you find out you actually have strong opinions — you just didn't know them until you saw the wrong version. Almost every client's first design feedback is "I don't like this," and that's the process working: eliminating options is easier than inventing them.

Then the design. Only after structure is agreed does the actual look arrive — built on decisions you've already approved. The "what will it look like" anxiety dissolves somewhere in here, because by the time real design appears, you've already agreed to its skeleton.

Then refinement. Where your reactions do their work. This is the phase that revision rounds exist for — not because clients are supposed to arrive with perfect taste, but because taste gets discovered in contact with drafts.

By the time you're looking at a real design, it feels inevitable rather than surprising — and clients routinely say "that's exactly what I would have wanted," which is a sentence that should end with "…if I could have described it."

What patience looks like, on both sides

In the stories clients tell about designers they loved, one theme recurs more than any other: patience. Clients describe designers who "showed great patience with my limited computer skills," who "never tired of hearing my thoughts," who took time to understand the business before proposing anything visual. That patience is the service. Designers who make you feel stupid for not knowing the jargon — or who can't explain why they made a choice — are failing at the job regardless of their portfolio.

Your side of the patience contract: give honest reactions, even negative ones, even vague ones. "I don't like it but can't say why" is useful feedback — a good designer will dig at it with options until it sharpens. What's not useful is approving things you don't love to avoid conflict. The site goes live with the shrug baked in.

The shortcut that isn't

One temptation worth naming: hiring a template-builder service specifically because it doesn't ask you any questions. It feels easier — no discovery call, no opinions needed, pick option three of twelve. But skipping the questions doesn't skip the decisions; it just makes them for you, generically. You get the site of a business that doesn't exist, and if it looks wrong, there's no process for finding out why — template vs. bespoke is a legitimate budget choice, but "I don't know what I want" is the one reason that shouldn't drive it, because not knowing is exactly what the bespoke process is for.

Before your first call

Do these three things, and bring them to any designer:

That last sentence, delivered at the first meeting, is not an admission of unpreparedness. It's the exact right brief.

Questions about what your site could be? We'll ask about your customers, not your favorite color. We answer every enquiry personally, within one business day.