1. Write the brief before comparing designs
Describe the business goal first. Are you launching a new brand, replacing an outdated site, generating qualified enquiries, publishing a service catalogue or supporting online sales? Choose one primary outcome and a small set of supporting outcomes. A supplier cannot make a useful recommendation when the brief is only “make it modern.”
List the audiences you need to serve, the services or products that matter most, the geographic coverage you actually support, and what customers usually need to know before they contact you. This gives the structure and content a reason to exist.
2. Confirm the pages and deliverables
Ask for a page list before work begins. A typical business site may need a homepage, service pages, about page, contact page, privacy policy and a set of useful supporting resources. Product catalogues, booking flows, recruitment pages or multiple languages change the scope and should be named explicitly.
Confirm who writes the copy, supplies images, checks facts and gives approvals. Clarify how many design revisions are included, what happens when requirements change, and whether responsive layouts are included for mobile, tablet and desktop.
3. Check the mobile customer journey
Test the proposed layout at real phone widths. Text should be legible without zooming; buttons should be easy to tap; menus should open predictably; forms should be usable with a mobile keyboard; and important information should not disappear behind decorative effects.
Put the next action where a customer expects it. Depending on the business, that may be a phone call, WhatsApp conversation, quote request, appointment or checkout. Keep one primary call to action per key section and make the destination clear.
4. Require measurable trust signals
Use real information: team or office details where appropriate, a clear delivery process, relevant qualifications, product specifications, genuine testimonials with permission, and accurate project examples. Do not publish invented client logos, fake reviews or unsupported performance claims.
A visitor should be able to understand what is included, what is not included, how the project proceeds and what to do when they have a question. Clear writing is a conversion feature.
5. Include SEO and performance in the build
The design handover should account for descriptive page titles, one clear main heading, crawlable links, unique page content, image alternative text, canonical URLs, a sitemap, a useful 404 page and an appropriate mobile layout. These are foundations, not a guarantee of rankings.
Images should be appropriately sized and compressed. Lazy-load below-the-fold imagery, avoid loading unnecessary libraries, and keep the first visible section fast. Measure the live site rather than relying only on a developer's local machine. Google recommends aiming for LCP within 2.5 seconds, INP under 200 milliseconds and CLS under 0.1, assessed with field data where available.
6. Confirm ownership and support
Make sure you control the domain, hosting account, analytics property, Search Console property, code repository and relevant platform accounts. Have the supplier document how to update content, renew services, make backups and request future changes. Avoid arrangements where the business cannot access its own website or data.
Questions to ask before approving a proposal
Ask the supplier to show a comparable live project, explain what the quote includes, identify any recurring charges, describe how search basics are handled, explain who owns the finished code and accounts, and demonstrate how enquiry actions will be tested. Compare clarity and evidence, not just the visual mock-up or lowest price.
Next step
Need help scoping a business website? Review our website design service or contact CodeMarkers with your page list and goals.
