# When your prospect&#8217;s current contract ends, and why your close date comes after the notice deadline

https://salesbond.app/blog/incumbent-contract-end-date-pipedrive/
Published: 2026-10-06 · Updated: 2026-10-25

Ask every prospect who already uses a competitor two dates: when their current contract ends and by when they must give notice to leave it. Put both in Pipedrive as date fields on the deal and set your expected close date after the notice deadline, because no demo makes a buyer switch inside a contract they cannot leave. This is about the other vendor’s contract with your prospect. Your own renewals are a different pipeline, and we covered them in [the customer renewal process in Pipedrive](https://salesbond.app/blog/customer-renewal-process-pipedrive/).

## The demo went great and nothing happened

Teodor sells scheduling software and had the best demo of his quarter in April. Four people on the call, the owner asked about pricing twice. Teodor moved the deal to Proposal, set the close date for the end of May and told the Monday meeting it was his most likely win.

May came and went. The owner answered emails a week late each time. In June Teodor finally asked the question he should have asked in April: what are you on now, and when does it end? A contract running to 31 March next year, with 90 days’ notice. Nothing could move before 31 December.

The demo was fine. So was the buyer. The deal sat in the pipeline seven months ahead of the only date that mattered, and every week it was listed as “closing this month” made the forecast a little more fictional.

## Two dates to ask: contract end and notice deadline

The first is when the current contract ends. We already count a buyer volunteering it as one of the [buying signals worth logging on a deal](https://salesbond.app/blog/buying-signals-pipedrive-deals/): someone who tells you their end date has started planning around you.

The second matters more and gets asked far less: the notice deadline. By cloudnuro’s account, written for the company holding the contract, notice periods usually run 30 to 90 days before the end of the term, and missing that window means the contract renews on its own ( [cloudnuro: renewal notice period](https://www.cloudnuro.ai/blog/renewal-notice-period)). So Teodor’s deal was really decided by 31 December. Show up with a proposal in February and you are selling into the next term. The same clause will sit on your side once you win: the [notice deadline on your own multi-year contract](https://salesbond.app/blog/multi-year-deals-pipedrive/) is one of three dates we put on the deal at signature.

Ask both on the discovery call, in plain words: “When does your agreement with them run out, and how much notice do you have to give?” If the buyer does not know the follow-up becomes the next activity on the deal: “Can you check the notice clause and send it over?” A buyer who checks is engaged. One who won’t is telling you something too.

## What the notice period does to your close date

A yes before the notice deadline costs the buyer nothing and reverses for free. A yes after it is a decision: they have told the incumbent they are leaving, and now they need somewhere to land. That is why we set the expected close date in the weeks after the notice deadline, not on the day of the demo or the quarter end the rep hopes for.

Until then the deal is pipeline in waiting. It can sit at Proposal with a real next activity, but it is not commit, and it should not be in the number you give the owner for this quarter. A January close date set once, honestly, seven months out, is more useful than one that gets [pushed a month at a time](https://salesbond.app/blog/pushed-close-dates-pipedrive/) until it lands where the contract always said it would.

Buyers sometimes break a contract early. That is their decision and their cost; plan on it and you are back to forecasting on hope.

![Sales representative discussing pipeline strategies during a meeting.](https://salesbond.app/wp-content/uploads/2026/10/incumbent-contract-end-date-pipedrive-2.png)

## Setting it up in Pipedrive: two date fields, one filter

Two custom deal fields, both of type Date: “Current contract end” and “Notice deadline”. You add them under Personal preferences > Data fields, pick Deal, click “+ Custom field”, and a name plus a type is all Pipedrive needs to create one ( [Pipedrive: custom fields](https://support.pipedrive.com/en/article/custom-fields)). On Growth and above you can add a field description, and ours says the one thing reps forget: “Notice deadline = contract end minus the notice period in the clause. Enter the date, not the number of days.”

Both dates are typed in by hand. Pipedrive’s formula fields take only numeric and monetary inputs, on Premium and above ( [Pipedrive: formula fields](https://support.pipedrive.com/en/article/custom-fields-formula-fields)), so one date won’t calculate the other.

The filter is a saved deal filter: Notice deadline is before a date about two months out, moved forward each month ( [Pipedrive: filtering](https://support.pipedrive.com/en/article/filtering)). It is the first list we open on Monday, because a deal on it is about to become real whether or not anyone is talking to the buyer.

## Working the waiting room

What a rep does between a good demo and the notice deadline decides whether the deal is still alive when the the window opens.

- Put the next activity a month before the notice deadline, not “follow up in two weeks” on repeat.
- Confirm both dates back to the buyer in writing. “You mentioned the agreement runs to 31 March with 90 days’ notice, so the decision point is late December. Does that match the contract?” You get the clause checked, and the buyer knows when they will hear from you and why.
- Send useful things in the pause and ask for nothing: a migration plan from the incumbent’s export format, a reference call with a customer who switched from the same tool, a note when thier budget cycle meets the notice date (the [year-end budget deadline](https://salesbond.app/blog/year-end-budget-deadline-deals-pipedrive/) often lands in the same month).
- Keep it off the commit list until the notice has gone in.

## When they renewed anyway

The buyer writes “we auto-renewed, sorry”. The deal is not dead. Move both dates and the close date forward by one term, put the next activity a month before the new notice deadline, and leave the stage alone. What kills the deal is marking it lost and forgetting, or leaving it at Proposal with a close date from last spring, which is how it ends up among the [no-decision deals](https://salesbond.app/blog/no-decision-deals-pipedrive/) nobody can explain in the review. A renewed buyer who liked your demo is the warmest deal in next year’s pipeline, as long as the calendar knows about it.

Two fields and one filter, and the Monday meeting stops arguing about whether Teodor’s deal is “this month”. We build SalesBond, a sales management layer on top of the CRM a team already uses, and it will flag a deal whose close date has passed with no next activity scheduled; whether anyone asked about the notice clause is still a question only the rep can answer. [Check your CRM with SalesBond](https://salesbond.app/).
