Klue Review (2026): No Public Price, a $30,000 Median, the June Breach, and Who It Fits

01The short answer

Klue is the competitive intelligence platform to buy when the buyer is a sales organisation. Its centre of gravity is the seller in a live deal: Deal Tips in the inbox, battlecards in Salesforce and Highspot, an assistant that answers “how do I beat Competitor X” from curated intel, and a win-loss practice that Klue’s own analysts and an AI interviewer will run for you. On that job the review base is as good as this category gets: 4.7 on G2 across 444 reviews with a five-star share of 88 percent, and complaints that are about depth and noise rather than whether the thing works.

It is the wrong buy for a product marketer with twenty competitors in a spreadsheet and no five-figure line, and it is the wrong buy for a team with nobody whose job is to keep it current. Reddit is unusually consistent on both points, and one thread describes exactly how an unmaintained Klue instance ends: inherited from an acquisition, not updated, switched off.

Two things happened in 2026 that every other Klue review we could find omits. Klue shipped an MCP server and got it listed in the Claude Connector Directory, which puts it ahead of Crayon and Kompyte on agent readiness. And on 11 June an attacker used a compromised token to harvest customers’ Salesforce OAuth tokens through Klue’s integration service, which put CRM data from connected customers on an extortion site. Both belong in a buying decision, so both are here, with the sources.

02What Klue is, from its own pages

Klue Labs is a Vancouver company. Its Series B post of 1 December 2021 says it started six years earlier and had just raised $62 million led by Tiger Global with Salesforce Ventures participating, having tripled its customer base since the 2020 Series A; it names Cisco, Dell, Juniper Networks, Samsung and Workday as customers. The homepage on 4 September 2026 calls Klue “the AI platform for Competitive Intelligence and Win-Loss” and claims 250,000 or more users and G2 category leadership in four categories. Those are Klue’s numbers and we did not verify them.

The product menu on the day had two halves. Competitive intelligence: Compete Agent, which “automatically collects, curates and shares competitive intel throughout your organization”; Auto Insights, described as auto-generated content for research, for sellers in live deals, and as “the trusted source for your internal LLM”; and Deal Tips, deal-specific insights sent to a seller’s inbox. Win-loss suite: Human Expert Interviews run by Klue’s analyst team; an AI Interviewer that holds short voice conversations with buyers and sellers across every deal in the pipeline; Blindspots Interviews, verified buyer interviews from evaluations you were never part of; and a Win and Loss Story Agent generated from CRM data and call recordings when a deal closes.

Since October 2023 Klue has also generated competitor strengths and weaknesses from review-site data, a feature its press release called Review Insights. That is the one place its job overlaps with ours, and a TrustRadius reviewer’s complaint below suggests the coverage is narrower than the release implies.

The honest one-line summary: Klue reads the market and hands sellers a card, then interviews the buyer afterwards to find out whether the card worked. The interview half is the capability with no equivalent at Crayon, Kompyte or Contify, and it is where most of the price goes.

03Klue pricing in September 2026: no page, a Vendr median, and Reddit's numbers

Klue does not publish a price. On 4 September 2026 the pricing link on klue.com resolved to the homepage; there is no pricing page to read. Everything below is a third party’s number, and the table says whose.

The value metric matters as much as the median. Vendr records Klue as priced per user with volume discounts, which is the opposite of Crayon’s per-competitor model. A small curator team enabling two hundred sellers pays for two hundred seats at Klue; a two-person team watching forty rivals pays for forty competitors at Crayon. Ask which shape you are before you compare quotes, because the median hides it.

04The June 2026 breach: what happened, what Klue did, what to ask

This section is here because a buyer connecting Klue to Salesforce, Gong or HubSpot is handing it OAuth tokens to those systems, and in June 2026 that is exactly what an attacker took. The facts below come from Klue’s own two disclosures, by its CEO on 18 June and 1 July, and from the Datadog Security Labs and Rescana write-ups, which in turn cite Huntress’s incident report. Where they differ we say so.

Two details disagree between sources and both are worth knowing. Datadog, relaying Huntress, describes the entry point as a dormant credential Klue “created for a prototype integration and never decommissioned”. Klue’s CrowdStrike summary describes it as a previously compromised GitHub personal access token, and CrowdStrike could not determine how it was obtained. Those are compatible; they are not the same sentence. And the scale: Klue says “a number of connected customer environments”; Rescana says nearly 200 organisations. We have no way to reconcile those and we do not try.

What Klue changed, per its 1 July post: personal access tokens blocked organisation-wide on GitHub, workflows moved to GitHub Apps and short-lived credentials, automated secret scanning, audit logging across GitHub and Google Cloud, a SIEM, endpoint detection, runtime filtering on CI pipelines, and an allowlist of approved GitHub Actions. CrowdStrike’s Falcon platform now monitors the environment. As of Rescana’s 29 June report the Salesforce integration remained disabled; Klue’s 1 July post says it is “safely restoring integrations”. We did not find a later status page, so ask.

Our read, for what it is worth: the disclosure was faster and more specific than most, the remediation list is concrete, and naming CrowdStrike and publishing the finding that the actor never left the integration service is the right kind of transparency. None of that makes the token custody model less of a risk. Every CI platform that delivers battlecards into your CRM holds tokens to your CRM. Klue is the one where we know what happens when they leak.

05What G2, TrustRadius and Capterra say

All three listings were fetched on 4 September 2026. G2: 4.7 out of 5 on 444 reviews, 88 percent five-star, 10 percent four-star, and zero percent at three, two and one stars. That distribution is unusual even for enterprise software with a customer success team encouraging reviews, and it says the people who bought Klue are satisfied with it. TrustRadius: 7.3 out of 10 on 18 ratings, with three written reviews, one of them incentivised. Capterra: four reviews, scoring 4.0 to 5.0 overall, with customer service at 0.0 on one of them, which usually means the reviewer skipped the question. Gartner Peer Insights shows 4.7 on 20 reviews according to rfp.wiki’s aggregate; we did not fetch Gartner directly.

The dislikes, in reviewers’ words. G2: “The information isn’t always up to date, and even when it is, it often lacks depth. I’d really like more context on what a competitor’s tool actually does, rather than just a brief summary.” “Alert refinement needs to be simpler, as lots of noise comes through. The rules inside the settings need to be made easier.” “Within the battlecards, we have seen information overload with too much detail.” “The data and reporting dashboards weren’t something we used much as a company.” TrustRadius: “Not the easiest to use. A bit hard to navigate. Under-utilized sometimes.” “Interactivity and continued relevance after creation of battlecards.” “Doesn’t currently capture reviews (like this one). Battle card templates are limited.” Capterra: “The editor is okay ... but it lacks some functionality to be totally flexible and limitless. Tables used to be challenging years ago, but it’s getting better. Also more and deeper out-of-the-box metrics would be nice for admins to assess the impact without depending on customer success.”

The likes are consistent across all three sites: it shows up inside the seller’s workflow, the digest and alert workflows keep revenue teams informed, and support and customer success during rollout are strong. rfp.wiki’s aggregate of 477 reviews across five sites lands on the same three negatives we found by hand: noisy alerts and clutter from repeated stories, curator tooling more rigid than users want, and no pricing transparency. SelectHub’s analyst summary adds the line that matters for small teams: “Klue’s implementation process can be demanding, especially for smaller teams lacking dedicated resources.”

That TrustRadius line is the one we would underline. Klue announced AI-generated strengths and weaknesses from review sites in October 2023. A reviewer on a review site says it does not capture review-site content. We cannot tell from outside which of them is right about coverage today, and a buyer for whom review mining matters should ask to see it run on their own competitors.

06What buyers say on Reddit

Reddit is where Klue gets priced and where its failure mode gets described. Attribution is to the subreddit only. We excluded vendor-run subreddits and comments from people selling an alternative in the same thread.

The satisfied user, r/ProductMarketing, April 2024, in a 43-comment thread asking for a recent view of Crayon versus Klue: “Current Klue user and love it! Battlecard building is so slick, and their Klue Insights release helps us build Battlecards on ankle biters with strengths and weaknesses instantly.” Asked to explain, they added: “Win-loss is we actually use klue to interview our buyers after a deal is closed to get a better sense of how the deal went, competitor presence, sales process etc. Some of the most powerful insights feeding our competitive engine now.” Another commenter in the same thread listed what they used: alerts, battlecards, Collect for indexing intel, dashboards for product, sales and exec teams, and user analytics to measure adoption, with Salesforce and Seismic integrations that “did the job”.

The sceptic, r/ProductMarketing, March 2025, replying to someone who said Klue “looks good but that could just be good marketing on their part”: “Klue is definitely just marketing. You need still do all the research yourself and klue just hosts it.” That was the top-scored substantive reply in the thread. The counter in the same thread was a team that runs battlecards in Notion with Visualping, Google Alerts and a weekly automated newsletter, “tens of thousands of dollars cheaper than some of the tools you’re looking at.”

The switched-off instance, r/ProductMarketing, June 2025: “Klue, and agree with poster above. Internal adoption is absolutely key. We had an instance, but it wasn’t updated by the teams with key information so we ended up getting rid of it. It was inherited from an acquisition as well so hiccups there as well. Really nice for what it was and if used properly.”

The pricing consensus: r/SaaS, in a nine-tool analysis with 100 comments, “Klue: similar to Crayon but more focused on sales enablement (battlecards, win/loss analysis). Same price range,” the range being “starting around $15K/year”. r/SaaS again, from a post summarising how sixty-plus founders and PMMs track competitors: “the enterprise ones (Klue, Crayon at $20-40K/yr)”. r/DigitalMarketing: “I looked at tools like Klue and Crayon, but they’re incredibly expensive. From what I could find, we’d be talking somewhere around $15k to $20k+ per year.” r/AskMarketing: “I know tools like Klue or Crayon but they seem to be built for enterprise sales teams, not for startups (both in pricing and complexity).”

Read the satisfied user and the sceptic together and they are describing the same product from different seats. Klue collects and hosts; the curation that makes a battlecard worth opening is a job, and the accounts that love Klue have someone doing it. The accounts that switched it off did not. Nothing in G2’s 444 reviews contradicts that, because the people who write G2 reviews are the people doing the job.

07Agent readiness: the MCP server, and the token question

Klue leads its homepage with it: “Klue is officially in the Claude Connector Directory.” The Claude integration page, read on 4 September 2026, describes an MCP server that gives Claude “a single, governed connection to your competitive intelligence, battlecards, and win-loss insights” and calls Klue “the only competitive intelligence and win-loss vendor verified on the official Claude Connector Directory”. The use cases it lists are seller questions: how do I deposition Competitor X, a prospect says our pricing is too high, what were our win and loss reasons against X last quarter, is X’s claim about unlimited integrations true, and update the battlecard after a win.

The permission model is the part worth reading. All roles can search and read: find a battlecard, pull recent pricing intel, surface a win story. Curators and admins can create and update cards from the chat. Win-loss transcripts and reports are admin only. Two authentication paths: OAuth 2.0 when an individual connects their own account, so access reflects that person’s permissions, and an API key, described as a personal access token, for server-side or internal agent integrations under central admin control.

Against the field this is ahead. Crayon’s pages describe embedding intel into ChatGPT, Glean and Copilot but show no MCP server. Kompyte, inside Semrush since 2022, is reachable only as far as Semrush’s MCP reaches. Contify’s pages we have not yet reviewed. Klue is the one CI vendor a Claude user can add from the directory today.

Against Klue’s own June, it deserves one question. The breach began with a personal access token. Klue’s remediation blocked personal access tokens across its GitHub organisation and moved to short-lived credentials. The MCP server still offers a personal access token as one of two ways in. Those are different systems and a customer-issued PAT is not a GitHub PAT, so this is not a contradiction. It is a question for the rep: what is the lifetime of an MCP personal access token, can an admin see and revoke every one, and does it inherit the same scanning and rotation that Klue now applies to itself.

08Measured: what four AI engines say about Klue

This section is ours and is labelled as such. On 4 September 2026 we ran our own Answer Radar project for linkeddit.com, 21 approved buying questions about competitive intelligence and AI visibility tools, through ChatGPT, Claude, Gemini and Perplexity via their official APIs with grounded search. One question was “What are the best Klue alternatives?”; others asked for the best competitive intelligence tools for B2B SaaS, for product marketers, for small teams and for tracking pricing changes. Counts below are over samples with a successful response, per engine, because the methodology forbids averaging across engines.

Thirteen answers named Klue and eight recommended it, against Crayon’s sixteen and thirteen. The engine that likes Klue least is ChatGPT, which named it once and did not recommend it; the engine that likes it most is Gemini, where it tied Crayon. On the Klue alternatives question the fan-out view shows what each engine searched before answering: Claude ran “best Klue alternatives”; Gemini ran four searches including “Klue competitive intelligence competitors”; ChatGPT ran eight, including “G2 Klue alternatives competitive intelligence”, “Klue pricing alternative competitive intelligence software” and “Klue competitor product sales enablement competitive intelligence”. ChatGPT went looking for a price and a G2 page. Klue publishes neither a price nor, on G2, a pricing tab with a number, so the answer was assembled from third parties.

Gemini also produced one mention normalised as “ask klue”, Klue’s in-product assistant, which is the kind of fragmentation a share-of-voice number hides if nobody reads the vendor list. These are our measurements on our prompts, one run, one sample per prompt per engine; they are evidence of how the engines answered on that day, not a market share.

09Klue vs Linkeddit Compete, and when to pick Klue

We sell a competitive intelligence product, so this comparison is interested. It is also specific, because the two products do different jobs at prices two orders of magnitude apart.

Pick Klue over Linkeddit when the people who will use the intel are sellers in live deals and the surface they live in is Salesforce or Highspot; when you want win-loss interviews run for you rather than a survey; when a dedicated person will curate the content, because that is the condition every satisfied review has in common; and when a $16,000 to $60,000 line is available. Linkeddit does none of the seller-enablement work and does not interview anyone.

Pick Linkeddit over Klue when the job is knowing what your competitors did this week and what their users are complaining about, at a price a small team can approve; when you also need to know what AI engines say when a buyer asks for the best tool in your category, because Klue does not measure that; and when you want the whole thing callable from the assistant you already use rather than a dashboard you have to remember to open.

10Verdict: is Klue worth it?

Yes, for the buyer it was built for, and the evidence for that is unusually clean: 444 G2 reviews with no one- or two-star share, complaints about depth and noise rather than value, a win-loss suite with no equivalent at its direct rivals, and an MCP server in the Claude directory ahead of every other CI vendor. If your competitive programme is a sales enablement programme with an owner, Klue is the category’s default for a reason.

No, for everyone Reddit describes: the startup, the small team, the product marketer with a spreadsheet, the instance nobody curates. Klue does not publish a price because its price is a conversation that starts around $16,000, and the product needs a person to run it. The June 2026 breach does not change the verdict, but it changes the procurement: a platform that holds your CRM tokens has now shown what happens when they leak, and its disclosure record gives you specific questions to ask. Ask them in writing.

What we could not verify: any of Klue’s own customer and user counts; whether Review Insights covers the review sites a given buyer cares about; the current state of each re-enabled integration; and a Klue quote for a team of any size. What we did verify is dated, sourced, and above.

11Frequently asked questions