# How to handle requests for custom pricing quotes
> How to reply when a prospect asks for a custom quote on LinkedIn without underpricing your work or losing the lead to a rushed estimate that feels too high.
- HTML: https://getkinlead.com/handle-prospect-asking-for-custom-pricing
- Markdown: https://getkinlead.com/handle-prospect-asking-for-custom-pricing.md

**Short answer:** When a prospect asks for a custom quote on LinkedIn, don't send a number immediately. Use a qualifying response to learn their scale and specific needs first. That keeps you from underpricing the work or losing the lead to an estimate that feels too high for their actual problem.

## Why you shouldn't send a price immediately

Sending a number too early turns your service into a commodity. When you give a price without knowing the scope, the prospect stops looking at the value you provide and starts comparing your number to other vendors.

If you give a low estimate to be safe, you risk underpricing yourself as the scope grows. You'll either lose money on the project or have to explain a price increase later, which makes you look inexperienced.

A high estimate intended to cover all bases can scare off buyers who have a smaller, solvable problem that you could have handled profitably with a different package. The number is not wrong, but it answers a question you have not asked yet.

**The immediate number**

- It usually costs about the same as our other projects of this size.
- Our monthly retainer starts at our entry package.

**The qualifying response**

- I can put a quote together for you. To make sure it's accurate for your scale, I just need two details first.
- I'm happy to provide a quote. Since we tailor the price to the volume of work, could you tell me more about your current setup?

## The qualifying response framework

The goal of your first reply is to move the prospect from a price-shopping mindset to a problem-solving mindset. Acknowledge their request so they feel heard, then pivot the conversation toward the specifics of their business.

Explain why you aren't giving a number yet. By framing the delay as a way to ensure accuracy, you show that your pricing is based on actual needs rather than a random guess. Keep this short. A long explanation sounds like you are avoiding the question.

Ask two questions at most in the first reply. More than that feels like a form. The answers should tell you whether the deal is worth a proposal and what variables will drive the price.

- **them:** This looks interesting. Can you send over a custom quote for a 40-person agency?
- **you:** I can put a quote together for you, Sarah. To make sure the pricing is accurate and reflects your specific scale, I need two details first: how many users will need access, and what is the primary goal you want to hit in the first 90 days?
- **them:** We'll have 12 users. The main goal is to migrate our lead data from a legacy system without losing history.
- **you:** That helps a lot. Since migration is the priority, I'll put together a few options that include the data cleanup. I'll send that over shortly.

```
Hi {{first_name}}, I can put a quote together for you. To make it accurate for {{company}}, I need two details: how many people will use it, and what you want to fix in the first 90 days. Once I have those, I'll send a clear price and scope.
```

## Identifying the scale of the need

To price accurately, identify the variables that drive your costs or the value you create. If you price based on hours, you need to know the volume of work. If you price based on value, you need to know the cost of the problem they're solving.

Use a set of standard qualifying questions for every quote request. This ensures you don't forget a detail that could double the amount of work required. Write the answers in the same place you keep the deal, not in your head.

If the prospect cannot answer a question, offer examples. For instance, ask 'Do you need this for a team of five or a department of fifty?' That gives them a way to respond without guessing.

| | Dimension | What to ask | Why it matters |
| --- | --- | --- | --- |
| Volume | How many seats or assets are involved? | Determines the base cost and resource load. |
| Urgency | When does this need to be live? | Determines if a rush fee or priority scheduling is needed. |
| Complexity | What tools are you currently using? | Identifies if migration or integration work is required. |
| Success | What does a win look like in 3 months? | Allows you to price based on the value of the outcome. |

## Moving from the chat to a proposal

Once you have the answers, don't drop a number back into the LinkedIn chat. A formal proposal makes the price easier to discuss than a chat message. It also gives the prospect something to share with a boss or a partner.

Summarize their needs back to them first. This proves you listened and that the quote is custom, not a template. This makes the prospect less likely to haggle because the quote is tied to their specific goals.

Offer two or three options. A single price invites a yes or no. Two options invite a choice about scope. Keep the options easy to compare: same format, same terms, different levels of work.

1. **Summarize the scope.** Send a message saying, 'Based on our chat, you need a solution for 12 users with a focus on legacy data migration by next month.'
2. **Offer tiered options.** Create two or three distinct packages, such as Standard and Growth. This moves the decision from 'Yes or No' to 'Which one is better?'
3. **Deliver a formal document.** Send the quote as a PDF or a dedicated link. This separates the formal agreement from the casual nature of LinkedIn messaging.
4. **Request a walkthrough.** Ask for a 10-minute call to explain the options and answer questions, rather than letting them interpret the PDF alone.

> Avoid offering a discount in the first proposal. Instead, offer a smaller package that fits a lower budget.

## What to do when they push back on price

A pushback on price is not always a no. It can mean the prospect does not see the scope yet, or they expected a different kind of package. Your job is to find out which one it is before you change the number.

Ask which part of the scope they would remove to lower the price. This keeps the conversation on the work, not on your margin. If they want the same result for less, you can explain what changes.

If they need a smaller start, offer a smaller first step. A paid pilot or a single module can prove value without asking them to commit to the full scope. Do not cut the price on the same scope. That teaches them that your first number was not real.

- **them:** Thanks for the quote. It's higher than we expected. Is there any flexibility?
- **you:** I can work with your budget. Which part is less urgent: the migration itself or the reporting after it?
- **them:** The reporting can wait until next quarter.
- **you:** Then I can remove reporting from this phase and send a revised scope. The migration and cleanup stay the same. Does that fit what you need now?

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe and scores each lead from 0 to 100. Leads below the fit line are not kept. That means you spend your qualifying questions on people who look like your actual buyers.

You can set a campaign to hand the conversation to you at the first reply, so you handle every quote request yourself. Replies from every campaign land in one [unified inbox](/features/unified-inbox), classified by intent, with interested replies first. You get an email when someone replies.

If you want the AI to handle early replies, you can let it reply until there is real interest. Use hand-off mode when the next message is likely to be about price.

## Related

- [Playbook for managing replies](https://getkinlead.com/playbook-for-managing-linkedin-sales-replies.md)
- [Outbound for founders](https://getkinlead.com/use-cases/outbound-for-founders.md)
- [Booking LinkedIn demos](https://getkinlead.com/use-cases/book-linkedin-demos.md)

## Common questions

**What if they insist on a price before answering my questions?**

Give a broad range and explain that the final price depends on the variables you asked about. Say, 'Projects like this usually fall in a range, but I can give you a firm number once I know your user count.'

**Should I offer a discount if they are a large company?**

No. Large companies often have larger budgets but more complex requirements. Instead of discounting, offer a volume-based tier that provides more value for their scale.

**How do I handle a prospect who says the quote is too high?**

Ask which part of the scope they're willing to remove to lower the price. This reinforces that the price is tied to the work, not a random number you can just lower.

**Should I send the quote in a LinkedIn message or a separate document?**

Send a short summary in the chat and the full quote as a document. The chat keeps the conversation moving, and the document gives them something to review and share.

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