Write the message you’d actually send

Read the opening before writing the pitch

Imagine you sell software that helps B2B companies reuse approved answers to security questionnaires. You publish a post about how those reviews can interrupt a product team’s week.

Daniel, a CTO you already know on LinkedIn, leaves this comment:

We have a folder called “final answers”. There are eight versions.

The business, person and conversation in this guide are fictional.

It is a recognisable problem and a natural opening. What you still do not know is how much it matters to Daniel, who handles it and whether his team is looking for a different process.

That is what the next message should help you learn. If you have not checked the person’s fit, review the profile and company first.

Continue where the relationship makes sense

A public comment can stay a public conversation. You do not have to move every exchange into an inbox. A direct message can be useful when there is already a connection and you want to ask something more specific.

In this example, you and Daniel are already connected. You have enough context for a short DM. If you were strangers, you could ask the same question under his comment and let him decide whether to continue.

Email makes sense when it is already an appropriate channel between you. An introduction needs a real mutual relationship. The channel should follow the situation; the fact that a tool can send a message somewhere does not make it the right place.

Ask something easy to answer

Possible LinkedIn DM

Hey Daniel, who ends up sorting through those answers when a deal is waiting?

The message connects directly to his comment. It asks about one part of the process. Daniel can answer in a sentence, and his answer will tell you something useful.

There is no need to open with a paragraph about his impressive background or ask for a call immediately. Read the message aloud. If it sounds like a campaign, simplify it until it sounds like a person picking up a conversation.

A public reply could be even shorter:

Possible reply under the post

Who has to find the right version when sales needs an answer?

Choose the version that fits your relationship and your normal voice. The point is the question, not a formula that every prospect should receive.

Use the answer to decide what comes next

Suppose Daniel replies: “Usually me. Sales pings me, I find the answer, then we do it again for the next customer.” You now understand who does the work and that it is recurring.

If your product actually addresses that process, you can explain the connection directly:

Possible follow-up when the product fits

That’s what we’re working on: sales can reuse the answers engineering has already approved. Want me to send you a quick example?

The security-questionnaire product is illustrative; this is not a Camus feature claim.

If Daniel says they have already fixed the process, accept the answer. If he asks how your product works, answer that question. A useful exchange follows what the person says, rather than forcing them through a predetermined sequence.

A relevant example may earn a meeting. A reply alone does not establish a sales opportunity.

Keep enough context for the next conversation

Record the original comment, what the person confirmed, what remains unknown and the action you agreed on. If a colleague takes over, they should understand the exchange without asking the prospect to repeat it.

If there is no response, leave the outcome as no response. Silence does not tell you whether the problem matters or whether the person has budget. Any follow-up should add a useful detail connected to the conversation.

A practical final check before sending: can you explain why this person, why this message and why this channel? If one of those answers is vague, improve the context first.