Does being in two counties actually change anything you would build?
Yes, and it is one of the few genuinely local design decisions we make here. An address on North Lightfoot Road and an address on East Fort Street can land you in different offices for the same job. Jobs get tagged by jurisdiction from the address, correspondence gets filed to the right county automatically, and the requirement sets are kept separate rather than merged into one generic checklist. It sounds small. It is the difference between one submission and three.
Our records go on paper in the truck and get typed up later, if at all. Realistic to change that?
Only if the phone version is faster than the paper version. That is the bar we hold ourselves to — photograph the ticket, done, no fields to fill. If a driver has to stop and type, it will not get used and we will have wasted your money. We would rather build the smallest capture that works and add to it once people trust it.
Harvest is the only time anything is really on fire. Is a year-round system worth it?
Only if it earns something in the other ten months. Usually it does, because the same records that keep harvest straight also make winter billing, insurance and landlord reporting quick. But if the honest answer for your operation is a seasonal tool and a spreadsheet the rest of the year, we will say that.
Would you touch anything on the machinery side?
No. Equipment telematics, monitors and controllers belong to the manufacturers and the dealers, and we do not put our hands on them. We work with what comes off them and around them — work orders, records, invoices, scheduling. Where a dealer system already does the job, we integrate rather than duplicate.
If we hire you, who can see our operation's numbers?
Us, only while we are building, only under a signed NDA, and only the parts we need. After handover it is your system with your accounts. Yields, rates, customer lists and rates charged are exportable by you at any time and are never reused, aggregated or shown to anyone else. We are a US-based team and nothing is subcontracted overseas.
What does "a person approves it" mean in practice?
It means a queue and a name. Drafts — an invoice, a record, a message — sit behind a review gate called SolaceSentry until a specific person clicks approve, and the system logs who did and when. Nothing here fires off at midnight because a rule matched. Around applications and licensed work, that is not a preference, it is the whole design.
How do you decide whether to build something or tell us to buy it?
We map the process first, before any code. If what comes out of that looks like something already sold off the shelf, we tell you the product name and stop. We lose some work that way. We would rather lose it than sell you a custom version of software that already exists and costs less.
How quickly could something be running?
A first build is normally four to eight weeks from the mapping session, at a fixed price agreed before we start. For anything meant to carry a season, we aim to finish well ahead of it rather than commissioning in the middle of the work. If your window is tighter than that, tell us and we will cut the scope rather than the schedule.