# How to answer a prospect who asks how long setup takes
> A prospect asking how long setup takes wants to know when they see a result. Here is how to answer on LinkedIn without overselling or hiding the work.
- HTML: https://getkinlead.com/handle-prospect-asking-about-implementation-time
- Markdown: https://getkinlead.com/handle-prospect-asking-about-implementation-time.md

**Short answer:** When a prospect asks how long setup takes, they're asking how much work lands on them before anything works. Answer with the date of their first result, then give the honest length of the full rollout. Do both and the timeline stops being the objection.

## What the prospect is really asking

A message that asks how long setup takes is rarely a request for a project plan. The person is working out two things at once: how much of the work lands on them, and how long they pay before anything works.

Most buyers have lived through a rollout that ate a month of someone's time and produced nothing they could show a manager. That memory sits in the conversation whether they mention it or not.

The question also arrives in different clothes. 'How involved does my team need to be', 'what does the first week look like', 'do we need IT for this'. Treat all of them as the same question and answer them the same way.

So the reply needs two parts: the date of their first result, and the honest length of the full rollout. Leave out the first and you sound like you're dodging. Leave out the second and they find out later, which costs more.

> Answer the fear before the calendar. A prospect who believes the first result is coming will sit through a long rollout. One who doesn't will hear every timeline as too long.

## Put the first result before the full timeline

Order matters more than wording. If the timeline comes first, the prospect spends the rest of the message deciding whether they have the time. If the result comes first, they read the timeline as context.

Keep the result specific and dated. 'Faster onboarding' means nothing. 'A list of 40 target accounts by Thursday' is something they can hold you to, which is why it works.

Give the timeline in the units they think in. 'Ten business days' sounds longer than 'two weeks' even when it's the same thing, and 'by Thursday' beats both.

Never give a range you can't hit. If the honest answer is three weeks, say three weeks and explain which part is slow. Buyers forgive a slow step they understand. They don't forgive a date that slips.

**Timeline first, no result**

- Our onboarding runs about four weeks, including data migration and training.
- Setup is roughly 10 business days depending on your stack.
- We'll have you fully implemented within a month.

**Result first, timeline second**

- You'll have your first scored lead list by Thursday. The full rollout takes about three weeks after that.
- Your first campaign can go live Wednesday. The reporting setup keeps running in the background for two weeks.
- Day one you get the workspace. Day three you get leads. Day ten everything is connected.

## Work out what you can actually promise

Before you type a date, check it against three things: what works without setup, who does the work, and which step is genuinely slow. Most reps skip this and guess, then spend the next month explaining.

1. **Find the smallest real result.** Ask what a new customer can see working in week one with no integration at all. For most tools it's one campaign, one list, one report. That's your headline.
2. **Write down what the customer has to do.** List the tasks that land on them: export data, invite the team, connect an account. If the list runs past three items, the timeline is the problem, not the wording.
3. **Set the date from your own calendar.** Pick the day you can personally deliver the first result, not the day the process theoretically ends. If you're away that Thursday, the date moves.
4. **Attach the slow step to the full timeline.** Say which part takes longest and why. 'Three weeks, and the slow part is moving your old data across' is a sentence a buyer can plan around.

> If you can't answer step two honestly, don't send a date. Ask one question first: 'who on your side would pull the data?' The answer tells you more about the timeline than your own process doc.

## A reply you can send today

Keep it short. On LinkedIn a long onboarding explanation reads as anxiety. Three or four sentences, one date, one dependency.

Don't open with 'great question' and don't offer a call before you've answered. The call is the next step, not the answer.

- **them:** How long does setup take? We've been burned before by a tool that took six weeks to get going.
- **you:** Fair question. Full setup here is about three weeks, and the slow part is moving your old data across. What you'd see first is a working list of target accounts by Thursday of week one, built from your website. If that list is wrong you've lost two days, not a month.
- **them:** Who does the data move?
- **you:** We do the import, you check it. It's one CSV and a call.
- **them:** OK, send me a time Thursday.

> That reply works because it puts a number on the risk: two days lost, not a month. Small, specific losses are easier to accept than vague reassurance.

## When the honest answer is that setup is slow

Some rollouts really do take a month. You still have a good answer, as long as you separate the slow part from the part that produces something.

The pattern is the same in every row below: name the slow step, give the date for the fast result, and let both be true at once.

| | Situation | What to say | What to do next |
| --- | --- | --- | --- |
| Long data migration | The import takes about three weeks. Your first campaign can run on new data while it happens. | Start the campaign on fresh leads and migrate history in parallel. |
| Their team has no bandwidth | You need about an hour in week one, from one person. I'll do the rest. | Name the one person and the one hour before the call ends. |
| They need IT approval | Security review usually adds a week. Everything else can run before it finishes. | Send the security docs the same day, not after the call. |
| They're switching from a competitor | Exporting from the old tool is the slow part. Most teams keep both running for a month. | Ask what they'd keep the old tool for, then plan around that. |

## What to do in the week after you answer

Send the first result before the next call. If you promised a list by Thursday, the list arrives Wednesday with a short note about how it was built. That single action does more for the deal than another call about implementation.

Put the date in your own calendar with the prospect's name on it. Most missed onboarding promises are missed because nobody wrote them down.

If the date is going to slip, say so before they ask. One message on Wednesday morning costs you nothing. A prospect finding out on Friday costs you the deal.

```
Hi Dana, the list is attached: 38 accounts that match the profile you described. I'd skip two of them, they look like agencies rather than end customers. Full rollout is still on track for the 14th.
```

## Doing this with Kinlead

Kinlead shortens the part of setup that usually takes longest, which is finding the first people to contact. You describe the customer you want, or point it at your website, and it scores each lead from 0 to 100 against that profile. Leads below the fit line aren't kept.

The [Steal Customers agent](/features/steal-customers) watches competitor company pages and optional founder profiles, reads the comments on their recent posts, and turns commenters who look like buyers into leads, with the post and the comment attached.

Leads sit in groups, and any campaign can point at any group. If you already have a list, import a CSV of LinkedIn profile URLs and start the same day. Replies from every campaign land in one inbox, so the first result you can promise is a real conversation rather than a finished implementation.

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [Set your fit line](https://getkinlead.com/ai-lead-scoring-fit-line-setup.md)
- [Campaigns and send windows](https://getkinlead.com/features/campaigns-and-send-windows.md)

## Common questions

**Should I give a shorter timeline than the real one to keep the deal moving?**

No. The deal you win on a short timeline comes back as an angry customer in week three. Give the real date and put the first result in front of it.

**What if the product really does take a month to implement?**

Find the part that works in days and sell that as week one. Move the heavy setup to a second phase and say so out loud.

**How do I answer when they ask for a detailed project plan?**

Send the plan, then point at the two dates that matter: the first result and the full rollout. A plan where every milestone carries the same weight tells them nothing.

**What if they go quiet after I answer?**

Send the first result anyway if you can build a small version of it. A sample list or a short audit beats a follow-up message asking whether they saw your reply.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
