How ALCS transformed trucking operations with Vektor TMS

James Almquist had already been through one TMS migration. It had not gone well. The system was for his brokerage operation, and by the time it was over he had spent months fighting software that seemed designed to create work rather than eliminate it. When someone suggested looking at Vektor for the carrier side of his business in 2023, his first instinct was to say no.

ALCS, based in Noblesville, Indiana, was running general freight on 10 trucks at the time. James had built the operation methodically — nothing flashy, just reliable service and careful back-office discipline. He was doing invoicing manually, keeping driver settlements straight in spreadsheets, and pushing everything into QuickBooks by hand. It was tedious, but it worked, and it was something he could control. Another TMS that promised to make things easier but delivered complexity instead was not a trade he was ready to make.

He agreed to a conversation mostly out of curiosity. What changed his mind was the QuickBooks integration demo. ALCS ran entirely on QuickBooks for accounting — it was the one non-negotiable in his tech stack. What Vektor showed him was not a one-way export or a weekly sync file. It was a live, two-way connection: invoices generated in Vektor posting automatically to QuickBooks, and driver settlement records syncing at the same time. Both sides of the ledger, in one flow, without anyone touching a keyboard to make it happen.

For someone who had been doing that work manually, the implications landed immediately.

James started cautiously, the way someone does when they have been burned before. He brought 10 trucks onto the platform and watched closely — not just whether it worked, but whether anything broke. The first billing cycle was the real test. Invoices posted to QuickBooks without manual intervention. Driver settlements matched. Deductions tracked correctly through BillIQ. Nothing needed to be fixed by hand.

The second cycle went the same way. By the third, James stopped watching quite so closely.

What he noticed next was the Driver App. His drivers were scanning BOLs and delivery confirmations at the stop and uploading them before they were back in the cab. Documents that used to arrive in the office a day or two after delivery — sometimes longer — were now in the billing queue within minutes of the final signature. The back-office team was not chasing paperwork anymore. The billing cycle accelerated, and cash flow followed.

Then came the feature James had not been looking for. The AI load entry pulled rate cons from his email, read them, and built the loads in Vektor without a dispatcher touching the keyboard. He had heard about this kind of automation in the context of large fleets with staffed IT departments, not for a 10-truck general freight carrier in Indiana. It worked the same either way. His dispatchers were entering loads in seconds instead of minutes, and the accuracy was better than manual entry had ever been.

What followed was less a deliberate growth strategy and more a removal of friction. With the back office running cleanly and the dispatch workflow leaner, the ceiling on how many trucks ALCS could practically manage had gone up. James added trucks. Then more. By the time a year had passed, he was running 50 — five times the fleet he had started with on the platform.

The growth from 10 to 50 trucks is the headline number, but James would be the first to say the platform did not build the business — he did. What Vektor changed was how much capacity he had left over to build it. Every hour that used to go into manual QuickBooks entry, paper document chasing, and re-keying rate confirmations became an hour available for something else. Over the course of a year, those hours add up to something significant.

The QuickBooks integration remains the feature James comes back to when he explains the platform to other carriers. It is not complicated — invoices sync, settlements sync, deductions track — but for an owner-operator running a growing fleet without a dedicated accounting staff, "not complicated" is exactly the point. The integration he had expected to spend hours managing each week manages itself. The books stay current, and the audit trail is clean.

The Customer Portal quietly changed the nature of his customer relationships. Shippers who freight-match with ALCS used to call dispatch for status updates on loads in transit. Now they log in and check for themselves. James estimates his team fields a fraction of the status calls they once did, and the shippers seem to prefer the self-service model. It projects a level of operational transparency that used to require a much bigger back-office team to maintain.

James is not a person who describes himself as enthusiastic about software. He would still tell you to be cautious going into a TMS migration, to start small, to verify everything before you trust it. What he would also tell you is that he found features on Vektor before Vektor announced them — that he was testing capabilities ahead of general release and building workflows around them while other carriers were still doing things the old way. The person who called in 2023 skeptical that any system could deliver on what it promised has become one of the most deeply embedded users on the platform.

Fifty trucks. Clean books. Drivers who upload documents from the road. Customers who track their own freight. And a back-office workload that has not grown proportionally to a fleet that quintupled in size. That is what changing your TMS can look like when the migration actually goes the way it was supposed to.