Skip to main content

The Problem With "Summarise This" in Sales

  • July 21, 2026
  • 2 replies
  • 17 views

JamesABarton
RevStarter

Talking with our sales team yesterday, a recurring theme was the experience they’re having with sellers using “summarise” functions in AI tools. Especially the one‑click, buttonised versions baked into  platforms. On paper, these are great for speed as sellers don’t have to type notes, they just hit “Summarise” and move on.

The pattern we’re seeing, though, is that a lot of nuance gets lost. When a seller presses a generic summarise button, they’re usually not adding any context about the opportunity, stakeholder dynamics, methodology (MEDDICC, SPIN, etc.), or what “good” looks like in their environment. Unsurprisingly, we end up with summaries that are fast but shallow.

From an enablement perspective, that creates some interesting challenges:

  • If sellers and managers start operating primarily off AI summaries, any distortion in those summaries becomes a second‑order enablement problem as coaching is based on partial reality, pipeline reviews miss key context, and training content calibrates against noisy data.

  • At the same time, summarisation clearly has upside in as much as call notes synced to CRM, quick recap emails, digestible deal histories – so “turn it off” doesn’t feel like the right answer either.

I’ve written a LinkedIn piece on this, but I’d really like to hear what other enablement leaders are doing in practice.

Would love to hear specific practices, policies or even horror stories if you’re willing to share them. It feels like one of those areas where enablement has to actively shape how AI is used, not just accept whatever the tools ship by default.

2 replies

Brennan Peyton
Showpad Team

Hi ​@JamesABarton its a really good question.  I am wondering if you are talking about AI tools generally here or a specific experience in Showpad? 

We surface AI summaries in a number of different ways in the platform to avoid exactly the issue you describe.  If its by “asset” then the AI summary is specifically linked to that asset (Doc, Deck, Txt file) and shows next to that asset.

If you are using our new Field Meeting Agent and its summarising a note (or ingesting a call from teams) then it will specifically reference your CRM and gives the detail around the stake-holder and chosen sales methodology (if thats been set up as a requirement)

The Meeting Overview below is the output from a Demo Meeting with Hick’s Software to show the details that the AI Generates including “missing fields” from our CRM that should have been captured as part of our methodology along with suggested questions that might uncover these needs.  One of the Showpad Team would be happy to arrange a demo for you of this - just let us know.

I hope this is useful as context on how we approach AI and making sure it helps both the seller and enablement team.
 

Meeting Title: Hicks Software

Meeting Date/Time: 16 July 2026 at 17:00

Related CRM Record: Hicks Software LTD

Participants:

Lydia Hicks (lydia.hicks@showpad.com)

Meeting Overview — Hicks Software

Meeting Title: Lena Meeting – Lunar Arm Deal Pricing & Q4 Delivery Discussion Organizer: Brennan Peyton (brennan.peyton@showpad.com) Scheduled: July 16, 2026 | 4:00 PM – 5:00 PM UTC Account ID: 01KRK5TDSSHK6E47NHM36KYP6N

Participants

Name Title Email Role
Brennan Peyton brennan.peyton@showpad.com Internal – Organizer / AE
Lydia Hicks   External – Customer Contact

Note: Job titles are not available for either participant. See Discovery Questions below for recommended follow-up.

Meeting Summary

A post-meeting note was recorded by Brennan Peyton following a discussion with Lena (Lydia Hicks) regarding the Lunar Arm Deal. Key themes included Q4 delivery expectations, a pricing discount contingency, and a significant logistics constraint tied to rocket booster readiness impacting Mars delivery feasibility.

Topics Discussed

  • Q4 delivery timeline for the Lunar Arm deal
  • Pricing discount request (12%) contingent on Q4 delivery
  • Rocket booster readiness — not expected until Q2 of the following year
  • Mars logistics constraint and its impact on delivery
  • Technology team consultation requirement
  • Deal structuring to account for delivery risk

Key Discussion Points

  • Lydia is ready to move forward with the Lunar Arm deal, targeting Q4 as her preferred delivery window
  • Pricing is a critical sticking point: Lydia is requesting a 12% discount if delivery is confirmed by Q4; failure to deliver on time will result in a reduced pricing obligation for the seller
  • A material constraint exists: Rocket boosters required to complete the Mars delivery route are not expected to be ready until at least Q2 of the following year — this directly threatens Q4 delivery feasibility
  • The technology team has not yet been consulted to validate whether Q4 delivery is achievable under current constraints
  • The deal structure does not yet account for the rocket booster delay or the associated pricing risk

Salesforce Data — Missing Fields & Discovery Questions

The following key Salesforce fields appear to be missing or unpopulated. These gaps should be addressed to maintain CRM hygiene and support accurate forecasting and pipeline management.

Missing CRM Fields

Field Status Why It Matters
Contact Title / Role (Lydia Hicks) Missing Required to understand decision-making authority and tailor messaging
Opportunity Name / ID Not referenced Needed to link notes and next steps to a trackable opportunity record
Opportunity Stage Missing Critical for pipeline visibility and forecast accuracy
Close Date Missing Q4 intent noted verbally — needs to be formalized in CRM
Deal Amount / Contract Value Missing Pricing discount discussed but no baseline price captured
Discount Approval Status Missing 12% discount contingency needs formal approval tracking
Decision Maker(s) Missing Is Lydia the sole decision maker? Are other stakeholders involved?
Competitor / Alternative Solutions Missing No competitive landscape captured
Next Step Date Missing Follow-up timing not formalized
Account Address / Territory Missing Useful for logistics and territory alignment

Recommended Discovery Questions

  • "Lydia, can you help me understand your role in the approval process — are you the primary decision maker, or are there other stakeholders we should include?"
  • "What does success look like for you if we deliver the Lunar Arm by Q4 — what are the business outcomes you're working toward?"
  • "If Q4 delivery is not achievable due to logistics constraints, what would your revised timeline look like, and how would that affect your budget planning?"
  • "Are there other vendors or solutions you're currently evaluating alongside this?"
  • "What internal approvals do you need to finalize a deal of this size and scope?"
  • "Can you walk me through what the procurement or contract sign-off process looks like on your end?"

Outstanding Tasks

  • Loop in the Technology Team to assess Q4 delivery feasibility for the Lunar Arm given rocket booster readiness constraints
  • Investigate rocket booster readiness timeline — currently not expected until Q2 of the following year — and determine the downstream impact on Mars delivery
  • Restructure the deal to incorporate the booster delay and Mars logistics risk, protecting against the reduced pricing clause if Q4 delivery cannot be guaranteed
  • Clarify pricing implications with Lydia — confirm what pricing applies if Q4 delivery cannot be committed to
  • Create / update the Salesforce Opportunity with deal details, stage, close date, and pricing information
  • Document Lydia's title and stakeholder map to confirm decision-making authority
  • Obtain internal discount approval for the 12% contingency request

Key Next Steps & Prep Steps

Immediate Actions (Owner: Brennan Peyton)

  • Schedule a call with the Technology team to get a definitive answer on Q4 delivery feasibility — this is the blocker for the entire deal structure
  • Do not commit to the 12% discount until internal technology and logistics confirmation is received
  • Prepare a risk-adjusted deal proposal with two pricing scenarios: (1) Q4 delivery confirmed and (2) Q4 delivery not achievable — present both to Lydia transparently

Before the Next Customer Meeting

  • Confirm technology team's assessment of Q4 delivery feasibility
  • Prepare a clear timeline showing the rocket booster constraint and how it interacts with the Lunar Arm delivery schedule
  • Update the Salesforce Opportunity with current stage, close date, and deal value prior to the next touchpoint
  • Prepare supporting materials (case studies, technical specs, delivery track record) to reinforce confidence in your delivery capability

Recommended Next Steps Aligned to Sales Methodology

  1. Confirm Business Impact & Urgency — Quantify what Q4 delivery means to Lena's business; understand the cost of delay from her perspective to strengthen mutual commitment
  2. Map the Decision Process — Identify all stakeholders, approval steps, and procurement timelines to avoid late-stage surprises
  3. De-risk the Deal Commercially — Work with leadership to define acceptable discount thresholds and build contractual protections (e.g., delivery milestones, force majeure clauses) tied to the booster constraint
  4. Advance the Opportunity Stage — Once technology confirms feasibility, move the opportunity to the next stage in CRM and propose a formal Business Review or Solution Presentation
  5. Establish a Mutual Action Plan (MAP) — Co-create a written timeline with Lena outlining key milestones, decision dates, and sign-off requirements to align both sides toward a defined close date

Notes recorded by Brennan Peyton on July 17, 2026. Transcript not available — summary based on audio note.


JamesABarton
RevStarter
  • Author
  • RevStarter
  • July 21, 2026

Hi ​@Brennan Peyton.  It was a general comment, not specific to Showpad, but the buttonising issue is pervasive, as you dont get a chance to choose what's important in the summary (the lens by which its viewing it), and this the bit, for me anyway, is an opportunity missed (pun intended).