Twelve hundred people. Are we too small for you to bother with?
No, but you may be too small for the project you think you are asking for, and we would rather say that early. The businesses here are a fuel yard, a tile works, an ag service, a repair bay and a village hall on North Fourth Street, and none of them needs a platform. Village-scale work here is usually one build doing one job well — a record made in the cab, a queue that sorts itself. If what you actually need is a better spreadsheet and an hour of training, we will tell you that and charge for the hour.
Our applicators are in the field fourteen hours a day. They will not use a system with twelve fields on a form.
Then it is the wrong form. Anything meant to be filled in from a cab has to work in under thirty seconds with gloves on, which usually means picking from a short list rather than typing, and pulling the weather and the location automatically. If the crew will not use it in the second week, it does not matter how correct it is.
What happens if the internet drops out in the middle of a field?
The entry is stored on the phone and goes up when signal comes back. This is farm country and coverage is patchy, so anything we build for field use has to assume the connection is not there. Records queue locally, nothing is lost, and the person entering it sees whether it has synced.
The fire department is volunteers. Does software help or just add another thing to ignore?
It helps if it removes work rather than adding it. Availability by text reply, certification dates in one place, and an early warning when a shift is heading toward nobody are the three that earn their keep. Anything that requires a volunteer to log in to a portal after a twelve-hour day will be ignored, and rightly.
Could this ever dispatch a call or send something out on our behalf?
It will not. We put a review gate in front of anything that leaves the system — we call it SolaceSentry — and for a department that gate is a named officer. Machines are good at assembling a roster and terrible at judging an emergency. We keep that line hard because blurring it is how small organisations get hurt.
Who has access to the field data and where does it live?
Your operation does, and it stays in a system you can export from in a plain file on any day you ask. Field-level application data is commercially sensitive and in some cases legally sensitive, and we treat it that way: written into the agreement, covered by NDA, never used for anything but your work.
We keep hearing about AI in agriculture. Is any of this that?
Some of it is, in a narrow way. Reading a blend ticket, matching an odd product name to the right label, sorting a repair queue by whether a machine is stopped — those are worth doing with it. Yield prediction and agronomic advice are not what we sell, and there are people far better placed than us to do that. If a job is better done by a plain database and a rule, that is what we will build.
How do you price something like this?
Fixed and written down before any work starts, after we have walked through the actual process with the people who do it. No hourly meter, no scope creep conversation in week six. If the price turns out to be more than the problem is worth, we would rather find that in the mapping session than after you have paid a deposit.