How to Require Fields Before a Deal Moves to Closed Won in HubSpot

Sales marks a deal closed with nothing but a dollar amount.

No go-live date. No billing contact. No product details. No implementation notes.

Now your onboarding team is chasing down information that should have been captured at close. They are sending Slack messages, scheduling calls, and digging through email threads to piece together context that the sales rep had in their head two days ago.

This is one of the most common handoff failures in B2B companies. And HubSpot has a native feature that prevents it entirely.

The Handoff Problem

When a deal moves to Closed Won, it triggers a handoff. Sales is done. Onboarding, implementation, or customer success takes over.

That handoff requires information:

Who is the primary contact for onboarding? When does the customer expect to go live? What exactly did they buy? Are there special terms or implementation requirements?

If that information is not in the deal record, someone has to go find it. Usually that means the onboarding team interrupts the sales rep, who has already moved on to new opportunities. Or worse, they reach out to the customer and ask questions the customer already answered during the sales process.

Both scenarios waste time. Both create friction. Both make your company look disorganized.

Why This Happens

Sales reps are incentivized to close deals. They are not incentivized to fill in administrative fields after the deal is already won.

From the rep's perspective, the work is done. They got the signature. They hit their number. Moving on to the next opportunity feels more valuable than documenting details in the CRM.

This is not a training problem. It is a system design problem. If the system allows deals to close without complete information, deals will close without complete information.

The solution is to make complete information a requirement for closing, not a suggestion.

The Fix Takes 2 Minutes

HubSpot lets you require specific properties before a deal can move to Closed Won. If the fields are not filled in, the deal cannot move. Period.

This is called "conditional stage properties." You define which properties must be completed for a deal to enter a specific stage. HubSpot enforces it automatically.

No reminders. No training. No hoping reps remember. The system simply will not let them skip the fields.

How to Set Up Required Fields at Closed Won

Settings → Objects → Deals → Pipelines tab

1. Select your pipeline from the dropdown
2. Find the Closed Won stage row
3. Hover over "Conditional stage properties" column
4. Click "Edit properties"

In the left panel:

1. Click "+ Add dependent property"
2. Select a property from the dropdown
3. Check the "Required" box to make it mandatory
4. Repeat for each property you need
5. Drag to reorder the fields
6. Click "Apply logic"
7. Click "Save"

Now when a rep tries to move a deal to Closed Won, they will see those fields. If Required is checked, they cannot save until the fields are complete.

Properties to Consider Requiring

The right properties depend on your handoff process. Here are common ones that solve real problems:

Go-live date. When does the customer expect to be live? Onboarding needs this to plan resources and set expectations.

Billing contact. Who should receive invoices? This is often different from the primary sales contact. Capturing it at close prevents accounts receivable delays.

Contract term length. Is this a monthly, annual, or multi-year deal? Customer success needs this for renewal planning.

Product or service purchased. What exactly did they buy? If you sell multiple products or tiers, this determines which onboarding track to use.

Special implementation notes. Are there custom requirements, integrations, or timeline constraints? Free text field for anything the onboarding team needs to know.

Primary contact for onboarding. Who should the implementation team reach out to? This is often different from the economic buyer who signed the deal.

Start with the fields your onboarding team asks about most frequently. Those are the ones that are consistently missing from deal records today.

The Result

When you require fields at Closed Won, three things change:

Sales enters the same fields every time. There is no variability based on how thorough individual reps are. The system enforces consistency.

Onboarding starts with complete, accurate context. No more chasing down information. No more Slack threads asking "who is the contact for this account?" The data is in the deal record because it had to be.

Handoff quality becomes measurable. If you want to audit whether deals are closing with good data, you can. Every Closed Won deal has the required fields populated. No exceptions.

This is a two-minute configuration change that eliminates an entire category of operational friction. The fix is simple. The impact compounds with every deal you close.

Frequently Asked Questions

Can I require fields at other deal stages, not just Closed Won?

Yes. Conditional stage properties work on any deal stage. You might require different fields at "Contract Sent" or "Negotiation" depending on your process. The setup is the same.

What happens if a required field is blank and the rep tries to move the deal?

HubSpot blocks the stage change. The rep sees a prompt showing which required fields need to be completed. They cannot save the deal in the new stage until all required fields have values.

What if we have multiple pipelines?

Each pipeline has its own conditional stage properties. You configure them separately. This is useful because different pipelines often have different handoff requirements.

Next Step

Required fields at Closed Won solve one handoff problem. But most sales processes have friction at multiple stages, not just the final one.

If your team is still chasing down information, routing deals manually, or working around HubSpot instead of through it, the problem is bigger than one configuration screen.

We will audit your entire deal pipeline and show you where data, automation, and handoff processes are breaking down.