The Questions Nobody Tells You to Ask Before You Build a Website

When organizations start planning a new website, the first conversations are usually about the things they can see. What should it look like? How many pages do we need? What features should it have? How much will it cost?

Those are reasonable questions. They’re just not the only questions that matter.

Some of the decisions that will have the biggest effect on the life of your website are almost invisible when the project begins. They show up later, when the business changes, the site grows, a new system needs to be integrated, more people need access, or someone asks for a feature nobody imagined during the original build.

A website can be a perfect fit for today and still quietly limit tomorrow.

The website decision you think you’re making

At the beginning of a project, the decision often appears to be about design, price, platform, and a list of requested features. These are all important in their own right, but underneath them, you’re also making decisions about flexibility, ownership, integration, maintainability, and future change.

The visible question is what will it look like?

The deeper question is whether we can change the experience and customize later without rebuilding the entire system.

The visible question is what does it cost?

The deeper question is what it will cost to maintain, extend, integrate, and eventually hand off.

The question I wish more organizations asked

Every technology choice has its trade-offs. The problem isn’t accepting a limitation. The problem lies in accepting one without understanding it or even knowing about it.

What limitations are we accepting if we choose this?

A lower-cost platform may be exactly right for a small organization that needs a simple site and expects it to stay that way. The same platform may be a poor fit for an organization that expects complex integrations, thousands of pieces of content, multiple editorial users, custom workflows, members, or enterprise access requirements.

Understanding what you’re trading away in exchange for simplicity, speed, or lower upfront cost is important.

Ask what happens when your business changes

No one can predict every future requirement. Businesses sometimes grow in unexpected ways. But you need to know whether the system is at least capable of change.

• What happens if we add a second audience or line of business?
• What happens if our content or visitors grow from hundreds to thousands?
• What happens if several team members need different publishing permissions?
• What happens if we need to connect the website to our CRM, ERP, AI tools, or another business platform?
• What happens if our accessibility, privacy, or security requirements become more demanding?
• What happens if our internal team wants more control?

You’re not looking for a guarantee that every future idea will be simple. You’re just trying to understand whether the architecture gives you reasonable paths forward.

Ask who really owns the website

Ownership sounds obvious until an organization tries to leave a platform, change vendors, retrieve its data, or move its hosting.

• Do we own the domain?
• Do we own or control the hosting account?
• Can we export all of our content and data in a usable form?
• Are there proprietary components that only one vendor can maintain?
• Can another qualified engineering team take over the system if necessary?

A healthy technology relationship should not depend on keeping a client trapped. Even if you love the team you choose, your organization should understand what it owns and what it would take to transition later.

The questions to take into your next website project

• What limitations are we accepting if we choose this platform or architecture?
• What parts of the system will we own?
• Can another qualified team maintain it?
• How does the system handle more content, users, roles, traffic, or complexity?
• What is likely to become difficult if our organization grows?
• Which decisions we make now would be expensive to reverse later?

The answers don’t have to be perfect, but they do need to be honest.

Not sure which of these apply to your situation? Book a free 30-minute consult, and we'll walk through it together.

Related article by Liz Krukosky:

What Did We Ever Do Without It?