A practical guide for teams preparing a website budget in 2026, with the scope decisions, ownership questions and delivery evidence needed before any price can be credible.
There is no honest price before there is an honest scope
Search for website design cost in Kenya and you will find confident numbers attached to vague labels such as basic, professional or corporate. The trouble is not that every range is wrong. It is that the label usually tells you almost nothing about the work. A five-page brochure assembled from approved copy is a different engagement from a multilingual corporate site with stakeholder review, accessibility testing, analytics, migration and an integration to a live business system.
Avidni does not publish a universal price band without approved pricing assumptions. That would turn an estimate into theatre. A useful budget begins with the audience, content volume, approval process, technical dependencies, risk and ownership after launch. If a supplier produces a figure before asking about those matters, the missing questions have not disappeared. They are likely waiting as exclusions, change requests or compromises.
What a serious website budget actually buys
| Workstream | What it should cover | Evidence to request |
|---|---|---|
| Discovery and scope | Audience, business goals, page inventory, integrations, responsibilities and acceptance criteria | Approved brief, sitemap and scope boundaries |
| Content | Research, interviews, copywriting, editing, migration, image selection and approvals | Content matrix with a named owner and due dates |
| Experience design | Information architecture, page journeys, responsive layouts, accessibility and interaction states | Reviewed wireframes and interface designs |
| Engineering | CMS setup, components, forms, integrations, security controls and deployment | Working staging site, repository and release notes |
| Quality assurance | Browser, device, form, accessibility, performance and content checks | Test record with defects and resolutions |
| Launch and migration | Domain, redirects, analytics, search controls, backups and rollback planning | Launch checklist, URL map and verified production checks |
| Handover and care | Accounts, training, documentation, update responsibility and support boundaries | Access register, handover pack and support agreement |
The six decisions that move the estimate
- How many distinct page types are required, not merely how many menu links?
- Who writes, verifies and approves the copy, and in how many review rounds?
- Does existing content move cleanly, or must it be audited, rewritten and redirected?
- Which systems must the site exchange data with, and who controls those accounts?
- What level of accessibility, privacy, security and performance evidence is required?
- Who owns updates, incidents and improvement work after launch?
A focused website can still be excellent. The goal is not to make every project large. It is to stop small words from hiding large responsibilities. For example, one enquiry form may require spam controls, consent language, file handling, routing, acknowledgements, analytics and a failure path. Calling it ‘just a form’ does not remove that work.
Use scope bands before you use price bands
A focused business site normally has a limited set of audiences, page types and integrations. A corporate publishing site adds a deeper content model, multiple reviewers, governance, migration and reporting. Commerce and portal work introduces transaction states, permissions, operational data and support obligations. These are useful scope bands because they describe complexity without pretending that two projects in the same band are identical.
Accessibility and performance belong inside the scope, not in a polite footer. The Web Content Accessibility Guidelines provide a testable reference for access needs, while Google defines good Core Web Vitals around loading, responsiveness and visual stability in its Web Vitals guidance. Neither is achieved by adding a plugin on launch day.
The cheapest proposal may simply postpone the cost
Watch for proposals that omit content responsibility, mobile layouts, redirect mapping, form delivery testing, analytics access, backups, source files, administrator training or post-launch support. The headline fee can look tidy because the business is being asked to carry the unpriced work later. A low fee is not automatically a problem. An unexplained fee is.
What to send when requesting an estimate
- A short description of the business problem and the decision the website should improve.
- The primary audiences and the most important action for each one.
- A current page or content inventory, even if it is rough.
- Known integrations, languages, legal reviews and approval roles.
- Examples of evidence required at handover, such as training, accessibility checks or redirect reports.
- A realistic target window and any fixed event that creates it.
That information gives a Business Websites team enough context to challenge assumptions and price the work that must actually happen. It also makes competing proposals easier to compare because each supplier is answering the same problem.
A useful number comes after useful questions
The right website budget is not the highest one your company can tolerate. It is the amount attached to a clear release, named responsibilities and evidence that the finished site can be operated. Start there, and the estimate becomes a decision document rather than a hopeful total at the bottom of a PDF.
Request a Scope-Based Estimate