I recently offered to help Green Ridge, Missouri with their town website. Green Ridge is a small community, maybe 500 people. They don't have a website. If you want to pay your water bill, you drive to city hall during business hours, walk in, and pay with cash or a check. That's it. That's the system.
Green Ridge isn't unusual. Most small towns across central Missouri work exactly this way. La Monte, Cole Camp, Smithton. Same story. The town collects utility payments in person, posts meeting notices on a physical bulletin board, and communicates with residents through word of mouth or a Facebook page if they're lucky. It works, but it doesn't have to be this hard.
The Real Problem for Residents
Think about who lives in these towns. A lot of younger residents commute to Sedalia, Warrensburg, or even Kansas City for work. They leave before city hall opens and get home after it closes. Paying a utility bill in person means taking time off, making a special trip, or asking someone else to do it for them.
Older residents have it tough too. Driving to city hall in January to pay a water bill isn't fun for anyone, especially if you're dealing with icy roads or mobility issues.
Then there's the mail option. Some towns accept checks by mail, which helps. But checks take days to arrive, they get lost, and the town clerk still has to process each one manually. It's slow for the resident and slow for the office.
The expectation has shifted. People pay their electric bill online. They pay their phone bill online. They pay their credit card, their mortgage, their car insurance all from their phone. When the water bill is the one thing that requires a trip to a building during banker's hours, that feels broken. Because it is.
What a Small Town Website Should Include
A town website doesn't need to be complicated. It's not a social media platform or an e-commerce store. It's a simple, organized place where residents can find information and take care of basic tasks. Here's what actually matters:
- Online utility payment portal. Residents log in, see their balance, and pay with a credit card, debit card, or bank transfer. Takes two minutes. No driving, no stamps, no waiting in line.
- Resident account lookup. Each household has an account tied to their address. They can check their current balance, due date, and payment status anytime.
- Bill history. A record of past bills and payments. Useful when residents need records for tax purposes or if there's ever a billing dispute.
- Auto-pay enrollment. Residents who want their bill charged automatically each month can set it up once and never think about it again. The town gets paid on time. The resident never gets a late fee.
- Town announcements and news. Boil water advisories, road closures, holiday schedules, events. Right now this information travels by word of mouth or a Facebook post that half the town never sees.
- Meeting minutes and agendas. City council meetings are public record. Posting minutes and upcoming agendas online makes the town more transparent and saves the clerk from fielding phone calls about what happened at last Tuesday's meeting.
- Department contact information. Phone numbers, emails, office hours for water, sewer, streets, parks. A simple directory that answers the question "who do I call about this?"
- Emergency alerts. Water main breaks, severe weather notices, utility shutoffs. A prominent alert bar on the website gets the word out fast.
- Park and facility reservation forms. If the town has a community center, pavilion, or ball field that residents can reserve, an online form replaces the phone tag.
None of this is cutting-edge technology. It's standard web development. The tools exist. The hard part is just getting started.
How Online Utility Payments Actually Work
The payment processing side is simpler than most people think. I use Stripe for payment integration on the websites I build. Stripe handles all the credit card processing and security. The town never sees, stores, or touches a card number. That data goes straight to Stripe's servers.
Here's what the flow looks like for a resident. They go to the town website, log in with their account number and a password (or address lookup), see their current balance, and click "Pay Now." They enter their card or bank info, confirm the amount, and they're done. They get an email receipt. The payment shows up in the town's Stripe dashboard and gets deposited into the town's bank account within a couple of business days.
For the clerk, the admin panel shows every payment that came in, who paid, the amount, and the date. It can generate reports. It can flag overdue accounts. Instead of opening envelopes and recording check numbers in a ledger, the clerk sees a clean dashboard with everything organized.
Square works well for this too, especially if the town also wants to accept card payments in person at the counter. Same card reader system, same dashboard, online and in-person payments all in one place.
Security and PCI Compliance
This is the first question any town board will ask, and they should. "What about security? What if we get hacked?"
When you use Stripe or Square, you're not storing payment data on the town's server. The card numbers are tokenized, meaning they're converted into a random string of characters the moment they're entered. Only Stripe (or Square) can decode them. The town's website never has access to the actual card numbers.
This is called PCI compliance, and it's the same standard that banks and major retailers follow. By using a processor like Stripe, the compliance burden falls on Stripe, not on the town. The town doesn't need a security team or a special certification. The processor handles it.
The website itself needs an SSL certificate (the padlock icon in the browser), which encrypts all data in transit. Every site I build includes SSL. It's not optional and it's not an upgrade. It's standard.
Honestly, online payments through Stripe are more secure than a check in the mail. A check has your bank account number, routing number, name, and address printed right on it. Anyone who handles that check has all of that information. A Stripe payment exposes none of it.
What This Actually Costs
Small towns assume a website with billing capability costs six figures. They've probably gotten quotes from government software vendors who charge $30,000 for a "municipal portal" plus $500 a month in licensing fees. Those vendors exist, and they're wildly overpriced for what a town of 500 or 1,000 people needs.
A custom-built town website with an online billing portal, an admin panel for the clerk, and all the features I listed above does not cost $30,000. Not even close. We're talking about a fraction of that, with a reasonable monthly hosting and maintenance fee to keep it running, secure, and updated.
Payment processing fees are the standard 2.9% plus $0.30 per transaction. On a $75 water bill, that's about $2.48. The town can choose to absorb that cost (which is offset by the savings in staff time and postage) or pass it along to residents as a small convenience fee. Most towns I've seen charge a flat $2 or $3 convenience fee for online payments, and residents are happy to pay it because the alternative is driving to city hall.
Here's the part that matters for budgeting: towns have actual budget line items for technology, administration, and infrastructure. This isn't like pitching a website to a sole proprietor who has to pull money from personal savings. Towns plan for expenditures. They allocate funds. A website project fits into that process naturally.
The State of Small Town Websites in Missouri
I've looked. Most small towns in central Missouri fall into one of three categories:
- No website at all. Green Ridge, for example. If you Google them, you get a Wikipedia page and a Facebook page. That's it.
- A basic WordPress site from 2015. Usually one or two pages with outdated information, a phone number, and maybe a stock photo of a courthouse. No functionality beyond being a digital brochure that nobody updates.
- A vendor-provided site. Some towns use platforms like CivicPlus or Municode. These work, but they're expensive, templated, and the town has very little control over the design or features.
There's a massive gap between "no website" and "expensive government vendor." That gap is exactly where I work. A clean, fast, custom site that does what the town actually needs without the bloat or the price tag of enterprise software.
Ongoing Maintenance: Why This Is a Long-Term Relationship
A town website isn't a "build it and walk away" project. Billing rates change. New announcements need to be posted. Meeting minutes need to be uploaded. The SSL certificate needs to be renewed. Security patches need to be applied. Someone has to make sure the site stays up and running.
That's why I include a hosting and maintenance plan with every site I build. The town gets a reliable contact person (me, not a call center) who keeps the lights on, makes updates when needed, and fixes things when something breaks. For a small town that doesn't have an IT department, this is the whole point. You don't need to hire someone full-time. You just need a developer who picks up the phone.
This is real recurring revenue for my business, and it's real value for the town. Everybody wins.
Getting Started
If you work for a small town in Missouri (or you're on the board, or you know someone who is), I'd love to have a conversation about what a website could look like for your community. No pressure, no long sales pitch. Just an honest assessment of what you need, what it would cost, and how long it would take to build.
I'm local. I'm in Sedalia. I understand how small towns work because I live in one. If this sounds like something your community could use, reach out and let's talk.