Someone replies to your product post with “interesting.” You have their attention, but you do not yet know what they want. Sending a demo link, a pricing page and a meeting invitation at once asks them to make a much bigger decision than their comment expressed.
A useful follow-up starts with the actual request. Answer what was asked, resolve one uncertainty and make the next step easy to accept or decline. This guide offers a practical method for that moment between a friendly response and a concrete product conversation.
The examples below are fictional. They illustrate wording and decisions, not customer results or a sequence proven to convert.
- How to distinguish curiosity from a specific request
- How to offer one relevant next step without creating extra work
- How to track a promise and close the conversation cleanly
01Read the signal before choosing the action
Different comments call for different responses. Treat the words as evidence of the person's current interest, not as a stage you can automatically advance.
- Acknowledgment: “Nice work” may simply deserve a thank-you.
- Curiosity: “How does this work?” calls for a clear explanation.
- Fit question: “Can this handle two workspaces?” needs a factual answer and any relevant limitation.
- Specific request: “Could you send an example?” gives you a concrete thing to deliver.
Read the surrounding exchange before responding. A short comment may refer to the design, a technical detail or the problem itself rather than an intention to use your product. The guide to SaaS buying intent helps separate these signals without inventing urgency or budget.
02Answer before asking for another commitment
If someone asks a factual question, answer it directly before suggesting a call. Making them book time to learn a basic limitation adds unnecessary work.
Imagine a fictional founder asking about an analytics product:
“Can I combine two workspaces into one report?”
If the product cannot do that, a useful answer would be:
“Not in a single report at the moment. Each workspace has its own view. If a combined report is essential, our current setup probably won't fit.”
This answer gives the person enough information to decide. It does not promise a roadmap item or describe an unsupported workaround. Verify the capability before writing it, including when a draft suggests a confident answer.
When you need clarification, ask the one question that would change your recommendation. Avoid collecting company size, budget and timeline before you know whether the product solves the stated problem.
03Choose one next step that matches the uncertainty
Choose the smallest action that can answer the remaining question. Different uncertainties need different material:
- “I don't understand the workflow.” Offer a short example showing the relevant step.
- “Will it fit my setup?” Point to the exact requirement or limitation that matters.
- “What does the output look like?” Share a representative sample with sensitive details removed.
- “How do I start?” Give the current starting link and explain what happens next.
Do not attach every resource you have. A collection of links makes the recipient decide which one answers their question. Select one and describe why it is relevant.
For example: “I can share a short sample showing how the workspace summary looks. Would that help?” This is an offer the person can evaluate without committing to a meeting.
04Keep the channel and promise explicit
If the answer is short and suitable for public discussion, keep it in the thread. Other readers can understand the exchange, and the original author does not need to open another conversation.
If the person asks for a private follow-up, keep it focused on the item they requested. A request for one example is not an invitation to start an ongoing promotional sequence.
Compare these fictional responses to “I'd like to see an example”:
“Great, book a demo and I'll walk you through everything.”
“Sure. Here's a sample of the weekly summary, using fictional data. The second section shows the comparison you asked about.”
The second response delivers the requested thing and tells the person where to look. If you need time to prepare it, say what you will send and when you realistically expect to have it. Then record the promise.
05Track the open question, not a label like hot lead
A small note is enough: source conversation, stated question, material requested, what you promised and whether you delivered it. Record an agreed follow-up date only when one exists.
Keep assumptions separate. “Asked for a sample” is observable. “Ready to buy” is an interpretation. This distinction helps your next message stay relevant instead of sounding as though you are continuing a sales conversation the other person never agreed to.
Check that the delivered link works and shows the intended example. Review any generated wording for invented features or outcomes using the AI reply review checklist.
06Let delivery be a complete outcome
After answering the question or sending the requested material, you do not always need another message. Silence does not tell you why someone stopped replying, and it does not create a new obligation for them.
If you agreed to check back, follow that agreement. If you discover a material correction, share it plainly. Otherwise, avoid repeatedly asking whether they saw the link. When there is a useful reason to return later, follow the conversation re-entry guide rather than repeating the original pitch.
For your next product conversation, write down the exact request before drafting. Choose one answer and, only if needed, one optional next step. If you use Replivio to prepare the reply, review it against that request before posting. A good follow-up makes the decision clearer, including when the answer is no.
07Frequently asked questions
Does an interested comment justify sending a demo link?
Not automatically. First identify what the person is interested in. Answer a specific question directly, and offer a demo only when it would help resolve the uncertainty they expressed.
How soon should I follow up after sharing an example?
Use an agreed timing if there is one. Without an agreement or new information to add, delivery can be the end of the exchange. There is no universal follow-up interval in this method.
What should I do when my product does not fit?
State the relevant limitation clearly. Do not invent a workaround or promise a future feature. A direct answer lets the other person decide without spending more time on an unsuitable option.
