eltyoCheck the evidence for each deal before deciding what needs action, what can wait and what the sales rep needs to clarify.
Review time changes the equation.
Adjust the assumptions. Checking the result takes time too.
Assumption: 2 minutes of AI-assisted preparation per task. Calculation: tasks × (current time − 2 min − review) ÷ 60. Excludes setup, maintenance and other costs.
Before your sales meeting, give Claude the record IDs for a handful of open HubSpot deals. Ask for one row per deal, with the activity behind the decision, the proposed next step and anything that still needs checking. The sales rep opens the records and makes the final call during the review.
HubSpot provides the MCP server that exposes CRM data. Claude uses it through the official directory connector. You start this read-only review in chat when you need it. A scheduled run would require a scheduler and a way to route decisions for review. The steps below follow the vendors’ documentation. The exercise uses fictional data. HubSpot connector for Claude
1. Pick the deals and agree what to read
In CRM → Deals, choose three to five open deals from one pipeline. Note their Record IDs and set the review date and activity window. The sales lead picks the deals. Each deal owner checks the context and confirms the decision.
| Data | What you use it for |
|---|---|
| ID, stage and owner | Open the right record and find the person who can confirm the next step. |
| Next step | Read the existing text and check it against recent conversations. |
| Associated notes, meetings and tasks | Verify recent commitments and spot an open task that already covers the action. |
| Close date | Place the deal in the pipeline. Use a task due date or a dated commitment for the action deadline. |
An activity may be missing because it was logged elsewhere or the connected user cannot see it. Check the source coverage before treating a deal as neglected. HubSpot’s default deal properties
2. Connect HubSpot with limited read access
In Claude on the web, open Profile → Settings → Connectors → Browse. Select HubSpot, choose Connect, and select the intended HubSpot account on the authorisation screen. A Super Admin or a user with App Marketplace Access can connect the app. Other users need a Super Admin to approve the app and configure its access first. Set up the HubSpot connector
Use an account that can view the selected records. Block the connector’s write tools for the pilot where your settings allow it. Ask for a first read on one ID and compare the stage and owner with the record. If you cannot restrict writes through account permissions or connector settings, run the exercise with a small, anonymised export in a chat without CRM access. Claude connector permissions
HubSpot lists the connector as available on all its plans. Anthropic includes connectors in Claude’s free plan, subject to usage limits. Check which permissions and tools are available in your account before the pilot. When Sensitive Data is enabled in HubSpot, this connector cannot read associated engagement data. Ask the deal owner to check the history they are authorised to see. Connector requirements and limits · Claude plans
3. Copy the review prompt
Prepare the [date] review for deal IDs [IDs] in the [name] pipeline. Use HubSpot read tools. For each ID, retrieve the stage, owner, next step, relevant notes and meetings between [start] and [end], and associated open tasks. Read only what is needed for the decision.
Give me one row per ID with the owner, stage, status, proposed decision and evidence. Include a record link or a verifiable reference and the date of the supporting note or task where available. Keep only explicit deadlines. Mark closed deals and deals in a different pipeline as “Out of scope”.
Apply these rules in order. “Check” if necessary details are missing or conflict. “Wait” if a conversation confirms a future date for resuming contact. “Already tracked” if an open task covers the action, flagging anything overdue. “Review” if a dated source supports an action that still needs to be scheduled. Keep all proposals in chat and finish with the records to reopen during the meeting.
4. Check the decisions on four fictional deals
This example uses 10 November 2026 as the review date and covers activity from 1 to 10 November. The rows below show the expected result after human review.
| What the record shows | Expected decision |
|---|---|
| 3101. Open task T-91, “Send the revised estimate”, was due on 9 November. | Already tracked. Eloise checks the overdue task and decides whether to complete or reschedule it. |
| 3102. A note from 5 November says the prospect wants to resume on 16 November. | Wait. Malik keeps the agreed date and checks whether a reminder exists. |
| 3103. The next step is blank and the connector returned no engagement data. | Check. Lina opens the record and checks authorised sources before proposing an action. |
| 3104. The 9 November meeting calls for two demo slots to be proposed before 12 November. The open tasks reviewed contain no matching item. | Review. Nora checks the tasks, then confirms who will offer the slots and by when. |
During the meeting, open each record. Check the ID, source, date and any open task that already covers the action. The owner then records the decision in HubSpot. If the answer is incomplete or a usage limit interrupts the read, split the batch and retry only the missing IDs. For a quote, check the conversation and agreed date before sending a follow-up. Eltyo’s quote follow-up guide
To decide whether to repeat the exercise, time two reviews with the same scope, including verification. Count decisions that needed correction and existing tasks the team found. Keep the rules that help the team decide with the evidence it has.
Explore the original sources.
The references behind this approach. Examples and exercises in this article are illustrative.