How to ask a prospect for a workflow recording on LinkedIn
Ask a prospect to record their workflow before a demo so you can see real friction points and build a sales presentation around their actual process.
Get startedShort answer
Ask prospects for a workflow recording after they agree to a meeting but before you finalize the invite. You see actual friction points instead of relying on their memory. The demo can focus on the steps that cause them trouble.
Why a workflow recording beats a discovery call
A discovery call depends on what the prospect remembers at that moment. People forget the small repeated steps that annoy them, and they often describe their process as cleaner than it is. You end up building a demo around the version they wish they had.
A short screen recording shows the actual clicks, errors, and workarounds. If the prospect copies a value from one tab to another, that is a concrete problem you can solve. You do not have to ask whether the process is tedious. You can see where it breaks.
The recording also filters for intent. Someone who will spend five minutes showing you their workflow has a real reason to talk. Someone who will not may still be worth a call, but you should treat that call as early discovery, not a demo. That difference matters when you have limited time and a full calendar.
Standard discovery
- Asking 'What are your main pain points?'
- Spending 20 minutes of a call explaining features they might not need
- Relying on the prospect to remember every step of their process
Workflow recording
- Seeing exactly where the prospect hesitates or clicks the wrong button
- Preparing a demo that only shows the two features that solve their specific gap
- Filtering for people who are willing to invest five minutes in a video
When to make the request
Do not ask in the first message. A request for a video before you have established a problem feels like homework. The prospect has no reason to believe the recording will change the call.
Ask after they agree to a meeting but before you send the calendar invite. At that point they have said yes to a conversation. The recording becomes the agenda for that conversation. You are not adding a hurdle. You are replacing a vague discovery call with a specific one.
If you use a scheduling link, put the request in the same message as the link. Do not send the link first and the request later. The prospect will book the call and ignore the follow-up. If they book before you ask, send the request right after the booking confirmation and explain that it will make the call more useful.
- 1
Establish the pain
Exchange two or three messages to confirm the specific part of their workflow that is broken.
- 2
Confirm the fit
Explain how your product solves that specific problem so they know the recording is worth their time.
- 3
Request the video
Ask for the recording immediately after they say yes to a call to make the meeting more efficient.
- 4
Send the invite
Send the calendar link once the request is made and mention you will review the video before the call.
The exact script to use
Keep the request small and specific. Name the process you want to see. Give a time limit. Mention the tool if it helps them move faster. Do not ask for a polished walkthrough. A raw clip is better because it shows the real steps.
Make the recording about their time, not your sales process. The prospect should understand that five minutes now saves them from a generic demo later. If they think the video is for your benefit only, they will put it off.
Write the request in the same tone as the rest of the conversation. If you have been direct, stay direct. If you have been casual, stay casual. A sudden formal paragraph about a video will read like a template.
Paste this job
I want our call to focus on the part of [Process Name] that causes the most friction. If you have 5 minutes, could you record a quick Loom of that process? A raw clip is fine. I will review it beforehand so I can show you exactly how we handle those steps during our call.
Handling common objections
The most common objection is time. The second is sensitive data. Both are reasonable. Your job is to lower the effort, not to argue.
If they say they are too busy, offer a smaller ask. A two-minute clip of one screen is enough. If they worry about client data, tell them to use a test account, blur the data, or skip that screen. You only need the steps.
If they still say no, move on. Do not make the recording a condition of the meeting. Use the call to ask the questions they would have answered in the video. You can ask again after the call if the demo depends on seeing the workflow. Some prospects need to meet you before they will share their screen.
Example
- Prospect
I'm not sure I have time to put together a recording right now.
- You
No need to put anything together. A raw, unedited two-minute clip of you just clicking through the process is actually better than a polished one. It helps me see the real friction.
- Prospect
I'm worried about showing sensitive client data in the video.
- You
Totally understand. Feel free to blur that data, use a test account, or just skip that specific screen. I only need to see the workflow steps.
How to analyze the recording for the demo
Watch the recording once without pausing. Then watch it again with a notebook. You are looking for hesitation, repeated actions, and moments where the prospect complains out loud.
Map each moment to a feature. Do not map every feature you have. Pick the two or three that remove the exact steps you saw. If the prospect sighed while waiting for a page to load, show the part of your product that removes that wait. If they copied a value between screens, show the automation.
Build a short demo outline before the call. Start with the moment that caused the most friction. Then show the fix. Then ask how that compares to their current process. Keep the rest of the demo in reserve. A demo that follows the recording feels like a response to their situation. Keep the product tour for another call.
If the recording is long, use timestamps. Write down the minute and second of each friction point. That makes it easy to return to the exact moment during the call. It also helps if a teammate joins and needs context.
- 1
Spot the hesitation
Identify dead air where the prospect pauses or looks for a button. This shows a confusing interface or a missing feature.
- 2
Track the manual work
Note every instance of manual data entry, copy-pasting, or switching between browser tabs.
- 3
Listen for frustration
Listen for sighs, comments of annoyance, or mentions of the old way of doing things.
- 4
Build the map
List these moments and match them directly to the features in your product that eliminate those steps.
They pause before clicking a button
- What you see
- The label is unclear or the next step is hidden
- What it means
- The screen that makes that step obvious
They copy a value into another tab
- What you see
- The systems do not talk to each other
- What it means
- The integration or import that removes the copy
They sigh when a page loads
- What you see
- The wait is a daily cost
- What it means
- The part of your product that shortens the wait
They mention a workaround they built
- What you see
- They have already invested time in a fix
- What it means
- The feature that replaces the workaround without losing their data
Do not praise the current process. Acknowledge the effort it takes to keep it running, then show the shorter path.
What to send after the call
Send a short follow-up within a day. Reference the exact moment from the recording. Attach a link to the part of the demo that addressed it. Do not send a generic recap.
If the prospect did not record a video, use the call notes instead. Write down the steps they described and repeat them back in the follow-up. This shows you listened even without the recording.
If the call went well, ask for the recording again for the next step. A technical review or a stakeholder call often needs the same context. The second ask is easier because they already know you. Keep the request just as small as the first one.
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. That means you ask for a workflow recording only from people who look like the buyers you want.
The Steal Customers agent watches competitor company pages and optional founder or employee profiles, reads the 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. You can use that context in your first message and in the follow-up that asks for the recording.
Messages and follow-ups are written by AI from the campaign's goal, tone, and an optional sales playbook, which is your own sales script. You can put the workflow request script in that playbook. Replies from every campaign land in one inbox, classified by intent, with interested replies first. You can hand the conversation to yourself at the first reply, so you take over once the prospect responds.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to ask a prospect for a workflow recording on LinkedIn.md