SteelCollar Robotics and Aeronautics
Home / Orbit / Do you need a satellite, or the data?

Do you need your own satellite, or just the data?

The honest first question in this market, and the one that dissolves a surprising number of missions.

On our robotics side, the first honest question is whether the job needs a robot at all, and often it does not. Orbit has an exact twin: a striking number of satellite projects are really data projects wearing hardware ambitions, and the data usually costs a fraction of the constellation.

If what you need is imagery, weather, ship positions, radio occultation, or almost any Earth observation product, there is a decent chance somebody's satellites are already collecting it and will sell it to you: as archive, as tasking, or as a subscription. The commercial data market has matured quietly and quickly, and buying from it means someone else carried the launch risk, the insurance, the licensing and the ground segment, and you carried a purchase order.

Owning makes sense when one of a few things is true. The data you need does not exist and cannot be tasked: an unusual sensor, an unusual revisit pattern, an unusual place. Control is the point: sovereignty, security or guaranteed access that a vendor relationship cannot promise. The satellite is the product: you are building a communications or services business where the asset is the business. Or you need to fly something of your own, an instrument, a technology demonstration, a payload that proves a thesis.

There is a middle path worth knowing about: hosted payloads. Your instrument rides on someone else's satellite, using their power, pointing and downlink. You get your sensor in orbit without building a spacecraft company around it. Access to hosting opportunities is patchy and relationship driven, which is precisely the kind of thing an introduction is for.

Bring us the underlying need rather than the architecture. If the honest answer is a data subscription, we will say so, the same way Joe tells a machine shop that a conveyor beats a robot. If it truly is your own hardware, then the conversations that follow, about launch, ground and licensing, all get easier, because you will know exactly why you are flying.

The takeaway

Ask what you would do with the data before asking about the satellite. Buy the data when it exists, host the payload when only the sensor is yours, and build only when the reason survives that questioning.

Have a mission in mind?

Describe it to Joe in plain language. In this market he will not recommend a provider or quote a cost; he will help frame the problem and, when it is real, our team makes introductions after confirming interest and availability.

All Orbit notes