Presenting Value & Handling Objections

Presenting Value & Handling Objections

The presentation phase — demo and proposal — is where most salespeople spend the majority of their preparation time. It is also where most of them fail, because they prepare the wrong thing: a generic product tour rather than a tailored demonstration of value specific to this prospect's situation.

The Discovery-Demo Connection

A great demo is built from great discovery. Every significant feature shown should connect to a specific pain point uncovered in discovery: "You mentioned that your team spends 3 hours every Monday reconciling these reports. Here's exactly how that works with our tool — let me show you the same scenario with your data."

Generic demos ("Here's the dashboard, here's the reporting, here's the analytics...") are commodity. They signal that the salesperson did not listen carefully enough in discovery to understand which parts of the product are relevant. They also put the cognitive burden on the prospect to connect features to their situation — work the prospect should not have to do.

A strong demo follows this structure:

1. Set up the situation: "Based on what you told me, your primary pain point is [X]. Let me show you how we address that specifically."
2. Show the solution: demonstrate the relevant feature in context of their described use case
3. Confirm the value: "Does this solve the problem you described? How would this change your Monday morning workflow?"
4. Transition to the next pain point: move through each major pain point from discovery

The confirmation questions serve two purposes: they check comprehension, and they get the prospect to verbally affirm value — creating ownership of the conclusion. "Yes, that would save us those 3 hours" is more valuable than the salesperson claiming it will.

Building the ROI Case

Every purchase decision involves an implicit ROI calculation. Making it explicit — in numbers — dramatically increases the salesperson's ability to justify the price and build internal consensus.

ROI components:

• Cost reduction: time saved × blended cost per hour; subscriptions eliminated; headcount avoided
• Revenue increase: deals won faster, capacity to handle more volume, reduced churn
• Risk reduction: compliance fines avoided, security incidents prevented, regulatory penalties reduced

The ROI calculation must be anchored to the prospect's own numbers — their team size, their cost per hour, their revenue impact per day of delay. A generic "our customers save X" claim is not as convincing as "based on what you told me, your team of 12 spends approximately 5 hours per week on this — at your blended cost of $75/hour, that's $2,250/week or $117,000/year. Our tool reduces that by 70%, saving approximately $82,000/year against a cost of $24,000/year."

The ROI case becomes a tool the champion can use internally to justify the purchase to the economic buyer and the CFO without the salesperson in the room.

Handling Objections

Objections are not attacks to be defended against — they are concerns that, if addressed well, move the deal forward. An objection is evidence that the prospect is engaged enough to think through whether to buy.

The most common objections and how to handle them:

"It's too expensive."

This usually means: the value is not yet clear enough to justify the price. The response is to deepen the ROI case, not to immediately discount. "Let's go back to the calculation — you mentioned this problem costs your team $X/year. At our pricing, that's a payback in under 3 months. Does the investment feel different in that context?" If price is still the objection after a clear ROI case, explore budget constraints and pricing flexibility.

"We already have a solution."

This is a status quo objection. The response: "That makes sense — most of our customers were using [common alternative] before switching. What made them move was [specific weakness]. Is that something you're experiencing?" Acknowledge their current investment, then specifically address the gap that brings companies to you.

"We're not ready right now."

This is a timing objection, often linked to no compelling event. Revisit the cost of delay. If the prospect genuinely has a competing priority, negotiate: "What would need to be true for this to move up the priority list? If we could start with a smaller scope that takes two weeks to implement rather than two months, would that change the timeline?"

"We need to think about it."

Often means: a concern hasn't been surfaced yet. "That makes sense. In my experience, when people say that, there's usually a specific concern that we haven't addressed. Can you help me understand what the hesitation is?" This opens the door to the real objection.

What NOT to Do with Objections

• Argue: "No, actually our pricing is very competitive" — this triggers defensiveness and damages trust
• Concede immediately: "OK, I can offer a 30% discount" — signals that the original price was not justified, undermines value positioning
• Ignore and pivot: changing the subject signals the concern wasn't worth addressing
• Dismiss: "Everyone says that at first" — patronising, shuts down the conversation