HubSpot deal pipelines work best when each stage describes evidence of progress towards a specific sale. Start with a simple process that colleagues can explain, then add required fields and automation. A busier board does not necessarily mean a healthier pipeline.
A deal tracks an opportunity. It serves a different purpose from the contact properties covered in our HubSpot lifecycle stage versus lead status guide. Keep contact qualification and the progress of a particular sale distinct.
Table of Contents
Choose one process and check your allowance
HubSpot recommends separate pipelines when processes need different stages. Under its current pipeline setup guidance, custom pipeline allowances are shared across objects and exclude each object’s default pipeline. Free tools allow no custom pipelines; Starter allows 15. Higher limits depend on the plan and pricing model. Check Data Management → Data Model → Limits → Pipelines for your account’s allocation.
To configure deals, open Settings, then Data Management → Objects, select Deals and open Pipelines. Choose an existing pipeline, or create one from scratch if your subscription allows it. Editing requires Edit property settings permission. Add or edit stages, set their probabilities and save. Include both Won and Lost probability states so reporting handles closed deals correctly.
If several salespeople follow the same steps, agree one shared definition first. Splitting by salesperson can make comparisons harder without improving the underlying process. Our HubSpot plan guide for UK startups covers the broader subscription decision.
Define what each stage actually means
Illustrative workflow: a consultancy sells fixed-scope projects. These are suggested working definitions, not HubSpot defaults or a process we have tested.
| Stage | Evidence needed | Next action |
|---|---|---|
| Scope agreed | The buyer confirms the problem and desired outcome. | Prepare the commercial proposal. |
| Proposal shared | The intended decision-maker has the proposal. | Agree a review conversation. |
| Decision pending | Open questions and the decision date are recorded. | Resolve the remaining questions. |
| Closed won | The agreed acceptance condition is met. | Arrange delivery handover. |
| Closed lost | The opportunity has ended. | Record the reason. |
Define acceptance: for example, a signed agreement rather than a friendly verbal response. Avoid stages for every email. A stage should help another colleague understand what changed and what needs doing.
Create a complete sample deal
From the Deals board, use the creation control in the appropriate stage. HubSpot’s record creation instructions explain that the pipeline and stage are prefilled there. Enter the deal details and associate the relevant existing company and contact. Give the sample an obvious practice name so colleagues do not confuse it with real business.
Agree who owns the next action before adding more fields. If two colleagues would both assume the other is following up, the process is incomplete even when the record looks tidy.
Treat probabilities as assumptions
HubSpot’s deal property reference defines weighted amount as amount multiplied by deal probability. An illustrative £10,000 deal at 40% contributes £4,000 of weighted amount; that does not make £4,000 guaranteed revenue. Editing probability manually stops automatic updates between open stages. Moving to a closed outcome sets it to 100% for won or 0% for lost. Avoid individual overrides without an agreed reason.
Require useful information at the right moment
For example, make a proposal date necessary when the deal reaches Proposal shared. HubSpot distinguishes stage-specific conditional logic, available to Starter users, from broader conditional property logic, which requires a listed Professional or Enterprise subscription. The latter can display dependent fields and require values during manual edits; it does not apply to workflow updates. In the conditional logic editor, add the existing date property as a dependent field, select Required and save.
Require information that helps the next person act. A mandatory field filled with “unknown” adds friction without improving the handover. Explain where the answer should come from and who can resolve a genuine exception.
Add rules and one useful automation
Pipeline rules require a supported Professional or Enterprise subscription and a Super Admin to configure them. They can restrict creation stages, skipped stages and backward movement. Deal approval specifically requires Sales Hub Enterprise. Other rules have documented bypasses, including privileged users, workflows and API updates; do not treat them as universal enforcement. Test the actual route your team uses.
For a modest starting point, create a follow-up task when a deal enters Proposal shared. HubSpot’s pipeline automation instructions list Sales Hub Starter and above, with permissions and feature qualifications. In board view, use the stage’s Automate menu, configure the task action and create the workflow. Check the owner and timing before enabling it for real opportunities.
Check the handover before rolling it out
These are illustrative acceptance checks, not reported test results:
- Move the sample into Proposal shared without its required date. Confirm a normal user’s manual edit requests the missing information.
- Enter the date and complete the move. Confirm the follow-up task has the intended owner and deadline.
- Try your actual integration or workflow update route separately. Confirm whether it bypasses the controls and document how missing data will be caught.
Use board view to inspect the resulting cards. Properties displayed on cards can be edited there; task and note shortcuts require the relevant quick-action settings. During a weekly review, ask each owner to explain the next step and evidence supporting the current stage. Correct stale records before interpreting totals.
If a value changes unexpectedly, open the record and use its property history. HubSpot shows the changed value, date and source. Compare that trail with the intended handover before adjusting the rules. A process is easier to maintain when the team can explain both the current record and how it got there.
Sources reviewed 29 September 2026 against official HubSpot documentation. The consultancy workflow, calculation and acceptance checks are illustrative recommendations.
