GigaOm Radar: What Vendors Need to Understand

GigaOm is a technology research and advisory firm whose Radar reports compare solutions in defined enterprise technology markets. For a vendor, the useful question is whether the assessment helps the right buyers understand its product, its limits and the evidence behind its claims. A familiar-looking graphic can conceal a different evaluation model. Preparing for the wrong model can leave a capable product poorly explained.

That matters particularly with GigaOm’s refreshed Radar. The current framework connects technology assessment to three executive buying perspectives, while treating buyer fit, assessed position and development momentum as separate ideas. Vendors need to establish which methodology applies to the edition they are entering before reusing a previous submission or promising leadership a particular outcome.

What Does the GigaOm Radar Assess?

GigaOm’s current Radar framework uses the CTO, CIO and CISO as evaluation lenses. These cover new capability and competitive advantage; operational efficiency, reliability and cost; and governance, risk, compliance and security. Inclusion begins with a separate pass-or-fail criteria gate. Meeting that baseline establishes eligibility for assessment rather than earning a strong comparative score.

For preparation, this means that a product demonstration should answer more than a technical feature question. A capability may be useful to a CTO because it enables something new, to a CIO because it reduces operating work, and to a CISO because it strengthens control. The evidence for each claim may differ. A single architecture slide cannot automatically establish all three outcomes.

How Should Vendors Read the Chart?

The refreshed framework has four quadrants: Foundation Builders, Agile Optimizers, Enduring Innovators and Disruptive Pioneers. They describe different kinds of buyer fit rather than a hierarchy in which one quadrant is best. Leader and Challenger are ring designations, distinct from the quadrants. A vendor should therefore read the written assessment alongside its plotted position.

GigaOm also separates velocity from placement. Its current labels are Outpacing, Fast Following and Slow Following. These concern the pace of capability development relative to the market. A strong momentum assessment and a strong current position answer different questions; neither should be presented as proof of the other.

Older Radar editions can use different terminology and graphics. When comparing editions, check the methodology first. A changed label or location can reflect a framework change, a different scope or new evidence. Kea’s advice is to explain those differences before showing leadership a comparison that appears to demonstrate progress or decline.

When Should a Vendor Engage?

GigaOm publishes a Research Topic Calendar that identifies areas of planned coverage. It explicitly describes this as a topic forecast, subject to change, rather than a confirmed publication schedule. A topic on that calendar is a reason to ask about scope and participation. It does not establish a report title, a guaranteed place in the evaluation or a fixed deadline for a questionnaire.

The practical first conversation should establish which product is being considered, which buyers and use cases define the category, who owns the research and what information is needed next. Record the answer and the next contact date. If the product is outside scope, record the reason and check whether another research topic provides a better fit. Repeated outreach without a clear question adds little.

During an active evaluation, use the instructions supplied for that edition. GigaOm’s vendor guidance calls for timely responses, verifiable evidence, briefings and factual review. Its factual-review window is an opportunity to correct inaccuracies. It does not give a vendor ownership of the analyst’s judgement.

What Evidence Makes Participation Useful?

Kea recommends an evidence register that connects each requested criterion to a specific product capability, a current source and a named internal owner. Distinguish what is available today from what is committed on the roadmap. Where a capability depends on a particular deployment, integration, licence or third-party component, make that dependency explicit. Precision gives an analyst something that can be checked.

For example, a claim that a product reduces operating effort should identify the workflow, the comparison and the conditions under which the improvement was observed. A security claim should explain the control and its coverage. A new capability should show a usable outcome. Where evidence is incomplete, describe the limit rather than turn an ambition into an established result.

The same discipline should connect the questionnaire, briefing, demonstration and subsequent factual corrections. Give one person responsibility for the submission and keep the supporting specialists involved. That reduces contradictions and makes it easier to respond when the analyst asks a question that the presentation did not anticipate.

What Can a Vendor Do With the Result?

Participation, the published assessment and permission to use research in marketing are separate matters. GigaOm’s usage guidance makes promotional rights dependent on the particular report and licence. Before planning a launch, confirm what can be reproduced, which claims are permitted and what review is required. An attractive chart position does not itself authorise a broader leadership claim.

GigaOm also offers commissioned research and other commercial formats alongside its syndicated research. Confirm what an engagement actually delivers. A commissioned asset, a benchmark exercise and a Radar assessment should each be described according to its purpose; buying one does not establish the outcome of another.

How Kea Helps Vendors Work With GigaOm

Kea helps establish whether GigaOm belongs in the vendor’s analyst programme, then connects the relevant research topic to an accountable engagement plan. We map the analyst and product scope, clarify participation requirements, organise the evidence and prepare the team for questions that cross product, operations and security. Research tracking includes replies, deadlines, exclusions and the next action.

After the assessment, we help leadership interpret the result and decide what deserves action. That may be a product evidence gap, a clearer explanation of buyer fit, a factual correction or a permitted use of the published findings. The first step is to identify the relevant Radar edition and compare its requirements with the evidence the business can support. That creates a useful plan before anyone starts chasing a badge.