How to Respond to “It'll Take Too Long to Set Up”: 3 Answers
“It'll take too long to set up.”
The buyer fears weeks of configuration, data migration, and staff training. Three responses that shrink the first step to an afternoon's work.
Practice this objectionWhy buyers say it
Behind this line is a memory: a previous piece of software that took months, a consultant who never finished, a staff that complained. The buyer isn't evaluating your product; they're projecting last time's pain. If you built practice management software for medical offices, you know setup is mostly done already, but saying so isn't enough, because the last vendor said it too. What works is breaking the rollout into concrete pieces, saying how long each one takes, and starting the first piece right away, small, so the buyer sees with their own eyes that the wall is lower than they feared.
What it often means
- A previous implementation that went badly
- Fear of migrating data and losing some of it
- Nobody at the company has time to spare, and they already know it
Three answers that work
Depends what “set up” means to you. To see your first appointments on the calendar, it takes forty minutes, together, on a call. The rest, importing history and training the front desk, we do afterward and in pieces. Which piece worries you the most?
Why it works: You separate the first visible result from everything else. The buyer learns the opening step is small, and the final question tells you where the real fear sits.
That comes up a lot, and it's usually the memory of last time. Can you tell me how that went? I'm asking because I want to know exactly what must not happen again. Then I'll tell you what I do, what you do, and how long each part takes.
Why it works: You surface the bad experience instead of fighting it blind. Splitting tasks between you and them makes the plan concrete and checkable.
Let's do a test that costs you no time: send me your list of services and your hours, I'll load everything myself, and Friday I'll show you the system already running with your data. If you see it's truly ready, the objection goes away; if not, you've lost five minutes of email.
Why it works: You take on the initial effort yourself. Seeing the product already configured with their own data is more convincing than any time estimate.
Avoid this one
No way, it takes five minutes, it's super easy, you don't have to do anything.
Why not: If it then takes two weeks, you lied, and the buyer will remember it at every little hiccup. Easy promises create impossible expectations.
Example dialogue
BuyerLast time it took three months to get the practice software running. I don't have time to do that again.
YouThree months is a lot. What ate up most of the time?
BuyerMoving the patient records and explaining everything to the receptionist.
YouThen I'll import the history myself: you send me the export and just check the result. And I'll do an hour with your receptionist, whenever suits her.
BuyerAnd when do I see the calendar actually working?
YouForty minutes, Thursday, together on a call. From there you can already book appointments; the rest comes later without stopping anyone.
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.
FAQ
How do I estimate my product's setup time honestly?
Look at the last customers you onboarded and count the real days between signing and first genuine use, not the days you planned. Separate your working time from the customer's: they're two different numbers and the buyer wants the second one. If you have no customers yet, double your estimate and say so.
Should I offer to do the setup myself?
Early on, almost always yes. It costs you a few hours, but it removes the main fear, shows you where the product is hard to configure, and gives you a customer who actually starts. Once you have many customers you can automate onboarding, but that work should come after watching it by hand a few times.
What if the buyer's staff doesn't want to learn a new tool?
Ask who will use it every day and involve them right away, before the decision. A short session where that person does one concrete thing themselves is worth more than any reassurance to the owner. If that person is the one saying “this is simple,” the setup-time objection disappears on its own.