What should a non-space software company bring to Connect by CNES?

A non-space software company should approach Connect by CNES with a customer problem and a question about how space data or technology might help. It does not need to pretend to be a satellite manufacturer. The useful discussion concerns whether a space component improves a service enough to justify the cost and complexity of using it.

CNES describes Connect by CNES as support for companies and public organisations developing applications using space data and technologies. Its services include technical expertise, incubation, acceleration, access to intellectual property and other business support. The stated fields include environmental, mobility and territorial applications. Connect by CNES service description Read the CNES contract documents for software suppliers before pricing the integration, rights and support responsibilities.

For a company building environmental reporting software, the initial problem might be inconsistent information across a customer's property portfolio. The question is whether an appropriate space-derived input can improve a specific reporting decision. That is more useful than starting with a commitment to use a particular satellite dataset regardless of the customer's needs.

Describe the current workflow. Who supplies information, how often it is updated and what decisions depend on it? Identify the cost of the existing limitation. A more detailed dataset is not automatically more valuable if the customer cannot use the extra detail or if the workflow only changes annually.

Bring evidence from intended users where possible. A discussion with a prospective customer can establish the format, update frequency and explanation the customer expects. It should not be presented as a purchase commitment unless one exists. Technical support becomes more targeted when the service requirements are explicit.

The company should also identify what it already knows and what it needs help determining. Perhaps its software integration is mature but it lacks experience assessing data suitability. Perhaps it understands the data but has not established a viable service model. These are different support needs and may lead to different next steps.

Ask about the boundaries of any proposed support. What expertise is included? What would the company need to provide? Are there separate application, eligibility or contractual conditions? The public overview describes a service offering, not an unconditional entitlement to resources.

Plan for the commercial service beyond the supported activity. Data access, processing, customer support and quality control may create recurring costs. A successful prototype should help estimate those costs rather than conceal them behind temporary support. The product team needs to know whether the service remains affordable at the customer's likely usage level. The GEODES booster cost review makes the cost of continuing an Earth-observation service visible after initial support.

Keep the relationship accurately described in marketing. Receiving advice from CNES does not mean CNES is the company's customer, investor or certifier. Public references should reflect the actual agreed relationship and any conditions on names or logos.

CNES assesses the support request as well as the technology

CNES's Comité des nouveaux entrants explains how incoming support requests are considered. Its review covers the team, technical realism, market, environmental responsibility and strategic relevance, alongside the sustainability of the requested assistance for CNES. The committee can select a level of support and designate a continuing point of contact. This gives a first meeting a clearer purpose: establish the company's problem and the assistance that would usefully address it.

For a non-space business, the market element can be its strongest contribution. A company already serving environmental consultancies or local authorities may understand a workflow that space specialists do not encounter directly. It can explain the existing product, the customer's decision and the information that is missing. CNES expertise can then help examine whether a space-derived input would improve that service.

The technical question should be proportionate to the product decision. A company considering an annual environmental report does not need the same input or delivery model as one offering a frequently updated operational dashboard. Starting with the customer's timing and output requirements allows the discussion to identify relevant data characteristics without turning it into an unfocused tour of available missions.

The commercial buyer may differ from the ultimate beneficiary

Space applications often serve several organisations in a chain. A data-processing company might sell to a consultancy, which incorporates the output into advice for a property owner. A software platform might serve a public authority whose reports are used by several departments. The organisation benefiting from better information is therefore not always the one selecting and paying the immediate supplier.

Consider a hypothetical property-reporting business. Its end users want clearer information about environmental change across a portfolio, but their advisers already prepare the formal reports. The startup could sell a finished report directly or provide a data product to those advisers. The first model requires customer acquisition and a reporting service; the second requires integration into an existing professional workflow. Both may use the same space data, yet they imply different development and support needs.

A productive CNES discussion can examine which of those models makes the space component useful. If advisers require an output that fits their established reporting process, a technically richer dashboard may have little commercial advantage. The relevant development question could concern format, explanation or repeatability rather than adding more observations. That is why evidence about customer practice belongs beside a description of the proposed technology.

The choice also affects scale. A direct service can require substantial individual customer support. A partner-delivered product may reach more end users through fewer commercial relationships, while depending on the partner's sales and delivery priorities. The company should be able to explain which trade-off it is pursuing and what it needs to learn before committing development resources.

Different forms of assistance create different company commitments

The newcomer committee's explanation allows several legal forms for support, and says some assistance can involve payment or an agreed contribution in kind. That makes the requested relationship commercially relevant in its own right. Technical advice, a software licence, access to resources and a development agreement can all be useful, but they place different obligations on the company.

A startup should connect those obligations to the product decision being made. Limited expert assistance may be sufficient to establish whether an input is suitable. A deeper development relationship may be appropriate once the company knows the intended service and the work needed to deliver it. Moving directly to the most extensive form of support can create unnecessary complexity when the unresolved question is still relatively narrow.

The GEODES route offers a concrete example of a later, more specific need: an application using Earth-observation data may need help maturing its processing and preparing for industrial delivery. That is different from an initial discussion about whether space data belongs in the product at all. Recognising the stages helps the company explain why it is asking for a particular kind of assistance now.

The first meeting is therefore most useful when it produces a sharper commercial and technical question. The company leaves with a clearer view of the space component, the evidence needed to evaluate it and the form of assistance suited to that work. That is a substantive product-development outcome even before a larger programme or contract enters the picture.

This is a route for exploring business applications of space technology, with potential relevance to companies operating across civilian and defence-adjacent markets. It is not evidence that every resulting service is suitable for a government use. The immediate objective is a better-founded product decision: whether the space component solves a real problem and what would be required to commercialise it.