Salesforce
Gong
Gmail

Build a Deal Loss Analyzer Agent withSalesforce, Gong, and Gmail

Right now the forecast means stitching Gmail, Salesforce, and Gong by hand. Understanding loss patterns requires querying months of historical data across systems; then correlating textual analysis (calls, emails) with structured data (deal size, stage progression, competitors), so the work lands late and half-blind.

Try in Claude

Deal Loss Analyzer runs on deal data split across 3 tools.
The forecast pays for it.

The forecast pays for it.

SalesforceGong

Salesforce is a step behind.

Fields in Salesforce move whenever someone logs them; to identifies systematic reasons deals are lost by analyzing closed-lost opportunities you need salesforce closed-lost opportunities fresher than that.

GongGmail

Gong tells a different story.

What Gong knows about related conversations rarely flows back to Salesforce. Two tools, one unreconciled gap.

GmailSalesforce

Gmail catches it quietly.

Competitor presence surfaces in Gmail ahead of time, but that tab is closed during deal loss analyzer.

Under The Hood

Identifies systematic reasons deals are lost by analyzing closed-lost opportunities from Salesforce, Gong, and Gmail in one prompt, nothing to stitch. Already connected.

01

Read identifies systematic reasons deals are lost by analyzing closed-lost opportunities from Salesforce (system of record)

Salesforce closed-lost opportunities

Salesforce
02

Query related conversations from Gong (call platform)

email threads

Gong
03

Read competitor presence from Gmail (comms layer)

Gong calls

Gmail
output

Agent-ready output

Identifies systematic reasons deals are lost by analyzing closed-lost opportunities, related conversations, and competitor presence, returned as one digest deal loss analyzer ranks for you.

The Context Store

Salesforce closed-lost opportunities from Gmail, Salesforce, and Gong, pre-joined before the agent runs.

Gmail, Salesforce, and Gong and 3 more get reconciled up front for deal loss analyzer: salesforce closed-lost opportunities, email threads, Gong calls, competitive data, pricing/proposal documents mapped to a single deal view instead of 6 separate APIs.

Your agent queries one surface instead of three APIs. Faster responses, lower cost per query, and results that work because the relationships were built before you asked the question.

SHARED KEY6 SOURCESONE VIEWLIVE READS

The Prompt

Copy. Paste.
a Deal Loss Analyzer Agent

Two steps. Your data, your results, under 60 seconds.

01installOne-time setup. ~2 min.
Connect the Airbyte Agent MCP
02copy and run
Prompt
Help me turn Salesforce, Gong, and Gmail into a single forecast I can act on.

SETUP
You have the Airbyte MCP layer, wiring up 6+ tools you can query in plain language.

WORKFLOW
connect Salesforce, Gong, and Gmail -> read salesforce closed-lost opportunities, email threads, Gong calls, competitive data, pricing/proposal documents -> merge into one deal view -> rank and explain. Each unconnected source is a single OAuth click away.

TASK
Identifies systematic reasons deals are lost by analyzing closed-lost opportunities, related conversations, and competitor presence, then give me a single digest: sorted by what needs me first, each line with the why and the move.

The Outcome

Identifies systematic reasons deals are lost by analyzing closed-lost opportunities drops from 3 hours to under a minute. Now your agent can fix it.

10x

Faster

~10x. Deal loss analyzer drops from a 3-hour chore to one query.

90%

Cheaper to run

~90% cheaper: zero new infra and no seats added to identifies systematic reasons deals are lost by analyzing closed-lost opportunities.

3 -> 1

Tools, one query

3 tabs into 1: Salesforce, Gong, and Gmail collapse to one view to identifies systematic reasons deals are lost by analyzing closed-lost opportunities.

Based on internal benchmarks comparing Context Store queries to sequential API calls across equivalent datasets.

01 · Output

Priority scoring

Every deal scored 1-10, so deal loss analyzer surfaces what needs you first instead of an alphabetized list.

02 · Signal

Mismatch alerts

Salesforce vs Gong mismatches on identifies systematic reasons deals are lost by analyzing closed-lost opportunities get called out so you decide, not the math.

03 · Context

The why, attached

Related conversations from Gong and Gmail sits beside each item, letting you identifies systematic reasons deals are lost by analyzing closed-lost opportunities without switching tabs.

04 · Action

Tells you what to do

For each deal, deal loss analyzer names the next step. Who to contact and what to send. Not just a number.

05 · Brief

Paste-ready output

The digest arrives meeting-ready: salesforce closed-lost opportunities first, sources attached, Salesforce, Gong, and Gmail reconciled.

Common questions

Didn't find your answer? Please don't hesitate to reach out.

Contact us

What Salesforce data does Deal Loss Analyzer touch?

Just salesforce closed-lost opportunities, plus email threads, Gong calls, competitive data, pricing/proposal documents, via Salesforce's scoped permissions. Deal loss analyzer copies nothing outside your stack.

How do I trust the forecast?

Deal Loss Analyzer cites a source per line. Salesforce closed-lost opportunities from Salesforce, the rest from Gong and Gmail. So any figure traces back.

Can I tweak what Deal Loss Analyzer returns?

Edit the TASK line. Change the ranking, the digest format, or which of Salesforce, Gong, and Gmail it leans on.

Does Deal Loss Analyzer replace Salesforce?

No, it reads Salesforce and writes back the digest. Your record systems stay put.

Stop tab-switching to identifies systematic reasons deals are lost by analyzing closed-lost opportunities. Let the agent read Gmail, Salesforce, and Gong.

51+ connectors including Salesforce, Gong, and Gmail are ready. Give deal loss analyzer the access to identifies systematic reasons deals are lost by analyzing closed-lost opportunities.