The town website that builds itself

Four things, and you need all four

Most platforms manage one of these. A couple manage two. Nobody ships all four, which is a decent explanation of why town websites are the way they are.

• Agentic

  The software does the work and hands you a decision.

• Accessible

  Built so the usual mistakes are not available to make.

• Adaptable

  Your boards, your approvals, your look.

• Easy to use

  If it needs a training day, we got it wrong.

Agentic

The software does the work. Your staff say yes or no.

Everyone has added AI to their product this year. Mostly it is a button in the corner of the editor that will help you write a paragraph, once you are already in the editor, doing the work.

That does not change who does the job. You still open the tool, still face the empty page, still build the site by hand. The button helps with the typing, and typing was never the hard part.

Baseline works the other way round. Nobody on your staff starts from a blank screen. They start from a draft.

1. It builds your site before you have signed anything

   We read the website you have now and rebuild it. Your departments, your boards, your pages. You get to judge us by looking at your own town rather than somebody else's demo.

2. Then it drafts everything after that

   Send it whatever you were going to post anyway. A document, an email, a date, one sentence. It writes the page, files it under the right board, and puts the meeting on the calendar.

3. It does the jobs nobody gets to

   Describing photos, writing summaries, translating. The things that get dropped at 4pm on a busy day, which are also the things that get a town in trouble.

4. A person approves it

   Every time. Nothing the software writes goes public on its own. You can see what it changed and which parts it touched before you agree to any of it.

5. Nothing happens quietly

   A town gets held to account in ways a business does not. Software that quietly reworded a page of bylaws is not a bug you file, it is a phone call from your attorney. So we keep the receipts and we are happy to show them to anyone who asks.

The goal is not a site that passes. It is a site that cannot fail.

If software is going to write most of your website, it had better not be able to write a broken one. Otherwise you have just automated the problem.

We looked at the homepages of 324 towns, expecting a hundred different problems. We found about ten, over and over. Unreadable text. Links that are just an icon. Photos with no description. Nothing exotic, nothing expensive, and none of it anyone's fault in particular. Ordinary people doing ordinary things in software that let them.

• You cannot pick a bad color
  Your palette gets checked before it is offered to you, not after you have used it. You still look like your town.
• Nobody writes the underlying code
  Not your staff and not the AI. Both work with pieces we built and tested first.
• Nothing goes out unnamed
  A photo or a button without a description does not publish. The software writes one and asks you to check it.
• No third-party widgets
  We cannot fix somebody else's code, so we do not put it on your site.

We aim high on the published standards and we will go through the detail with your counsel. What we will not do is hand you a certificate and call it settled, because a lot of what matters here cannot be checked by a machine at all.

Adaptable

Every town is a different shape. The software should bend, not the town.

Government software has a habit of showing up with opinions about how your town ought to work. We have strong opinions about how a web page should be built and none whatsoever about your charter.

• Your approval process
  One person signing off, or the Clerk then the Administrator then the board. Whatever your bylaws actually say, including when different things take different routes.
• Your boards and departments
  Named the way your town names them. Not a fixed list of departments somebody invented in another state.
• Your colors
  Within limits that keep the site readable. You get to look like your town, you just do not get to ship something nobody can read.
• Whatever you need to publish
  Meetings, notices, permits, projects. Adding a new kind of thing is a setting, not a rebuild and an invoice.
• Your data, on the way out
  All of it, whenever you ask, including the history. If leaving is hard then everything above is just a nicer cage.

Easy to use

If it needs a training day, we got it wrong.

The person looking after your website is probably the Town Clerk, and their actual job is vital records, licensing, elections and minutes. The website gets a couple of hours a month if it is lucky. Everything here is designed for that person.

• Never a blank page
  Every job starts from something that already exists. A document, a date, last year's version.
• One screen
  Here is the draft, here is what changed, here is the button. That is the whole thing.
• Nothing to break at 11pm
  No plugins to update, nothing to conflict, no call at 2am because a widget went down.
• No manual
  We do not sell training, because needing it would mean we failed. If your Clerk cannot post a meeting notice on the first try without help, tell us and we will go fix the screen.

Not an empty platform you have to build a town website out of. The town website, already there, with your content in it.

• Departments and services

  Every board and office, with the pages people actually come looking for. Licences, permits, forms, hours, who to call.

• Meetings, agendas and minutes

  Posted ahead of time, filed under the right board, and readable as pages instead of a pile of attachments.

• News and notices

  Closures, announcements, the emergency banner. Things that need to be up a minute after you hear about them.

• An events calendar

  Town meeting, the Council on Aging trip, the library reading. It never quietly turns back into a dead PDF.

• Documents people can read

  Upload the bylaw or the budget and it becomes a real page, with the original file still there underneath it.

• Search that finds things

  Including inside your documents. People are looking for what the minutes said, not for the name of the file.

Built for the towns nobody builds for

No IT department, no webmaster, and nothing like the budget for a five-figure contract. Every platform out there is built for a full-time communications person that these towns do not have. Ours is built for whoever ended up with the job.

Figures from our survey of 29,498 US municipalities, August 2026. The two hours is our estimate and we have not measured it. See the evidence.

What we do not do

Better you hear it now than in month three.

• We never touch public money. Payments stay with whoever you use already. We link to it and stay out of it.
• No permitting or licensing. That is a whole other product with fifty states of integrations behind it.
• No mapping, no council voting records. A town of 900 has a three-person Select Board, not a forty-member council.

Other people sell all of those, and sell them well. Every one we skip is a month we spend on your website instead.

See your own town on it

We will rebuild your current site on Baseline and walk you through it. Twenty minutes, and you are looking at your town rather than a sample one.

Request a demo