Key takeaways
- Most stage changes show up in an email before anyone updates the CRM.
- Let the assistant propose the change and point to the line that justifies it.
- Approve changes to stage, amount and close date; never let them drift unseen.
- Written exit criteria per stage let the assistant and the team judge alike.
Why do deal stages fall behind
Deal stages fall behind because the evidence arrives in the inbox while the record lives somewhere else. A buyer confirms a proposal review or pushes the decision to next quarter, and the seller means to update the CRM after the next call.
By the weekly pipeline review, half the board shows where deals were, not where they are. Forecast conversations then start with correcting the data instead of discussing the deals.
What should trigger a deal stage change
A deal stage should change when the buyer does something that meets the stage's exit criteria, not when the seller feels optimistic. Write one or two criteria per stage so a person or an assistant can test an email against them.
The stages below are an illustrative set; use your own names and criteria.
- Qualification to Discovery: the buyer agrees a first call about their problem.
- Discovery to Proposal: the buyer confirms the need and asks what it would cost.
- Proposal to Negotiation: the buyer comes back on terms, price or scope.
- Any stage to closed lost: the buyer says no, or goes silent past an agreed date.
Can you move a deal stage with AI on its own
An assistant can propose a stage move from an email, but a person should approve it, because an email can sound warmer than the deal really is. Polite enthusiasm is not a signed order.
This differs from classic deal stage automation, where a rule moves a deal when a fixed event happens, such as a document being sent. Rules are predictable but blind to what the buyer wrote; an assistant reads the words and explains its reasoning, which suits real, untidy conversations better.
How do you update the close date with AI
Ask the assistant to look for any date the buyer mentions, such as a board meeting, a budget cycle or a planned start, and propose a close date that follows from it. Ask it to quote the sentence it relied on.
Close dates drift quietly when nobody owns them. A proposed date tied to the buyer's own words gives the seller something concrete to confirm on the next call.
How do you keep the pipeline honest after AI updates
Keep the pipeline honest by reviewing the board weekly and questioning any deal that has not moved, whatever updated it last. AI updates remove retyping; they do not remove the need for a seller to own each deal.
Look for patterns in what you correct. If the assistant keeps proposing Negotiation too early, tighten the written criteria for that stage rather than overriding it every time.
How to update deals from email threads, step by step
Set the criteria once, then run the loop after every meaningful email.
- Write one or two exit criteria for each deal stage, so every change has a clear test.
- Connect the mailbox where buyer conversations happen, Gmail or Outlook.
- After a meaningful email, ask the assistant to read the thread and propose updates to the deal's stage, amount, close date or probability.
- Check each proposed change against the buyer's own words, then approve or correct it.
- Review the board weekly and question any deal whose stage has not moved.
Where Pebbles Ai fits
- CapabilityProspecting & customer recordsDeals in the Pebbles Ai CRM (in Beta) hold a name, description, stage, amount, currency, close date and probability, with a board view, saved views and filters. In Manual mode a CRM write from the assistant waits for your approval before the deal changes.
- FoundationIntegrationsWith Gmail or Outlook connected, the assistants can search and read the thread behind a deal. For deals kept in Attio or Pipedrive, they update the record through MCP, each write an approval action under the execution mode.
Common questions
Which deal fields can AI update from an email?
Any field the email gives evidence for: usually the stage, close date, amount and next step. Probability is a judgement, so treat an AI suggestion there as a prompt for discussion.
Is an AI deal update the same as a workflow trigger?
No. A trigger moves a deal when a fixed event happens. An assistant reads what the buyer wrote and proposes a change with its reasoning, which a person then approves.
Should reps still update their own deals?
Reps should still own their deals. The assistant removes the retyping, but the rep confirms each change and adds what only they know from calls.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
