What a municipal website actually costs
You have to put a number in the budget, and you do not want to be the person who put $8,000 next to a line that turns out to be $60,000. The honest answer is that the sticker prices in this market are not comparable to each other — so here is what the components actually cost, what the published prices really are, and the costs that do not show up until year three.
The short version
- Headline prices in this market are not comparable, because the quotes are different shapes: some are one-time, some are monthly, some are per-resident, some hide the build fee inside a five-year term.
- The only number that compares like with like is the five-year total cost of ownership. Ask every vendor for it in writing.
- Published prices really do span from about $73/month at the entry level to six figures for a large-city build. Both are "a municipal website."
- Content migration is the cost everyone underestimates, and it is frequently the largest single line in the project.
- The annual escalator is the cost that only appears in year three. Real, signed public contracts in this market raise the fee by 5% every renewal term. Over ten years that compounds into roughly a quarter more than the flat number you budgeted.
- Accessibility is now a budget line, not an extra. WCAG 2.1 AA is required by the ADA Title II rule and is already written into most municipal website RFPs.
Why nobody will just tell you the number
Search for what a municipal website costs and you will get four vendor blog posts, each of which answers the question in the shape of its own price list. This is not a conspiracy. It is that the products genuinely are priced in incompatible ways, and each vendor naturally frames the comparison on the axis where it looks best.
There are, broadly, four shapes of quote in this market:
- One-time build plus a small annual fee. You pay for design and implementation once, then a modest recurring charge for hosting and support. The big number is at the front.
- Low build fee, high annual subscription. The build looks cheap — sometimes free — because it is being recovered through a platform fee for as long as you stay. The big number is spread out, and it never stops.
- Per-resident or population-tiered pricing. Common at the entry level. Sensible on its face, but it means two towns with identical needs pay different amounts for identical software.
- Monthly-only, no build fee at all. Attractive on a small budget. Usually template-based, and the templates are where the accessibility and ownership questions get interesting.
A $99/month subscription and a $28,000 one-time build cannot be compared as printed. One of them is a rate; the other is a total. The only way to put them side by side is to pick a horizon — five years is the conventional one in municipal procurement, because it matches the typical contract term — and add everything up.
"What is the total amount my municipality will have paid you at the end of five years, including all increases, and what do we own at that point?" Ask for it in writing, in the proposal. A vendor who will not put a five-year total on paper has told you something useful. Our RFP template includes this as a required response field.
The real cost components
Whatever the shape of the quote, the same work has to happen. Here is what is actually in the box — including the parts that are often quietly left out of the headline figure and reappear as a change order.
| Component | What it covers | Where it hides |
|---|---|---|
| Discovery & information architecture | Working out what your site should contain and how residents will find it. Usually a few weeks of interviews and a sitemap. | Often bundled into "design." Ask whether you are getting a real IA exercise or a template with your logo on it. |
| Design | The look: brand, colours, typography, page templates. | "Custom design" sometimes means "choose one of six themes." The word to look for in the contract is bespoke. |
| Content migration | Moving your existing pages, agendas, minutes, bylaws, forms and PDFs onto the new platform — and fixing them on the way. | The one everybody underestimates, and usually the largest hidden cost. See below. |
| Platform licence or subscription | The right to run the software. One-time in an ownership model; recurring in a subscription model. | In subscription models this is the line that carries the escalator. |
| Accessibility conformance | Building to WCAG 2.1 AA, and remediating the documents you are bringing across. | Frequently priced as an add-on, or scoped to "the templates only" — which does not make your content accessible. |
| Training | Teaching the two or three people who will actually publish to the site. | Sometimes one webinar. Ask how many hours, for how many staff, and whether refreshers cost extra. |
| Hosting | The servers, the CDN, the backups, the uptime. | Bundled and invisible in subscription models. Genuinely cheap when bought directly — see below. |
| Domain & SSL | Your .gov or .ca name and the certificate. |
Small money. A .gov domain is free to U.S. governments; certificates are free from Let's Encrypt. Do not pay much for either. |
| Ongoing support & maintenance | Security patches, software updates, someone to call. | Independent agency guidance puts annual external support at roughly 10–15% of the initial project cost. |
| The annual increase | The clause that raises your fee every renewal term. | Page four of the agreement. This is the heart of the piece — keep reading. |
Why migration is the line that ruins budgets
A small municipal website is rarely small. A town of 3,000 people typically has somewhere between 60 and 200 pages, plus a decade of council packets, minutes, budgets, bylaws and permit forms — often several hundred PDFs. Every one of those has to be inventoried, decided about, moved, and (if it is still load-bearing) made accessible.
Vendors quote migration in wildly different ways: a flat "up to 50 pages included," a per-page rate, or "you migrate it yourself in the CMS." That last option is not free. It is a cost you have moved onto your clerk's evenings.
Before you accept any migration number, count two things: how many pages you actually have, and how many of your documents are still used to apply for, pay for, or participate in something. The second number is your real accessibility scope, and it is almost always much smaller than "all our PDFs." We work through that arithmetic in fixing an inaccessible website versus replacing it.
What the market actually publishes
Most vendors in this market publish no price at all — "all projects are custom-quoted" is a common line on a page titled Pricing. But some do publish, and the RFP responses that municipalities file publicly fill in much of the rest. Here is what is genuinely on the record, in ranges. Sources are listed at the foot of the page; we do not name vendors in our copy.
| Tier | Published pricing | What you typically get |
|---|---|---|
| Entry-level subscription platforms | Roughly $73–$137/month, tiered by population, plus a one-time setup fee of roughly $550–$800. One publishes a flat rate starting at $99/month with no setup fee below 10,000 population. | A template site with government-specific modules (agendas, alerts, forms). Fast and cheap. Little or no bespoke design. |
| Small design-and-host shops | Setup $2,000–$4,000 for a town of about 1,000; $5,000–$10,000 for a town of about 15,000. Hosting from $50/month. | A real design pass on a common CMS. Support depends heavily on the shop. |
| Proprietary government platforms | Build fees commonly in the $25,000–$35,000 band for a small municipality, plus an annual platform fee that in real signed contracts we hold runs from about $5,700 to about $11,000 a year — with a 5% annual increase. | A full-service build, modules, training and support — on software you rent. Implementation is often quoted at 16–28 weeks. |
| Independent agency guidance (all vendors) | Population under 8,000: $5,000–$20,000. 8,000–20,000: $25,000–$100,000. 20,000–50,000: $50,000–$125,000. 50,000–100,000: $75,000–$250,000. | Budget guidance, not a quote — but it is the most honest published picture of the spread, and it is not written by someone selling you a platform. |
Two things stand out. First, the spread is real: the same phrase — "a municipal website" — covers a $99/month template and a $125,000 build, and both are legitimate answers for some town. Second, the ranges overlap so heavily that the tier you choose matters far less than the structure of what you sign.
Which brings us to the part that decides your five-year number.
The costs that only show up in year three
Nothing in this section is a secret. All of it is in contracts that municipalities have signed and published. It is simply not in the sales deck, and it is not in the first year of the budget — which is why so many clerks meet it for the first time when a renewal invoice arrives and it does not match the one from last year.
1. The annual escalator
Real, signed public contracts in this market contain a clause providing for "an annual increase of 5% each Renewal Term." That is a verbatim quotation from more than one municipality's signed agreement. We hold the documents and will share them with any municipality that asks.
Five percent sounds trivial. It is not, because it compounds, and because the base it compounds on is the whole platform fee. Here is what a real annual fee — $5,730, taken from a signed contract we hold — does over a decade under that clause.
| Year | Fee that year | Paid to date | Paid to date if the fee never rose |
|---|---|---|---|
| Year 1 | $5,730 | $5,730 | $5,730 |
| Year 3 | $6,317 | $18,064 | $17,190 |
| Year 5 | $6,965 | $31,662 | $28,650 |
| Year 7 | $7,679 | $46,654 | $40,110 |
| Year 10 | $8,889 | $72,071 | $57,300 |
By year ten the fee is 55% higher than the one you were quoted, and you have paid roughly $14,800 more than the flat number in your original budget forecast — about a quarter more. Nobody misled you. It was in clause 3.
The practical consequence for budgeting: if you are forecasting a subscription platform over more than two years, forecasting the year-one fee as a flat recurring line will understate your costs, and the gap grows every year you stay.
You can negotiate this. Ask for the escalator to be capped — at CPI, or at a fixed percentage lower than 5%, or removed for the initial term. Vendors do agree to this, particularly during a competitive procurement, and almost nobody asks. If it stays in, at minimum model it properly in your multi-year forecast rather than carrying the year-one figure forward.
2. The cost of getting your own content back
One major municipal platform's standard master services agreement provides that a data export is available "for a fee to be quoted at time of request." Again, verbatim; again, we hold the document.
Read that carefully. It is not a promise that your data is portable. It is a promise that a price will exist at the moment you want to leave — a price set by the party you are leaving, at the moment you have the least leverage you will ever have. It is unbudgetable by construction, because it is unspecified by design.
This is the single most consequential clause in a municipal website contract, and it is almost never scored in an RFP evaluation. It should be. Ask, in writing, before you sign: what is the fee to export all our content, in what format, and how long does it take? A vendor whose answer is a specific number, or "nothing, it's yours," is telling you something. So is a vendor whose answer is a paragraph.
3. Redesign cycles — and, to be fair, a genuine benefit
It would be dishonest to run through the downsides of subscription contracts without noting the real upside, so here it is: many of them include a free redesign every three to five years, folded into the annual fee.
That is a genuine benefit, and for some municipalities it is the right trade. A refresh from a design shop is real money and real project management, and a council that will never again find the appetite for a website project may reasonably prefer a fee that quietly keeps the site from ageing. If you buy a site outright and never touch it again, it will look like 2026 in 2036.
The honest framing is not "subscriptions are bad." It is: you are paying for that redesign either way. The question is whether you would rather pay for it as a compounding annual fee that continues whether or not you use it, or as a project you commission when you actually want one — competitively, from anyone you like, on code you own.
A worked five-year comparison
Here are the two structures side by side, using real figures rather than invented ones. The subscription column uses a build fee and an annual fee taken from a signed public contract we hold, with the 5% escalator applied as written. The ownership column uses our own published pricing.
| Line | Subscription platform | Ownership model (Munikit) |
|---|---|---|
| Build / implementation | $25,700 | $17,500–$27,500 all-in, one-time |
| Year 1 platform fee | $5,730 | $0 — included |
| Years 2–5 fees (5% escalator) | $25,932 | $2,400 — optional renewal, $600/yr, updates only |
| Hosting, 5 years | Bundled into the platform fee | $0–$1,500, billed by your host, not by us |
| Five-year total | ~$57,400 | ~$26,400 (at the midpoint) |
| What you own at the end | A licence that ends when you stop paying. Export quoted on request. | The source code, in your own git repository. The content, in a standard PostgreSQL database. |
| Year 6 onward | $7,313 and rising 5% a year, indefinitely | $600/yr if you want updates. $0 if you don't — the site keeps running. |
Two things about that table deserve stating plainly, because the temptation in a page like this is to load the dice.
We used the cheaper of the two real contracts we hold. The other one — also a small municipality, also 2025 — came in around $33,000 up front with an annual fee reported at about $11,000. Using that one would have made our number look considerably better. We used the conservative one on purpose.
The ownership column is not free after year five. You will still want someone to patch it, and eventually you will want it to look different. The difference is that at that point you are commissioning work on an asset you own, from any developer you choose, at a price you negotiate — rather than continuing to pay for the right to keep using something.
Hosting deserves one honest note too, because it is a line clerks worry about needlessly. For a municipality of a few thousand people, hosting on modern infrastructure genuinely costs somewhere between nothing and about $25 a month. It is billed to you by the hosting provider directly. Anyone charging you hundreds of dollars a month for "hosting" is not selling you servers.
Change any of these assumptions — your build fee, your annual fee, your escalator, your horizon — on the savings calculator. It is the same arithmetic with your own numbers in it. If you want the fuller side-by-side of the two models, that is our comparison page.
Accessibility is a cost line now, not an optional extra
If your budget line does not include accessibility, it is not a complete budget line.
The U.S. Department of Justice's Title II rule sets WCAG 2.1 Level AA as the standard for state and local government websites. The compliance dates moved in April 2026: municipalities of 50,000 or more must comply by April 26, 2027; municipalities under 50,000, and any special district, by April 26, 2028. We keep a maintained page on where the rule actually stands, because a great deal of what is online about it is now out of date.
But set the regulation aside for a moment, because the budget argument does not actually depend on it. Read a handful of municipal website RFPs published this year and you will find WCAG 2.1 AA specified as a requirement in most of them — frequently as "WCAG 2.1 AA at minimum, or the most current standard at the time of implementation." That language came from procurement officers and peer municipalities, not from Washington. Whatever happens to the rule, this is now simply what a professional municipal website is expected to be.
Which gives you two ways to fund it, and only two:
- Budget for it as a work item — an audit, a remediation pass on the templates, and a document remediation pass on your load-bearing PDFs. This is real money and should be a named line in the request.
- Buy a platform where conformance is built into the templates, so that the only ongoing accessibility work is the content your staff publish from here on.
What does not work is treating it as something to sort out later. Retrofitting accessibility onto a platform whose templates generate non-conformant markup is money spent renting a problem — the templates are not yours to fix.
Be sceptical of any vendor, including us, who tells you a website is "100% compliant" or "fully ADA compliant, guaranteed." Accessibility is a property of your content as well as your platform, and your content changes every week. Munikit is built to WCAG 2.1 AA — the templates, the components, the admin. Keeping it there depends on what gets published, which is why we train your staff rather than promising you a certificate.
So what do you actually put in the budget?
Honest guidance, including for the case where you buy from somebody else entirely. These are budget lines to request, not quotes.
| Your municipality | What to put in the request | Also budget for |
|---|---|---|
| Under ~1,500 residents | $3,000–$15,000 one-time, or an entry-level subscription at roughly $75–$100/month | Document accessibility — it is your real cost, and it does not scale down with your population. |
| ~1,500–8,000 residents | $15,000–$30,000 one-time, or a subscription with the five-year total written into the proposal | Migration. Count your pages and your load-bearing PDFs before you take a quote. |
| ~8,000–25,000 residents | $25,000–$60,000 one-time is a realistic and defensible request | Integrations — agendas, permits, payments, alerts. This is where the scope creeps. |
| 25,000–50,000 residents | $50,000–$125,000 is the published guidance range, and it is not unreasonable | A named project owner on staff. At this size the biggest risk to the budget is nobody owning the project. |
| Any size | 10–15% of the build, annually, for support | The exit. Establish the cost of leaving before you sign, not when you want to go. |
Three pieces of advice that will serve you regardless of who you buy from:
- Ask for the five-year total in writing, in the proposal. Not the annual fee. The total, with all increases applied. This one request does more to protect your budget than any other single thing you can do.
- Get the exit priced before you enter. "What does it cost to export all our content, and in what format?" If the answer is "a fee to be quoted at the time," you have found an unbudgetable liability, and you should say so in your recommendation to council.
- Count your content before you take a quote. A migration price quoted against a number you have not counted is not a price. It is an opening position.
If you are about to write the procurement document, our municipal website RFP template is free and ungated, and it already contains the clauses above as required response fields — including the five-year total, the escalator, and who owns the code.
The number, if you need one today
For a typical small municipality — a few thousand residents, a couple of hundred pages, a decade of documents, no unusual integrations — a realistic, defensible budget request for a modern, accessible, professionally built website is $20,000 to $30,000 one-time, plus a small recurring line for hosting and support.
That number is neither the cheapest thing you can buy nor anywhere near the most expensive. It will not embarrass you in front of council, and it will not turn out to have been naive in year three.
Munikit sits inside it deliberately: $17,500–$27,500, all-in, one-time, launched in six to eight weeks, built to WCAG 2.1 AA, with the source code delivered to your own git repository and your content in a standard PostgreSQL database. The optional $600/year renewal buys software updates and nothing else — let it lapse and the site keeps running. There is no escalator, because there is nothing to escalate.
And if, having read all of this, the right answer for your town is a $99/month template site — that is a perfectly respectable answer, and we would rather you reached it with the arithmetic in front of you.
Sources
- Vendor-published pricing, entry-level municipal platforms (population-tiered monthly rates and one-time setup fees), retrieved 13 July 2026: https://municipalimpact.com/pricing/ and https://www.munibit.com/pricing-municipalities.
- Vendor-published setup and hosting pricing, small design-and-host shop, retrieved 13 July 2026: https://townwebsites.com/p/27/Pricing.
- Example of a municipal platform vendor publishing no price at all ("all projects are custom-quoted"), retrieved 13 July 2026: https://www.evogov.com/pricing.
- Independent agency budget guidance by municipal population, and the 10–15%-of-build figure for annual external support: https://www.upanup.com/article/right-budget-municipal-website.
- The 5% annual escalator — "an annual increase of 5% each Renewal Term" — appears verbatim in signed statements of work between a major municipal-website vendor and more than one U.S. municipality (2023 and 2024). Documents held on file; available to any municipality on request.
- Data export "for a fee to be quoted at time of request" — verbatim from a major municipal platform's standard master services agreement, as published by the vendor. Document held on file; available on request.
- Build and annual fees used in the worked comparison ($25,686 build / $5,730 annual, 2025; and approximately $33,000 build with an annual fee reported at about $11,000, 2025) are taken from signed contracts approved in public session by two U.S. municipalities. Records held on file; available on request.
- U.S. Department of Justice, State and Local Governments: First Steps Toward Complying with the ADA Title II Web and Mobile Application Accessibility Rule — WCAG 2.1 AA standard and compliance dates. Rule published April 24, 2024; dates extended by interim final rule effective April 20, 2026.
- Munikit pricing and the $600/year optional renewal: munikit.app/pricing. Hosting costs are billed by your hosting provider, not by Munikit.
We do not name vendors on this site. The figures above are real, and we will substantiate any of them for a municipality that asks — we would simply rather you evaluated the structure of a contract than the reputation of a logo. This page is maintained; if the published prices move, we update it and change the "last reviewed" date above.