What happens to our paperwork when the load is already three hours away?
That is the specific gap most hauling operations have. The freight moves at highway speed and the documentation moves at whatever speed somebody gets round to photographing it. We close it by making the capture happen at the point of the event — a photograph at the scale, a tap at the drop — so the record exists before the truck pulls out, not on Sunday evening.
The school is closing. Can software really do anything about that?
It cannot replace a building and we will not pretend otherwise. What it can do is stop the practical damage: groups that used the school as their venue and their noticeboard need somewhere else to be findable, book rooms and keep their rosters. That is a small, cheap build and it is worth doing before the year it happens, not after.
We are a shop with three bays. Is this over-engineering?
It would be if we built you a plant system, which is why we do not. Three bays needs a shared queue, parts linked to jobs, and a status a customer can be told without anyone walking outside. That is a small piece of software, quoted flat, and finished in weeks. If the sensible answer turns out to be a whiteboard used properly, we will say that too.
Who reads what gets sent out?
A person you name, every time, through the review gate we call SolaceSentry. A delay notice to a customer, a message to members, a status update — the system prepares it and holds it. Automatic sending is where small operations get burned, because the one wrong message is the one everybody remembers.
Our drivers are not going to use a complicated app.
Then it will not be complicated. The design target for a driver interface is a photograph and two taps, working with poor signal, without a login every time. If a build cannot meet that, it is the wrong build — we have cut features for exactly this reason, because a driver-facing tool that gets ignored is worse than nothing.
Can we get our data out if we part company?
Yes, in an ordinary format, whenever you ask, and it is in the agreement before you pay. Load history, customer records, membership lists — none of it is held hostage. We work under NDA and the accounts are yours from the beginning, which also means you are never locked out of your own system if we are unreachable.
How long does a build take here?
Four to eight weeks for most of it, with a week or two of mapping before that. For anything to do with grain movement we aim to be finished and practised before harvest, because there is no version of October where anyone has time to learn a new system. We will tell you straight if a start date does not leave room.
Is AI actually doing anything, or is it a label?
It is doing the reading. Turning a photographed bill of lading into a matched, checked record is real work that used to require a person and an evening. Everything else in these builds — the queue, the calendar, the reminders — is ordinary software and we price it as ordinary software. You can see the split on the proposal.