Everyone here knows everyone. Will a system make us sound like a call centre?
It will if it is built badly, and that is a real risk in a village this size. So we do not put a machine in front of a customer who knows you. What software does here is behind the counter — reading a booking off a text message, filing a form, chasing a part. The voice your customers hear stays yours, because a person is still writing it.
Eight hundred people. Are we too small for you to bother with?
No, but you may be too small for the project you have in mind, and we would rather establish that on the first call than three weeks in. A single job done properly — the booking diary, the parts chase, the community building calendar — is a good build at this scale. Anything wider usually costs more to maintain than it saves.
Our customers ring, text and stop us in the street. None of that is in a system.
It does not have to start there. What we build takes whatever arrives — a voicemail, a text, a note somebody wrote at the counter — and puts it into one queue so nothing depends on remembering. The street conversation still happens. It just gets written down once, by the person who had it, in under a minute.
The village has almost no budget. Where would you start?
The calendar, nine times out of ten. A shared booking view for the park and the community building removes the most annoying recurring problem a small village has — two groups told yes for the same evening — and it is cheap because it is narrow. Fixed price, one measurable thing, and no ongoing commitment we would be embarrassed to explain to a board.
Is our information kept private in a place where everyone talks?
That is a fair question and it is more pointed here than in a city. Records live in infrastructure held in your name, access is set per person rather than per office, and nothing is shared or used to train anything. Pupil and family information gets stricter handling again. And you can export the lot, whenever you want, in ordinary formats — that is written into the agreement rather than assumed.
Would you tell us not to buy something from you?
Regularly. Half the enquiries we get from villages this size are better answered by an off-the-shelf booking tool or a better-organised spreadsheet, and we say so and lose the sale. It is not charity; a customer who was talked into the wrong build tells everyone, and in a county this size that matters more than one invoice.
How long would something like this take?
Four to eight weeks for most first builds, plus a week at the start where we sit with whoever actually does the job and map it. Small projects sometimes land quicker. We plan the go-live for a quiet stretch — not spring, not harvest, and not the week the festival is being set up.
What is this SolaceSentry we keep seeing mentioned?
It is the review gate. Every message, invoice, notice or letter that leaves a system we build is held until a named person releases it. There is no configuration option to switch that off, because the moment something goes out in your name that you did not approve, the system has cost you more than it saved.