Pipedrive: available on request.

A competitor card on your Pipedrive records and win/loss by competitor, set up when your team asks for it. Here is where it would sit and what your reps would see.

Set up on request

Where it would sit in Pipedrive

Pipedrive supports custom UI panels on the Deal detail view through its App Extensions SDK. The competitor read would sit as a panel under the deal’s existing fields, with a link out to the full IndustryLens battlecard.

Deal · Acme Co — Pipedrive
Record fields
Stage: Negotiation
Close date: this quarter
Owner: (rep)
IndustryLens · competitor on this record
Competitor
Cognism
Our read

Cognism shipped an MCP connector linking ChatGPT and Claude to its sales data, and is pushing a report claiming 47% of European firms hiring GTM engineers did so in the past nine months — positioning itself as the AI-ready data layer for technical revenue teams, which raises the odds buyers default to it when they want governed data inside AI workflows.

How to win

Cognism sells contact and intent data; we sell competitive intelligence. Don’t compete on data coverage — ask whether the prospect’s AI workflow has a source for what competitors are actually doing, which Cognism’s connector doesn’t cover.

Latest move

Cognism combined its MCP connector news with a published claim that 47% of European firms hiring GTM engineers did so in the past nine months, reinforcing its AI-ready data positioning. — Nov 2026

Illustrative mock-up of what an IndustryLens panel could look like inside Pipedrive. The competitor move shown (Cognism, Nov 2026) is real, publicly tracked IndustryLens data; the record fields and deal name around it are fictional.

What win/loss would need from Pipedrive’s data model

Pipedrive deals have a built-in "Lost reason" field on closed-lost deals, but no standard competitor field. Win/loss would need a custom field (single or multi-select) your team already uses to record which competitor a deal was against, mapped the same way the HubSpot app maps its competitor field today.

Win rate per competitor would read Pipedrive deals where status is won or lost, grouped by the mapped competitor custom field, with Pipedrive’s native lost-reason field grouped and counted the same way HubSpot’s closed-lost reason is today.

What your reps would see

A few examples of how a competitor card on the Pipedrive record would play out, using a real IndustryLens-tracked move from Cognism (Nov 2026) to show what “our read” and “how to win” would actually say.

On the deal

A deal’s custom competitor field is set to Cognism during a pricing discussion.

The panel shows

Our read on Cognism’s AI-data positioning and the How to win line on category difference (data vs. intelligence).

What the rep does

Leads with "we’re not replacing your data tool" instead of a head-to-head feature fight the deal can’t win.

On the deal

A deal closes lost and the rep records "Price" as the lost reason, with Cognism named in a note.

The panel shows

Latest tracked move (the MCP connector launch), with a note that the credit-based pricing contrast against Cognism’s quote-gated model is covered in the full battlecard.

What the rep does

Adds the real pricing-model contrast to the loss write-up instead of a one-word "price" reason.

On the deal

A rep preps for a renewal call where the account also uses Cognism for data.

The panel shows

Latest tracked move and a link to the full Cognism battlecard.

What the rep does

Positions IndustryLens as complementary to Cognism rather than competing, matching how the account actually uses both.

What works today without it

You don’t need a Pipedrive integration to use IndustryLens. Every battlecard is available on your IndustryLens dashboard already, the weekly briefing lands by email regardless of CRM, and the MCP connector gives any AI assistant your team uses live access to the same competitor data — none of that waits on a Pipedrive build.

Want IndustryLens for Pipedrive?

Tell us how your team uses Pipedrive and we'll scope the build.

Request this integration