Over the years we've seen a huge number of website projects, and our experience is surprisingly consistent. Most problems weren't caused by development, by design, or by technology, but by a single sentence, well before the work even began, in the very first meeting: "we'd like a nice website." A project's fate isn't decided during execution. It's decided here.
Almost every website project starts with the same sentence. Something like "we'd like a nice, modern website that looks good and brings in customers." Sometimes the request is more specific: "make it like our competitor's, just better." Sometimes it's bolder: "something unique that sets us apart."
All three of these opening lines fall into the same trap: they describe the visible end result, not the business goal behind it. That's why it's worth saying out loud in the very first meeting: "nice" is not a brief. "Why" is — and that difference is what decides whether website design remains a purely aesthetic exercise, or becomes a real business website.
Why has this question suddenly become expensive?
This brief was always weak. In 2026, though, it's also become costly. In recent years the market for AI-based website builders has exploded — from Wix ADI to Framer AI to Lovable, anyone can type a sentence and have a finished site thirty minutes later. The problem isn't that these are bad. It's that they're all the same: the same hero section, the same card grid, the same purple-blue gradient. Open an AI generator, type in that you want a nice site, then look at five competitors in your own market — they'll look like siblings.
A "we'd like a nice, modern site" request is no longer harmless today. In this crowd, an average site isn't a disadvantage. It's the reason nobody notices you.
The brief isn't a formality, it's a diagnosis
A bad brief isn't dangerous because it's a project management problem. It's dangerous because it only becomes clear weeks later that the project started in the wrong direction — at which point changing course costs an order of magnitude more than it would have at the start.
"We'd like a nice website" — that's an aesthetic expectation. "We want more qualified leads from B2B customers who already know who we are" — that's a business goal. The first tells the person building it what something should look like. The second tells them what needs to work. Anyone can build a nice site based on the first. Based on the second, you can build an effective system — but that requires understanding the business behind it, and that's the real starting point of website strategy.
A concrete example. In one of our recent projects, the client asked for a new, "more modern" website because they felt the old one was no longer competitive. During the discovery conversation, though, it turned out that most visitors never even reached the contact page, because the service pages didn't distinguish between their two completely different target audiences. What was needed wasn't a new design, but a clearer navigation logic. In the end the website wasn't better because it was prettier, but because it finally did what it needed to do.
What the word "nice" hides
"Nice" is one of the most overloaded words in a website project, because everyone means something different by it, and nobody says so out loud. The CEO means it should look premium and trustworthy. The marketer means it should convert well. The head of sales means that people requesting quotes should see the company as a quality partner before they even call. The developer means clean code and good structure underneath.
All four are right. But if this isn't said out loud at the start of the project, everyone ends up dissatisfied at the end, even though the site technically fulfilled the brief. This is one of our most common experiences: the project goes through review after review, the client says in every round "it's good, but something's missing," and nobody can quite say what. Usually what's missing is that at the start, it was never made clear who meant what by the project's success.
Why "like our competitor's, just better" isn't enough
This type of brief is even more dangerous, because it seems specific. The client shows you the competitor's website, points to a few elements they like and don't like — and thinks that gives you direction.
But the competitor's site wasn't made by the competitor: it too is the result of a negotiation, full of compromises and decisions that aren't visible from the outside. And most importantly: your competitor's business goals aren't the same as yours. Their customer base is different, their sales process is different, their positioning is different. A website that looks like theirs won't make you as successful as they are, it will just look like theirs. Similarity is the most expensive thing a website can produce.
Another case. A client specifically wanted a new webshop because the old one "converted slowly." During the strategy phase, though, it turned out the problem wasn't the webshop itself, but that the product pages didn't answer the questions buyers ran into before making a decision — questions the sales team explained individually on every single phone call. If we'd jumped straight into development, this would never have come to light.
The website as a system, not a product
A website is made up of at least five layers, each of which affects all the others:
- Strategic layer — what the website's purpose is, who it's for, what it needs to achieve for the business. This is the foundation of digital strategy, the layer everything else is built on.
- Content layer — what we say, in what order, in what depth.
- Structural layer — how the site is put together, what path the visitor takes from arrival to conversion.
- Visual layer — what it looks like, what feeling it creates. This is what clients talk about the most, and it's the layer that on its own achieves the least.
- Technical layer — how it's built, how fast it loads, how search engines index it.
A "we'd like a nice website" brief starts from the fifth layer, and works backward to infer all the others. A good B2B website strategy starts from the first layer, and builds forward.
The website's new readers: AI systems
There's an audience for this whole system that hasn't been mentioned yet — even though in 2026 it's one of the biggest changes. In the past we designed websites for a single audience: the human who opens them. Today, that same page is "read" the same way by Google, ChatGPT, Gemini, Claude, and Perplexity too. A visually beautiful but poorly structured site is something a human visitor will still forgive. AI simply skips it.
In the past, the website was the digital entry point. Today, increasingly, it's the AI that forms the first impression, and the website becomes the place where trust is confirmed and built. Today it matters just as much that ChatGPT, Gemini, or another AI system recognizes and cites your content as a credible source, as it does to rank on the first page of Google. A website is no longer built just to rank, it's built to be cited too — that's the essence of GEO and AI Visibility, and it requires exactly the three layers (strategy, content, structure) that a "let's make a nice website" request most often skips.
What questions are worth thinking through
A useful brief isn't a template to fill in. It's more of a thinking process that produces a result.
- Who arrives at the website, and what do they want to do? Not demographics — behavior. In a B2B context: which touchpoint is this in the buying process?
- What's the one thing we want them to do? A website can't optimize for everything at once.
- What makes a visitor distrustful, and how can that be resolved? Especially in a B2B context, where the decision is long and involves multiple people.
- What isn't working right now? What do salespeople always end up explaining before a pitch, even though it's already on the site?
- What will still be true about the company in five years? This is the foundation of positioning, not current design trends.
- How is success measured? Organic traffic, conversion rate, bounce rate, number of inquiries — all of these are measurable.
This also includes considerations a client would rarely think to put in a brief themselves, yet which fundamentally shape the direction of the project: are there multiple, distinct target audiences that need separate messaging; how does the site fit into the sales process; who will update the content, and how often; should you plan for headcount growth or a new language market within two years. A site that's made multilingual after the fact, or wasn't designed to scale, typically ends up costing twice as much as one that was built for this from the start.
When is all of this NOT necessary?
In the interest of honesty: not every website needs a deep, multi-week strategy phase. If a local business simply needs a simple page showing contact details and a few references, a long discovery process is an unnecessary burden. In that case, a good template, or even an AI tool, is enough.
Deep strategic work really pays off when the website has to actually work: generating leads, supporting a long B2B decision, guiding multiple audiences, or building trust before a high-stakes purchase.
What we do differently
Whether a project needs this depth can't be decided from the first "we'd like a nice website" sentence — so we start every project with a short, clarifying conversation, even when the client initially says they just want "a simple website." If it turns out a simple site really is all that's needed, we say so, and we don't push a longer process on you — because the most expensive advice of all is when someone sells you something you don't need. But if it turns out the website really does need to work hard, we move into the deep phase.
Strategy, content, technological infrastructure, SEO, GEO, and AI visibility are all parts of the same one system. That's why we don't just build websites or produce content — we build digital growth systems.
Most websites don't fail to deliver results because they were poorly built. They fail because they started with the wrong question. That's why we don't ask first what the website should look like, but what it needs to achieve.
The most expensive sentence isn't "Make it nice." It's "I wish we'd thought this through at the start." If you're thinking about a new project, and you'd rather not find out what the real goal was during the third round of reviews, let's start with a strategy conversation.
