# Web development for businesses: from needs to a website that works

> Does your business need a new website, online store or web app? Use a concrete specification to choose the right solution and verify the delivery at launch.

By Media Access. Published: 2026-09-06. Updated: 2026-09-06.

Original: [Web development for businesses: from needs to a website that works](https://mediaaccess.uk/insights/web-development-for-businesses/)

A new website for your business should do a specific job: explain the offer, generate relevant enquiries, sell products or let the customer complete a task on their own. When that job is clear, it becomes easier to assess the technology, scope and price.

This guide is about buying web development services. It helps you write a solid request for proposal and check that the delivery works in practice, whether you need a company website, an online store or a web application.

## What you will learn

- Choose the solution based on the customer’s task and the company’s workflow.
- Describe requirements as actions that can be demonstrated and tested.
- Include content, integrations, migration and operations in the order.

## Website, online store or web app?

Start with the most important thing the user needs to do. A website may be the right choice when the customer needs information and then gets in touch. An online store must also handle the purchase and the follow-up around the order. A web app becomes relevant when the user will be working with data, processes or personal information over time.

The boundaries can overlap. A company website can include booking, and an online store can have a customer portal. So ask what needs to work at the first launch. Extra features should be justified by a specific need and a person who will use them.

A starting point for defining the project scope

| Solution | Typical main task | Clarify early |
| --- | --- | --- |
| Company website | Explain the offering and generate enquiries. | Content, editing, contact flow and visibility. |
| Online store | Let the customer choose, order and pay. | Product data, shipping, payment, orders and customer service. |
| Web app or portal | Let the customer carry out a task over time. | Login, roles, data sources, history and integrations. |

## Describe three tasks the site must solve

Choose three important tasks and write them as short situations. For a service business, they might be: a new customer needs to find out whether you cover the area, a buyer needs to understand what a service agreement includes, and an existing customer needs to ask for help.

Review your current solution using these tasks. Note where information is missing, where the customer has to search, and where employees have to do duplicate work. This is a better basis for web design and development than a list of websites you think look nice.

Also describe a successful end point. “The form works” is unclear. “A customer can send an enquiry on mobile, receives confirmation, and the enquiry appears with the correct person responsible” can be demonstrated. This is how you connect the visual work to an actual delivery.

## Write a requirements specification you can use

Split the requirements into must-have at launch, should-have and can-wait. Each requirement should have an owner and a simple way to approve it. Ask the supplier to explain assumptions, dependencies and what falls outside the proposal.

The table shows suggested requirements. Adapt the details to the business, especially roles, integrations and what you need to be able to change yourselves.

Examples of requirements that can be verified

| Area | Requirement | How it can be approved |
| --- | --- | --- |
| Content | An editor can update service text and contact information. | An employee makes the change after training. |
| Contact | Submitted enquiries go to the correct team. | A labelled test is tracked from form to recipient. |
| Mobile | Key tasks work on small screens. | The tasks are completed on the agreed phones and browsers. |
| Integration | Agreed fields are transferred to the correct system. | Test with both complete and incomplete submissions. |
| Handover | Access, documentation and operational responsibility have been clarified. | The company receives and checks a handover list. |

## Assign the content an owner before the design is finished

A new solution needs text, images and clarified information about the services. Assign responsibility for each page. Decide who can confirm prices, delivery areas, product descriptions and any customer references. Content that is “on the way” should have an agreed delivery date.

Use an actual service page in the design process. It shows whether headlines, explanations, images and call-to-action buttons work together. A polished draft with short sample text can hide problems that only appear when the real description needs to go in.

For an online store, product data needs the same attention. Decide where names, variants, stock status and images come from, and who corrects errors. A new design does not solve unclear product data or unclear responsibilities.

## Agree on quality in use, not just a score

Ask for testing of the most important user tasks on mobile and with a keyboard. Include clear field labels, readable text and understandable error messages. W3C recommends that accessibility be part of the production process and be assessed early and regularly. So make this part of the work from the start.

Performance should also be assessed using real content. Google’s Core Web Vitals describe the loading of main content, responsiveness to actions and visual stability. Use measurements to find problems, and combine them with practical task testing. A fast homepage is of little help if the contact form is difficult to use.

Ask for the test basis to be described: which pages, devices and situations were checked, which errors have been fixed, and what, if anything, remains.

Source: [W3C WAI: Planning and Managing Web Accessibility](https://www.w3.org/WAI/planning-and-managing/)

Source: [web.dev: Web performance and Core Web Vitals](https://web.dev/performance)

## Plan the launch and ownership before the final week

When replacing an existing website, important URLs must be mapped. If the addresses change, Google recommends a plan that links old pages to relevant new pages and redirects traffic. Include this in the scope, together with checks of internal links and important forms.

Agree who owns the domain, the publishing platform and the necessary accounts. The company should know who monitors operations, takes backups where relevant, handles errors and carries out updates. Also describe how you order minor changes after launch.

Set a separate time for handover. The person who will edit the site should try the tasks themselves. Only when content, contact flow, measurement and responsibilities work together do you have a solid basis for using the website in marketing.

Source: [Google Search Central: site moves with changed URLs](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes)

## Questions and answers

### Do we need to choose the technology before contacting a development agency?

Usually, it is better to describe user tasks, editing needs and integrations first. If you have internal system requirements or expertise that should be used going forward, this should of course be included in the needs description.

### Does a small business need a custom-built website?

Not necessarily. Clarify which requirements a standard solution covers, and which needs genuinely require customization. Also compare editing, operations, further development and the possibility of moving later.

### What should we have ready before asking for web development proposals?

Describe the main goal, the most important user tasks, approximate page types, content ownership, integrations and the desired launch. Include the link to your current website and what you want to improve.

## Sources and further reading

- [W3C WAI: Planning and Managing Web Accessibility](https://www.w3.org/WAI/planning-and-managing/)
- [web.dev: Web performance and Core Web Vitals](https://web.dev/performance)
- [Google Search Central: site moves with changed URLs](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes)

## Read more

- [What Does a Website Cost? How to Assess Price and Total Cost](https://mediaaccess.uk/insights/how-much-does-a-website-cost/index.md)
- [Systems development and integrations: when should a business build a custom solution?](https://mediaaccess.uk/insights/software-development-and-integrations/index.md)
- [How to build a landing page for relevant enquiries](https://mediaaccess.uk/insights/landing-pages-that-generate-enquiries/index.md)

[Discuss your company’s new website](https://mediaaccess.uk/contact/)