Your team already knows someone inside hundreds of carriers. Nobody has ever been able to tell you which.
RadarNetwork matches the people your reps already know to a USDOT number, then goes one hop further — to the people they can reach through a colleague, and the name of the colleague who can make that introduction. It runs as a panel beside the LinkedIn page a rep already had open. Knowing someone is not intelligence. Knowing the bridge is — and it is the one thing no carrier database can sell you, because it comes out of your own company.
The panel, on the page they were already on
Open a carrier on LinkedIn and RadarNetwork identifies it as a real motor carrier — fleet size, domicile, USDOT — then shows who you already know there, first-degree connections first, with the colleague who can bridge the rest.
Panel layout is the shipping one. Carrier and contact names here are fictional.
“Somebody here is connected” is not a warm path
Plenty of tools will tell you your company has a connection at an account. That is a dead end dressed as a lead, because the rep still has to work out who, ask around, and hope. RadarNetwork resolves all three:
The specific person inside the carrier — VP of Safety, Director of Recruiting, the operations manager — not a count of anonymous connections.
The named colleague on your own team who can make the introduction, and how strong the tie is. That is the sentence a rep can actually act on in Slack this afternoon.
Every contact carries the date it was last seen on a page. A bought contact list cannot tell you that, which is why so much of one is quietly wrong.
The date is the part people underestimate. A purchased contact record has no honest freshness — the vendor knows when they scraped it, not when the person was last actually in that seat. Every name in RadarNetwork is stamped with the day LinkedIn last rendered it on a page one of your reps opened, so a stale record looks stale instead of looking like a lead.
Three steps, and then it maintains itself
Setting it up — about ten minutes, once
Nothing to configure afterwards, and nothing for a rep to remember to do
On LinkedIn, request a copy of your data with Connections ticked. When the archive arrives, drop the CSV into RadarNetwork. That maps your whole first-degree network onto carriers, in any browser, before you install anything.
Install from the Chrome Web Store, pin it, and link your DotRadar account with the platform tab open. It reads your session from that tab — it never sees your password.
Open a carrier and the panel fills in beside the page. Open a person and it shows the carrier they work for. One visit to a company’s People tab maps who works there and which of your connections can introduce you — and it only ever reads a page you opened yourself.
Step one works with no extension at all, which is the fastest way to see whether the map is worth having.
What it will never do
It never navigates, clicks, paginates, sends a connection request, sends a message, or runs on a timer, and nothing is ever posted to LinkedIn. It keeps only what LinkedIn already rendered on a page a rep chose to open, and your data is not shared outside your own account and team.
That list is short on purpose, and every clause in it is a decision. Automation tools that click through LinkedIn on a rep’s behalf put the rep’s account at risk and put your company on the wrong side of the platform’s terms. RadarNetwork is a reader. It sees exactly what the human sitting in front of it sees, at the moment they choose to look, and it writes down the part that is about a trucking company.
The consequence is that coverage grows out of prospecting rather than out of a crawl. A rep who works twenty carriers this week has mapped twenty carriers. Nobody is scheduled, nothing runs overnight, and there is no volume to throttle.
It belongs to the company, not the laptop
The map is scoped to your team and stays with it. When a rep leaves, the introductions they could make do not walk out with them — the paths their colleagues can still use are already recorded, dated and attributed. And a rep’s own connections are never exposed to the rest of the team as a contact list; what the team sees is that a path exists and who can open it.
The numbers on the dashboard are recomputable from dated records rather than assembled into a score: carriers you can reach, carriers with a named introduction path, second-degree contacts mapped, contacts kept from pages you opened, and how each moved in the last thirty days. It is a picture of your prospecting surface, and you can check it.
Built to survive LinkedIn changing its mind
This is the unglamorous part that decides whether a LinkedIn reader is still working in six months, so it is worth being specific about.
Almost everything a reader like this gets wrong, it gets wrong because LinkedIn changed a string or a piece of markup. The clearest case in our own history: LinkedIn switched the connection-degree badge from one form to another, the company reader went quiet, and captures degraded for everyone. The code fix was a single expression. Getting that one expression to a rep took a Chrome Web Store submission and days of review, during which the product was broken for every user.
The strings, selectors and thresholds the reader consumes are served from DotRadar and refreshed on a short cycle. A change LinkedIn makes at four in the afternoon can be answered the same afternoon, with no new version to install and nothing for a rep to update.
The version installed on the rep’s machine is the floor. It checks every value it is handed against what it shipped with and takes only what survives — so a bad configuration, a truncated response or no response at all leaves a working reader running last week’s rules.
Every capture records the reader version and the configuration in force when it was made, so a bad rule can be identified and rolled back rather than quietly poisoning the graph. A single switch reverts every reader to its packaged behaviour.
Two consequences a buyer should care about. First, the parsing logic itself stays inside the installed extension — Chrome’s extension platform forbids fetching and running remote code, and a product that did it would be removed from the store. What moves over the wire is data the packaged code consumes, which is the difference between a maintainable reader and a policy violation.
Second, when it cannot read a page, it says so. A reader that reports an unreadable page as an empty company is worse than one that fails loudly, because it turns a parser bug into a wrong answer that looks like a finding. RadarNetwork tells the rep which of those two things happened.
RadarIQ, in the weeds →
Try DotRadar free