10 Questions to Answer Before Building a Business Website

A website project can become confusing before a single page is designed. One person wants a fresh look, another wants online booking, and someone else assumes all the writing is included. Those are different expectations, even when everyone agrees that the business needs a better website.

You do not need a technical specification to begin. You need a shared understanding of the job the website should do. Answer these ten questions in plain English, and bring the answers to your first planning conversation.

1. What should the website help your business accomplish?

Choose a primary purpose: explain your services, generate relevant inquiries, take bookings, sell products, or support existing customers. A local contractor might want visitors to understand its specialties and request a project conversation. A shop might need dependable opening hours and product information before considering online sales.

Write one sentence describing success. Avoid making “a modern website” the whole objective; appearance matters, but it does not define what customers should be able to do.

2. Who is the website for?

Describe the people making the decision, not just a broad demographic. Are they homeowners comparing contractors, office managers researching support, or visitors planning an event? What do they already know, and what are they uncertain about?

List their three most important questions. Those questions should influence your navigation, service descriptions, and contact process more than internal department names do.

3. What is the most useful next step?

Decide what a visitor should do after reading: call, request an estimate, book an appointment, or send a qualified inquiry. Make that step easy to recognize and realistic for the service you provide.

If you cannot quote without a conversation, do not promise an instant price. If you need several project details, ask for enough to start—not a lengthy application before anyone has spoken.

4. Which pages and functions are actually necessary?

Separate essential launch requirements from later improvements. Core pages might include services, relevant work, company information, and contact details. Functions could include a form, booking link, document download, or online payment.

For each function, ask who will use it and who will maintain it. A complex feature that nobody owns can create more work than it removes. A clear service page and reliable inquiry path may be a better starting point.

5. What content and evidence do you already have?

Gather accurate service descriptions, approved photographs, project examples, brand files, and testimonials you have permission to use. Note what is missing and who can supply it.

Do not assume the designer knows your processes or can invent customer evidence. A useful project example explains the situation and work performed without claiming results you cannot support. Authentic, modest evidence is more credible than polished but unsupported promises.

6. Who will write, review, and approve the content?

Agree whether the project includes writing, editing supplied material, or simply placing approved copy. Identify one person who can consolidate feedback and make final decisions.

Set realistic review windows. Design and development can stall when five people provide conflicting comments or key service information arrives late. A short approval process protects both the schedule and the quality of the finished content.

7. Who controls the domain, hosting, and connected accounts?

Identify the business-controlled accounts for the domain, website hosting, email, booking software, and other integrations. Confirm that an authorized person can access them securely. Share access through appropriate invitations or agreed secure methods—not passwords pasted into inquiry forms.

Email and the website may depend on related domain settings. Any launch plan should identify those dependencies before changes are made, rather than treating them as an afterthought.

8. What budget and timing constraints should shape the scope?

Explain what you can invest and why the timing matters. A seasonal opening, event, or new service may create a genuine deadline. Distinguish that from a preferred date that can move.

Ask what is included, what would be priced separately, and how changes are approved. A smaller, complete first release can be more useful than an ambitious plan with unfinished sections. Do not accept a schedule without understanding your own content and review responsibilities.

9. What will happen after launch?

Determine who handles content changes, software updates where applicable, hosting coordination, renewals, and troubleshooting. Ask what support is included and what requires a separate agreement.

“Maintenance” can mean different things. A static website, a content-management system, and an online store have different needs. Write down responsibilities rather than assuming the original project covers every future task.

10. How will you evaluate whether it is useful?

Choose measures connected to your original purpose: relevant inquiries, booking requests, completed purchases, or fewer repeated customer questions. Agree how those signals will be recorded without collecting unnecessary personal information.

For a service business, a simple record of how qualified inquiries found you can complement website data. Page views alone do not establish customer value, and a new site does not guarantee demand.

Turn the answers into a short project brief

Put your answers on one or two pages. Mark unknowns honestly, attach useful existing material, and identify the decisions that need help. You can refine the brief together; its purpose is to prevent avoidable misunderstandings, not to make you a web specialist.

If you are still deciding whether a website is the right investment, start with whether your small business needs a website. For help turning an initial brief into an agreed project, explore Amminist’s Web Presence services.