← All writing

Writing · Tagged

objection-handling

3 pieces on this thread.

Positioning · September 12, 2026 · 8 min read

What to say when a customer says "I'll just build this myself"

When a prospect says they'll just build your product themselves, arguing features loses, because features are the part AI coding tools made cheap. The weekend prototype really does work. What it lacks is Day 2, the infrastructure term for everything that starts once software ships. Broken integrations, security reviews, patches, and the handoff when the builder leaves. Retool's 2026 survey found 35% of teams have already replaced functionality of at least one SaaS tool, so the objection is no longer a bluff. It's also a positioning signal. Most SaaS messaging sells what the product does, which is Day 1, and buries ownership in pricing-page footnotes. Answer the objection with questions about month six, then rewrite the homepage around what it takes to own the thing.

positioningobjection-handlingbuild-vs-buyb2b-saassales-enablement

Positioning · August 29, 2026 · 10 min read

How to handle the "you're too expensive" objection in B2B SaaS

Expensive is a comparative word. When a prospect says your price is too high, they're reporting on a comparison they built weeks before you were in the room, usually against a category floor, a headcount, or the cost of doing nothing. Standard objection handling assumes that comparison is fair, so quantifying ROI only makes you a well-documented version of the wrong thing. Discounting is worse, because it ratifies the comparison and puts your signature on it. The real work happens earlier, in the messaging and on the pricing page, where you decide what your price gets measured against before a buyer picks something for you.

pricingpositioningobjection-handlingb2b-saassales-enablement

Competitive Strategy · August 8, 2026 · 8 min read

What to say when a prospect calls you "just like [competitor], but worse"

When a prospect says you're just like a competitor but worse, the winning move isn't a better rebuttal. Arguing the comparison ratifies it. Whatever gets named first in a judgment anchors everything after it, so every counterpoint ends up scored on the competitor's rows and phrased in the competitor's vocabulary. Winning that exchange still loses the frame. "Worse" is also rarely about features. It usually stands in for risk, an existing budget line, or a half-remembered opinion from someone's boss. The reset has three moves. Name the comparison out loud, refuse to argue it explicitly, then change what's being compared and hand the prospect a question on the new axis. If you can't state your axis in one sentence without opening a document, the problem is positioning, not objection handling.

competitive-positioningobjection-handlingsales-enablementb2b-saasmessaging