56KGen · Viewport

That window is a bit too cramped

Give the browser a little more breathing room so the interface can render properly.

Width ≥ 320 pxHeight ≥ 250 px

Everything will snap back into place once the window is wide enough.

← All articlesWebsites & experience

Which features should a business website have first?

Begin with what customers need to do, rather than a long feature list. A practical way to prioritise a new website.

2 min read

Begin with what customers need to do, rather than a long feature list. A practical way to prioritise a new website.

Do not start with the number of pages

Before asking how many pages a website needs, write down three things customers want to know: what the business does, whether it suits them and how to make contact. A short structure answering those questions clearly is often more useful than many repetitive pages.

Review the questions customers ask by phone or message. They are useful material for service content, frequently asked questions and forms.

Prioritise information that supports decisions

Each service should explain who it suits, the problem it solves, how it is delivered and the next step. If you publish a price, put its conditions nearby so customers understand the scope.

Project images are useful when viewers understand the original problem and the work completed. Only publish names, images and results you have permission to share; clearly label a demonstration as a demo.

Make one contact path work well

A consistent action button and a short form show customers what to do next. Ask only for information needed to start a conversation; do not require an account just to send an enquiry.

After submission, customers need to know whether the request was received. If it fails, keep their input and allow another attempt. The business also needs someone responsible for reviewing requests.

Add features when there is work for them to support

Search helps when a catalogue or content collection is large enough. Member accounts help when customers have private data to view or manage. Booking only makes sense when someone manages availability and confirmations are clear.

For each feature, ask who uses it, why and who maintains it after handover. If those answers are unclear, it can wait for a later phase.

Before implementation

Prepare the main content; identify the priority action; check on phones; test forms and result messages; and agree who updates content and receives enquiries.

A website can start small. What must be clear from the beginning is its goal, scope and how you will know it serves the work.

Keep reading

All articles ↗