We'll tell you what isn't built
Vektra is young. Some things you need may not exist yet. You'll hear that on the demo call rather than discovering it in month three, because a customer who leaves angry costs more than a deal we didn't close.
About
Built by someone who ran the board
Most transportation software is built for brokerages with a hundred seats and sold to carriers as an afterthought. Vektra started the other way around.
01 · The origin
From the desk, not the deck
Vektra came out of the dispatch desk, the settlement sheet, and the customer calling at four in the afternoon asking where their truck is. Not out of a product roadmap meeting.
Spend enough time on a board and you notice the same thing over and over: the software isn't wrong so much as disconnected. The shop knows a unit is down. Dispatch doesn't. Accounting knows an invoice is short. The person who could fix it never sees the flag. Every one of those gaps is a phone call, and every phone call is somebody's afternoon.
The systems that were supposed to close those gaps mostly just recorded them. A maintenance record filed away. A red swatch in a legend that a human is expected to notice. A board with a timestamp and a refresh button, quietly going stale while three people make decisions from it.
Vektra is the argument that a status should have consequences. If the shop takes a unit out of service, dispatch shouldn't be able to put a load on it — not warned, blocked. If a contract expires, it should stop generating work at the source instead of turning into a colour someone learns to ignore. That's a design decision you have to make at the foundation. It's very hard to retrofit into software that's been shipping for twenty years, which is exactly why there's room for this.
02 · Who's building it
Alister
CEO & Principal Engineer
I've worked the operational side of transportation and the software side of it, which is a less common combination than it should be. Vektra is what I wanted to be handed on the desk and never was.
Right now I'm building it, running the demos, and doing the migrations personally. That's a real constraint on how fast we can grow, and it's also the reason founding carriers get to shape what gets built next. When you flag something, you're talking to the person who'll write it.
03 · How we work
Four commitments we'd rather be held to
Your data is yours
Exportable on demand, in a usable format, for as long as you're a customer and on the way out the door. Nobody should stay on a platform because leaving is expensive.
Price you can predict
Per truck, month to month, published up front. Adding a user never increases your bill, and neither does having a good quarter.
Anything exported weekly is a missing feature
When a customer exports the same spreadsheet every Friday, that's not a workflow — it's a gap in the product. We track it and we build it.
04 · Where we are
Founding carrier program
We're onboarding a small number of carriers now, and being deliberate about it — enough operations to keep the product honest across different freight types, few enough that everyone gets real attention during migration.
The trade is straightforward. You're early, so you'll hit rough edges and occasionally wait on something. In exchange you get pricing locked for your first two years, a direct line to the person building the platform, and genuine influence over what ships next.
If your operation can't absorb that right now, that's a completely reasonable position and we'd rather you told us. Come back when we're further along.
Thirty minutes, your loads on the screen
No pitch deck, no pressure. Bring the part of your week that always goes wrong.