Before designing your website, define what it needs to solve.
A website starts with a business decision. These questions turn an idea into a project with a clear scope.
Start with a specific action
When a brand needs a website, the conversation often starts with colours, references and animation. At Agave, we prefer to start a step earlier: what should someone be able to do after visiting?
They might request a quote, book a meeting, buy a product or understand a service. Choose one primary action. It gives you a way to organise content and decide what the project needs.
Describe who you are speaking to
Someone who already knows your brand needs a different explanation from a first-time visitor. Write down what they know, what they need to compare and which questions they must answer before making contact.
A service business may need to explain its process, show past work and clarify its options. A store needs visitors to understand its products, purchase conditions and next steps.
Separate content, features and integrations
Content explains: copy, photography, projects and frequently asked questions. Features let people act: search, filter, submit a form or buy. Integrations connect those actions with your team’s work.
If a form should create a record in another tool, define which data it sends, who receives it and how the enquiry will be handled. These decisions belong in the scope, even when they are invisible in a design screenshot.
Plan how it will be maintained
Before publication, agree on who updates the content, which information changes frequently and who handles messages. A website needs a way to remain useful after the initial project ends.
Not every brand needs a custom dashboard. Some need a simple content structure; others need roles, approvals or a catalogue connected to their operation.
A brief you can prepare today
Write one sentence for each point: main objective, audience, expected action, available content, required features and the person responsible for updates. Add two references and explain what you find useful in each.
These answers move the conversation beyond appearance. They define what the website should solve, what to build first and how you will recognise whether it is working.
