Business with or without a website: what changes for customers and the team?
The most useful difference between having and not having a website lies in the tasks customers and the team can complete. A website can gather information, support a proposal and receive organised enquiries. To assess the investment, compare those journeys in your business and define what needs improving.
By the end, you can:
- Compare the current journey with the intended one
- Define the smallest website that meets the need
- Assess the investment with evidence and full costs
Compare capabilities, not labels of success
A company without a website may have loyal customers, good recommendations and effective support. A company with a website may present outdated information or lose enquiries. A domain alone does not demonstrate quality, profitability or trust: the difference should appear in a task made easier or better organised.
Start with observable situations. Can someone confirm the service outside support hours? Can you send a link with current terms? Does the team receive enough context to reply? A well-prepared website can address these needs; its value depends on implementation and use.
| Task | Without your own website | With a website prepared for the task |
|---|---|---|
| Confirm a service | Checks profiles or directories, or asks the team | Consults a page bringing together scope and terms |
| Share information | Sends scattered messages, files or posts | Shares a specific, updated address |
| Request a proposal | Uses available channels and sends context across several messages | Completes a request with relevant fields and confirmation |
| Track demand | Depends on existing channel records | Can connect enquiries to a process and defined measures |
Observe the current journey before buying technology
Choose a service and write a task: “Find out whether the company does this work, which information you need to send and how to request a proposal”. Ask people uninvolved in the company’s communications to carry it out. Use examples without personal data and do not explain where to click.
Record the starting point, questions, missing information and final action. A small observation session reveals specific problems but does not estimate market percentages. If everyone asks about the same requirement, you have a clear hypothesis for a page; if the difficulty is replying, you also need to review operations.
See the change in a fictitious example
Oficina Norte, a fictitious equipment-maintenance company, receives enquiries by email and messaging. The team keeps asking for the equipment type, symptom and service location. The proposal is to create a support page with service limits and a structured enquiry.
The website does not automatically diagnose a fault or confirm availability without checking operations. It explains what the team needs to know, confirms receipt and records the request. The benefit to assess is the quality of the context received and the work of preparing a reply; the example does not represent results from a Lyntev customer.
- Current situation
Messages arrive with incomplete information and in different formats.
- Proposed page
The visitor confirms the scope and prepares the necessary data.
- Request received
A reference links the data to the team’s next action.
- Comparison
Assess repeated questions, complete requests and preparation time.
Choose the smallest scope that solves the problem
A clear page may be enough to present a service and facilitate contact. Several services with different criteria may need their own pages. Reservations, payments, orders or customer areas add statuses, rules and tests. Choose those functions because they serve the process, including who maintains them.
Separate what is needed to start from what can evolve. Define content, main action, confirmation, enquiry destination and approval evidence. A large catalogue without prepared materials can delay delivery; an automatic function without an owner for exceptions can transfer the problem to support.
| Need | Possible scope | Evidence it works |
|---|---|---|
| Present an offer | Service page and contact options | The visitor explains the service and finds the action |
| Receive complete enquiries | Form and routing | A valid enquiry arrives with reference and context |
| Organise appointments | Calendar with availability and rules | Conflicts and cancellations are handled |
| Sell online | Catalogue, order, payment and follow-up | Purchase journey and exceptions tested |
Include discovery and use in delivery
A new website needs links in places where the company is already found: profiles, signatures, proposals and relevant communications. Google’s documentation explains that search engines need to discover and understand pages. Search is one area of work; the website should also serve visitors arriving through recommendations or direct links.
Check that information and actions work at different screen sizes, with a keyboard and with enlarged text. W3C describes accessibility as a component that broadens the ability to use a service. In a quote request, clear labels, visible focus and understandable errors are part of the main function.
Calculate costs including continuity
Compare creation, materials preparation, domain, hosting, maintenance, changes and team work over the same period. Confirm what is included and the conditions for ending or transferring the service. An isolated starting price cannot compare proposals with different scopes.
If you want to assess financial return, use contribution margin and costs the company actually knows. “Additional completed sales × average contribution margin per sale” is a hypothesis, not a sales forecast. Enquiries received are not yet completed sales. Separate new revenue from time freed up and do not count the same benefit twice. To begin, recording real tasks and costs is usually more useful than giving every visit a fictitious value.
Define how you will assess the result
Before publication, record the definitions of measures and the current process. Afterwards, track valid enquiries, missing context, response time and journey completion. Also observe qualitative problems: a page may reduce questions even if the number of enquiries stays similar.
Compare periods with comparable demand and operational capacity. Campaigns, seasonality, prices and support changes influence results. An increase after publication does not, by itself, prove causality. Use the comparison to decide the next improvement and identify where information is still missing.
- Confirm enquiries reach the right destination.
- Review repeated questions the page still does not answer.
- Distinguish enquiries received from eligible enquiries and business won.
- Repeat the usability test when content or functionality changes.
Prepare the decision with this worksheet
The decision is grounded when you can describe the problem, scope and acceptance evidence. You may proceed with a small website, improve an existing one or prepare materials and support first. In every case, you have an executable next step and an evaluation criterion.
Worksheet for your project
Decision about the company website Priority service or journey: How it works today: Observed difficulty and evidence: What the customer should be able to do: Information that needs to be available: Initial scope and excluded functions: Who maintains content: Who receives and follows up enquiries: Creation and continuity costs over the chosen period: Measures and definitions before the change: Acceptance test: Timing and person responsible for review: Next decision:
Sources and criteria
Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.
