We supply a food manufacturer and get audited. What do you actually build for that?
The record chain, not the food safety programme itself. Your quality plan stays yours and your auditor stays your auditor. What we build is the plumbing that makes the evidence findable — certificates filed against the right lot as they arrive, intake linked to output, and a trace that runs in minutes. Your quality lead still releases everything that goes to a customer.
Most of our year happens on one August weekend. Can software help with that?
It can, mostly by making next August better than this one. Pre-orders taken properly, staffing planned against what actually happened last year, and a record of what sold out and when. It is not glamorous work and it is not expensive work, but shops on West Washington Street and North Dixie Highway tell us the difference between a good festival and a great one is usually stock they ran out of by Saturday noon.
We farm and deliver into the processors. Is there anything in this for us?
The intake side. Knowing your contracted acres, your delivery windows and where your loads stand without ringing anyone saves a surprising amount of the season, and having quality readings and deductions written down with a reason attached ends most of the arguments at settlement time. That is usually a small, cheap first project.
What happens to the data if we part ways?
It goes with you. Lot histories, grower records, customer documents, bookings — exported in an open format on request, no exit fee, no negotiation. We put it in the contract before the first invoice. Given that some of these records need keeping for years for audit reasons, that is not a small thing.
Do you use AI on anything that affects food safety decisions?
No. AI reads documents here — a certificate of analysis, a delivery note, an insurance certificate — and files them where they belong. Hold, release, reject and recall decisions are made by your named quality person, and the system is built so that gate cannot be bypassed. We would not want it any other way and neither would your auditor.
How long does a build take, and when should we start?
Four to eight weeks is typical. For anything tied to a season, start early — a traceability build wants to land well before your next customer audit, and a festival build wants to be running by June so it has time to collect real numbers before August. Coming to us in July about August is possible, but you will get a narrower system.
We already pay for software that half works. Do we have to throw it out?
Almost certainly not. Most operations here have accounting and something for scheduling that are fine on their own terms. We connect to those and build the missing link between them. If the honest answer is that your existing package would do the job with two days of configuration, we will tell you and charge you for the two days.
Who are we dealing with, and will you sign an NDA?
A US-based team, and yes — routinely, before we see anything. Nothing is subcontracted overseas and nobody outside the named team touches your systems. We work up and down this corridor, so you will not spend the first meeting explaining what a trace request is or why August matters.