DealkataItaliano

How to Respond to “It Looks Too Complicated”: 3 Practical Answers

“It looks too complicated.”

The buyer sees too many features and backs off. Three ways to shrink the product to what they actually need and get them to take the first step.

Practice this objection

Why buyers say it

Often the problem isn't the product, it's the demo: you showed everything it can do and the buyer saw a mountain of things to learn. Someone who says “too complicated” is picturing hours of setup, questions from coworkers, mistakes in the first week. They're also telling you, without saying it, that they have no time to study a tool. They want a problem solved. Sometimes it hides a fear of not being up to it, especially in people who don't feel comfortable with technology. More explanation makes it worse. Taking things away works.

What it often means

  • Fear of not being capable and looking bad
  • Zero time to spend learning a tool
  • A demo that showed too much, too fast

Three answers that work

  1. You're right, I showed you way too much. Forget the rest: for your first month you only need [two or three features]. Tell me the thing you do most often and I'll walk through it with your own data.

    Why it works: You take the blame for the complexity onto the demo, not the buyer, and immediately shrink the scope. Working on their real case turns an abstract tool into a motion they recognize.

  2. Here's what I'd suggest: we do the initial setup together on a [length] call, and by the end you've already sent your first real [quote]. After that it's the same motion every time. If it still feels complicated after that call, we stop there.

    Why it works: You remove the weight of getting started, which is the scary part, and give a clear point to bail. The buyer isn't committing to learning, they're committing to one call: a small, reversible step.

  3. Tell me what felt complicated, so I can see if it's something we can hide. A lot of features can be switched off, so you only see what you use. The best starting point is whatever you do today on paper or in a spreadsheet, rebuilt exactly the same way.

    Why it works: You ask where the complexity is instead of assuming, and offer a concrete fix: fewer screens. Starting from the buyer's current workflow respects their habits instead of asking them to change.

Avoid this one

It's actually super simple, it just takes a little practice and after two days you'll use it with your eyes closed.

Why not: You contradict what the buyer just told you and essentially say the problem is them. It doesn't reassure anyone, it makes them feel inadequate, and nobody buys a tool that makes them feel dumb.

Example dialogue

BuyerNice, but I've been doing quotes for twenty years with a notepad and a calculator. There are too many screens here.

YouFair. I showed you the whole program, and you need two things: write the quote and send it. We hide the rest. Got a quote you did last week? Let's redo it right here, together.

BuyerI've got one here, the bathroom job for Mrs. Ross.

YouPerfect. See, you typed the line items, the program totals it and sends it. Three minutes. If you do one on your own next week and it still feels complicated, call me and we'll sort it out.

BuyerPut that way, it's a different story. Let's try it.

Practice this objection

A simulated buyer says it to you out loud (or in writing), you answer, and you get a score plus the model answer. Free, no account, 2 minutes.

Practice this objection

FAQ

How do I run a demo that doesn't look complicated?

Show one thing: the action the buyer repeats most often, done with their data. No full feature tour, no settings. Before the demo, ask what they do today and how, then replicate exactly that. They'll discover the other features when they need them, not before.

Should I simplify the product if a lot of buyers say this?

If you hear it often, yes: it's a signal about the product, not just the sales call. You don't have to remove features, just hide them at the start and reveal them progressively. A good guided setup or a ready-made template for that type of customer also goes a long way toward reducing the feeling of complexity.

What if “too complicated” really means they don't want to change?

It happens. To find out, ask: “If it were as easy as what you use now, would you take it?” If you get a firm yes, work on simplicity. If the answer is vague, the issue is elsewhere: the need isn't strong enough or the decision isn't theirs. Change the conversation accordingly.

Related objections