Six months after launch, the prices shown are wrong, the opening hours have changed and the cover photograph is of the old shop. The owner knows, and can do nothing about it: they would have to call the provider back, and the provider no longer answers. The site is new and already false. That scenario is not a technical accident; it is the result of choices made when the work was ordered.
A team, not one person
A web agency brings together skills one person rarely holds all of: scoping and project management, graphic design, development, help with writing the content, sometimes payment integration or data migration.
That plurality is its value — a project passes through different trades — and its difficulty: the client should not have to live with the internal organisation, and one point of contact who knows the file beats four specialists who each need briefing again.
An agency differs from an independent developer less in the size of projects than in how they are run: divided roles, formal follow-up, the ability to absorb one person's absence.
Turning an idea into a scope
"I want a site like that one" is not a brief. It is a starting point, and the scoping work consists in turning it into something verifiable.
A useful scope answers concrete questions: what objectives, what pages, what features, what users, what data, what integrations, who provides text and photographs, what timescales, what deliverables, and above all what is not included.
That last column is the more useful. A project rarely goes wrong on what was written down; it goes wrong on what each side assumed.
"A five-page site" means nothing
Two five-page sites can require unrelated amounts of work. One shows five pages of text and contact details; the other has a form connected to a database, a customer area, payment, migration of existing content and three languages.
What drives cost is not the number of pages: it is the number of features, the complexity of integrations, the level of design, the amount of content, the security requirements, the migration of what exists and the support after launch.
Hence the value of an itemised quotation rather than a lump sum: a client who sees the cost of each feature can drop two to stay within budget. Price levels depend on the market, the country and the agency: no general scale means anything.
A website is not one indivisible block
This is one of the commonest misunderstandings. A live site rests on several distinct elements, which may belong to different people and be paid for separately: the design work, the graphic design, the development, the content, the hosting, the domain name, the associated email and the maintenance.
The domain name deserves particular attention. ICANN, which coordinates the domain name system, publishes a list of registrants' rights and responsibilities: registration is the subject of an agreement with an accredited registrar, the registrant may review that agreement at any time and is entitled to accurate information on pricing, support and the processes for registering, managing, transferring, renewing and restoring the name. In return, they assume sole responsibility for the registration and use of the name, must provide accurate information and keep it current, and must respond to their registrar's enquiries within fifteen days.
The governance rule that follows is simple: the domain, the hosting and the associated accounts are opened in the client's name, even if the agency configures and administers them. A client who cannot change provider without losing their address has not bought a site, they have rented a dependency. Rights over the code and the content are a matter for the contract signed and the applicable law: they are written down, not assumed.
Design serves a journey
Designing a site's interface is not making it pretty. It is deciding what a visitor sees first, what they understand in three seconds, how they reach the information they came for, and what is expected of them.
That means knowing the real users: what they come to do, on what device, in what conditions. A clear hierarchy, understandable labels, consistency from page to page and correct display on a small screen do more than any visual effect.
One common promise is worth resisting: a redesign does not by itself increase sales. It removes obstacles — an unreadable page, a form that fails, a phone number nobody can find. What follows depends on the offer, the price and the competition.
Accessibility: a reference, not a universal obligation
Making a site usable by people with disabilities comes down to concrete choices: sufficient contrast, a consistent heading structure, keyboard navigation, alternative text on meaningful images, labelled forms, readable content.
The international reference is the Web Content Accessibility Guidelines published by the World Wide Web Consortium through its Web Accessibility Initiative. They have the status of a W3C Recommendation, are organised around four principles — perceivable, operable, understandable and robust — and define three conformance levels, A, AA and AAA. Versions 2.0, 2.1 and 2.2 follow one another while remaining compatible.
One point deserves stating clearly: these guidelines are not legally binding by themselves. They become so where national legislation adopts them, which some countries do and others do not. A serious agency applies them as professional good practice, and separately checks what local law actually requires.
Application security from the design stage
A public site is permanently exposed, and most attacks are automated: they do not choose their targets.
The most widespread defensive reference is the OWASP Top 10, published by the OWASP Foundation. That awareness document, aimed at developers and web application security teams, sets out the most critical risk categories for web applications and serves as a first step towards more secure development. It is used as a defensive checklist, not as a catalogue of techniques.
In practice: keeping the software base and its components up to date, validating incoming data, limiting the rights of technical accounts, logging what needs logging, holding tested backups. An agency that delivers without saying how the site will be updated leaves a vulnerability that grows on its own.
Acceptance, delivery and handover of access
A project does not end by sending a link. Acceptance testing is a stage in its own right: the client goes through the site, tests the intended journeys, flags anything that does not match the scope, the agency corrects, and it is checked again.
Delivery then includes what makes the client self-sufficient: access to the administration interface, accounts and their rights, short documentation of what they can change themselves, training in using it, the state of the backups, the contact details of the host and the registrar, and the list of renewal dates.
Passwords are handed over carefully: named accounts rather than a shared one, rights limited to what is necessary, stronger authentication where available, and the provider's access revoked when the engagement ends. A password circulating in a group chat or stored in an unprotected file cannot be taken back.
Maintenance: what is included, what is not
Not every request after delivery is covered by the initial price. Four things need separating: correcting a defect against the agreed scope, technical maintenance of the platform, an enhancement adding a new feature, and help with using it.
A legible contract says what is covered, how often, with what response times, what happens to backups, and how out-of-scope requests are handled. The times announced are the agency's commitment, not a standard, and no duration is universal.
Search visibility: what can be worked on, what cannot be promised
Organic search visibility can genuinely be worked on: useful and current content, a coherent page structure, relevant titles and descriptions, correct indexability, performance, accurate local information, reputation.
What cannot be promised is equally precise: no first place, no guaranteed number of visitors, no certain timescale for ranking. Rankings depend on algorithms that are neither public nor stable, and on competition nobody controls. An agency selling a ranking result is selling something it does not control.
Performance: the site must open where the customers are
A site tested on a fast office connection can be unusable elsewhere. The weight of images, the number of resources loaded, caching and behaviour on mobile determine whether the page appears or the visitor leaves.
The International Telecommunication Union states that 74 per cent of the world's population uses the Internet in 2025, some six billion people, and that 2.2 billion remain offline. It also notes that mobile broadband coverage is nearly universal, but that gaps in quality and affordability persist. In other words: connectivity is progressing, connection quality remains very uneven, and a site should be built for that reality rather than for its designer's connection.
In African contexts
Working conditions vary sharply from one country and one city to another, and there is no single African context. The ITU puts internet use at 36 per cent for Africa in 2025, the lowest of the regions it measures, with 23 per cent in low-income countries — but those averages cover situations with nothing in common between a capital's business district, a secondary city and a rural area.
Several practical consequences follow, depending on the place. Where the connection is metered by volume or irregular, making pages lighter is not a refinement but a condition of use. Where most traffic comes from phones, design starts with the small screen rather than adapting to it afterwards. Where mobile money is the ordinary means of payment, a shop must integrate it to exist commercially — and the available solutions differ from country to country.
Other elements follow the same reasoning: the availability and cost of local hosting, whether national domain extensions exist and on what conditions, the applicable data rules, and how formalised the clients being served are. Each is checked locally; none is deduced from the continent.
What an agency does not guarantee
A web agency guarantees neither a ranking, nor a volume of visits, nor revenue, nor total availability of the site. It depends on a host, a registrar, an operator, sometimes a payment service or a software library: it cannot commit on a chain it does not fully control.
What it does commit to can be checked: a written scope, an itemised quotation, approved mock-ups, joint acceptance testing, a site matching what was ordered, training, documentation, access handed over in the client's name, and a maintenance contract that says what it covers.
That is also what makes an agency credible: a stable name and contact details, completed work presented as it is, legible quotations, invoices, request tracking and verifiable references. Artificial intelligence can help draft content, produce design variants or prepare documentation; it can also be wrong, produce inaccurate text or reuse protected content. What is delivered to the client remains the agency's responsibility, and is read before it goes out.
Finally, this article describes a trade; it replaces neither a brief nor legal advice. The rules mentioned vary from country to country.