1 · Discovery: Rep asks about the current process
Sales rep: Walk me through how your team handles this today—from first conversation to updating the CRM.
Prospect: It’s mostly manual. Reps take notes, then someone tries to update Salesforce later. It works until volume spikes.
Amotions (Next Question): The prospect described a process, not yet the underlying failure mode. Clarify before proposing a fix. Dig into the handoff, not the tool list: “Where does that break down most often—during the call, or after?”
2 · Adaptive pivot: Prospect unexpectedly reveals a major problem
Sales rep: Where does that break down most often—during the call, or after?
Prospect: Actually, our biggest problem isn’t the workflow. It’s that our team can’t get the information into Salesforce. Deals stall because the data never lands.
Amotions (Adaptive Pivot): The prospect pivoted from “manual workflow” to Salesforce data-entry as the core pain. Staying on the original process path would miss the real qualification thread. Adapt the discovery sequence. Suggested question: “What happens today between completing the work and getting that information into Salesforce?”
3 · Objection: Prospect pushes back on “another tool”
Sales rep: What happens today between completing the work and getting that information into Salesforce?
Prospect: We’ve already tried CRM cleanup projects. I’m not sure another tool would stick—our reps ignore process after the kickoff.
Amotions (Objection Response): Adoption skepticism after acknowledging Salesforce pain—“tools don’t stick.” Pitching features now confirms the objection. Clarify what failed before you talk product. Clarify-first: “When those cleanup projects stalled, was it missing fields, missing coaching in the moment, or no owner after go-live?”
4 · Buying signal: Prospect shows a buying signal
Sales rep: When those cleanup projects stalled, was it missing fields, missing coaching in the moment, or no owner after go-live?
Prospect: Mostly coaching in the moment. If you could guide reps on Salesforce hygiene during the call—without another training deck—we’d want our RevOps lead in the next conversation.
Amotions (Buying Signal): Buyer named the desired outcome (in-the-moment guidance) and invited a next stakeholder (RevOps). This is a multi-thread buying cue. Lock the next step while criteria are explicit—don’t restart a product dump. Next action: confirm RevOps availability this week and propose a short working session on two Salesforce friction moments from recent calls.