# How to respond to requests for custom onboarding
> Learn how to handle prospects who ask for custom onboarding on LinkedIn, separate real requirements from anxiety, and set limits without losing the deal.
- HTML: https://getkinlead.com/respond-to-prospect-asking-for-custom-onboarding
- Markdown: https://getkinlead.com/respond-to-prospect-asking-for-custom-onboarding.md

**Short answer:** When a prospect asks for custom onboarding on LinkedIn, they usually want proof that setup will not fail for their team. Ask what outcome the plan must protect, then answer with a one-page sequence of milestones, owners and dates. If the request needs work you do not sell, say so and qualify out before you promise a roadmap item.

## Identify what the request is really about

A prospect who asks for custom onboarding on LinkedIn is not always asking for new code. They may be worried about switching systems, testing your flexibility, or describing a gap your product does not cover. If you treat every request as a technical requirement, you end up arguing about features instead of showing how setup will work.

Sort the request before you reply. A reassurance request needs a named owner, dates and a clear first win. A real gap needs an honest answer about what your product does. A procurement move needs a firm line on what you sell and what you do not. The label changes your next message.

Look at the wording. 'Can you send a plan?' usually means 'I need to see that this will not be a mess.' 'Can you build X?' usually means 'I have a workflow your product may not cover.' 'We need this before we can sign' usually means 'I am testing your terms.' The same phrase can hide different requests, so ask before you write.

Write the category in your notes after the first call. If you cannot name it, you do not know enough to write a plan. A plan built on a guess will be wrong in a way the customer notices at kickoff.

**Weak responses**

- Treating every request as a custom build and pulling in engineering before you know the gap.
- Saying yes to keep the deal alive, then hoping the product team can catch up.
- Sending your standard onboarding PDF and calling it a custom plan.

**Strong responses**

- Ask what outcome the plan has to protect, then map it to your current setup.
- Name the owner, the first milestone and the date you will review it.
- Say what you do not support and offer a workaround only if it is real.

## Ask one question before you answer

Your first reply should not be yes or no. A yes gives the prospect room to add requirements before you know what they need. A no closes a conversation that may still be winnable. Ask for the outcome the plan must protect.

Use one question: 'What has to be true in the first 30 days for this setup to count as a success?' That answer tells you whether you are dealing with anxiety, a real gap or a procurement test. Then you can answer with a sequence instead of a promise.

If they cannot name an outcome, ask about the last setup that failed. People describe risk through past pain. A prospect who says 'our last vendor took six weeks to connect the data' is telling you the plan needs a clear connection milestone and a named owner. Write that down before you reply.

Do not ask five questions in the first message. One good question gets a useful answer. A list of questions feels like a form and slows the conversation down.

- **them:** Can you send a custom onboarding plan for our team?
- **you:** I can put one together. What has to be true in the first 30 days for this setup to count as a success?
- **them:** We need the data flowing into our weekly report and the team trained before the next quarter.
- **you:** That helps. I will map the report setup, the training session and the owner for each step. If the sequence looks right, we can book 15 minutes to confirm dates.

## Write a one-page plan, not a spec

A custom onboarding plan is a project tool. It shows how the customer gets to the first win, who does what and when you will check the result. Keep the settings list out of it.

Keep it to one page. Put the first win at the top, then the milestones, owners and dates. Separate your work from the customer's work. If they need to provide access, data or a sales script, write that down. This prevents the 'we thought you were handling that' conversation later.

Use the customer's words for the first win. If they said 'we need the weekly report to include pipeline by rep', do not translate that into a feature name. The plan should read like their goal, not your product tour.

Send the plan before the call, not after. Ask the customer to mark anything that is wrong or missing. A plan they edit is a plan they own. A plan they receive after the call is a document they skim.

1. **Define the first win.** Name the one result the customer wants in the first 30 days. Use their words, not a feature name.
2. **List the milestones.** Break setup into phases. Example: Week 1 connect accounts, Week 2 import leads, Week 3 launch the first campaign.
3. **Assign owners.** Put a name beside every task. You own configuration and training. The customer owns access, data and review time.
4. **Set the review date.** Book a check-in 14 days after launch. Use it to adjust the plan based on what actually happened.

```
Custom onboarding plan: [Customer]
First win: [result] by [date]

Milestones
1. [date] [task] - owner: [name]
2. [date] [task] - owner: [name]
3. [date] [task] - owner: [name]

Customer provides
- [access/data/script]
- [review time]

Review call: [date/time]
Open questions: [list]
```

## Handle the feature gap without promising a roadmap item

Some requests are real gaps. The product does not do what the prospect needs. The weak move is to promise a future update to close the deal. That creates a customer who is unhappy at kickoff because the product does not match the promise.

Answer the underlying problem. Most custom requests describe a result, not a feature. If you can reach the result through a different workflow, show it. If you cannot, say so and qualify out. A clear no protects your delivery team and your reputation.

Keep the answer short. Long explanations sound like excuses. State the gap, state the workaround if one exists, and ask whether the workaround meets the requirement. If it does not, move to the next step.

Do not use the phrase 'on the roadmap' unless you have a date and a commitment from product. A maybe is worse than a no because it keeps the deal alive on false hope.

| | Request | What to say | What to do next |
| --- | --- | --- | --- |
| Specific feature request | We do not support that exact feature. Teams with the same goal use this workflow instead: [workflow]. | Show the workflow on a call. Do not promise a build. |
| Custom build request | We sell a standard product. I cannot promise a custom build, but I can show you what the current setup can do. | Send a short video or screenshot of the current setup. |
| Hard requirement | That is not supported today. If it is required for the project to move forward, we may not be the right fit. | Ask if the requirement can move to phase two. If not, close the loop. |

> Never promise a feature that is not in the current build to win a deal. A lost lead costs less than a customer who signs expecting something you cannot deliver.

## When to qualify out

Qualify out when the request is a hard requirement and your product cannot meet it. Do it early, before you write a plan. A custom onboarding document will not fix a missing core capability. It only delays the no.

Use a direct message. Thank them for the detail, restate the gap in their words, and say you are not the right fit right now. If they might fit later, tell them what would need to change. This keeps the door open without wasting their time or yours.

Do not send a proposal and hope the gap disappears. If the requirement is legal, security or a core workflow, it will come back at signature or at kickoff. The earlier you name it, the less work you waste.

If the prospect pushes back, ask one question: 'If we cannot meet this requirement, does the project stop?' If the answer is yes, stop. If the answer is no, ask what workaround they would accept. That answer tells you whether the gap is real or a negotiating position.

A clean no also gives you a reason to follow up later. If they change tools or drop the requirement, you are the person who was honest with them.

- They need a feature you do not have and cannot work around.
- They need a custom build before they can go live.
- They need a legal or security term you cannot meet.
- They keep adding requirements after you have agreed the scope.

## Put the plan in the deal, not in a slide deck

A plan that lives in a slide deck dies after the call. Put the milestones, owners and dates in the proposal or the shared document the customer will use during kickoff. The plan should be the same document your delivery team reads on day one.

Add one line to the proposal: 'This plan assumes the customer provides access, data and a review contact by [date]. If those slip, the dates move with them.' That line protects you from a delay you did not cause.

If the customer asks for a custom plan before they have seen a demo, slow down. A plan without a shared understanding of the product is a guess. Show the workflow first, then write the plan around the workflow they agreed to.

Send the plan as a PDF and a shared doc. The PDF is for procurement. The shared doc is for the people doing the work. Keep both in sync. If the shared doc changes, update the PDF before the next call.

Keep the plan short enough to read in one sitting. If it needs an appendix, the appendix is a separate document for the delivery team. The customer needs the milestones, not the internal checklist.

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe, or your website, and scores each lead from 0 to 100 against that profile. Leads below the fit line are not kept, so you spend plan-writing time on prospects who look like your existing customers.

The [Steal Customers agent](/features/steal-customers) watches competitor company pages and optional founder or employee profiles, reads comments on recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented. That context helps you open with a relevant question instead of a generic pitch.

Outreach runs from your own LinkedIn account through Unipile, at a human pace inside the limits and send window you set. Messages and follow-ups are written by AI from the campaign goal, tone and your sales playbook. Replies land in one inbox, classified by intent, so you can step in when a prospect asks for a custom onboarding plan.

## Related

- [Find leads](https://getkinlead.com/tools/find-leads.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)

## Common questions

**Should I charge extra for a custom onboarding plan?**

If the plan needs manual setup or consulting hours from your team, charge for it. That qualifies the lead and pays for the work. If the plan is a one-page sequence of standard milestones, include it in the deal.

**How long should a custom onboarding document be?**

One page. It should list the first win, milestones, owners and the review date. If you need an internal checklist, keep it in a separate document for the delivery team.

**What do I do if the prospect keeps adding requirements after the plan is signed?**

Point to the signed plan and put the new requests in a phase two list. Agree to review them after the first 30 day goal is met. If the new request is a hard requirement, treat it as a new qualification call.

**Can I say a feature is on the roadmap?**

Only if product has given you a date and a commitment. A maybe keeps the deal alive on false hope and creates a customer who is unhappy at kickoff.

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