Nearly 4,000 townships have no website. Not because they didn't want one.
There are 6,084 townships under 3,000 people in Illinois, Indiana, Michigan, Minnesota, Ohio and Pennsylvania. We went through them one by one. Only 2,260 have a website. The other 3,824 don't.
That's not clerks dragging their feet. It's arithmetic. A salesperson's time, a designer's time and a project manager's time spread over a township's website budget has never added up, so the industry pointed itself at cities and left townships to sort themselves out. When the only quotes you can get are written for a city of 40,000, you don't get a website.
We use AI to do the building. That's what brings the cost of a properly made site down to where a township of 900 can actually pay for it. It isn't a gimmick and it isn't the product — it's the reason this company can exist at all.
And it's why we're strict about where it stops. AI builds. People talk. There's no chatbot on your homepage, no AI writing your reminders, and no bot answering your email. The tools make us fast and cheap. The people are what you're actually hiring.
Before taking a single client we crawled 1,184 township websites, close to 72,000 pages, and read 956 of them in full — what they have, what they're missing, and what residents are trying to do when they land there.
We wanted to know what townships are actually working with before telling anybody what they needed.
A small elected board. A clerk who's often part-time and doing four jobs. A budget argued over in public. Deadlines that don't move for anybody. That's not a small city and it shouldn't be sold to like one. Every decision we've made about pricing, scope and support comes out of that.
Your posting deadlines aren't optional, so neither are ours. Your account manager watches your board's calendar and tells you what's coming due before it's late. If we ever drop something, you'll hear it from us first, along with what we're doing about it.
Who's behind this
A small team that spent years working on local government websites before starting this one.
Between us we've spent years building and supporting websites for local government. Long enough to know how a township differs from a city, what a clerk actually needs on a Tuesday afternoon, and where this industry quietly lets small places down.
We're deliberately small and we mean to stay that way. You'll work with the same people every time, and they'll know your township without looking it up.
- Support should be a person. Not a chatbot, not a ticket queue, not an AI trained on a help page.
- Your account manager should know your township, not your account number.
- Small is the point, not a stage we're trying to grow out of.
- A public body isn't recurring revenue. You're a township with a board and a budget, and you should be dealt with like one.