Hands-on consulting for trucking and warehousing businesses — custom software built around how your operation actually runs.
Plain software for the working side of logistics — the tools your crew lives in every day. Every build starts from your workflow, never a product menu.
Two businesses, two systems already in production — both built one-on-one with the people who run them.
I built a full inventory system for a warehousing operation — replacing manual tracking with one place everyone could rely on for what was in stock.
For a trucking company owner, I built a system to run jobs, billing, and margins from one place — no more guessing at the end of the month.
A direct, plain-spoken engagement. You work with the person building the software — no account managers, no handoffs.
I learn how your operation actually runs — the steps, the people, and where the real friction is.
I lay out what the software will track, who uses it, and what it does — agreed before any code.
You see it come together in working pieces you can react to. No black box, no surprises.
Once it's live I keep close — fixing, refining, and growing it as the business changes.
Our stock used to live in spreadsheets and people's heads. Now it's one system everyone trusts — and our clients can check their own inventory without calling us.
I can finally see which jobs actually make money. Invoicing that used to take an evening comes straight out of the work now.
The specific stack is chosen to fit each job — and to stay maintainable long after it’s handed over.
Small trucking, freight and warehousing operators in Ontario — owner-operators running a handful of trucks, and 3PL or warehouse teams handling receiving, picking and shipping. The work is deliberately narrow to that world rather than generic business software.
A packaged system asks you to change how you work to fit its assumptions. A custom build starts from how your operation already runs — your steps, your paperwork, your exceptions — so nobody has to keep a spreadsheet on the side to make it usable.
You do. Full ownership of the code transfers to you at handoff. You are not renting access to it, and you are not locked to me to keep running it.
We talk through how your operation runs, then I write a specification covering every screen, user and edge case. You sign that off before any code is written, so the scope and cost are agreed in advance rather than discovered halfway through.
Both depend on scope, so neither is quoted before the spec exists. The written specification is what produces an honest timeline and price — and you see a live staging link from early in the build, so progress is something you can click rather than take on trust.
Usually, yes. Common integrations are accounting systems such as QuickBooks Online, ELD and telematics data, broker feeds, and email or SMS alerts. The goal is ending double entry between systems, not adding another one.
No. Most operations start with the single worst bottleneck — stock counts, dispatch, or invoicing — get that working properly, then extend from there once it has earned trust on the floor.
I stay on. Fixing, refining and extending the system as the business changes is part of the work, not a separate contract you have to negotiate later.
Tell me what's slowing your operation down. I'll tell you straight whether custom software is the right call.
Start a project →