"Can't I Just Use ChatGPT?" - How I Answer the Objection That Kills Deals

Duncan RogoffDuncan Rogoff July 18, 2026 8 min read
A branded illustration of a small hollow speech bubble and a bold solid one resolving into a handshake - an objection turning into agreement
Illustration by Claude Code Club

"Can't I Just Use ChatGPT?" Answer the Real Question, Not the Words

Straight up: when a prospect asks why they should pay you when they can just use ChatGPT, do not answer the words - answer the fear underneath them. The words sound like a tool comparison. The fear is that they are about to overpay for something they suspect they could do themselves. So the move is not to argue that your AI is better than their AI. It is to agree that the tool is cheap and available, then move the conversation to the thing they are actually buying: a finished result, done right, that they did not have to build or own the risk on. The instant you make it about the tool, you lose. The instant you make it about the outcome, you win.

Why Arguing About Features Always Loses

The trap is to answer with a spec sheet - my tool has bigger context, it edits files, it runs commands, it uses MCP servers. All true, and all a losing move in a sales conversation, because now you are two vendors arguing over horsepower while the prospect quietly decides they will just try it themselves for twenty bucks a month. Features are a comparison, and comparisons invite the prospect to become the expert who judges them. You do not want them judging tools. You want them judging outcomes, where the honest comparison is not your AI versus their AI - it is a finished, working thing versus a folder of half-built attempts and a weekend they will not get back.

The Reframe: They Are Not Buying AI, They Are Buying the Result

Here is the line I actually use, close to word for word: "You are completely right that the tool is cheap - I use these tools too, that is exactly how I get you a result this fast. What you are paying me for is that it works, it is done this week, and if it breaks it is my problem to fix, not yours." That reframe does three things at once. It agrees, so I am not fighting them. It repositions the AI as my cost, not the product. And it names the two things a chatbot can never sell them: a finished outcome and accountability. A prompt gives you an answer. It does not give you a shipped, working result with a name attached to it if something goes wrong.

  • Agree first: yes, the tool is cheap and available - remove the fight.
  • Reposition the tool as your cost, not the deliverable, so the price is about the outcome.
  • Name what they cannot buy from a chatbot: a finished result, on a deadline, with your accountability behind it.

The Close Is a Question About Their Time

After the reframe, do not pitch - ask. "If you did this yourself with ChatGPT, honestly, how many hours do you think it takes you to get it fully working, and what is an hour of your time worth?" Then be quiet. They will do the math out loud, and almost every time the number they land on is bigger than your fee, because they are not just pricing the typing - they are pricing the learning curve, the dead ends, and the risk of getting it subtly wrong. You did not tell them your service was worth it. You asked a question that let them prove it to themselves. That is the whole close, and it works precisely because you let them build the case instead of arguing it for them.

When "Just Use ChatGPT" Is Actually the Right Answer

One more thing, because pretending it is never true will cost you trust. Sometimes a prospect really should just use ChatGPT, and saying so is how you win the next, bigger job. If someone needs a quick draft, a one-off script, or help thinking something through, tell them plainly that a chat tool is the right call and they do not need to hire anyone. You lose a small deal you did not want and you become the person who told them the truth. When the real project shows up - the one with a deadline, a budget, and a cost of being wrong - you are the first call. Honesty about when they do not need you is the cheapest marketing there is.

Make the Objection Work for You

The "can't I just use ChatGPT" objection is not a wall, it is a door. It tells you the prospect is weighing doing it themselves, which means they are close enough to buying to imagine the work. Meet it by agreeing, repositioning the tool as your cost, and asking what their time and their risk are really worth. Inside the Profit Room we keep the exact scripts our members use to handle this and the other three objections that kill most deals, with the wording that has actually closed them. If you sell anything built with AI, come grab the scripts and stop losing deals to a twenty-dollar subscription.

Free Claude Code drops, straight to your inbox

Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.

Frequently asked questions

How do I answer a client who says they can just use ChatGPT?

Do not argue about which AI is better. Agree that the tool is cheap, then reframe what they are actually paying for: a finished, working result delivered on a deadline, with your accountability if anything breaks. A chatbot gives them answers; you give them an outcome they can trust and did not have to build.

Why does arguing tool features lose the sale?

Because it turns the conversation into a comparison, and comparisons invite the prospect to decide they can just judge and use the tool themselves for a few dollars a month. You want them weighing outcomes, not horsepower - a finished result versus a folder of half-built attempts and a lost weekend.

What is the best way to close after the reframe?

Ask a question instead of pitching: how many hours would it take them to get it fully working themselves, and what is an hour of their time worth? Then stay silent. They will price in the learning curve and the risk of getting it wrong, and that number usually beats your fee - so they close themselves.

Should I ever tell a prospect to just use ChatGPT?

Yes, when it is true. If they need a quick draft or a one-off, tell them a chat tool is the right call and they do not need to hire anyone. You lose a small deal you did not want and become the honest expert they call first when the real, higher-stakes project arrives.

Is the objection a bad sign?

No, it is usually a buying signal. It means the prospect is imagining doing the work, which means they are close. Treat it as a door, not a wall - agree, reposition the tool as your cost, and ask what their time and their risk are truly worth.

What am I really selling if the AI is cheap?

You are selling the result and the accountability, not the software. The prospect is buying not having to become the builder - no learning curve, no dead ends, no owning the risk if it breaks. The AI is your cost of delivering fast; the finished outcome with your name on it is the product.

Last reviewed by Duncan Rogoff on July 18, 2026

Duncan Rogoff

Written by

Duncan Rogoff

Apple · PlayStation · Charles Schwab

Keep reading

Claude CodeWorkflow

Claude Code Hooks: Which Ones Actually Earn Their Keep

Most Claude Code hooks look clever and then get deleted a week later. After running them on real client builds, here are the three hooks I actually kept, the ones I dropped, and how to add your first one without breaking anything.

David Iya 9 min
Read article
Claude CodeMCP

The Best Claude Code MCP Servers (and What Each One Unlocks)

MCP servers are how Claude Code reaches past your code and into your real tools. Here are the best Claude Code MCP servers to install first, grouped by what they let the agent actually do - from your repos and the live web to browsers, databases, and your workspace.

David Iya 10 min
Read article

Ready to build it yourself?

Join Claude Code Club, the #1 community for learning claude code, for $9/month.

← Back to the blog