Customers say “We’re too big and complex for something like this” for a reason. Here is what usually sits behind it, how to respond and what to avoid.
The customer expects your solution to be too simple for their scale or their needs. They may fear that it will not handle their complexity, or that integrating it will be harder than for others. The worry is capability and risk, not interest.
Typical in: Software and SaaS, Manufacturing and logistics
Pick the framework that fits the customer. The wording is an example direction, not a script: say it in your own words.
Ask what sits behind the objection, so you answer the real concern.
“What makes your situation more complex than most: the number of people, the systems or the rules you work under? I would like to understand exactly where it would be stretched.”
Shrink the decision to something low-risk that moves things forward.
“We could start with one team or one use case, and see how it handles your complexity before you consider anything larger. That limits the risk to a small part of the organisation.”
Offer an example, a reference or a sample the customer can check. Never an invented figure.
“I can describe how we have dealt with larger or more complex set-ups, honestly including where there were limits. Would that help you judge whether it could work for you?”
After your response, ask:
Which part of your set-up would be the hardest test for something new?
Avoid: We have worked with companies bigger than yours.
Without details, it is an empty claim. A specific, truthful example would help; a bare comparison does not.
Reading is not the same as saying it. Talk to an AI customer who raises this kind of objection and see in the report which sentence helped.
Practise this objectionThe customer expects your solution to be too simple for their scale or their needs. They may fear that it will not handle their complexity, or that integrating it will be harder than for others. The worry is capability and risk, not interest.
Clarify before you answer: “What makes your situation more complex than most: the number of people, the systems or the rules you work under? I would like to understand exactly where it would be stretched.” Propose a smaller step: “We could start with one team or one use case, and see how it handles your complexity before you consider anything larger. That limits the risk to a small part of the organisation.” Offer proof: “I can describe how we have dealt with larger or more complex set-ups, honestly including where there were limits. Would that help you judge whether it could work for you?”
Which part of your set-up would be the hardest test for something new?
Avoid “We have worked with companies bigger than yours.” Without details, it is an empty claim. A specific, truthful example would help; a bare comparison does not.
Educational conversation training. It is not legal or financial advice and it promises no results. Always follow your company’s rules, the terms of the product and a customer’s clear no.