← All articles

"It doesn't do X": treat the job, not the feature

Objection Handling Playbook · September 15, 2026

How do you handle "your product is missing X"? Don't promise the roadmap and don't argue X doesn't matter. Ask what job X does: "what would you use X for, day to day?" Half the time your product does that job another way; sometimes X is a checklist item copied from a competitor's page; and sometimes it's real, in which case honesty now saves a churned customer later.

Throw this objection at Objeq right now → Live demo, the real engine answers. No signup.

Features are proxies, jobs are real

Nobody wants a feature; they want what it does. "Do you integrate with our CRM?" might mean "I don't want manual data entry," "my boss lives in dashboards," or "the last tool made us copy-paste everything." Each of those jobs may have an answer that isn't the named feature. Until you know the job, you're negotiating about a word.

The treatment, step by step

  1. Confirm without flinching. "Correct. We don't have X today." Dodging a factual question costs more than the missing feature does.
  2. Ask for the job. "Help me understand the day-to-day: what would X handle for you?" Asked with genuine curiosity, this reframes the whole conversation from checklist to workflow.
  3. If the job has another path, show it live. Not "you could theoretically..." but a 60-second demonstration of the alternative. A job done differently is a job done.
  4. If X is a checklist item, test its weight. "Is X a must-have that kills the deal, or a nice-to-have from the comparison sheet?" Buyers often deflate their own checklist when asked directly.
  5. If it's real and central, say so and stand down. "If X is the core of your workflow, we're honestly not your tool this year." You lose the deal you were going to lose anyway, and keep the reputation.
  6. Roadmap honesty only. Share plans only if they're real, with no dates you can't keep. A missed roadmap promise is churn with a delay timer.
Prospect: "We need Salesforce integration and you don't have it."
Rep: "True, we don't today. What's the job, logging calls automatically, or something else?"
Prospect: "Mostly that reps don't do data entry."
Rep: "That job we do differently, the debrief generates the call summary for them. Want to see the 60-second version?"

FAQ

Should I ever promise a feature to close a deal?

Only if it's genuinely on the roadmap with a date you control, and even then, close on today's product with the feature as upside. Deals closed on promises become support tickets and churn.

What if the missing feature comes up in every deal?

Then it's not an objection, it's product feedback with revenue attached, bring the pattern to the product team with the deal sizes it's blocking. Sales is the cheapest user-research channel a company has.

What does Objeq say about its own missing features?

The same thing this article says: what we don't do (desk-phone telephony, CRM writes) we say out loud, and what job we do differently we show in the demo. Check the honest edges before the trial, not after.

Handle it live, not in the postmortem

Reading about objections is training. Handling them is a live skill under pressure, which is why Objeq whispers the treatment to your rep during the call, in under two seconds, visible only to them. See pricing or how it compares to Gong.

Start free, 3-day trial

From $99 / seat / mo after the trial · card up front, charged only when the 3 days end · cancel in one click