# How to handle requests to see your software UI
> How to answer a LinkedIn prospect who asks for screenshots or a deck: send less, ask one qualifying question, and move the request to a short live walk-through.
- HTML: https://getkinlead.com/handle-prospects-who-ask-to-see-ui
- Markdown: https://getkinlead.com/handle-prospects-who-ask-to-see-ui.md

**Short answer:** When a prospect asks for screenshots, they are usually trying to check whether your product is real and whether it fits before they spend time on a call. A static image cannot answer their questions, and it gives them room to disqualify you without a conversation. Reply by offering a short live walk-through of the one workflow they mentioned, then give two specific times.

## Why screenshots stall the conversation

Most screenshot requests are not really about screenshots. The prospect wants to know whether your product is real, whether it looks usable, and whether it is worth an hour of their week. A static image can answer the first question and nothing else.

When you send a screenshot, you hand over the conversation. The prospect looks at one screen and fills in the missing context themselves. If they do not understand a button or a layout choice in three seconds, they may decide the tool is too complex for their team. You never hear the objection.

Screenshots also travel without you. The prospect forwards the image to a colleague who did not see your message, and that colleague makes a call based on a crop of your product. A live walk-through keeps the questions in the room. It lets you show the one view that matches their workflow and ask whether the screen matches how they work today.

**Sending images**

- Prospect views a generic dashboard.
- Prospect decides it looks too cluttered.
- Conversation ends without a call.

**Live walk-through**

- You show the one screen that solves their main pain.
- You answer a question about a feature instantly.
- You guide them toward a booking.

## How to read the request before you answer

Not every request for visuals means the same thing. A founder asking for a deck is often preparing for a partner review. A manager asking for screenshots may be comparing three tools before they book anything. The reply should match the reason behind the request.

If you treat every request as a demand for a full media kit, you spend time building assets for people who are not ready. If you refuse every request, you look like you have something to hide. Read the request, name the likely reason, and answer with the smallest useful next step.

| | Request | What it usually means | What to send back |
| --- | --- | --- | --- |
| Can you send screenshots? | They want proof the product is real before they book. | One screen of the workflow they named, then two times for a 10 minute walk-through. |
| Can you send a deck? | They need something to share with a manager or a partner. | Ask who will review it. Offer to walk that person through the two or three slides that matter. |
| Can you show me the product? | They are open to a call but have not said what they want to see. | Ask which workflow matters most, then offer a short call around that workflow. |
| Can you send a video? | They do not want a live call yet, or they want to review on their own time. | Send a short clip that answers one question, then ask one question that earns the call. |

## The reply that turns a screenshot request into a short call

Do not start with why you cannot send screenshots. Agree with the request, then explain what a static image leaves out. Keep the reason specific to their workflow: the dashboard changes by role, the report changes by data source, the view changes by pipeline stage. A generic line about your product being hard to show in screenshots sounds like an excuse.

Ask for ten minutes, not thirty. A ten minute tour feels like a small favor. A thirty minute demo feels like a sales meeting. Give two named times and ask one question about the workflow so the call has a purpose.

- **them:** Looks interesting. Do you have screenshots or a deck I can look at first?
- **you:** I can show you the UI. Since the dashboard changes based on the leads you target, a screenshot would show a generic view. I can walk you through the view for your team in 10 minutes. Does Tuesday at 2 or Wednesday at 10 work?
- **them:** Tuesday at 2 works. We mainly want to see how you handle reporting.
- **you:** Good. I will keep it to the reporting view and one filter example. If it is not a fit, you will know in 10 minutes.

> Do not say you cannot send screenshots. Say the live view is easier for them to judge.

```
I can definitely do that. Because the UI adapts to the [industry/role] workflow you use, a static image does not show the part that matters. I can give you a 10 minute tour of the specific views you would use. Would [day] at [time] or [day] at [time] work better?
```

## What to show in ten minutes

Ten minutes is enough if you prepare. Do not open with company history or a slide. Ask the prospect to describe the task they want to complete, then show only the screens that touch that task. If they ask about a feature outside the path, answer it and return to the main workflow.

Keep one tab open with their LinkedIn profile or website if you have it. Use their words: 'You said your team loses track of follow-ups. This is the view where that handoff happens.' That is more convincing than a tour of every menu.

1. **Confirm the workflow.** Ask one question: what do you want to be able to do after this call? Write their answer down and use it as the agenda.
2. **Show the starting point.** Open the screen where their work begins. If they import leads, show the import. If they track replies, show the inbox. Skip the settings.
3. **Show one decision.** Walk through one filter, one report or one handoff. Pause after each click and ask whether that matches how their team works.
4. **Close on the next step.** If the fit is clear, ask what needs to happen to move forward. If it is not, say so. A short call that ends honestly is better than a long call that ends with a maybe.

## When they insist on images anyway

Some prospects will insist on seeing images before they agree to a call. They are usually protecting their calendar or gathering proof for someone else. If you refuse entirely, you look suspicious. If you send everything, you lose control of the conversation and the reason for the call.

The middle path is a limited sample. Send one screen tied to the problem they named, not a generic dashboard. Then ask a qualifying question and tie the answer back to the walk-through. The sample proves the product exists. The question gives you a reason to keep talking.

1. **Send a limited sample.** Send one screen or a short clip of the result they asked about. Do not send a folder of images.
2. **Ask a qualifying question.** Ask what they are trying to fix or compare. The answer tells you which view to show live.
3. **Tie the sample to the call.** Explain that the sample is one view and the live call will show how it works with their data.
4. **Set the boundary.** Say the full UI is easier to judge in context. Do not apologize for not sending everything.

- **them:** Just send the screenshots. I will review them with my team.
- **you:** I can send one view. So I send the right one, are you trying to fix lead routing or reporting for your manager?
- **them:** Reporting.
- **you:** Here is the report view. The filter setup is where most teams get stuck, so I can show that part in 10 minutes tomorrow at 10 or Thursday at 2.
- **them:** Send the invite for tomorrow.

## Doing this with Kinlead

Kinlead finds LinkedIn leads that 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 the screenshot request you handle is more likely to come from someone who fits.

The Steal Customers agent watches competitor company pages and optional founder or employee profiles, reads comments on their 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.

Outreach runs from your own LinkedIn account through Unipile at a human pace. When someone replies, the reply lands in the [unified inbox](/features/unified-inbox) and you get an email. You can handle the UI request there and book the call yourself.

## Related

- [AI outreach for founders](https://getkinlead.com/ai-outreach-for-founder-led-sales.md)
- [Book LinkedIn demos](https://getkinlead.com/use-cases/book-linkedin-demos.md)
- [Lead scoring examples](https://getkinlead.com/ai-lead-scoring-fit-line-examples.md)

## Common questions

**Is it ever okay to send a PDF deck with screenshots?**

Yes, when the prospect needs something for an internal review and you know who will read it. Keep it short, label it as a summary, and offer to walk the reviewer through the live product.

**How do I handle prospects who say they are too busy for a call?**

Offer a short personalized video that answers one question, not a generic tour. Use their own profile or website in the first frame so they know it is for them, then ask for ten minutes to show the rest.

**Should I record a generic demo video instead of a live call?**

Generic videos get skimmed and rarely answer the objection in front of the prospect. Use short clips for one question, and treat the clip as a bridge to a live conversation.

**What if they ask for screenshots in the first message?**

Treat it as early interest, not a commitment. Send one relevant screen if you have it, ask what they are comparing, and offer a ten minute walk-through of that workflow.

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