Starlink for Installers and Professionals
A professional Starlink job has five stages: survey the site, commission the dish, verify the installation with a soak test, hand the customer a report, and diagnose from data when they call later. The official app sites the dish, confirms it is online, and runs a speed test, but it keeps no record you can attach to a job sheet.
This page is the spine of our professional guides. It applies whether you install on rooftops, vessels, vehicles, or remote sites: the workflow is the same, only the mount changes. Where a dedicated desktop tool makes a stage easier, we point to how Nexus Telemetry Pro handles it.
What does a professional Starlink workflow look like?
Survey before you drill. Use the Starlink app's obstruction check to choose the position and aim the dish before you mount, scanning from the exact spot and height it will sit. The dish then builds its own obstruction map from what it sees, a first pass within about an hour on current firmware and settled by the next day, so you get an early read before leaving and confirm it the next day. A mount moved a metre at survey costs nothing. The same mount moved after handover costs a return visit.
How to do a Starlink site survey →
Commission with a recording running. Session recording captures every metric at one-second resolution while you work: obstruction, latency, drop rate, power, and the dish's own event log. Twenty to thirty minutes recorded alongside your normal commissioning work becomes the baseline for everything that follows.
Verify against known-good numbers. A verified installation shows stable latency to the Starlink point of presence in the 20 to 40 ms range, a drop rate at or near zero outside satellite handovers, and a quiet event log across the soak, plus 0% obstruction confirmed by the app and the dish's own map. Anything persistently outside those ranges gets solved from the ladder, not from a return visit.
How to verify a Starlink installation →
Hand over a report, not a reassurance. The recorded session exports as a PDF: executive summary, full charts, every event and marker timestamped, speed test results, and network diagnostics by region. For marine and vehicle work it includes a route map coloured by latency, so a sea trial becomes a single persuasive page. The customer gets proof. You get a baseline on file for every job.
Diagnose from data when the phone rings. Most return visits are not faults, they are disagreements about what "working properly" looked like on day one. With a baseline on file, a fault report becomes a comparison. And the single most valuable diagnostic in the field is separating a dish problem from a LAN problem, which Pro does by running the same test from your laptop and through the Starlink router's API side by side.
Is it Starlink or the Wi-Fi? →
Which tools does a professional actually need?
The dish itself provides the telemetry, free, on the local network. What you add is the software to read, record, and report it.
The official app is the right tool for activation, account setup, and the obstruction check that sites and aligns the dish. Use it for what it is.
Command-line tools like iPerf remain the standard for raw throughput testing between two machines you control. iPerf is awkward to set up on Windows, so we wrote the missing instructions.
How to install iPerf on Windows →
Nexus Telemetry Pro covers the rest of the workflow in one native application for Windows, macOS, and Linux: live telemetry at one-second resolution, the obstruction map, session recording, the diagnostics suite (ping, traceroute, iPerf, DNS, port checks), the event log, and PDF session reports. One licence covers two devices, so the shop machine and the field laptop are both covered. There is a free trial, so you can run a full verification session on your own dish before deciding.
What about consumer-facing problems?
The consumer guides cover the underlying mechanics that professional work touches constantly: how obstruction works and how to fix it, what a good ping looks like, why a dish keeps dropping, and how much power a dish really draws, which matters for every battery and solar quote. For the full metric-by-metric picture, start at How to Monitor Your Starlink.
Monitoring beyond handover
If you maintain the connections you install, or you manage terminals for clients on an ongoing basis, single-dish tools stop being practical at somewhere around the third site. That is a fleet problem: unattended collectors at each site, one dashboard for the estate, alerts when a terminal degrades.
How Nexus Telemetry Fleet handles multi-terminal monitoring →
Where to start
If you have an installation booked this week, read the verification guide and run the workflow on the free trial. It adds twenty minutes of recording to a job you were doing anyway, and it ends with a document your competitors do not leave behind.
Nexus Telemetry is built by Liquidbinary Ltd, the team behind the first Starlink Enterprise management platform, in production across thousands of terminals from 2022 to 2025. More about the team →