Close fixes deal confidence at 100 for won deals and 0 for lost deals, so forecast calls only need to debate the deals still open. The two fixed values turn the most subjective field on the board into facts at both ends of the scale.
- Once a deal is closed, the number stops being a judgment call: Close forces confidence to 100 when the status is won, and to 0 when the status is lost.
- Only won deals at 100 and lost deals at 0 are free of debate. Every other number you see before a call is someone's opinion.
- HubSpot treats the deal stage as the source of truth for closed deals, and warns that its own deal scores are for information only.
TL;DR
- Once a deal is closed, the number stops being a judgment call. Close forces confidence to 100 when the status is won, and to 0 when the status is lost (Developer API Documentation).
- That means only won deals at 100 and lost deals at 0 are free of debate, because open deals can also hold 100 or 0.
- HubSpot treats the deal stage as the source of truth for closed deals, and warns that its own deal scores are for information only (HubSpot).
- For a revenue leader, the useful move is to stop arguing about confidence on deals that already closed, and spend the call on the open ones where judgment still applies.
What Close actually does with the number
When you set confidence in Close, you are entering a likelihood of winning the opportunity as a percentage from 0 to 100 (Developer API Documentation). That is the whole range. Confidence is the likelihood of winning the opportunity, expressed as a percentage from 0 to 100.
While a deal is open, that number is yours to set. You look at the buying signals, the last conversation, the competitive pressure, and you put a number on it. Two reps on the same team will often land on different numbers for the same deal. That is normal. That is the point of having a judgment field at all.
The interesting behavior starts when a deal leaves the open state. Close's API documentation states that opportunities with a won or lost status always have a confidence of 100 or 0 (Developer API Documentation). The field description itself says the value is always 100 when status_type is won and 0 when it is lost (Developer API Documentation).
So the system does not ask you what your confidence is after the deal closes. It overrides you. It writes the answer for you. Won is 100. Lost is 0. There is no in-between state once the status has moved.
This is a small design decision with a large effect on how a forecast call runs.
Why those two fixed values matter more than the rest of the scale
Most forecast conversations go badly in the same way. Someone reads a number off the board. Someone else questions it. The rep defends it. Ten minutes disappear. Nothing about the actual forecast has changed.
The reason is that on an open deal, confidence is a forecast of something that has not happened. Reasonable people disagree. There is no way to settle the argument in the room without settling the deal itself.
Closed deals are different. The outcome is known. There is nothing left to predict. If your board still shows a confidence number on a won deal, and that number is anything other than 100, the number is wrong. The same holds for a lost deal showing any value other than 0.
Close removes this class of argument entirely. Close pins won deals to 100 and lost deals to 0, so every closed row on your forecast carries the outcome the status recorded. Nobody has to re-litigate a number that the outcome has already settled.
HubSpot makes a parallel point from a different angle. Its knowledge base article on deal scores states plainly that the deal stage is the source of truth to indicate a deal is closed (HubSpot). The stage, not a derived score, tells you the deal is done. A score that disagrees with a closed stage is simply not carrying real information.
That principle lines up with what Close does to the confidence field. In both systems, the closed state outranks the scored estimate. The fixed values are not a limitation on your judgment. They are a sign that judgment is no longer the right tool for that row.
Here is how the two closed states compare on a single dimension:
| Status | Confidence value | What it means |
|---|---|---|
| Won | 100 | The deal is closed and the outcome is known |
| Lost | 0 | The deal is closed and the outcome is known |
Source: Close, "Update an opportunity | Close | Developer API Documentation" (Developer API Documentation).
The two closed statuses, in plain terms
There are only two closed statuses to get right, and Close writes the confidence for both of them.
Won. The deal closed in your favor. Confidence is set to 100. There is no partial win, no mostly-won, no might-renew. Won means won, and the number says so.
Lost. The deal closed against you. Confidence is set to 0. It does not matter how close it was, how much budget they had, or how likely a rematch looks next quarter. This opportunity finished at 0.
Everything between those two states belongs to deals that are still open. Those are the deals where your 0-to-100 percentage carries real information, because the outcome has not landed yet.
The practical consequence for your forecast call is a clean split. Rows whose status is won or lost, which read 100 or 0, are history. An open row can also read 100 or 0, so status must decide which rows are closed. Rows that read anything else are live. Your agenda should follow that split, and the fixed values make the split visible without anyone having to check a status column first.
What HubSpot's deal scores tell us about reading confidence
HubSpot's guidance on deal scores is worth reading next to Close's rule, because it draws a boundary around what a number like this is for.
The article includes two notes that matter. The first: deal scores are for information only and shouldn't be used as the only factor in making business decisions (HubSpot). The second, quoted above, is that the deal stage is the source of truth to indicate a deal is closed (HubSpot).
Taken together, these say that a score is a lens, not a verdict. HubSpot says deal scores are for information only and shouldn't be used as the only factor in business decisions. And when a deal closes, the score step aside for the stage.
Now carry that back to a 0-to-100 field you set yourself. In Close, you set the confidence value yourself through the update endpoint. You set it. Which means the number is a record of your belief, not a measurement of the deal. HubSpot's caution applies with even more force: your belief field should inform the conversation, and the closed status should end it.
This is exactly why the two fixed closed values are so useful. They take the field that is most subjective on your board and make it objective at the two ends of the range. The 100s and 0s on won and lost deals are facts; a 100 or 0 on an open deal is still an owner's estimate. The numbers in between are opinions, and they should be labeled as such in how you talk about them.
Running the forecast call with the fixed values in view
Walk into the call with the board already sorted by what kind of number you are looking at.
Start with the 100s. Check that these rows are recorded as won. A 100 can also sit on an open deal. Confirm they are recorded as won, confirm revenue is booked against the right period, and move on. There is nothing to forecast here.
Next, the 0s. Check that these rows are recorded as lost. A 0 can also sit on an open deal. Review them only long enough to capture what killed them, and to confirm they are logged as lost. A 0 on a deal you thought was still alive should be checked for an owner's estimate or a status error before you rely on the rollup.
Then the middle of the range. This is where the call earns its keep. Every open number is a claim someone is making. Your job is to find the claims that are weakest, because those are where the forecast is most exposed.
The strongest conversation focuses on two questions. What changed since the last call, and what would have to be true for this number to move. A rep who cannot answer either is holding a number by inertia rather than by evidence.
A useful discipline: pick the open deals whose confidence sits at a level the team has never examined together, and ask what evidence supports that exact placement. You will often find the number was chosen for comfort, not for signal. Those are the deals where the forecast is quietly built on nothing.
Where permissions change what you can fix
There is a practical wrinkle if you try to clean up the board from an account that does not own everything on it.
Close's update endpoint will return a 403 if you don't have access to its lead, or if another user owns it and you don't have permission to manage other users' opportunities (Developer API Documentation).
So a manager auditing confidence across the team may hit walls on specific rows. That is not a bug in the data. It is a permission boundary. Two things follow.
First, decide who owns the correction. If the owner is the only person who can edit the row, the fastest path is a short list sent to each owner before the call, rather than a live edit session during it.
Second, check your role settings before you assume a row is unfixable.
This also shapes how you should think about accountability. If only the owner can move a confidence figure, then the number on the board is a direct statement from that owner. Treating it that way in the call, rather than as a floating team estimate, tends to produce better answers.
The honest limits of a 0-to-100 field
A few things this system will not do for you.
It will not tell you your open numbers are well calibrated. Close defines the field and pins the closed ends. The accuracy of everything in between is still on your team.
It will not surface disagreements between reps on its own. If two people hold different beliefs about the same open deal, only one number can sit on the record. The other view lives in someone's head until the call draws it out.
And there is one point the sources leave open: how often confidence should be revisited on open deals, or what cadence keeps the middle of the range meaningful. Ask your own revenue operations lead what cadence your team has committed to, and hold the team to it.
The fix for the limits is procedural, not technical. Write down what evidence supports each open confidence band, revisit it on a fixed rhythm, and treat the 100s and 0s as the only rows that need no discussion at all.
A worked pass over a small board
Imagine a five-row forecast going into a Tuesday call. Two rows read 100. One reads 0. Two read open values.
You spend almost no time on the three closed rows. You verify statuses, book the won revenue, log the loss reason, and move on. That is roughly three-fifths of the board handled without a single debate.
The entire call now sits on two open deals. For each, you ask what moved since last week and what evidence supports the current number. Because nothing else is competing for airtime, you can go deep instead of broad.
That shift is the whole return on the design. The fixed closed values do not improve your judgment on open deals. They protect the time you need in order to exercise it.
Related guides
FAQs
What does confidence mean in Close?
It is a likelihood of winning the opportunity, expressed as a percentage from 0 to 100 (Developer API Documentation). On an open deal it records your belief about the outcome. On a closed deal it is no longer a belief, because Close writes the value for you.
Does a won deal always show 100 in Close?
Yes. The field description states it is always 100 when status_type is won and 0 when it is lost (Developer API Documentation). A won deal reading anything else would indicate a status problem rather than a confidence problem.
Why does my board show different confidence numbers for two similar open deals?
Because both numbers are judgments, not measurements. Close defines the range and fixes the closed ends; the middle is whatever the owner believes at the time they last set it. The forecast call is where those beliefs get examined.
Should I treat a low confidence number on an open deal as bad news?
Not by itself. The number is the owner's estimate of likelihood, and a low estimate on a deal still worth pursuing can be perfectly accurate. What matters is whether the estimate matches the evidence and has moved when the evidence moved.
Can I change confidence on a deal owned by someone else?
Only if you have permission. Close's update endpoint returns a 403 if you don't have access to its lead, or if another user owns it and you don't have permission to manage other users' opportunities (Developer API Documentation). Check your role before assuming a row is broken.
How is this different from a HubSpot deal score?
HubSpot computes a score for you and labels it for information only, while the deal stage remains the source of truth to indicate a deal is closed (HubSpot). In Close, you set the 0-to-100 number yourself, and the system only overrides it once the deal closes.
What is the fastest way to run a forecast call using these fixed values?
Sort the board so the 100s and 0s sit together, confirm each one's won or lost status, and clear only the confirmed closed rows quickly. The closed values are facts about history, and facts about history do not need a meeting.