ShapedSI Journal · Web & software
Website design in Canada: shape the customer’s next step
A business website needs to help somebody understand the offer and take the next useful step. Start with the person visiting it: what they need to know, what they need to trust and how they can reach your team. The visual direction should make that journey feel clear and consistent on a phone as well as a larger screen.
In this guide
01
Make the offer understandable
Write a short description of what the business does, who the service is for and where it is available. Put that information near the beginning of the page. Avoid asking a visitor to infer the offer from a slogan or a collection of technical terms. A service page can be specific without making promises the team cannot keep.
Choose a primary next step for each page. It might be an enquiry, a call, a booking request or a purchase through a separate checkout. Explain what happens after that step. Collecting an enquiry should not look like a confirmed booking, and a request for a quote should not suggest that the final scope is already agreed.
02
Use evidence the business can stand behind
Gather accurate service descriptions, current contact details and examples you have permission to share. For a portfolio item, explain the work and the business’s role in it. If an image is an illustration or a concept, label it accordingly. The page should help a visitor distinguish an actual project from a visual direction.
Choose a manageable set of content to maintain. A few useful service pages are easier to keep accurate than a large collection of pages that repeat the same offer. Give somebody responsibility for checking availability, descriptions and contact information when the business changes.
03
Design the enquiry for a real person
Ask only for the information the team needs to begin a reply. Give each field a clear label and explain an unusual request. Show useful feedback when a field is missing or the form cannot submit. Include a phone option if it is part of the business’s normal service.
Test the complete handoff. A successful screen message is only one part of it: the request must reach the intended destination, carry enough context and remain accessible to the person following up. Review the form on a phone, with a keyboard and with the labels and error messages visible.
04
Choose a site the team can operate
Agree on who controls the domain, hosting, content and analytics accounts. Document how to update a page, where enquiries are stored and who handles a broken integration. Those decisions matter when the site launches and when you eventually change providers.
Before publishing, test the pages people are most likely to use, the contact options and any purchase path. Use the actual text and images, rather than judging an unfinished template. Once the site is live, keep a short routine for checking the important links and reviewing enquiries for signs of confusion.
Bring this to the conversation
A working brief.
- A specific service description
- One clear next step per page
- Accurate proof and image labels
- Accessible fields and error messages
- Domain, account and maintenance ownership
A few useful questions.
How many pages do we need?
Enough to answer the customer’s important questions clearly. Start with useful service and contact pages, then add content where there is a distinct need.
Is the visual style the first decision?
It helps to agree on a direction early, but the offer, evidence and customer journey give that direction something useful to communicate.
Original sources
Sources and further reading.
W3C’s forms guidance explains how labels and structure help people understand and operate form controls, including with assistive technologies. Treat that as part of the enquiry design.
Shape the next step