Celeste Berke Knisely, homeCeleste Berke
KniselySALES METHODOLOGY TRAINER
Talk about your team

Your Ghosted Pipeline Might Start With Free Access

One discovery call - turned into an article with a lesson and a resource to fix it!

I hear it constantly. "We're going to provide value first. For free."

It sounds generous. It sounds like the kind of thing that builds trust. It's like a try before you buy move. Many teams are running this. They are letting the demo or the product do the heavy lifting.

But here is what is actually happening when you hand over free access before you've done real discovery.

The prospect pokes around. They don't know what they're looking for. They don't have a business case driving urgency. So they do nothing, go quiet, or come back and tell you the price is too high. OR, they use it, get what they want, test another cheaper vendor and you are left wondering what ever happened to them when they don't return the calls.

And you're stuck. Because you never built the case for why they needed to change in the first place.

I was on a call recently with a team who had three opportunities in their pipeline they were actively trying to close - one of them - a WHALE of a deal. One of them: they'd already given free product access after a single discovery call. Kind of like a one-call close, they beamed.

Except...I reviewed the notes for this discovery and in no way was this a one call close.

But here's what was missing.

The team hadn't quantified the business problem. They hadn't asked how many deals they were losing per month. They hadn't tied it to a number. They hadn't built anything that would make staying the same feel more painful than changing.

So when the prospect logs in and "tests it out," what are they evaluating against?

Nothing. There's no business case. No cost of inaction. No urgency.

That's not a sales motion. That's hopium. :)

Nobody changes their environment unless their current state is untenable or intolerable. That's the whole game. Your team's job isn't to hand over access and let them figure it out. Your team's job is to make the cost of staying exactly where they are crystal clear.

When your team does that, free access becomes a tool, not the only thing that determines if someone moves forward.

When your team solely relies on demoing the product and giving someone access, they have nothing to talk about so it defaults to price. It's a lose lose yet companies continue to do this over and over again.

The reps and teams we work with stop leading with demos and free trials. They start leading with the business problems they solve for their prospects, they quantify the impacts of those business problems, they identify what it stems from (the root causes) and create a clear business case the buyer can defend internally without your team in the room.

That's how win rates go from 7% to north of 50%.

So if you have been nodding along thinking - wow - our team lets prospects play around or have access and our discovery is rather surface.....we have ghosted pipeline....deals we can't defend, start here:

What do you solve for?

That's not rhetorical. It's not to make you feel small or that you don't know what your org solves for its customers. We get it. You are in leadership...this is a new concept - a different selling muscle, so it's OK to not get it. That's why we are here.

It's the reality that almost every team we work with has no alignment around what they solve for. Recently, I did this workshop with a team and they submitted 38 business problems. After four hours we identified five (5) and all 38 of what they originally submitted ended up in the root cause (broken process) column.

For 25 years they had been selling to root causes. The CEO said to me..."I can't believe we haven't thought about our business in this way in 25 years.".

I hear it daily. It's in all my DM. Everyone who knows what the PIC is and says they have done it. I do a quick check of Salesforce and think "not with us". So I already know that most likely they are selling to process. So I ask and I get:

  • "we solve so many problems we can't list them
  • "it's hard to explain - it's different for every customer"
  • "we solve inefficiencies and broken process - insert siloed data, disparate systems, manual entries, taking too long, etc."
  • "we help statements"

We help is a future state. It's what you can do for them. It says nothing about what's going on now.

A broken process or missing tool is a root cause - not why a CFO will fork over $100k.

Identifying the business problems is HARD. It's why we do it AS A PAID SERVICE. And why we get so frustrated with teams that DIY it because they get it wrong and don't yet see the value as they haven't done a thorough diagnostic of what not getting this right is costing their org.

And then we see the downstream impact (low win rate, weak pipeline, long sales cycle lengths, poor quota attainment, low acv).

Because once you nail (as a company) what you solve for at the business level, everything revolves around that. Outbound, discovery, call coaching, deal review, pipeline movement, forecast....marketing messaging, website copy....everything. It becomes the lens that you run everything through. Yes, even your demo, and yes, even when you tie how you'll solve their problems when they access your tool.

Because buyers buy to solve business problems (The data is here. How Buyers Want To Be Sold.)

But skipping your problems, or diy'ing it and not getting it right....well, that can cost you millions, and I'm trying to help you avoid what most of our customers realized too late...

Want to understand more about what the Problem Identification Chart is? Snag the guide here. If you already have one completed that you did internally - and want someone from the org who created this concept to review it - shoot me a dm. Happy to give you a few pointers.

Celeste Berke Knisely

Celeste Berke Knisely

Certified Gap Selling trainer and sales coach in Denver. 20+ years in sales and sales leadership, and she still runs her own discovery calls.

More about Celeste
Download the Problem Identification ChartThe #1 recommendation we have for a team moving into problem-centricity.
Email me the PIC