A new dispatcher starts Monday at twenty-one dollars an hour. Payroll shows her wage from day one. What payroll does not show is the stretch — commonly around ninety days — when most of her output is questions, and every question lands on the one person who already had a full job.
The cost that never gets its own line
Hiring cost is usually discussed as a wage. The real figure is the wage plus everything around it: the senior hours spent answering questions, the part ordered in the wrong size, the warranty promise nobody authorized, the estimate that missed a line item and gave away the margin. None of it appears anywhere labeled "ramp." It is smeared across payroll, cost of goods, and rework, which is exactly why it never gets managed. A cost with no line item has no owner.
The interruption tax
Watch what actually happens when the new hire hits a question she cannot answer. She walks over to the senior estimator — someone whose time bills out at, say, ninety-five dollars an hour — and asks which price tier applies to a repeat commercial customer. The answer takes forty seconds. The interruption costs far more than forty seconds, because the estimator was halfway through a takeoff and now has to rebuild the thread she was holding in her head. Multiply that by ten questions a day across a ninety-day ramp and the tax gets large. The new hire is not the problem. The problem is that the answer existed in exactly one head, or in a shared-drive folder named "NEW pricing FINAL v2" that nobody trusts.
What actually slows a new hire down
It is rarely the software and almost never intelligence. It is provenance — knowing which document is the real one. Which price sheet is current after the March vendor increase. Whether the shop follows version 3 of the lockout procedure that lives in the drive or version 7 that went around by email last fall. Which customers get the loyalty rate and who approved it. A veteran carries this map in their head. A new hire has to rebuild it one embarrassing question at a time, and half the map was never written down in the first place.
A system that has read your paperwork
The mechanical fix we build is an internal assistant that has been given your documents — the price book, the warranty terms, the equipment manuals, the employee handbook, the procedures — and answers questions from them, citing the document and section each answer came from. The new hire asks in plain language and gets back the relevant paragraph, with its source, in seconds. She can check the citation herself, which is how trust in a tool like this is earned rather than asserted. The senior estimator still gets interrupted, but for judgment calls, which is what her hourly rate is actually for. Built properly, the system also says so when the answer is not in the documents instead of improvising one — and you should insist on seeing that refusal behavior in any demonstration, ours included.
Day one runs on paperwork, and paperwork takes a checklist
The unglamorous half of onboarding automates cleanly because it is pure sequence. Federal law requires the employer's section of Form I-9 to be completed within three business days of the start date. The W-4, the direct deposit form, the handbook acknowledgment, the software accounts, the door code — every one of these can key off a single date, the accepted offer, and fire in order without anyone needing to remember to remember. A new hire whose first morning involves a working login instead of an hour spent hunting for someone with admin rights learns something true about the company before lunch.
What this does not shorten
An assistant cannot teach judgment, and it cannot replace shadowing. Knowing which paragraph governs a warranty claim is not the same as knowing when a customer needs to hear the answer from the owner personally. More important: the system can only retrieve what was written down. If the real procedure lives in a retiring foreman's head, there is nothing to index until someone sits with him and writes it out — and that writing is genuine work, a real phase with real hours, not a detail the technology handles for you. The same goes for contradictions. If version 3 and version 7 of a procedure are both in the pile, the system will retrieve both and answer confidently from the mess. Document cleanup comes first. Point a retrieval system at a contradictory pile and it will answer confidently from the mess — no software fixes that after the fact.
Where to start
Before changing anything, run a one-week tally. Ask your most-interrupted person to make a mark, with a word or two of context, every time a newer employee asks them a question. At the end of the week the tally shows which documents to fix first, how large the interruption tax actually runs in your shop, and whether this is worth building at all. If the sheet is nearly empty, you do not need us. If it is full, you already knew.