We are a machine shop that sells to one of the big plants. Where would you start?
Almost always with quote turnaround and the document packet, because those are the two things a buyer notices. We look at how a request comes in today, how long it sits, and what has to be attached before it goes back. The first build usually gets the estimator a pre-filled draft and keeps the certificates current in one place. That is a small, fixed-price piece of work and you can measure whether it helped inside a month.
Our people go through site orientation at three different plants. Can that be tracked in one place?
Yes, and it is one of the more useful things we build here. Each site has its own rules about refreshers, screens and badge validity, so we keep one record per worker and one set of rules per site, then show you the crossover. What you get is a list weeks ahead of a shutdown telling you who needs what — instead of finding out at six in the morning that two pipefitters cannot go in.
Do you build anything that runs inside a plant?
No. Process control, plant networks and anything touching operational technology are outside what we do, and we will say that in the first conversation instead of taking the work and finding out later. What we build sits in your office and talks to the plant the way you already do — by document, by email, by portal upload.
We run trucks. Is there anything here that a normal dispatch package does not already do?
Sometimes not, and we will say so. If your problem is purely load boards and driver settlements, buy a TMS. Where we help is the seam — the ticket photograph that has to become an invoice line, the receiving appointment that has to line up with a driver's remaining hours, the detention claim nobody wrote up. Those seams are where the money leaks and they are usually specific to how you work.
Third shift is killing us. Can software fix a labour problem?
Not the labour problem, no. It can fix the leak between someone applying and someone starting. In a city where ADM, Caterpillar and Primient are all hiring from the same pool, the employer who answers an application the same hour wins candidates from the employer who answers on Thursday. We build the pipeline and the follow-ups. We deliberately do not build automatic candidate scoring.
Everything we send gets audited eventually. Will the system survive that?
That is designed in from the start. Superseded documents are archived rather than overwritten, every send is logged with a timestamp and a named sender, and you can produce the exact version a customer received two years ago. If we cannot show you that on day one of the demo, do not buy it from us or from anyone else.
Suppose the relationship ends. What comes with us?
All of it. Customer files, worker documents, quote history and load records export in standard formats on request, and the hosting accounts carry your company name from the first week. That goes in the agreement before you pay us anything, because a firm that makes leaving expensive has told you exactly what it thinks of its own work.
How much of this is really AI, and how much is ordinary software?
Reading dates off a certification card, pulling weights off a scale ticket photo, and sorting a stack of quote requests by what they actually are — those are real machine-learning jobs and they save hours. Scheduling, billing, and deciding who is cleared to work are ordinary programming, and we build them that way because it is cheaper and more reliable. We are happy to itemise which is which before you commit.