HubSpot Deal Pipeline and Deal Stage Setup Plan
Plan a HubSpot deal pipeline with stages, required properties, task automation, views and a rollout checklist for a small sales team.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Help me set up a HubSpot deal pipeline for a small sales team. What we sell and the sales process in a few lines: [SALES_PROCESS]. Team size and roles: [TEAM_SIZE_AND_ROLES]. Current tracking method: [CURRENT_TRACKING]. Deal sources: [DEAL_SOURCES]. Information we need on every deal: [REQUIRED_DEAL_INFO]. Produce: a pipeline stage table with the columns Stage, Meaning, Exit evidence, Probability idea, Required properties, Automation idea (task, notification, property update); a property list with the field name, type, who fills it and when, limited to what we really need; suggestions for saved views or boards for reps and for the manager; three automation ideas with the trigger, action and risk; a data migration plan from the current tracking method with a test import of 10 records first; a rollout checklist with training, a freeze date and a review after two weeks; and a short guide for reps of under 150 words on daily CRM habits. Calculate a simple pipeline coverage figure: pipeline value divided by the sales target, showing the arithmetic and explaining that the right coverage depends on our own win rate, which I must supply. Pipeline limits, required property settings, automation features and report types depend on your HubSpot plan and version; mark every one [VERIFY]. Do not invent HubSpot capabilities or click-by-click steps. Do not import data without a backup and consent for contact data under your privacy rules [VERIFY]. Add a worked example with invented figures: a quarterly target of 300,000, a pipeline of 750,000 and a win rate of 28 percent, and compute coverage and expected closed revenue.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Invented figures. Coverage = pipeline 750,000 / target 300,000 = 2.5 times. Expected closed revenue at a 28 percent win rate = 750,000 x 0.28 = 210,000, which is 90,000 short of the 300,000 target, so coverage of 2.5 is not enough on this win rate. To hit target you would need about 300,000 / 0.28 = 1,071,429 of pipeline. Stage row: Proposal sent | Meaning: written offer delivered | Exit evidence: buyer replied in writing | Required properties: amount, close date, decision maker | Automation idea: create a task to follow up in 3 working days [VERIFY availability on your plan].
Illustrative only, made-up data. Your results will differ and must be reviewed.