Start with the job it needs to do.
A company website may need to explain complex services, present projects or attract suitable enquiries. Those goals determine its pages and information hierarchy. Before discussing colours, establish who will visit and what they need to be able to do.
Content is part of the project.
Clarify who writes the copy, selects images and organises translations. Page count alone does not describe the work involved. A useful service page needs an explanation, deliverables, examples and answers to the customer’s actual questions.
Custom design means considered decisions.
An original design starts with your content and identity. Using established code libraries does not turn it into a template. The difference is whether structure, visuals and journeys were designed for the particular business, including mobile and accessibility needs.
Handover needs clear boundaries.
A proposal should define features, revisions, integrations, languages, file ownership and access. It should also distinguish the initial project from hosting, third-party licences and future support. This makes it possible to compare the actual value of two proposals.
Written by the Omnica team.