ChatGPT + HubSpot: 12 ways to spend less time on sales admin

When to use it

You sell, and after every conversation there is admin: notes, a reminder, a deal update, a follow-up. Before the next one, preparation all over again. These prompts assume the official HubSpot app is connected in ChatGPT with access to your deals, contacts and activity. Each one is scoped to a single chore, asks for record links so you can check the answer, and either makes no changes or shows the proposed change before saving. Replace the [BRACKETS] with your own deal, pipeline, owner and dates.

1. Finish the call, finish the admin

Give it your rough notes while the conversation is fresh and let it prepare the note and the follow-up task together. Check three things before approving: did it capture the conversation, is it the right deal, and does the task have the right owner and date.

Using the HubSpot connector, find the deal [DEAL NAME]. Turn these call notes into a concise note: [PASTE NOTES]. Prepare one task to [TASK, e.g. send the demo agenda], assigned to [OWNER NAME], due [DATE]. Associate both the note and the task with this deal. Show the proposed note and task before saving anything. Ask me if any detail is missing.

2. Decide who needs your attention today

Twenty open deals is not a plan. Turn it into a specific question: approaching close date, gone quiet, or no next step. The useful part is the reason behind each suggestion.

Using the HubSpot connector, review open deals owned by [OWNER NAME] in [PIPELINE], due to close between [START DATE] and [END DATE]. Find up to five that need attention because of an approaching close date, no logged activity in 14 days, or a missing next step. Show amount and currency, close date, last activity, next step, and a record link for each. Explain the priority using only those facts. State how many records you checked and any retrieval limits. Make no changes.

3. Prepare for a meeting without opening five tabs

Five minutes before the call, you recognise the company but not where you left things. Ask for goals, the latest discussion, the people, open questions and what you promised. That last one matters most.

Prepare a one-screen meeting brief for [DEAL NAME] using accessible HubSpot records and activity from the last 60 days. Include the customer's stated goals, the latest discussion, the people involved, unresolved questions, and commitments we made. Suggest three useful questions for the meeting. Link to evidence and flag missing information. Make no changes.

4. Find out who else needs to be involved

A good contact who likes the product is not a buying decision. This shows where you are relying on assumptions: a user without a budget holder, a commercial contact without anyone from implementation.

For [COMPANY], list the associated contacts, their job titles, documented buying roles, and their most recent accessible interaction with us. Separate activity on [DEAL NAME] from other account activity. Identify buying roles we have not confirmed. Do not infer purchasing authority from job title alone. Link to sources and suggest two questions to clarify the decision process. Make no changes.

5. Give your stalled deal a useful next step

When a deal stalls it is easy to keep creating the same task: follow up. Follow up about what? Look for the unresolved questions first, and separate confirmed blockers from things the CRM simply does not record.

Review [DEAL NAME] and its accessible activity. Summarize documented concerns, outstanding commitments, decision requirements, and unanswered questions. Separate confirmed blockers from information missing from the CRM. Cite the evidence. Suggest three questions to clarify what needs to happen next. Make no changes.

6. Write a follow-up that sounds like you paid attention

Instead of reconstructing the conversation from a blank email, draft from the deal record. Check that it reflects the customer's priority, that your commitment is accurate and that the next step is clear. Then change anything that does not sound like you.

Draft a follow-up email to [CONTACT NAME] about [DEAL NAME], using accessible HubSpot history and notes from the deal record. Reflect their main priority, summarize our commitment, and state the agreed next step. Keep it under 120 words in a direct, conversational tone. Do not invent pricing, promises, or dates. List anything I need to confirm separately. Draft only; do not send.

7. Reopen a quiet conversation with something relevant

Before another reminder, look at why they were interested and what they said about timing. Maybe they told you to come back after a project. Maybe they were waiting on you. Those need different messages.

Review [DEAL NAME] and its accessible activity. Summarize the original customer need, the last meaningful exchange, and any documented reason for delay. Draft a short re-engagement email to [CONTACT NAME] grounded in those facts. Do not assume why they have not replied and do not invent a new offer. Flag uncertainty. Draft only; do not send.

8. Fill missing deal information without making it up

A filled field is not automatically better data. This finds the gaps, looks for evidence in the activity, and asks you when there is none. What you want is a record you can come back to tomorrow and understand.

Find up to five open deals owned by [OWNER NAME] in [PIPELINE] with a missing next step or close date. Show record links. Look for explicit supporting information in accessible activity. Suggest a value only when it is supported; otherwise ask me what is needed. Do not estimate dates or invent next steps. Show the proposed updates for review before saving.

9. Prepare for your pipeline review

Arrive ready to discuss decisions, not to remember conversations. The part to focus on is where you need help: a technical colleague on a call, a decision on terms, an implementation answer. If you want to know what changed this week, the model needs history or an earlier snapshot; today's pipeline alone cannot tell it.

Prepare a pipeline-review brief for deals owned by [OWNER NAME] in [PIPELINE] for [START DATE] to [END DATE]. Summarize current status, documented progress, outstanding commitments, and next actions. Report stage or amount changes only when accessible history or a supplied earlier snapshot establishes them; otherwise describe current status only. Include where I may need help, supported by the records. Link to sources and disclose retrieval limits. Make no changes.

10. Find an expansion conversation in your existing accounts

Look for a connection between something a customer told you and something you can help with, such as a goal that was never part of the original project. The output is a discovery question, not a forecast.

Review [CUSTOMER SEGMENT, e.g. all customers with an active subscription] for relevance to an expansion conversation about [OFFER]. Use available company properties, deal history, products or line items, and documented customer goals. Suggest up to five accounts worth exploring, each with the evidence, the missing information, and one discovery question. Do not assume budget or buying intent. State records reviewed and retrieval limits. Make no changes.

11. Combine your CRM history with account research

HubSpot tells you about your relationship. Public announcements tell you what is changing in their business. Use this for an important account where a little more preparation makes the meeting better. Keep confidential CRM details out of web searches.

Build a concise account brief for [COMPANY] using accessible HubSpot history, recent public company announcements, and the attached public report. Separate internal relationship facts, dated external facts, and hypotheses. Cite sources. Suggest three conversation topics relevant to [OFFER], with a question to test each. Do not assume budget or buying intent. Keep confidential CRM details out of public web searches.

12. Learn something useful from lost deals

If the same concern keeps appearing, something in how you sell may be worth changing. Several deals mentioning price can mean no budget, too large a scope, or a cheaper alternative. Sometimes the records cannot say, and the improvement is to ask better questions when you lose.

Review closed-lost deals in [PIPELINE] for [START DATE] to [END DATE], using recorded loss reasons and accessible supporting activity. Group recurring themes and show counts within the records reviewed. Separate recorded customer reasons, salesperson interpretations, and your own inferences. Identify missing information and link to representative deals. Suggest three improvements to test in future sales conversations. Disclose retrieval limits. Make no changes.

Bonus: do it by voice

With ChatGPT's voice mode and HubSpot connected, prompt 1 works while you walk back to the car. Talk through what happened, ask for a summary, and have it prepare the note and task. The review step is the same: approve the proposed write, then check the saved record.

How to use it

1. 1Connect the official HubSpot app in ChatGPT. Your HubSpot Super Admin approves the access. Set it to ask before making changes.
2. 2Pick one prompt and try it on a deal you know well, so you can spot a good result or a mistake quickly.
3. 3Replace the [BRACKETS] with your own deal name, pipeline, owner, contact and dates. Keep the sentences that say 'make no changes' or 'show before saving'.
4. 4Open one cited record and compare it with the answer before you act on it. For writes, approve the proposal and then check the saved note, task or field.

Tips

• Name the deal, pipeline and date range exactly as they appear in HubSpot. Vague requests produce vague, unverifiable answers.
• Missing activity is not proof a conversation never happened. Treat 'no logged activity' as a question, not a conclusion.
• Connector writes do not enforce HubSpot's custom validation rules. If you add a stage update, confirm the pipeline and stage first.
• Bulk changes have a documented ten-record limit. Keep write prompts to five records so every one gets reviewed.
• HubSpot notes that engagement data is unavailable when Sensitive Data is enabled in the account. The prompts ask the model to disclose what it could not retrieve.

Related resources