# How to respond when a prospect asks for your website
> Send the link, point at the part that matters, and ask one question that keeps the conversation in the chat. A practical reply formula for LinkedIn.
- HTML: https://getkinlead.com/reply-to-prospect-asks-for-website-link
- Markdown: https://getkinlead.com/reply-to-prospect-asks-for-website-link.md

**Short answer:** Send the link with one line that points at the part worth reading, then ask one question about how they work today. The question keeps the conversation in the chat and tells you whether they're a buyer or just browsing.

## Why the link ends conversations

A prospect who asks for your website on LinkedIn is often being polite. The request costs them nothing and gives them a clean way out of the chat. Reply with a bare URL and you're waiting on someone who has already moved on to their inbox.

Some do want to read. They want to check you're a real company, see the pricing, or forward the link to a colleague. That's a good sign, and it still doesn't mean they'll come back to the chat. People read a site, form a private opinion, and then decide whether to reply. If the answer is no, you never find out why.

There's a second problem: context. They land on a homepage written for everyone and have to work out whether any of it applies to them. They might read one line they disagree with, get pulled into a meeting, and never come back.

The site supports the sale, and the chat is where the sale happens. Send the link as a step toward a call, then ask something only they can answer.

**The passive reply**

- Sure, here is our site: acme.com
- You can find everything you need here: acme.com
- Check out our homepage for more details: acme.com

**The reply that keeps the thread**

- Here it is: acme.com. While you're on it, are you handling reporting in a tool today or in spreadsheets?
- Here you go: acme.com. I noticed you're at Northwind, are you looking at this for the whole team or just your group?
- Happy to share: acme.com. The second tab has the sample report. Is that the kind of output you're missing right now?

## The reply formula: link, frame, question

Every reply to a website request has three parts: the link, one line that frames what they'll see, and one question about how they work today.

The framing line does most of the work. Instead of dropping a homepage, point at the part you were just talking about. 'The pricing page has the plans, and the Northwind case study is the closest match to your team' takes ten seconds and makes the visit useful.

Then ask. The question should be answerable in one sentence from memory, without opening your site. If they have to research before answering, they'll postpone it and you've lost the thread.

Keep the whole reply under four lines. Long messages read like a pitch and get skimmed, and the question at the end is the first thing to go.

- **them:** This sounds interesting. Can you send over your website?
- **you:** Here it is: acme.com. The pricing page has the plans, and the case study on the second tab is a 40-person agency with a setup close to yours. While you're on it, are you doing this in a tool today or in spreadsheets?
- **them:** Spreadsheets, mostly. Two people own it.
- **you:** That's usually where the reporting breaks first. Which part eats the most time, pulling the numbers or checking them?

## Choosing the question that sorts buyers from browsers

Vague questions put the work on the prospect. 'Let me know what you think' asks them to invent feedback. 'Any questions?' asks them to find the gap in a product they learned about ninety seconds ago.

Good questions are about their process, their team or their timing. Pick the one that separates a buyer from a browser for your product. If your deals hinge on who owns the budget, ask who else is involved. If they hinge on a current tool, ask what they use today. If they hinge on a deadline, ask what's driving the timing.

Ask one question per message. Two questions let them answer the easier one and skip the other, and you'll never know which one they dodged.

Write it so a stranger could answer without knowing your product. 'Are you running this in house or through an agency?' works. 'How do you handle attribution today?' only works if they already speak your vocabulary.

| | Avoid this (too vague) | Use this (specific) |
| --- | --- | --- |
| General interest | Do you have any questions after looking? | Are you trying to fix the reporting gap or just comparing options? |
| Team and ownership | Let me know what you think of the site. | I noticed you're at Northwind, are you handling this for the whole team or just your group? |
| Current setup | Does this look like a fit? | Are you using a tool for this today or a manual workaround? |
| Timing | When would you want to start? | Is this something you need this quarter, or further out? |

## Which page to send

Send the page that matches the conversation. If they asked about price, send pricing. If they asked how it works with their CRM, send the integrations page. Use the homepage only when nothing more specific fits.

When nothing specific exists, send the homepage and name the section to read: 'the three steps under How it works.' A named section is easier to act on than a whole site, and it tells you what they cared about if they mention it later.

One link per message. Three links look like a newsletter and get skimmed. If you have a case study and a pricing page, pick the one that answers the question they actually asked.

If your site is thin, or you're a one-person shop, say so and send the most concrete thing you have: a sample report, a screenshot of the dashboard, a public case study. 'The site is mostly a landing page, here's the sample output instead' beats a homepage that says nothing.

> Send one link and name the part to read. A prospect who knows where to look comes back with a real question instead of a polite no.

## Handling 'I'll check it out and get back to you'

Most people who say this are being polite rather than deciding. What you do next decides whether it becomes a call or a lead that sits in your pipeline for six weeks.

Agree, then put a day on it. 'Makes sense, I'll check in Thursday' is a small commitment they can accept without effort, and it gives you a reason to message that isn't a chase.

Add one question about timing. Whether they're solving this now or planning for next quarter changes how you follow up and whether they belong in the sequence at all.

If they answer with something vague, like 'probably next quarter', write it down and move them out of the active list. You'll want the detail when the quarter starts, and chasing in between burns the contact.

1. **Agree without arguing.** Confirm it's fine for them to read the site first. Fighting the request makes you sound like you have something to hide.
2. **Name the day.** Say exactly when you'll come back, using a weekday. 'I'll check in Thursday' is a commitment. 'I'll follow up soon' is noise.
3. **Ask about timing.** One question about whether this is current or later. Their answer decides whether you keep them warm or park them.

> Never write 'I'll follow up soon'. Name the day, then show up on it.

## When they go quiet after the link

Some people who ask for your site won't reply after you send it. That's normal. Usually the question was too easy to skip, or the week got away from them.

On the day you promised, send one short message that adds something. Don't ask whether they had a chance to look. Reference what you sent and give them a reason to answer: a detail that matches their setup, a company like theirs, a specific question about their process.

If that gets nothing, send one more a week later and stop. Two follow-ups after the link is enough for a cold conversation, and a third reads as pressure.

If they reply late, after you've stopped, answer as if no time passed. No 'circling back' and no comment on the delay. Pick up the question you asked and carry on.

```
Thursday follow-up, after sending the link

Hi Sam, the pricing page I sent has the three plans on it. The middle one is what most 40-person teams pick, because it includes the reporting you mentioned.

Quick one: is the reporting piece something you need this quarter, or is it further out?
```

## Doing this with Kinlead

Kinlead writes campaign messages and follow-ups from the campaign's goal, tone and an optional sales playbook, which is your own script. Put your link reply and your qualifying questions in the playbook and the AI will use them.

If you'd rather handle the link and the question yourself, set the campaign to hand replies to you at the first reply. Replies from every campaign land in one inbox, classified by intent, with interested ones first, and you get an email when someone replies.

Outreach runs from your own LinkedIn account at a human pace, one action every five minutes inside the daily limits and send window you set. Queued messages can be read and edited on the Actions page before they send.

## Related

- [AI sales playbook](https://getkinlead.com/ai-sales-playbook-for-linkedin-outreach.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)
- [Campaign send windows](https://getkinlead.com/features/campaigns-and-send-windows.md)
- [LinkedIn message scripts](https://getkinlead.com/ai-sales-script-for-linkedin-messages.md)

## Common questions

**Should I send a landing page or the homepage?**

Send the page that matches the problem you discussed in the chat. A specific page reduces the reading and shows you were listening. The homepage is the fallback when nothing else fits.

**What if they ask for a deck instead of a website?**

Treat a deck the same way. Send it, name the slide worth reading, and ask one question about their setup. The deck shouldn't be the last message in the thread.

**How long should I wait before following up?**

Follow up on the day you named. If you never named one, wait two or three business days, then send one message that adds something rather than asking whether they looked.

**What if they ask for the site in the first message, before I've said anything?**

Send it and ask a question in the same reply. A cold request usually means they want to check you're real, so give the link, one line about what you do, and a question about their current process.

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