# How to answer questions about implementation and effort
> Buyers who ask about setup are pricing your product in their own time. Here is how to answer with the first result instead of a task list of phases.
- HTML: https://getkinlead.com/reply-to-prospect-asking-about-implementation
- Markdown: https://getkinlead.com/reply-to-prospect-asking-about-implementation.md

**Short answer:** Buyers who ask about setup are working out what it costs them in their own time. Answer with the first result and the date it arrives, not with a list of phases. The work you describe is the work they picture doing.

## What the buyer is asking when they ask about setup

When someone on a LinkedIn call asks how long setup takes, they are working out what the thing will cost them in evenings and favors. Nobody asks that question to get a project plan. A $200 a month tool that eats two weekends is a $200 a month tool plus two weekends, and they know it.

The usual answer makes this worse. A list of phases, a mention of CSV imports, a note that someone from onboarding will be in touch: each of those tells the buyer they have taken on a project. They have not. They have bought a result.

So answer the question they meant. How much of my time, whose time, and when do I see something for it. If you can put a number on the first part and a date on the last, the rest of the conversation gets easier.

## Describe the first week, not the whole build

Most implementation stories are told from the inside: what your team does, in what order, with which systems. Buyers hear a queue of things that can go wrong and a set of meetings they have to attend.

Tell it from their side instead. The facts that matter early are what they hand over, what they get back, and when. Everything else can wait until they have seen the first result.

Take a 40-person agency that sells retainer work. What worries them is a week of list building before anything happens. The answer that lands is not a guided onboarding flow. It is: send me your website and the last three clients you loved, and you will have a scored list to review on Thursday. That is a promise you can keep, and it takes one email to make.

**Thinking about your process**

- We start with a data migration phase where you upload your CSVs.
- There is a four-step onboarding process, and someone from our team will walk you through it.
- You will need to configure your user permissions before we go live.

**Thinking about their week**

- Send me your website today and you will have a scored lead list to review on Thursday.
- You spend ten minutes on the first review, and I handle the import.
- We use your existing script, so the first messages sound like you wrote them.

## Turn each setup step into something they get

Every step in your process produces something. A data import produces a clean list. A script review produces messages that sound like the buyer. A permissions setup produces access for the team. Name the output, not the step.

This matters most for the parts you need from them. A sales playbook sounds like homework. A playbook that makes the AI write like their best rep sounds like a shortcut. It is the same request in a different sentence.

The table below is the swap I use most often. The middle column is what a seller says while thinking about their own process. The right column is the same fact from the buyer's chair.

| | Setup step | What the seller says | What the buyer hears when you say it their way |
| --- | --- | --- | --- |
| Lead list | We import a CSV of target accounts in week one. | You will have a list of people to look at by Thursday, and you can delete anyone who is wrong. |
| Messaging | You need to provide your sales script and tone guidance. | Send me two messages you have sent before. The first drafts will sound like those. |
| Access | You will need to set up user permissions for your team. | Your teammate can log in on Monday and see the same campaigns you do. |
| Review | We run a QA pass on the first campaign before launch. | You read the first ten messages before anything sends and change what you don't like. |

## Answer the 'I don't have time' objection

When a buyer says they do not have the bandwidth, they have done the math and the effort came out ahead of the result. Arguing that the tool is easy does not change the math. It tells them you were not listening.

Do two things instead. Agree that their week is full, then shrink the ask to something they can picture doing today. Thirty minutes is a real number a buyer can check against their calendar. Quick setup is not.

Then take the part they are dreading. If the blocker is a list, build the first one for them. If it is the script, draft it from messages they already sent. The objection usually names the exact piece of work to remove.

- **them:** This looks good, but I don't have the bandwidth for an implementation right now.
- **you:** Fair. How full is the rest of your week?
- **them:** Back to back until Friday. I also don't have a clean list of who we'd target.
- **you:** Then don't build one. Send me your website and the two clients you wish you had more of. I'll put a first list together and you can tell me who is wrong on Friday.
- **them:** That I can do. What do you need from me?
- **you:** Just those two things. The rest is my problem until you see the list.

> Never tell a busy buyer the setup is easy. Show them the smallest piece of work you can take off their desk this week.

## Write a timeline you can actually deliver

A timeline full of tasks reads like a project the buyer has to manage. A timeline of results reads like a schedule of things arriving. Keep it short enough that the first result lands inside their attention span.

Only promise dates you control. If a step depends on the buyer sending something, say what happens when it arrives late, and make sure the next milestone is still true. A slipped date costs more trust than a slower start.

Here is the shape I use for a first week of LinkedIn outbound. Change the days to fit your product, not the other way round.

1. **Day one: the target.** The buyer sends their website or describes their best customer in two sentences. You turn that into a scoring profile and a first lead group.
2. **Day two: the words.** You pull two messages they have sent before and use them as the tone reference. They read the first drafts and mark what sounds wrong.
3. **Day four: the first sends.** The campaign goes live inside their send window. They see the queued messages before anything leaves.
4. **Day seven: the review.** You go through replies together and change the goal or the script based on what came back. This is the first call where they are looking at results instead of setup.

## Put the answer in writing before the call

Buyers forward things. A short written answer to what does setup involve gets sent to a boss or a partner who was not on the call, and it gets read without your tone of voice. Write it so it survives that trip.

One page, three parts: what they give you, what you give back, and the date of the first result. No phases and no diagram. If they want the technical version, send it after, as an attachment.

Here is a template you can paste into an email or a LinkedIn message after the call.

```
Hi {first name},

Here is what getting started looks like from your side.

You send: your website and two messages you have sent before.
I send back: a scored list of people who match your best customer, and first drafts of the opening message in your tone.

You will have the list to review by {day}. The first messages go out inside your working hours, and you can read them before they send.

If the list is wrong, we change the profile before anything else happens. That is the whole first week.

{your name}
```

## Doing this with Kinlead

Kinlead is built around this answer. You describe the customer you want or paste your website, and it finds matching people on LinkedIn and scores each one from 0 to 100 against that profile. Leads under the fit line are dropped, so the first list you review is already filtered.

Setup stays short because lead search uses standard LinkedIn search, so no Sales Navigator seat is needed. If you would rather not describe an audience at all, the Steal Customers agent watches competitor company pages and the comments on their posts, then turns commenters who look like buyers into leads with the post and comment attached.

Connection notes and follow-ups are written from the campaign goal, tone and your own sales playbook, and queued messages can be read and edited on the Actions page before they send. Replies from every campaign land in one inbox sorted by intent, with interested ones first.

Pro is $49 a month after a 7-day free trial, and the minimum booking guarantee is set out at [the guarantee terms](/minimum-booking-guarantee).

## Related

- [AI sales playbook](https://getkinlead.com/ai-sales-playbook-for-linkedin-outreach.md)
- [Lead scoring setup](https://getkinlead.com/ai-lead-scoring-fit-line-setup.md)
- [Connection request templates](https://getkinlead.com/ai-linkedin-connection-request-templates.md)

## Common questions

**How do I handle a buyer who insists on a detailed technical implementation document?**

Send it, but don't lead with it. Put it after a one-page summary of what they give you and what they get back, so the document answers a question they already have instead of setting the agenda.

**What is the best way to prove a tool is easy without a demo?**

Give a time-to-first-result statement with a real date in it. You will have the list to review on Thursday is checkable. Easy setup is not.

**How do I move from setup to the contract?**

Once they agree the first week is small, use that agreement. Say that since the first week is one email from them, you can start Monday, then send the paperwork the same day.

**What if the implementation really is heavy?**

Say so early and split it. Sell the first milestone on its own, deliver it, then talk about the rest. A heavy build sold as light is the fastest way to lose the account in month two.

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