# When to create a deal in HubSpot: the rule that keeps junk out of your forecast https://salesbond.app/blog/hubspot-when-to-create-deal/ Published: 2026-10-24 · Updated: 2026-10-24 Create a HubSpot deal when a buyer has agreed to a dated next step and you can name an owner, an estimated amount and an expected close date. Until then the record stays a contact that the rep works through Lead status; a deal that exists only because a form was submitted inflates the pipeline and weakens the forecast. ## A deal is a sale with a date, not a name in a list Someone on r/hubspot asked exactly this: at what point should a team create a deal ( [r/hubspot thread](https://www.reddit.com/r/hubspot/comments/1i277ur/when_should_we_create_a_deal_in_hubspot_workflow/))? Search for it and you get HubSpot’s page on creating records, a glossary entry and the API docs. All correct, and none of them answers the question, because it is not about the button. It is about what a deal record means in your portal. Our answer: a deal is a record of a sale that might happen, with enough on it to be counted. The pipeline report sums Amount. A forecast needs a Close date to put the deal in a month ( [how stage probability feeds the forecast](https://salesbond.app/blog/hubspot-deal-stage-probability-forecast/)). Rep workload is read from Deal owner. Say a pipeline shows 140 deals and 60 of them are names that filled in a form. Its conversion rate means nothing, and half the Monday review goes to “what is this one?” We would rather have the 80. ## The entry rule: next step, amount, close date, owner Here is the rule we hand to HubSpot teams. Four conditions, and a deal is created only when all four hold. 1. **A dated next step the buyer agreed to.** A demo on Thursday, a proposal review next week, a call with the person who signs. Not “I’ll follow up”, which is the rep’s intention, not the buyer’s. 2. **Deal owner.** The rep who holds that next step. Not the SDR who booked it, unless the SDR runs the deal to close. 3. **Amount, even if it is a guess.** A first estimate from the buyer’s team size or the product they asked about. It will change. A wrong number that gets corrected is a working pipeline; a blank is not. 4. **Close date.** Also a guess at this point, and also fine. Pick the date the buyer gave you or the end of the quarter they named. Before that point the work lives on the contact. We wrote up [how Lead status and Lifecycle stage divide the work](https://salesbond.app/blog/hubspot-lead-status-vs-lifecycle-stage/) separately, so one line is enough here: Lead status tracks the chase, and the deal starts when the chase ends in an agreement. Teams on HubSpot’s separate Leads object convert a lead at the same moment. The rule also makes two reps’ pipelines comparable. Without it, one rep creates a deal at first reply and another at verbal yes, and their conversion rates say nothing about who sells better. ![Decision strip: a contact passes four checks to create a HubSpot deal; any No sends it back to Lead status](https://salesbond.app/wp-content/uploads/2026/10/hubspot-when-to-create-deal-2.png) ## Three ways to create a deal in HubSpot, and how each one goes wrong In practice a HubSpot deal gets born one of three ways, and each has it’s own failure mode. By hand, from the deals index. In the board view the rep hovers over a stage and clicks Create deal; in the table view it’s the Add deal menu, then Create new. On the board, HubSpot fills in Pipeline and Deal stage for you ( [HubSpot: create records on the index page](https://knowledge.hubspot.com/records/create-records-on-the-updated-index-page)). This is the most honest path, because a human decided the deal exists. Its weakness is speed. Amount and Close date sit in the same panel, and a rep in a hurry clicks Create with both empty. The fix is not a lecture but [required properties at the stage where deals enter](https://salesbond.app/blog/hubspot-stage-required-properties/). After a meeting or a call. The rep comes out of a discovery call, the buyer said “send me something”, and the deal gets created on the spot. Usually the right timing, with one risk: the enthusiasm of the moment becomes the Amount. We tell reps to enter the number the buyer reacted to, not the one they hope for. By workflow, when a status changes. The Create record action in a workflow can create deals automatically ( [HubSpot: create records with workflows](https://knowledge.hubspot.com/workflows/create-records-with-workflows)), and teams wire it so that a contact reaching a certain Lead status or Lifecycle stage spawns a deal. It fires on the status change, not on the agreement, and HubSpot requires only Deal name plus the pipeline and stage; Close date and Amount are recommended, not enforced. By default the new deal takes the contact’s existing owner, and if the contact has none, the deal has none either. Leave the optional fields out and you get a hundred deals with no amount, no close date and sometimes nobody’s name on them. ## If you automate creation: what the workflow must check first Automate deal creation only if the trigger means the same thing as the entry rule. Otherwise you have automated the junk. For a team where the SDR hands off to an AE at a known status that is doable, and the workflow saves a step and makes the handoff visible. So the enrollment should require what a human would have checked. The contact has an owner, because the action passes that owner to the deal. If SDRs own your contacts, change Assign to: it takes a specific user or another owner property, so the deal can land with the AE. The status that triggers enrollment means “buyer agreed to a next step”, not “we replied to the form”. And inside the action, set Close date to something deliberate and give Amount a value, even a placeholder your team agrees to overwrite within a week. Decide, too, what happens when a contact goes through the trigger status twice. Most teams want one open deal per contact per pipeline, and the enrollment needs a condition that says so. Can’t express it cleanly? Create deals by hand and let the workflow do the lighter job of creating a task for the AE. If you also [sync lifecycle stage and deal stage](https://salesbond.app/blog/hubspot-lifecycle-stage-vs-deal-stage-sync/), check that the creation workflow and the sync workflow don’t fight over the same records. ## The Monday filter: deals created last week that fail the rule Rules decay, so keep this one alive with a saved view on the deals index that a manager opens every Monday. In Advanced filters, build two filter groups joined by OR. Both start with Create date is less than 7 days ago; the first adds Amount is unknown, the second Close date is unknown. If workflows create deals for you, add a third group with Deal owner is unknown ( [HubSpot: filter criteria](https://knowledge.hubspot.com/segments/determine-filter-criteria)). One catch: HubSpot counts 0 as a known Amount, so a deal someone typed 0 into won’t show up here. The list should be short. If it is empty, good, say so at standup. If it has four deals on it, each one gets one of two outcomes within the day: the rep fills in the missing field, or the deal is closed and the contact goes back to Lead status. There is no third option where it sits. A rep who sees their own deal on this list twice stops creating deals before the agreement. We run the same kind of view for [deals without a next activity](https://salesbond.app/blog/hubspot-deals-without-next-activity-saved-view/). We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Its Deal Health product checks every deal in the connected CRM against the rules you switch on, more than 20 of them, and gives each deal a 0 to 100 score once at least three rules apply, with the specific violations listed. It does not create deals or stop anyone creating them. [Check your CRM with SalesBond](https://salesbond.app/) if you’d rather not maintain the filter. ## When a deal turns out not to be a deal It happens, and it should. The buyer agreed to a demo, the demo revealed they have no budget this year, and the deal you created correctly is now wrong. We say: Closed lost with a reason, not deletion and not an endless Open. Deletion erases the evidence that the rep qualified and found out early, which is exactly the behavior you want to reward. Leaving it open keeps the forecast dishonest. Closed lost with “no budget this year” and a task to re-contact in the right quarter keeps the history and clears the the pipeline. Too many early stages make this worse, because dead deals get parked in them ( [which stages a small team actually needs](https://salesbond.app/blog/hubspot-deal-stages-rename-defaults-small-team/)). The reverse happens too: a contact sits in Lead status for weeks, real conversations logged, and the rep keeps saying it’s not a deal yet. Don’t argue about it. At this Monday’s review, ask the four questions: what is the dated next step, who owns it, what is the number, when does it close. Four answers means the deal should exist today. Three means the rep is right to wait.