Why buy EO data through a platform when you could buy directly? Part 1: Choice, availability, and cost

For many organizations, buying Earth observation data often begins with a provider. The team knows the type of data they want, they've used it before, and they expect to continue ordering it. So going directly to that provider seems like the shortest and most economical route.

In a straightforward project, it might be. If the same sensor can meet every single request and the buying process is simple, a direct relationship works just fine. But real-world requirements rarely remain that tidy.

Just a few examples: an area may not be covered when it’s actually needed. Cloud cover can make an otherwise suitable optical acquisition unusable. A tasking request may be rejected because of capacity, lead time, acquisition geometry, local restrictions, collection restrictions due to geopolitical constraints, or competing priorities.

Or, a project that began with one geography can expand. New users need a different resolution, revisit frequency, spectral capability, licensing model, or delivery time.

At this point, good imagery isn't enough. Organizations need a dependable way to obtain the most appropriate data each time circumstances don't match or requirements change.

A preferred provider doesn't equal a complete sourcing strategy

Teams have sound reasons for favoring a particular provider. The imagery could already be validated for an internal workflow. Analysts know the product. A model may have been trained on it, or commercial terms may already be in place. But using a platform doesn't mean tossing all that work aside. The same provider and collection can remain the default choice, and the team will benefit from more alternatives through the same environment, especially if the default choice can't be used for any of the above reasons.

Consider an optical monitoring project and imagine the situation: The preferred collection may offer the right resolution and price under normal conditions. During a time-sensitive incident, however, cloud cover could make optical data useless, while a SAR sensor could get through those clouds. Meanwhile, over another location, there might already be existing archive imagery from a different provider, which removes the need for a new tasking order.

Without a platform, every exception can lead to a new search, vendor assessment, contract, integration, and purchasing process. With a platform, alternatives can be evaluated and ordered through an existing relationship and a consistent workflow. Less stress for everyone involved.

Tasking feasibility should be discovered early

Ordering archive imagery is relatively straightforward: the data either exists or it does not. Tasking introduces more uncertainty.

A collection might appear technically suitable, but the acquisition may not be feasible within the requested window. Satellite capacity, orbital opportunities, incidence angles, weather conditions, minimum order sizes, priority levels, and other constraints all influence the likelihood of success. Even a feasible request doesn't always result in a successful acquisition.

When working through a single provider, an unsuccessful feasibility check can send the buyer back to the beginning. The team then needs to identify another source, learn a different ordering process, and determine whether that provider can meet the same requirements. All while the acquisition window may be closing.

A multi-provider platform makes feasibility part of a broader sourcing decision. Users can compare suitable collections, inspect archive availability, and look at alternative tasking options without rebuilding entire workflows. In some cases, you can even view opportunity windows and task directly, skipping feasibility altogether.

On top of that, a dedicated customer success team can speed up this process by liaising with different providers, offering multi-source tasking for large projects, resolving constraints, and helping identify alternatives. If one route is unavailable, the project can adapt fast.

This matters most when imagery supports an operational deadline. Assessing a site before a field visit, monitoring construction progress, investigating an incident, documenting environmental change, or observing infrastructure during a defined period are all examples we've seen from customers. In these situations, access to an alternative, apart from its sheer convenience, protects the outcome of the project.

Does buying direct mean paying less?

The assumption that direct purchasing must be cheaper is understandable. Removing an intermediary sounds like removing a markup, but Earth observation procurement doesn't always work that way.

Platforms and providers operate through commercial partnership agreements. The price available through a platform can be aligned with the provider’s own pricing rather than carrying an automatic premium. The exact commercial model varies by provider, collection, order type, licensing terms, and committed volume, so buyers can evaluate pricing on a like-for-like basis within the platform using standardized commercial terms, rather than assuming differences based on sales channel.

The unit price of the image is also only one part of the cost. A direct relationship with several providers can create additional work across vendor onboarding, legal review, security assessment, procurement, account administration, credit management, invoicing, API integration, data normalization, support... These costs can spread across departments, and might not even be counted as part of the imagery budget, but the organization still pays them.

There's also a cost attached to delay. If a team spends days finding and onboarding an alternative after its preferred source cannot fulfill a request, the eventual image may have the same nominal price while the project becomes more expensive.

A complete cost comparison should include:

• The quoted price and licensing terms for equivalent data
• Minimum commitments, prepaid credits, and balance utilization considerations
• The internal effort required to onboard and manage each supplier
• Integration and maintenance work for separate APIs and data formats
• The time required to find an alternative when an order is not feasible
• The financial or operational impact of missing the required acquisition window

Access to alternative data and tasking options is an important part of the platform case. It's not the whole case, though. Once Earth observation becomes a recurring capability used by several teams, organizations also need a sustainable and efficient way to integrate providers, control spending, manage users and access, and govern their data.

We'll examine that enterprise dimension in Part II, coming in a few weeks.

‍