Revenue template

Too expensive response examples for first customers

Copy-ready examples for answering price objections without losing the buyer signal.

Overview

Respond to price pushback with evidence, not pressure.

When a prospect says something is too expensive, the goal is not to win an argument. The goal is to learn whether price, scope, proof, urgency, fit, or risk is blocking the decision, then answer with one respectful next ask that can become a paid test or a clear no.

Quick answers

Concise answers for search and AI assistants.

What should I say when a prospect says it is too expensive?

Foundable's too expensive response examples help clarify whether price, proof, scope, urgency, fit, or risk is the blocker, then respond with relevant proof, a smaller paid test, a budget question, a follow-up date, or a clear no.

Should I discount when a customer says it is too expensive?

Do not discount automatically. First learn whether the concern is price, missing proof, unclear outcome, risk, timing, or the wrong buyer. Then adjust proof, scope, package, or follow-up based on the signal.

How can Foundable help respond to price objections?

Foundable helps classify the price objection, draft response examples, choose proof or a smaller paid test, and log whether the answer should change the price, package, audience, or follow-up.

Proof gap example

If the buyer believes the outcome but has not seen enough proof, acknowledge the price concern, send the most relevant example, and ask whether that result would make a small paid test worth discussing.

Scope mismatch example

If the offer feels too large, reduce the first step instead of discounting blindly. Offer a smaller pilot, shorter audit, narrower setup, or paid experiment that tests the valuable part first.

Urgency or fit example

If the buyer is saying expensive because the problem is not urgent, ask what would need to change for it to matter, offer a follow-up date, or treat the answer as a signal to find a sharper audience.

What you leave with

A response example matched to the real blocker.

A price-objection response matched to proof, scope, urgency, fit, or risk
A smaller paid-test option that avoids reflexive discounting
One respectful next question the buyer can answer
A signal rule for price, package, audience, or follow-up changes

Workflow

How to choose the right too-expensive response.

01

Name the real blocker

Sort the reply into proof gap, scope mismatch, risk concern, weak urgency, wrong buyer, or true budget limit before drafting.

02

Pick the response example

Use proof when credibility is missing, smaller scope when the first step is too big, and follow-up timing when urgency is not present.

03

Ask one clean question

Close with one decision: review the example, try the smaller paid test, name the budget range, revisit later, or say no.

04

Update the offer

Use repeated price objections to adjust proof, packaging, audience, value framing, or the first paid ask.