Blog / Web design
Website costs in 2026: plan operations and changes
What costs continue after a website launches? Plan hosting, licences, maintenance, content and later changes as separate budget items.
Updated on
The build price is only part of a website budget. Once the site is live, someone must look after its operation, content and changes. This guide helps you plan those responsibilities separately. It is not a market-price survey or a list of Senorit package prices.
Define the one-off work
List planning, design, development, copy, images, data migration and training separately. The proposal should say which content you supply and which the agency creates. A contact form and a booking system with calendar synchronisation are different scopes.
Agree acceptance criteria too: supported devices, form delivery, redirects, editorial access and documented performance measurements. A high lab score cannot replace testing the full enquiry journey.
Assign ownership to every recurring cost
Record the provider, billing interval, renewal date and owner of each item. Check whether tax is included and whether charges depend on usage or the number of users.
- Domain and DNS: document ownership, access and annual renewal.
- Hosting and database: check storage, traffic, backups and overage charges.
- Licences and services: list booking, email, maps, media and payment fees separately.
- Maintenance: agree updates, restore tests, monitoring and response times.
- Editorial work: allow time for copy, services, photography and translations.
Calculate the first year of operation
Illustration only: suppose an individual proposal quotes EUR 5,000 for the build. You add EUR 300 a year for hosting and the domain, EUR 600 for licences and EUR 100 a month for agreed maintenance. The first-year total is EUR 7,100. Actual proposals must establish whether these assumptions fit your project.
The original build does not recur in year two unless you plan another rebuild. New content, features or usage charges may arise instead. Budget for changes separately rather than assuming a fixed annual percentage of the build price.
Separate support, maintenance and new development
Senorit provides an individual fixed-price proposal after consultation. It includes 30 days of support after launch. The proposal sets out the scope, recurring costs and any additional care.
Document which fixes are included and which requests constitute new work. Another language, new product logic or an extra integration changes the scope. A maintenance agreement should identify the systems covered and the incident reporting process.
Start with a small, complete first version
Prioritise the information and features needed for an enquiry or purchase. Delay extras whose value is still uncertain. Keep access credentials, recovery, clear content and a tested contact path in the initial scope.
Evaluate later spending using your own qualified enquiries, completed sales and contribution margin. Hypothetical extra revenue is not a promised return on investment.
Common questions
Is there a fixed minimum price?
Senorit prices the agreed scope individually after consultation. Example budgets in articles are not binding offers.
Does the build include ongoing care?
It includes 30 days of support after launch. Further maintenance, hosting and development are agreed separately.
How should I compare operating proposals?
Compare the same systems, tasks, response times, terms and usage limits. Check who owns access credentials and how data is handed over when changing providers.
Further reading
