SalesCoach
A buyer saying “sounds good” is a terrible CRM stage
Turn an AI call summary into a forecast a sales manager can inspect.
At the end of a demo, the buyer says, “Sounds good. I’ll see what procurement thinks.” An AI summary calls the meeting positive. A rep moves the deal to proposal. By Friday, the forecast says procurement is reviewing an offer that nobody actually sent.
Granola’s engineering team describes why meeting summaries and searchable transcripts can surface different details. Sales teams can use the distinction practically. Preserve an approved reference to the decisive sentence and ask what the buyer has committed to doing. Granola • Why agents missed transcript evidence
Give four kinds of statements different homes
| What the buyer says | A defensible CRM entry |
|---|---|
| “I like that view.” | Positive reaction to a feature. |
| “We need reporting by region.” | Stated requirement. |
| “I’ll ask Lee whether we have budget.” | Buyer-owned action, with date still open. |
| “Lee will join us Tuesday at ten.” | Scheduled buying step, once the meeting is confirmed. |
Have the rep read the original language before saving a stage change. For the procurement example, a useful follow-up is “What does procurement need to see, and when would it help to send it?” That asks for a concrete next step while respecting the buyer’s actual decision process.
At pipeline review, pick one opportunity the team recently advanced. Can a second rep identify the last action the customer took, who owns the next action, and when the forecast should be revisited? If the answer lives only in an adjective such as “engaged,” update the record before debating the probability. A clearer forecast starts with a more accurate verb.