The setting
offers , a cloud platform that gives sales teams insights, forecasts and coaching, and runs AI agents that carry out tasks and automate workflows.
A fresh sandbox dataset breaks the references needed for today's rehearsal.
Realistic refreshes protect the pilot's credibility, while a fixed dataset protects rehearsal availability.
Who you’d be doing this for
“I clicked the same deal twice this morning, and both times we hit a dead end.”
Mutoni Tekle · Sales Manager · a character in this brief
She has reserved an hour with six managers to rehearse pipeline inspection before the pilot.
What is at stake
A customer rehearsal has 8 broken inspections out of 20. You must weigh a reusable handoff change against a fixed dataset that preserves today's session.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fresh datasets vs. stable references
- reusable integration work vs. immediate configuration relief
- rehearsal realism vs. session certainty
Why Gong
The MCP demonstration depends on dataset lifecycle behavior as well as successful responses from Gong APIs.
Written with these in mind
Not your kind of problem? 21 more at Gong, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Gong. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- AI Enterprise Architect (opens in a new tab)
- You will help customers understand how Gong's AI capabilities, APIs, MCP, Gong Assistant, Deep Research, integrations, and broader platform fit into their enterprise AI strategy, technology ecosystem, and revenue workflows.
- Create and present customer-specific AI reference architectures, integration patterns, technical roadmaps, validation plans, risk registers, and implementation recommendations.
- Talent Engineer (opens in a new tab)
- Lead Solutions Engineer (opens in a new tab)
- Craft content to show customers how to leverage Gong for specific use cases including MCP (client and server) and integrations.
- Help eliminate bottlenecks by working cross-functionally (Sales, Customer Success, Support, Product Management, Engineering) in order to get deals across the line.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
The same setting, from another role
Each is set around Gong’s Gong Revenue AI OS, written for a different role. They’re separate briefs, not the same scenario.
RevOps leaders are appearing in two active corporate campaigns.
You must decide whether AI proposes segments only, or also recommends which active campaign yields.
Mid-market buyers question another revenue platform while cheaper AI tools promise deal-risk signals.
You must decide which consolidation concern earns a meeting and what proof belongs in the first message.
Enterprise CIOs are pausing technical validation over incompatible claims about revenue context.
You must choose a proof-backed story that can survive security review and still create qualified pipeline.
Other problems with a similar purpose
In each of these, as in this one, the aim is to find and fix the small everyday friction that quietly erodes people's confidence in a product.
Scroll latency in large issue lists rose from 45 ms to 210 ms after richer descriptions shipped.
You have to weigh rendering shortcuts against accurate, real-time issue state.
Only 54% of affected searches produce a top-three result click, and operations managers are returning to source apps for current files.
You must weigh a targeted relevance gain against keeping discovery strong for every other search.
Thirty-nine percent of source edits lead to manual recreation of a connected asset.
You have to weigh a faster confirmation flow against the review confidence that keeps approved variants aligned.
