Start with the job the website needs to do
Before requesting quotes or choosing software, write down the website’s main purpose. A small community organization might need visitors to find opening hours, understand its services and submit an enquiry. A membership group might also need event listings and a way to join. These are different projects, even if both begin with a homepage.
List the pages, features and integrations needed to support those goals. Separate essentials from ideas that can wait. For example, clear service pages and a working contact form may be essential, while a searchable archive could be a later improvement. This distinction helps you budget for a manageable first release without losing sight of future work.
Decide how you will judge whether the site is doing its job. Useful measures might include completed contact forms, visits to key information pages or fewer requests for information already published online. You do not need an elaborate measurement setup, but agreeing on a few questions early can prevent spending on features no one plans to use.
Separate launch costs from recurring costs
Create two columns in your budget: costs to plan and launch the site, and costs that continue afterward. Launch costs may include discovery, content writing, design, development, accessibility checks, testing, staff training and moving material from an old site. Ask suppliers to show which of these are included in a proposal rather than assuming that “website build” covers everything.
Recurring costs commonly include a domain name, hosting, software or plugin subscriptions, backups, technical updates and support. They may also include email services, form tools, image licensing or fees for systems connected to the site. Some services renew automatically or change price after an introductory period, so record the renewal terms as well as the initial charge.
Budget for people’s time, even when staff or volunteers will do the work. Publishing an event, checking a form submission, replacing an outdated document and reviewing a page all require attention. If those tasks have no named owner or available time, a low-cost website can become difficult to maintain.
Price the work that keeps the site useful
Content is not finished at launch. Identify pages likely to change, decide how often they need review and assign an owner. For a small service organization, that might mean checking contact details whenever staffing changes, reviewing service information periodically and removing past events promptly. Include time for writing, editing, image preparation and approval, not just the final act of publishing.
Plan for routine checks of the user experience. Someone should periodically try important tasks on a phone and with a keyboard, check that links and forms work, and confirm that instructions still make sense. Accessibility is easier to sustain when it is part of ordinary updates: staff can use descriptive link text, meaningful headings and alt text for informative images as they publish.
Measurement also needs upkeep. Decide who can access the reporting tools, who will review the agreed measures and what they will do with the findings. A brief regular review that leads to a clearer page or a simpler form may be more useful than paying for a complex dashboard that nobody opens.
Turn estimates into a workable plan
Use a simple worksheet with a row for each item, its expected frequency, its owner and how certain the estimate is. Request comparable quotes using the same list of requirements. Ask what happens after launch: who applies updates, how support is requested, whether backups can be restored and what work incurs an extra charge. Where costs are uncertain, label them rather than hiding them in a single total.
For example, an organization launching a five-page site might pay a supplier for design and setup while its staff provide approved text and photographs. Its continuing plan would still need room for hosting, domain renewal, software maintenance, staff content time and occasional supplier support. If the organization expects to add online bookings later, it can list that as a separate future project instead of treating it as a free addition.
Allow some flexibility for changes and repairs. The right amount will depend on the site’s complexity and the organization’s tolerance for interruptions. A contingency line makes it easier to handle an unexpected compatibility issue or a needed content revision without taking money from essential operating costs.
Make ownership part of the budget
A budget is most useful when it also records decisions. Keep a short handover document with account owners, renewal dates, support contacts and the steps for updating, backing up and restoring the site. Limit access to people who need it, use strong unique passwords and enable multi-factor authentication where available. These everyday practices require modest time but help reduce avoidable disruption.
Review the budget alongside the website plan at least once during each budgeting cycle and whenever the site’s purpose changes. Compare expected costs with what you actually paid and note work that was postponed. The goal is not to predict every future expense; it is to make the ongoing responsibility visible so the website can remain useful long after launch.
