Websites for SMEs: Key Questions Before Creating or Redesigning Yours

Your business receives enquiries through referrals, social media or phone calls, but when someone looks for information before getting in touch, they find an outdated, incomplete website—or no website at all. The question is usually not whether an online presence is worthwhile, but what an SME website needs to achieve in order to be worth maintaining.

The short answer is this: a website should clearly explain what you do, who it is for and what action the interested person should take next. By the end of this guide, you will be able to decide whether you need an informational website, a website designed to generate enquiries, an online shop or a project with more specific features.

Defining questions

What is a website for SMEs?

It is a digital space that presents your company's activity and enables specific actions, such as requesting information, booking an appointment, downloading documentation, making a purchase or accessing a private area.

It does not have to be extensive or include every conceivable feature. Its format depends on its purpose. A service business may need to explain each service and collect well-defined enquiries. A business with a catalogue may require a structure that helps users find products. If there are internal rules, multiple user profiles or complex processes, the need may go beyond a corporate website alone.

What should my website achieve?

It should fulfil a primary objective that you can recognise in practice. For example:

• Explain an offering that is currently unclear or communicated inconsistently.
• Help an interested person reach the right contact channel.
• Centralise information your team repeatedly has to provide.
• Present services, products, locations or resources in an organised way.
• Enable a specific action, such as submitting an enquiry or booking an appointment.

It is best to define the change you are looking for first and leave the technology until later. “I want a modern website” expresses a visual preference, but it does not indicate what visitors should do or how you will know that the website is fulfilling its purpose.

Are a corporate website and an enquiry-generation website the same thing?

They can overlap, but not necessarily.

A corporate website presents the company: its activity, services, team, contact information and other relevant content. A website designed to generate enquiries also structures the journey towards a specific action. This means deciding what information someone needs before writing to you, which questions should be addressed and what should happen when a form is submitted.

The difference is not merely aesthetic. It affects page structure, messaging, forms and the way you check whether enquiries reach their intended destination.

Scope questions

What pages does an SME need?

The necessary pages are those that allow users to understand your offering and complete the main action without leaving important questions unanswered.

In many cases, an initial structure may include a homepage, service or category pages, a company overview and a way to get in touch. However, this structure should not become a fixed rule. If you serve different audiences, have several business lines, need to display a catalogue or need to explain the process of engaging your services, the architecture may change.

Before deciding on the menu, answer these questions:

• Who visits the website, and what do they need to know first?
• What service, product or need are they trying to address?
• What action do you want them to complete?
• What information do they need to provide so your team can handle the enquiry?
• What content do you already have, and who can review or approve it?

Should I prepare the copy, images and documents before starting?

You do not need to have everything finished in order to define the project, but you should know what already exists, what is missing and who will be responsible for each part.

Content affects scope. Pending copy is not a minor detail if a page depends on it; nor are an image gallery, a catalogue, technical data sheets or a version in another language. Identifying these elements from the outset prevents the structure from being built around information that is not yet available.

It is also helpful to separate content from design. Design helps organise and make a message readable, but it does not replace a precise explanation of what you sell, how you work or what an interested person should do.

What should a contact form include?

It should collect only the information needed to handle the enquiry and work in a verifiable way.

Asking for “a form” is not enough. Define its fields, which ones are mandatory, who receives the messages and what confirmation the person will see after submitting it. It is also important to anticipate what happens if information is missing, submission fails or the message needs to reach more than one recipient.

If the form collects personal data, the applicable obligations and legal texts should be reviewed by the appropriate person or adviser. The website can implement what has been defined, but it does not replace that validation.

Which features should be included in the first version?

Those that are necessary to meet the initial objective. The rest can be documented for a later phase.

A useful way to decide is to classify each element as essential, desirable or future. For example, if the objective is to receive service enquiries, explaining the offering and having a defined form may be essential. A private area, integration with an external tool or a calculator may be desirable, but they need a specific justification before being included.

For each feature, ask: what objective does it support? Who will use it? What happens if it is postponed? What does it depend on, and how will you verify that it works? If you cannot answer these questions, it is not yet sufficiently defined to finalise the scope.

Technical questions

Do I need a template or a custom development?

It depends on whether your company's needs fit reasonably well within a standard solution and on the limitations you are willing to accept.

A template may be suitable when the structure, content editing and features are conventional. A custom development may make sense when there are bespoke user journeys, business rules, user profiles with different permissions, connections to other systems or expected changes that a standard solution does not handle well.

Do not choose based on the label. At a minimum, compare the following:

The technical choice should follow from the objective and scope, not be the starting point.

What does it mean for a website to be responsive?

It means that the interface adapts to different screen sizes so that content and actions remain usable on mobile phones, tablets and computers.

It should not be reduced to checking that the page “fits” on a mobile phone. You need to review whether text is readable, buttons can be tapped, forms can be completed and navigation still makes sense on the devices your audience is likely to use.

Do I need to be able to edit the website myself?

It depends on which content changes, how often it changes and who is responsible for keeping it up to date.

If you will regularly update services, news, products, documents or campaigns, you need an editing method that your team can understand. If changes will be occasional, an agreed maintenance procedure may be sufficient. In both cases, it is advisable to define what can be edited without affecting the structure and which changes require technical review.

What happens if the website connects to other tools?

An integration should be described as a flow, not as a word in a list.

If a form sends information to another tool, clarify which data is transferred, when it is sent, who maintains access and what should happen if the external service does not respond. The same applies to calendars, payments, catalogues, management systems or email platforms.

Integrations can add value, but they also add dependencies. They should therefore be included when they solve a specific need and can be maintained clearly.

Limitations and exceptions

Does a website alone guarantee sales or enquiries?

No. A website can explain an offering more effectively, make it easier to get in touch or reduce friction along a journey, but it cannot guarantee commercial results.

The outcome will also depend on factors beyond the website: the company's proposition, demand, clarity of messaging, the channels through which the audience arrives, response speed and competition, among others. It is more useful to define what action the website should facilitate and then review whether that journey is working than to promise an outcome that depends on multiple variables.

Does a website replace the company's internal tools?

Not always. A public website is used to provide information and support external actions. If you need to manage operations, users, orders, documentation, approvals or data governed by specific rules, you may need an application, an integration or an additional internal system.

Sometimes both needs coexist: the website presents the service and collects an enquiry, while an internal system then organises the work. It is advisable to separate them so that a corporate website is not overloaded with functions that require a different approach.

Is launching the website the end of the work?

Not necessarily. After a website is published, operational decisions remain: updating content, reviewing forms, renewing or managing third-party services, maintaining access and deciding which changes warrant a next phase.

Maintenance does not mean exactly the same thing in every project. It may cover technical tasks, support, content changes or functional evolution. This is why it should be defined what it includes, who performs it and what is excluded.

Which decisions require validation beyond web development?

Those related to legal, tax, sector-specific obligations or the processing of personal data should be reviewed by the appropriate professionals in each area.

Commercial content, the terms you communicate, the people responsible for approving changes and access to domain, hosting or external service accounts also require a clear internal decision. A technical solution can implement defined requirements, but it should not assume business or regulatory decisions that have not been confirmed.

The next decision

How do I know whether I am ready to plan a website for my SME?

You are in a good position to start defining it if you can explain, even provisionally, the objective, audience, main action and the content or features that shape the project.

You do not need to have every detail resolved. However, it helps to arrive with the uncertainties visible: which content is missing, which tools need to be connected, who will review decisions and which elements can wait. This conversation makes it possible to separate what is essential from what is secondary before choosing a solution.

If you would like to discuss the scope of your case, you can describe your web development project to AVSISTEC. The starting point will be to understand what the website needs to achieve, what information and features it requires, and which decisions should be defined before building it.