Best Practice for managing "On Hold" deals?

HDGM
HDGM Member Posts: 1 VERIFIED MEMBER
edited September 2023 in Sales CRM #1

We're a B2B SaaS business, currently our process is as follows:

  1. Lost deals - a deal where the customer explicitly says no (or chooses another product)
  2. On Hold deals - in all other cases, they are put on hold after a set period of time, by being moved to a separate "On Hold" pipeline, where they go through a reactivation funnel.

Our product can be defined as a "want" rather than a "need", so there are many more deals that meet the "on hold" criteria than the "lost" criteria, meaning we under report lost deals and that our funnel / sales cycle metrics are incorrect.

What is best practice to manage these "on hold" deals in Pipedrive to ensure focused sales teams and accurate reporting?

Thanks for your input!

Answers

  • Liz (Ops Designed)
    Liz (Ops Designed) Member Posts: 210 VERIFIED MEMBER
    Third Anniversary 100 Comments 5 Answers 25 Likes

    Hi @HDGM

    There are a few different ways to handle a situation like this in Pipedrive, but one option is to use an Automation to create a new Deal in your On Hold pipeline when a Deal in your Sales pipeline is marked as Lost for a specific reason. Take a look at this 1:15-min overview.

    The key benefits to this solution are:

    1. Since you’re not moving the deal across pipelines, you don’t lose data about the original sales deal
    2. Your Sales pipeline isn’t cluttered by low-priority “held” deals

    Please feel free to reach out if you would like additional support.

    - Liz

    Schedule a Working Session | Pipedrive for Beginners | Pipedrive Integrations

  • Amit Sarda (AmitSarda.xyz)
    Amit Sarda (AmitSarda.xyz) Member Posts: 1,602 VERIFIED MEMBER
    1000 Comments 250 Likes Fourth Anniversary 25 Answers

    Pipedrive's core philosophy used to be activity-based sales (until they added the ability to sort deal cards in the pipeline view). I wouldn't treat on-hold deals any differently if I am adding the appropriate next activity for a tentative date in the future. As far as messing up with the stats is concerned, you can add a custom field that indicates that a particular deal was 'on hold'. You can then use this field to exclude any deal that was 'on hold'.

  • Pipedrive User 164
    Pipedrive User 164 Member Posts: 163 VERIFIED MEMBER
    100 Comments Second Anniversary 25 Up Votes 25 Likes

    Based on your description I'd think management should want to put a time limit on it and then mark it as lost. At the maximum it should sit on hold for a calendar or fiscal year. More likely calendar. If it isn't sold in 2023 then it's lost. A new deal is created for the 2024 "season". An exception would be that a deal is opened in 2023 with the understanding that it will likely not close until 2024. If thats known, it should be understood from the beginning. Deals should be sitting perpetually on hold.

  • Jonathan Gennick
    Jonathan Gennick Member Posts: 88 VERIFIED MEMBER
    Fourth Anniversary 25 Likes 10 Comments 5 Up Votes

    My approach is to lose deals if they stall in one stage for too long and the prospect has stopped communicating. That works for me, because my use case is finding book authors for specific topics. If one prospect goes unresponsive, my time is better spent in recruiting someone else who is more interested and engaged.

    Sometimes an author will say to me something along the lines of "come back to me in six months". In those cases, I will lose the deal and add an activity to the lost deal scheduled for whatever future date fits the scenario.

  • Pipedrive User 164
    Pipedrive User 164 Member Posts: 163 VERIFIED MEMBER
    100 Comments Second Anniversary 25 Up Votes 25 Likes
    edited September 2023 #6

    Yeah, I have a lost reason called "Ghost" that I use for those that stop communicating.

  • Jonathan Gennick
    Jonathan Gennick Member Posts: 88 VERIFIED MEMBER
    Fourth Anniversary 25 Likes 10 Comments 5 Up Votes

    Ghost! @Pipedrive User 164 , I love that. It's colorful. I also have a lost reason for that instance, but mine is much more mundane sounding.

This discussion has been closed.