[← All articles](https://clarveni.com/blog) The Clarveni blog A competitor launches something new. Is it a threat or just noise? ==================================================================== Assess a competitor launch through availability, customer relevance and evidence of use before changing your roadmap, service or sales conversation. By Clarveni Published 5 October 2026 6 min read In this article 1. [Start with availability, not the launch headline](#content-start-with-availability-not-the-launch-headline) 2. [Use a descriptive scorecard, not a spurious total](#content-use-a-descriptive-scorecard-not-a-spurious-total) 3. [The two assessments lead to different next questions](#content-the-two-assessments-lead-to-different-next-questions) 4. [Make the response smaller than the speculation](#content-make-the-response-smaller-than-the-speculation) 5. [Keep the conclusion at the level the evidence supports](#content-keep-the-conclusion-at-the-level-the-evidence-supports) [Back to the top ↑](#article-h) In this article 5 sections 1. [Start with availability, not the launch headline](#content-start-with-availability-not-the-launch-headline) 2. [Use a descriptive scorecard, not a spurious total](#content-use-a-descriptive-scorecard-not-a-spurious-total) 3. [The two assessments lead to different next questions](#content-the-two-assessments-lead-to-different-next-questions) 4. [Make the response smaller than the speculation](#content-make-the-response-smaller-than-the-speculation) 5. [Keep the conclusion at the level the evidence supports](#content-keep-the-conclusion-at-the-level-the-evidence-supports) ![A launch announcement and two separate evidence notes connect to an open ring, leaving the assessment unresolved.](/prezet/img/blog/blog-14-launch-evidence-hero-v1.webp)A launch announcement and two separate evidence notes connect to an open ring, leaving the assessment unresolved. A competitor announces a new product or service. Someone asks whether it should move your roadmap, change a sales conversation or trigger a competing launch. Before choosing a response, establish what is actually available and whether it solves a problem your customers care about. An announcement can deserve attention without proving a threat. Equally, limited evidence of adoption is not a reason to dismiss an offer that removes an obstacle your buyers regularly face. Evaluate availability, customer relevance and commercial evidence separately. The useful question is not “Does this sound impressive?” It is “What buying decision could this change, and what do we know about that change?” [\#](#content-start-with-availability-not-the-launch-headline "Permalink")Start with availability, not the launch headline -------------------------------------------------------------------------------------------------------------------------- “Introduced”, “previewed” and “available” can describe different situations. Read the supporting material for who can obtain the offer, where it operates, which conditions apply and whether a meaningful part of it remains planned. A demonstration shows what was demonstrated. It does not establish that every customer can use the capability. An open booking page can establish a route to purchasing a service, but not that it has customers or has delivered the promised results. Where sources differ, preserve the narrower established scope until the discrepancy is resolved. Do not silently convert a broad announcement into proof that every associated capability has shipped. The distinction between [reported and observed change](/blog/reported-change-vs-observed-change) also matters when describing when the offer appeared. [\#](#content-use-a-descriptive-scorecard-not-a-spurious-total "Permalink")Use a descriptive scorecard, not a spurious total ---------------------------------------------------------------------------------------------------------------------------- Assess the launch against five questions: availability, customer problem, access to the intended buyers, evidence of use and relevance to your own position. Record the evidence and the gap for each question rather than awarding points that suggest a scientific threat rating. The two worked assessments below use that structure. One concerns software and the other a service; neither assumes that a louder launch deserves a bigger response. *These examples compare launch assessments. They are not the email layout.* ### [\#](#content-launch-a-an-inventory-planning-software-add-on "Permalink")Launch A: an inventory-planning software add-on **Availability:** A competing software supplier announces suggested replenishment quantities. Supporting documentation limits access to an invited pilot using a specified catalogue format. It does not describe automatic purchasing. The announcement supports a bounded trial, not general availability or end-to-end ordering. *These examples compare launch assessments. They are not the email layout.* **Access to buyers:** The pilot is described for selected existing accounts. Whether new buyers can obtain it, and on what terms, remains unclear. Do not describe the launch as a fully available alternative in every current sales discussion. **Evidence of use:** A staged demonstration appears in the announcement. There are no permission-cleared customer accounts of regular use, comparable results or switching decisions in the evidence set. The demonstration can explain the idea without settling its practical value. **Your position:** Your product already helps users review stock, but does not suggest replenishment quantities. The overlap is therefore a specific task, not proof that the competing product is superior in every respect. Your team needs to understand how much of the customer’s difficulty lies in that task. The proportionate response is to clarify pilot scope and examine the customer problem before promising a matching feature. Keep sales descriptions accurate: the capability has been announced for a restricted pilot, not established as broadly available. A later general release or credible evidence from relevant users would justify revisiting the assessment. ### [\#](#content-launch-b-evening-training-cohorts-for-shift-managers "Permalink")Launch B: evening training cohorts for shift managers *These examples compare launch assessments. They are not the email layout.* **Customer problem:** You provide daytime on-site management training. Existing customers have told your team that releasing shift managers together during working hours can be difficult. Evening delivery therefore addresses a known scheduling question, not merely a different course title. **Access to buyers:** Individual places are offered across several employers rather than through a single company booking. That may reduce the commitment needed to enrol a small group, but the total cost and suitability still depend on travel, working arrangements and the customer’s requirements. **Evidence of use:** A published timetable does not establish attendance or learning outcomes. There is no basis for claiming the courses are successful, unpopular or attracting your customers. Those remain separate questions. **Your position:** On-site delivery allows material to be connected to one employer’s working context. The competing cohorts may offer scheduling flexibility but not the same setting. The assessment should preserve that trade-off instead of treating format alone as a winner. Here a customer conversation may be useful before waiting for uptake figures. Ask whether the existing scheduling difficulty would be better addressed by a different time, smaller groups or another delivery arrangement. You can investigate that need without announcing a new evening programme or pretending to know what buyers will choose. [\#](#content-the-two-assessments-lead-to-different-next-questions "Permalink")The two assessments lead to different next questions ----------------------------------------------------------------------------------------------------------------------------------- For the software launch, availability is a material uncertainty. The next question concerns who can actually use the capability and whether it helps with the task customers describe. For the training launch, a route to purchase is clearer, while suitability and outcomes remain unresolved. In neither case does the assessment stop at “no adoption evidence, therefore no threat”. That would confuse a gap in knowledge with evidence of failure. A service can deserve investigation because it addresses an established customer difficulty, even before you know how it performs commercially. The opposite mistake is to interpret any customer relevance as a mandate to copy. A relevant offer may be a poor fit with your strengths, expensive to deliver or less useful than a simpler change. The assessment establishes what deserves consideration; it does not choose the roadmap on your behalf. [\#](#content-make-the-response-smaller-than-the-speculation "Permalink")Make the response smaller than the speculation ----------------------------------------------------------------------------------------------------------------------- Start with an action that answers the important question. That might be checking published eligibility, correcting an inaccurate sales claim or asking customers about an existing obstacle. A large investment needs more support than a launch announcement and an attractive explanation of what might happen. Also ask which response remains useful across plausible outcomes. Clarifying what your offer already does can help even if the competitor’s pilot expands slowly. Understanding training schedules can help even if customers prefer your existing delivery format. These are more defensible actions than reacting to an unverified success story. Where an offer does not overlap with the customers or problem you serve, record that reason and hold your position. Revisit it if availability, scope or evidence of use changes. A quiet decision can still be a considered one. [\#](#content-keep-the-conclusion-at-the-level-the-evidence-supports "Permalink")Keep the conclusion at the level the evidence supports --------------------------------------------------------------------------------------------------------------------------------------- A useful conclusion names what has launched, the relevant boundary and the question that follows. “An invited pilot addresses a task our customers have raised; establish eligibility and practical usefulness” says more than “a major threat is emerging”. The same discipline applies when reading a [weekly competitive intelligence briefing](/blog/weekly-competitive-intelligence-briefing-template). Treat the launch as evidence to interpret alongside your own customer knowledge, not a command to change direction. [Explore Clarveni](/) for a finished weekly briefing on the companies you choose to track, with the business response remaining yours to decide. You’ve reached the end. [Back to the top ↑](#article-h) Read next ----------- [### Act, watch or hold? A framework for responding to uncertain signals Separate exposure, confidence and decision timing. Four worked responses show when to act, verify, watch or hold without pretending uncertainty has gone. → ](https://clarveni.com/blog/respond-to-uncertain-company-signals) [### Before a key-account meeting: a company intelligence checklist Turn company developments into useful account-meeting questions. Recheck the dates and scope, separate assumptions and prepare a relevant follow-up. → ](https://clarveni.com/blog/company-intelligence-account-meetings)