We are a very small village office. Is this the sort of thing we can even run?
Only if it is built small. A village of this size does not need a case management platform; it needs one intake route, one status per request, and a way to produce a complete file when someone asks for one. We would rather deliver that in four weeks for a modest fixed price than sell you something that needs a full-time person to feed it.
Our address says Kankakee even though we are in Limestone. Does that hurt us?
It costs you some local searches, yes. The fix is unglamorous — being explicit on your own pages about the areas you actually serve, keeping your business listings consistent, and making sure a neighbour looking for a plumber in Limestone finds you rather than someone twenty minutes away. It is not an AI problem and we will not price it as one.
Would you build something that decides what an ordinance means?
No. That is exactly the line we do not cross. A system can find the right document and put it in front of a resident quickly, and it can draft a plain-language summary — clearly labelled as a summary. What the ordinance means and what the village decides stays with the clerk, the attorney and the board, and the build is arranged so it cannot be otherwise.
Winter is our whole year. Does a build make sense for a snow operation?
It makes sense if the contracts are recurring, because that is where money leaks — a property skipped twice, a renewal that went out late, a customer billed for a service they had cancelled. The route work itself is a scheduling problem more than a software one. We scope it small and aim to have it running before the first call-out, not in February.
What is the honest cost of something like this?
We map first, then quote a fixed figure against a written scope with the exclusions spelled out. Most first builds for businesses this size are four to eight weeks of work. If the mapping shows an existing tool covers you with a day of setup, that is the recommendation you get, and the invoice is for the mapping.
Who ends up owning what you build, and the information in it?
You do, on both counts. Village records, customer lists, job histories, delivery tickets — yours, exportable in a standard format whenever you want them, with no fee for asking. For a public body that is not a preference, it is a requirement, and we treat it the same way for private clients.
How much of this actually uses AI?
A modest amount, in specific places: reading a weigh ticket, sorting an incoming request, drafting a summary someone will edit. Routes, schedules and billing are ordinary software and should stay that way. Adding a model to a job that does not need one just makes it slower, dearer and harder to trust.
Are you a local outfit, and does that matter here?
US-based, working this corridor, and happy to sign an NDA before we see anything. It matters mostly at the start — the mapping session works far better in a room than on a call, and for a village or a small trade that session is where the value of the whole project gets decided.