# How to respond to questions about SOC2 or security certifications
> Answer SOC2 and security certification questions on LinkedIn with a clear yes or no, qualify the blocker, and decide when to send documents early.
- HTML: https://getkinlead.com/handle-prospect-asking-about-security-certs
- Markdown: https://getkinlead.com/handle-prospect-asking-about-security-certs.md

**Short answer:** Give a direct yes or no immediately when a prospect asks for SOC2 on LinkedIn. If you don't have it, explain your current security measures. Don't send full documentation until you've confirmed the product is a fit to avoid wasting time on leads that won't buy regardless of compliance.

## Answer the question before you send anything

Security questions arrive early in a LinkedIn thread. A prospect asks if you have SOC2 Type II, and the temptation is to attach a PDF or drop a link to your trust center in the first reply. That move changes the conversation from the problem you solve to a legal review. The prospect forwards the report to someone in security, and you wait on a review for a tool the prospect may not want yet.

A better first reply does two jobs. It answers the specific question, and it keeps the business conversation alive. If you have the certification, say yes. If you don't, say what you have. Then ask a question that tells you whether the security requirement is a formality or a hard blocker.

The answer should be short enough to read on a phone. One or two sentences for the compliance answer, one sentence that returns to the workflow or the outcome the prospect mentioned. Don't write a security essay in a LinkedIn message.

**Weak first reply**

- Sending the SOC2 report as an attachment in the first message.
- Writing 'we take security seriously' and linking to a generic security page.
- Asking the prospect to fill out a security questionnaire before you know they are a buyer.

**Strong first reply**

- Answering the certification question in one sentence.
- Naming the current control or audit status without apology.
- Asking whether the requirement blocks a first call or a security overview is enough.

## If you have SOC2, say yes and keep the deal moving

A clear yes is enough. 'Yes, we have SOC2 Type II. I can send the report and the security package after we confirm the product fits your workflow.' That reply gives the prospect confidence and sets a reasonable next step. It also avoids turning the report into a lead magnet.

Some buyers will ask for the report before any call. Treat that as a signal about their process. If the account is large and the use case is clear, send the report and ask for a short call after their security team reviews it. If the account is small and the buyer won't discuss the problem, the security request may be a polite way to end the conversation. Let it end.

Don't promise a report you can't send. If your report is under NDA, say that. If the report covers a different scope, say that. The goal is accuracy. Sounding impressive comes second.

- **them:** Do you have SOC2 Type II?
- **you:** Yes, we have SOC2 Type II. I can send the report and our security package once we confirm the platform fits your workflow. Is reducing manual data entry still a priority for your team this quarter?
- **them:** It is. Send the report and we can book a call after our security lead reviews it.
- **you:** Will do. I will send the report today and hold a slot Thursday. If your security lead has a specific control question, send it over and I will get a direct answer from our CTO.

## If you don't have SOC2, be direct about what you do have

Never claim a certification you don't hold. A false answer will surface in a security review, and it can end the deal and the relationship. The same rule applies to audit dates. If the audit is booked, say when. If it isn't booked, don't imply it is.

A company can follow the SOC2 framework or hold other controls before it pays for a formal audit. Say which parts you have: access reviews, encryption at rest, logging, a written incident response plan, a subprocessor list, or a completed security questionnaire. Then ask whether that evidence is enough for the next step.

The prospect may need SOC2 for a procurement rule. That is a real constraint. Your job is to find out whether the rule blocks a first call or only blocks a signed contract. Those are different problems, and they need different answers.

1. **State the status in one line.** Example: We don't have SOC2 Type II yet. We follow the SOC2 framework and can share our security overview.
2. **Name the evidence you can send.** List the documents you actually have, such as a security whitepaper, a completed SIG questionnaire, or a subprocessor list.
3. **Ask what the prospect needs for the next step.** Ask whether they need the certification for a first call, a pilot, or a signed contract. The answer changes your next move.
4. **Offer a technical call when the questions get specific.** A 20 minute call with your CTO or security lead can answer control questions faster than a long message thread.

> Use this reply when you lack the certification: We don't have SOC2 Type II yet. We follow the SOC2 framework and can share our security overview, subprocessor list, and a completed questionnaire. Is that enough for a first call, or does your process require the certification before we talk?

## Tell a formality from a hard blocker

Security questions range from a box a buyer checks to a rule a security team enforces. The language and timing tell you which one you face. A vague question in the first message often means the buyer wants to know you aren't a risk. A named review board, a vendor approval deadline, or a refusal to take a call before documents are reviewed means you face a process.

Don't spend a week on a security package for a prospect who won't describe the problem. Ask one qualifying question: 'Is the certification required for a first call, or can we talk while your team reviews the security overview?' The answer tells you where to spend your time.

If the blocker is real, ask for the steps and the owner. 'Who reviews the report, and what do they need to see?' That question turns a vague security concern into a checklist you can meet.

| | Signal | Looks like a formality | Looks like a hard blocker |
| --- | --- | --- | --- |
| Language | Asks if you have any certifications | Names a security review board or vendor risk team |
| Timing | Asks in the first two messages | Won't book a call until documents are reviewed |
| Scope | Wants a general security overview | Sends a questionnaire with a deadline and a named owner |
| Next step | Accepts a call while the review runs | Requires the report before any conversation |

## What to send, when to send it, and what to write

Keep a small security pack ready. A one page overview, a subprocessor list, a completed standard questionnaire, and the SOC2 report if you have one. Store them in a folder you can reach during a LinkedIn conversation. The pack should answer the common questions without a custom email for each prospect.

Send the pack after you know the prospect's problem and the security requirement. If the prospect asks for the report before a call, send it with a note that names the next step. 'Here is the report. I will follow up Thursday to see if your security lead has questions.' That note keeps the thread alive without pressuring the buyer.

Write the message in plain language. Don't use legal terms you can't explain. If a prospect asks about data residency, answer with the regions you use. If they ask about encryption, say how you encrypt data at rest and in transit. If you don't know, say you will ask your CTO and come back with an answer.

```
Subject: SOC2 report for [Company]

Hi [Name],

You asked about SOC2. We have [SOC2 Type II / a security overview that follows the SOC2 framework]. I attached [report / overview] and included our subprocessor list.

One question so I can point your security lead to the right section: is the certification required for a first call, or can we talk while your team reviews the documents?

[Your name]
```

## Doing this with Kinlead

Put your SOC2 answers, the security overview offer, and the qualifying question into a sales playbook in Kinlead. The AI writes replies from that playbook when a prospect asks about compliance, so the first response follows the same script.

Security replies need a person when the question is specific to your controls. Set the campaign to hand the conversation to you at the first reply. You then answer the security question yourself and keep control of the thread.

Kinlead sends from your LinkedIn account at one action every five minutes, inside the daily limits and send window you set. That pace leaves room for the security conversations that need a careful answer. You can see the campaign setup in [AI LinkedIn outreach](/features/ai-linkedin-outreach) and book a walkthrough at [book a demo](/demo).

## Related

- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**Is it unprofessional to withhold the SOC2 report until after a demo?**

No. It's reasonable to confirm business fit before a formal security review. A review can take time from your team.

**What if the prospect insists on the report before a meeting?**

If the account is large enough to justify it, send the report and ask for a call after their security team reviews it. If the account is small, say you can provide it once you have confirmed the product solves their problem.

**Should I mention my security roadmap if I'm not compliant yet?**

Yes, if you have a scheduled audit date. It shows the company is taking security seriously and gives the buyer a concrete timeline.

**What if the prospect asks for a SOC2 report in the first message?**

Answer the question and ask whether the report is required for a first call. Send the report if the account is large enough to justify it, and keep the next step in the same message.

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