Use daily Deal Snapshots to compare HubSpot pipeline movement, amount shrink, close-date slips, and owner changes before sales reviews.
Last updated: June 19, 2026
This tutorial shows how to use Sanka Deal Snapshot to keep a daily record of HubSpot deal movement. Start by asking Claude or Codex to review the latest snapshots, then confirm follow-up actions before changing any deal.
Claude/Codex
Review the latest two Deal Snapshots for our HubSpot pipeline. Show amount shrink, stage movement, close-date extensions, owner changes, and stalled deals. Prepare review notes only; do not update HubSpot yet.
Preparing Deal Snapshot reviewI found deals with amount shrink, close-date slips, and stage movement since the previous snapshot. Review the notes before assigning follow-up actions.
Ask for another snapshot review...
Before you start
Check that you have the following ready.
HubSpot is connected to Sanka
The target deal pipeline is clear
The fields you want to compare are defined, such as amount, stage, close date, probability, owner, and selected custom fields
A daily capture time and retention period are agreed with the sales team
Claude or Codex is connected to the same Sanka workspace
Set the daily snapshot scope
Decide which pipeline and fields should be captured each day. Keep the first setup focused so sales managers can trust the daily review.
Sample prompt
/sanka Help me define the daily Deal Snapshot scope for our HubSpot pipeline. Include pipeline, capture time, retention period, and fields for amount, stage, close date, probability, owner, and forecast review. Prepare a setup plan for review.
For most teams, start with:
Pipeline and stage
Deal amount and currency
Probability or forecast category
Close date
Owner
Status
Custom fields used in weekly pipeline review
Review yesterday-to-today movement
After daily snapshots are available, ask Claude or Codex to compare the latest two captures. The goal is to find meaningful movement before the sales review.
Sample prompt
/sanka Compare the latest two Deal Snapshots. Group changes by amount shrink, stage movement, close-date extension, new deals, removed deals, owner changes, and stale deals. Explain the top risks and keep follow-up actions pending for review.
Review these areas carefully:
Deals whose amount decreased
Deals that moved backward or skipped expected stages
Close dates pushed out from the previous snapshot
High-value deals with no movement
Deals reassigned to another owner
Pipeline totals that changed materially
Turn differences into follow-up actions
Use the snapshot diff as the evidence for follow-up, not as an automatic update. A manager should review the proposed actions before routing work or changing deal data.
Sample prompt
/sanka From this Deal Snapshot diff, draft follow-up actions for sales managers. Include deal name, owner, reason, recommended action, and urgency. Do not update records or send notifications until I approve.
Useful follow-up patterns include:
Ask the owner to confirm why a close date moved
Route discount or pricing changes to quote review
Create a manager review note for high-value shrink
Move stale deals out of commit after human approval
Prepare a forecast-risk summary for the pipeline meeting
Checkpoints
Use Sanka logs and reports to confirm when snapshots were captured, which deals changed, and who approved follow-up actions.
Search Sanka...
Review Deal Snapshot activity
Logs
Search logsAll actionsAll dates
ID / ActionDateTarget / ItemChangeActor
4Follow-up approved2026/06/18 09:40Q3 enterprise pipelineManager approved three follow-up actions from the snapshot diffSales manager
