A CEO opens the HubSpot pipeline report on a Monday and sees four times coverage for the quarter. The board deck says the team is in great shape. By week eight, half that pipeline has vanished into closed lost, and nobody can explain where the quarter went.

Nothing vanished. Those deals were never deals.

When to create a deal in HubSpot sounds like an admin question. It decides what your win rate means, what your sales cycle means and what your pipeline coverage means. Pick the moment once, write it down, and every number downstream starts telling the truth. Leave it to each rep and you get three different pipelines stitched into one report.

What are the options for when a rep creates a deal?

Most teams land on one of three rules, whether they chose it or not: create the deal on inquiry, when a meeting is booked, or after a qualified discovery call. Each one puts a different set of conversations into pipeline. That choice, more than rep skill or market conditions, decides what your win rate, sales cycle and pipeline coverage will look like on the next board slide.

On inquiry. Every form fill, demo request or inbound email becomes a deal. Nothing gets lost, and the pipeline fills up fast.

On meeting booked. The deal gets created when a first call lands on the calendar. The buyer has at least agreed to talk.

On qualified discovery. The deal gets created after a discovery call confirms a real problem, a buyer who can act on it and a reason to act this year. Everything before that lives as a lead or a contact.

Each rule is defensible. Each one changes your numbers in a different direction, and many leadership teams have never checked which way.

What does each rule do to win rate, cycle length and pipeline coverage?

Creating deals early pushes win rate down, stretches the measured cycle and inflates coverage. Creating them late does the opposite. The customers you win stay exactly the same under every rule. Only the denominator changes, which is why two companies with identical results can report win rates that look nothing alike, and why one team with mixed rules can’t trust its own numbers.

Take the same 100 inbound inquiries in a quarter and run them through all three rules. These are example numbers to show the mechanics, not client data. Say 40 of the 100 book a meeting, 20 pass discovery, and 6 close won. The six wins and the dates they closed never change. Only the deal creation moment does.

RuleDeals createdWin rateMeasured cyclePipeline coverage
On inquiry1006%LongestHighest
On meeting booked4015%MiddleMiddle
On qualified discovery2030%ShortestLowest

Same six customers. A win rate anywhere from 6% to 30%, depending on a rule nobody wrote down.

Create deals on inquiry and your win rate looks terrible, your cycle looks long, and your coverage looks heroic. Reps feel like they are drowning, and the forecast leans on deals that were never real. Create deals only after qualified discovery and your win rate looks great, your cycle looks short, and your coverage looks thin. Now the risk flips: the work before discovery is invisible, and nobody can see when top-of-funnel dries up until it is too late.

The worst version is all three at once. One rep creates deals on inquiry, another waits until the proposal, and the CEO reads a blended win rate that describes nobody.

Should you use HubSpot leads or deals for new inquiries?

Use leads for new inquiries and save deals for conversations that meet your written rule. HubSpot added a Leads object to Sales Hub so reps can prospect, qualify and disqualify early interest without touching pipeline. That keeps the forecast clean while early work stays visible, and it gives you a clear conversion point to measure between first interest and real opportunity.

The split works like this. Inquiries and early conversations live as leads. When the rule is met, the rep converts the lead into a deal, and the deal starts its life at the first pipeline stage.

If your HubSpot portal does not include the Leads object, lifecycle stage on the contact does the same job: keep the contact at lead or MQL until the rule is met, then create the deal and move the contact to opportunity.

Either way, the point is the same. Pipeline holds only what meets your rule. Everything else still gets worked. It stays out of the forecast.

What is the right rule for a team without RevOps?

For most B2B teams with a handful of reps and nobody owning the CRM full time, create the deal at qualified discovery, and track meetings booked as their own number. That rule keeps the pipeline report honest without an analyst cleaning it every week, and it still shows top-of-funnel activity where a sales leader can see it slowing down.

Here is why. A sales leader without an analyst needs the pipeline report to mean something on its own. Qualified discovery is the earliest point where a deal has a real chance of closing, so coverage and win rate reflect deals a rep can work. Meetings booked still matter, but as an activity metric on the lead side, not as inflated pipeline.

Write the rule in one sentence your reps can apply without asking you. For example: “Create a deal when discovery confirms the problem, a person who can buy, and a reason to act within two quarters.” If a rep can’t tell whether a conversation meets it, the sentence needs work, not the rep.

How do you set the rule up in HubSpot?

Three settings turn the written rule into something HubSpot enforces: a first deal stage named for the rule, required properties on that stage that prove the rule was met, and reports on both sides of the line. Once those exist, a rep can’t create an empty deal, and you can see the conversion from lead to deal every month.

  1. Make the first deal stage match the rule. If deals start at qualified discovery, the first stage should be named for it, so nobody creates a deal that skips the step.
  2. Require the properties that prove it. HubSpot lets you set required properties on a pipeline stage. Require the fields that show the rule was met, such as the confirmed problem, the buyer and the expected timeline, so a deal cannot enter the pipeline empty.
  3. Report on both sides of the line. Build one report for leads or meetings created and one for deals created, with the conversion between them. That conversion rate is the health check for your funnel, and it only exists once the line is clear.

Then audit it once a month. Pull deals created in the last 30 days and spot-check whether each one met the rule. The first audit often turns up a rep or two working from their own definition.

What changes when you switch rules mid-year?

Your numbers jump, and it is not a performance change. Move from creating deals on inquiry to creating them at discovery, and win rate climbs overnight while coverage drops. Move the other way and the reverse happens. Nothing about how the team sells has changed, so the board needs to hear about the new definition before it sees the chart.

Mark the date you changed the rule, report the before and after periods separately, and tell the board before they see the chart. A clean definition with a visible break beats a smooth line built on mixed rules.

Where should you start?

Start with last quarter’s closed deals. Pull the list, ask each rep when they created theirs, and compare the answers. If they differ, you have found why your win rate and coverage have never quite matched what the team feels on the ground, and you have the evidence you need to write one rule everybody follows.

If you want an outside read on how your CRM defines pipeline today, take our free CRM diagnostic. For what an inconsistent pipeline does to your forecast, read Why is my HubSpot forecast always wrong?.

Your pipeline report can show everything your reps touched, or everything they can close. Pick one, write it down, and make HubSpot hold the line.