How to Plan a Business Website Before Hiring a Web Designer

Looking at portfolios is useful, but it is not planning. Before you hire a web designer, you need to know what problem the website is supposed to solve. A law firm, a school, a hardware supplier, a consultant and a real estate agency may all ask for a "professional website", but the work behind each one is different. The pages, content, forms, proof, images, search opportunities and follow-up process will not be the same.

A business website normally has one of five jobs: create credibility, generate leads, explain services, support campaigns or reduce repetitive questions. It can do more than one, but one job should lead. If the website must generate leads, then the structure should prioritize services, proof, calls to action, forms and tracking. If the website is mainly for corporate credibility, the structure may need leadership, company history, sectors, tenders, certifications and project proof. This early decision helps you choose the right business website design scope instead of buying pages blindly.

Many businesses can describe what they do in a meeting, but their website content still ends up vague. Before hiring a designer, list your services the way customers think about them. Do not only use internal department names. Write the problem, the service, who it is for and the action a visitor should take. This helps the designer understand whether each service needs a page, a section, a landing page or a future content piece.

For example, "digital solutions" is too broad. "Website redesign for service businesses that need better leads and SEO-safe migration" is clearer. "IT support" is broad. "Website maintenance for WordPress sites with backups, updates, security checks and small fixes" is easier to scope. Clear service language also supports SEO because each major service can be matched to search intent instead of being hidden inside a general brochure page.

Design style matters, but page structure matters first. A beautiful one-page website may be fine for a temporary presence, but it can become limiting when the business needs service detail, local SEO, pricing education, case studies, FAQs or industry content. Before hiring a designer, sketch the pages you think the site needs. It does not need to be perfect. It just needs to show the shape of the business.

Most service businesses need a homepage, about page, service pages, proof or case studies, contact page and a quote path. Many also need pricing guidance, FAQs, blog or guide content, industry pages and landing pages for ads. If the business plans to grow search visibility, it should not hide every offer behind one broad "services" URL. A useful sitemap will give important services room to rank and give visitors room to compare.

If you are unsure how many pages are realistic, compare the sitemap to your budget. A web design cost guide can help you understand why content depth, copywriting, SEO and integrations affect price. The cheapest quote may only include layout production. A stronger quote should include planning, page structure, responsive design, forms, launch checks and at least basic SEO foundations.

Websites often feel generic because the business has not prepared proof. A designer can make sections look polished, but they cannot invent real credibility. Before the project starts, gather testimonials, project photos, before-and-after notes, client types, certifications, team photos, partnerships, media mentions, years of experience, service outcomes and common objections you overcome during sales calls.

Proof should be specific. "We serve many clients" is weak. "We built a searchable property website for a real estate agency with listing filters and WhatsApp enquiry paths" is stronger. "We are trusted" is weak. A team page, named projects, a clear process and visible contact details make the trust more believable. If you have an existing portfolio, decide which projects support the services you want to sell now, not only the work you did years ago.

This is also where industry fit appears. A school website should show admissions clarity, facilities and parent communication. An NGO website should show programmes, reports and partner trust. A corporate website may need leadership, sectors and tenders. If your business serves a specific market, share that context early so the designer can connect your site to relevant industry website pages and examples.

Some websites only need pages, forms and analytics. Others need payments, booking, ecommerce, member areas, downloads, integrations, CRM handoff, multilingual content or custom dashboards. These requirements affect price and timeline, so they should not appear halfway through the design process. Even a small feature can change the build if it affects data, security, user roles or third-party systems.

Also decide who will update the site after launch. If your team needs easy content editing, a WordPress build may make sense. If the site needs more controlled performance, custom interfaces or application logic, you may need a different development approach. The existing WordPress vs custom website guide can help you compare that decision before you ask for proposals.

A designer can ask better questions when they can see what already exists. Before the first serious meeting, collect your logo files, brand colors, current company profile, service brochures, old website link, social media links, product photos, team photos, project images, testimonials, certificates and any previous proposals or campaign materials. These do not all need to be used, but they reveal the current state of the brand.

This folder also exposes gaps. If every project photo is a low-resolution WhatsApp image, the new site may need a photography plan. If testimonials are scattered in message screenshots, someone needs to request permission and clean them up. If the company profile says one thing and the sales team sells another, the website brief should resolve that conflict before design starts. A professional website is often the first time a business notices that its materials are not aligned.

The asset folder should not become a dumping ground. Sort it by usefulness: brand, services, proof, team, legal or registration, photos, documents and access. If the site is a redesign, include analytics, Search Console access, hosting, domain and any old URLs that matter. That preparation helps the supplier protect existing visibility and decide whether the project needs a simple rebuild or a more careful website redesign plan.

You do not need to become a web expert before hiring a designer. You only need enough clarity to stop the project from becoming guesswork. A good supplier will still ask questions, challenge weak assumptions and help improve the sitemap. But if you bring a prepared brief, the conversation moves faster and the quote becomes more accurate.

These questions also make it easier to compare suppliers fairly. One proposal may be cheaper because it only covers page layouts. Another may include copy direction, SEO basics, form testing, analytics and handover. Without your own planning notes, those quotes can look similar when they are not. With clear answers, you can ask each supplier how they will handle the exact same needs and see who has understood the business.

If a supplier cannot explain how their approach supports your answers, pause. The issue may not be talent; it may be fit.

• What are the top three actions visitors should take?
• Which services are most profitable or strategically important?
• Which customers are best-fit, and which enquiries should the site filter out?
• Do we have proof, images, testimonials and project examples ready?
• Do we need WordPress, ecommerce, payments, bookings, downloads or integrations?
• Who will approve copy, design and launch decisions?
• How will we know whether the website is working after launch?

Once these answers are clear, use a tool like the website cost calculator to think through scope before asking for a formal proposal. The designer will still need to review details, but you will be discussing the right details: pages, outcomes, content, technical needs and lead quality, not only colors and page count.