Before You Build a Website: 5 Questions You Need to Answer

Many website problems don't start in design or development — they start before the first mockup is even opened, at the stage where the right questions haven't been answered yet. Before you reach out to any agency (including ours), think through the following 5 points. They'll save you time, money, and rework.

1. What's the real goal of the site?

"I want a nice website" isn't a goal, it's a wish. A goal is measurable: online sales, appointments/leads, informing customers, brand awareness, supporting an existing client base. Each goal leads to a different structure, different content, and different design priorities.

2. Who is the user who will visit it?

Knowing your audience's age or device isn't enough. The more important question is what the visitor is actually trying to do: Who are they, what are they looking for, what do they already know about the brand, and what action do we ultimately want them to take? A B2B site for industrial equipment doesn't have the same needs as a fashion e-shop targeting Gen Z — not just in aesthetics, but especially in the journey the user needs to take before reaching an action (a purchase, a request, a sign-up). Understanding this intent is what truly shapes the site's structure and experience.

3. What content already exists, and what's missing?

Many projects get delayed not because of design or development, but because the content isn't ready yet (copy, photos, products, certifications). It's worth checking early on what you already have available and what will need to be created from scratch.

4. What's a realistic budget and timeline?

Budget and timeline help define the project's actual scope and the priorities for the first version. A landing page, a corporate website, and a custom platform each have completely different design, development, and infrastructure requirements. Technology should be chosen based on the project's real needs and how it's expected to evolve — and then adapted to the available budget, not the other way around.

5. Who will manage the site after launch?

A website isn't finished once it "goes live." It needs content updates, security, backups, and possible product changes. If there's no internal team to manage it, a hosting & support arrangement should be in place from the start — not treated as an emergency later on.

The takeaway: The clearer the answers to these five questions, the more accurately a website's structure, experience, and technology can be planned. At dontmatter, every project starts with this conversation — before Figma, before development, and before any design decision is made.