Getting help, and where this fits
What LoadMargin does and doesn't replace, how to fix common problems, and how to reach me. Questions go to my email, and I answer them myself.
What this replaces, and what it does not
Most carriers already use something. Here's which job LoadMargin does and which it leaves to other tools.
| A spreadsheet you built | Load-board rate data | A full TMS | LoadMargin | |
|---|---|---|---|---|
| Tells you what a load nets against your costs | Yes, if you built it right | No: it shows the market, not your margin | Usually after the fact | Yes, before you accept |
| Counts deadhead in the rate per mile | Rarely | No | Sometimes | Always |
| Usable while a broker is on the phone | Not really | Yes | Depends | Yes |
| Shows what the market is paying on a lane | No | Yes: this is what it is for | Some do | No |
| Dispatch, documents, IFTA filing, settlements | No | No | Yes: this is what it is for | No |
| Invoicing and accounting | No | No | Yes | No |
| Stays current when your insurance renews | Only if you remember | N/A | Yes | One field, everything moves |
| Cost | Your time | Subscription | Subscription, often per seat | Free tools; paid help from $49, per service |
| Works with no account or upload | Yes | No | No | Yes |
If you have a spreadsheet
Keep it, and check it against the free calculator once. Spreadsheets do arithmetic perfectly well: they fail because they live on one laptop, they go stale silently when a cost changes, and nobody opens them mid-call. If a spreadsheet suits you, keep using it, and update it whenever a cost changes.
If you pay for rate data
Keep that too. Market rate data and your own cost model answer different questions: one tells you what a lane is paying, the other tells you whether you can afford to haul it. Knowing both puts you in a better spot when you negotiate.
If you run a TMS
A TMS runs your operation; this scores a decision. There is no TMS integration: you enter loads by hand or import a backup file.
Ten minutes, and most of it is finding one number
Find your monthly fixed cost
Truck and trailer payments, insurance, permits, parking, accounting, phone, and whatever you pay yourself that does not depend on miles. This is the part that takes the time, and it is the part everything else rests on.
Put it in the cost-per-mile builder
On the home page. Divide by the miles you actually run in a month, including empty ones. For many people the result is higher than they expected, which is exactly why it's worth doing.
Click Apply to calculator
Your cost base now drives every calculation on the site and every module in the console.
Score a load you already ran
Not a hypothetical one. Take a real load from last week where you know what you were paid and roughly what it cost you, and compare. If the answer doesn't match your books, email me and I'll look at why.
Then open the console
The eight-module console is free and unlimited. Log a few weeks of loads and the lane and customer reports start telling you things a single load never could.
Where it lives, and how to keep it
Nothing is uploaded
Every calculation runs in your browser. Open your developer tools, watch the Network tab, and use the calculator: there is no outbound request carrying your figures. The console stores your fleet in your browser's local storage.
The downside: I can't recover your data, because I never had it.
So take backups
Clearing your browsing data, using private browsing, or switching browser will lose the fleet. Keep the JSON somewhere you would keep an invoice.
What it runs on
Built to work on phones, including older ones, since a lot of this gets used in the cab.
| Platform | Supported | Notes |
|---|---|---|
| Chrome, Edge, Brave | Yes | Desktop and Android |
| Safari: macOS and iOS | Yes | |
| Firefox | Yes | Desktop and Android |
| Samsung Internet | Yes | |
| Older Android WebView | Yes | Reveal animations are skipped; every number still works |
| Internet Explorer 11 | No | Discontinued by Microsoft; not supported |
| Screen widths | 320px and up | No horizontal scrolling at any width |
| Offline | Partly | Once a page is loaded the calculations keep working; navigation needs the network |
There is nothing to install and no app to download. If a page needs JavaScript disabled to work in your environment, it will not: every calculation on this site is JavaScript, and that is also why none of it touches a server.
If something is not working
The numbers do not match my accountant
Most often this is the fixed cost per mile. Check two things: that your monthly overhead includes everything that does not depend on miles, and that you divided by total monthly miles including empty ones rather than by loaded miles. Dividing by loaded miles alone understates fixed cost per mile by whatever your deadhead percentage is.
My fleet data disappeared
The console stores everything in your browser's local storage, so clearing browsing data, using private browsing, or switching browser or device loses it. I can't restore it: I never had a copy. Going forward, use Fleet & Data → Export backup and keep the JSON file.
A number shows as a dash or NaN
Something is empty or zero where it is used as a divider, usually MPG or monthly miles. Every calculator guards against dividing by zero rather than crashing, so it shows a dash instead of a wrong figure. Fill the field in and it recalculates immediately.
The page looks broken on my phone
Try a hard refresh first: an old cached stylesheet is the usual cause after an update. If it persists, email me the phone, the browser and roughly the year of the device, and it gets tested against that.
Accessibility statement
I aim for WCAG 2.1 level AA. The site hasn't been independently audited, so this is a statement of intent and current practice rather than a certification. What is actually in place:
- Every interactive control is reachable and operable by keyboard, with a visible focus outline
- Form inputs have real <label> elements, not placeholder text standing in for one
- Body text is checked for contrast against the dark background; the gold accent is used for emphasis and never as the only way information is conveyed
- Colour is never the sole signal: a losing load says REJECT as well as turning red
- Text scales with the browser's font-size setting; nothing is locked to pixels that cannot grow
- Inputs are at least 16px on mobile so iOS does not zoom on focus
- Wide tables scroll inside their own container rather than forcing the page sideways
Known gaps: the reveal animations are decorative and currently do not respond to prefers-reduced-motion; the console's denser reports have not been tested with a screen reader. If something here blocks you, email me and I'll fix it first.
Email me
aleksnvkvc@gmail.com comes straight to me.
If a calculation looks wrong, tell me which page and what you entered, and I'll check it.