A city website is not a purchase. It is a recurring line item that spans technology, content, compliance, and staff time, and it competes for funding against street resurfacing and pension contributions. The cities that get one funded are not the ones with the best design mockups, they are the ones that bring finance a request structured the way finance already thinks.
This guide covers where a website belongs in your budget structure, what the request should contain, and how to present it so it survives council review.
Decide which budget it belongs in first
Most cities separate spending into an operating budget, a capital improvements budget, and a longer-range capital plan. A website can legitimately land in more than one. A platform purchase, migration, and redesign are often treated as capital improvement; subscription fees, hosting, and support are almost always operating costs.
Settle this with your finance director before you write anything else, because the classification determines the approval route, the funding source, and the fiscal year you are actually targeting. A request submitted to the wrong track loses a full budget cycle.
Build the departmental request from evidence, not estimates
The budget process usually opens several months ahead of the fiscal year, when the budget officer asks department heads for their submissions. The default method is incremental. Take last year’s number, adjust for inflation, submit. That works for utilities and office supplies. It does not work for a system your city has never bought before.
If there is no prior-year line to increment, build the baseline yourself. Inventory what the city currently spends on website-adjacent work, including the parts nobody has ever added up:
- Hosting, domain registration, SSL, and any legacy maintenance retainer
- Separate subscriptions for forms, surveys, payment processing, event calendars, agenda management, or mass notification
- Staff hours spent on routine content updates, re-keying paper forms, and answering phone calls that a working website would have deflected
- Any accessibility remediation already being paid for on a per-project basis
Most cities that run this exercise discover they are already paying four or five vendors for overlapping functions. That reframes the request entirely: it stops being a new expense and becomes a consolidation. Consolidation is a far easier argument to win.
Line items a complete request should show
- Platform licensing or subscription
- Domain registration and secure hosting
- Design, information architecture, and content migration
- Accessibility remediation and ongoing conformance testing
- Staff training and documentation
- Security monitoring and incident response
- Forms, payments, and service request tooling
- Events and news publishing
- Emergency notification and multi-channel communications
- Contingency — migrations surface content nobody knew existed
Budget accessibility as its own line
Accessibility is a regulatory obligation with a date attached, and it is the line item cities most often leave out. Under the DOJ’s Title II rule, municipal websites must conform to WCAG 2.1 Level AA by April 26, 2027 for populations of 50,000 or more, and April 26, 2028 for smaller entities and special districts.
The work is not only design. It includes remediating documents, labeling forms, testing with assistive technology, and re-testing as content changes. Cities that absorb this in-house pay for it in staff hours whether or not it appears in the budget. Cities that skip it carry legal exposure instead, and because Title II’s underlying nondiscrimination duty is already in force, that exposure exists now, not from 2027.
When comparing vendors, ask specifically whether conformance testing is included in the subscription or billed as a separate engagement. That single question can move the five-year total by a substantial margin, and vendors quote it inconsistently.
Present current state against proposed state
Councils and finance directors respond to comparisons, not to feature lists. Put the two columns side by side:
- What the city pays today across all tools, contracts, and staff time
- What the consolidated proposal costs
- What is retired in the process
- What risk is removed: specifically, accessibility exposure with a regulatory deadline attached
Then attach the request to priorities the council already cares about: emergency communications, economic development, hiring, and transparency. A website request framed as an IT project competes with IT projects. A website request framed as the delivery channel for public safety notifications and permit applications competes on different terms.
Watch the total cost of ownership, not the launch price
The most common budgeting error is funding year one and nothing after it. Ask any prospective vendor for a five-year total that includes renewal escalators, per-module fees, overage charges, and the cost of exporting your content if you leave. A low launch price with an aggressive renewal curve is a worse deal than a flat subscription, and it will land on a successor’s budget rather than yours.
Frequently asked questions
Which budget category covers a municipal website?
It varies by city. Many treat the initial platform purchase, design, and migration as a capital improvement, and subscription, hosting, and support as operating costs. Confirm with your finance department before submitting, because the classification determines the approval path.
What does a city website cost?
There is no single figure; it scales with population, feature scope, how much legacy content needs migrating, and your procurement method. Rather than anchoring on a published range, request itemized quotes from at least three vendors and compare them line by line, since what each includes in a base price differs substantially.
When should we start the budgeting process?
Start at the departmental request stage, several months before the new fiscal year opens. Document current spending, define required features, and coordinate with finance early. If accessibility conformance is part of the scope, work backward from your April 2027 or 2028 deadline. Remediation and testing take longer than procurement.
Can a new website reduce other costs?
It can, and quantifying that strengthens the request. Online forms and payments reduce paper, postage, and counter traffic. Self-service reduces call volume. Consolidating overlapping subscriptions removes contracts. Document those offsets to show net cost rather than gross.
Should we budget for one platform or several tools?
One contract with one renewal date is easier to track, audit, and defend than five small contracts spread across departments and it usually costs less in aggregate. The trade-off is vendor concentration risk, so weigh the exit terms carefully before consolidating.
Planning a website budget for the coming cycle? Run a free accessibility audit of your current site to size the remediation portion of your request, or book a 30-minute call and we’ll walk through the line items with you.
