A useful public reply does not create an obligation for the buyer to continue. Follow-up should be earned by the next visible signal: a question, a request for detail, an invitation to move channels, or new information that materially changes the answer. Silence, a polite acknowledgment, or a closed decision are stopping cues. This framework keeps follow-up attached to the conversation instead of converting every public interaction into a sequence.
The buyer's next action sets the follow-up state
A substantive question can invite another answer. A like, generic thanks, or profile view does not necessarily invite contact beyond the thread.
Public questions deserve public answers by default
Continue visibly when the answer can help the thread and no private information is required. Do not move the discussion into direct messages only to make it easier to sell.
One relevant update can be useful; repeated nudges are not
Follow up when new information changes the decision, not merely because time passed or the buyer has not replied.
Stopping is part of a complete workflow
Mark no response, decision closed, poor fit, request withdrawn, or community boundary as explicit outcomes so the interaction cannot drift into repeated contact.
A buyer-controlled follow-up sequence
The sequence advances only when the conversation supplies a new invitation or decision-relevant fact.
Finish the first answer cleanly
Give the useful tradeoff, disclose affiliation when relevant, and avoid ending with a forced meeting request or vague invitation to connect.
Read the next signal, not your desired outcome
Distinguish a real question or channel invitation from passive engagement such as a like, profile view, or generic acknowledgment.
Stay in the current channel when possible
Answer public follow-up questions publicly. Move privately only when the buyer asks or when necessary details should not be shared in the thread.
Add only decision-changing information
A follow-up should answer the new question, correct an important misunderstanding, or provide a requested resource. Do not resend the original pitch in different words.
Close on silence or completion
Do not chase a response. Record the outcome for learning and let the buyer reopen the conversation if their decision changes.
Representative: the buyer asks a specific public question
After the founder explains a tradeoff, the buyer asks whether the workflow supports a particular public source.
Why it matters: Answer in the thread so the clarification remains visible. State the limitation if the source is unsupported.
Representative: the buyer invites a private implementation discussion
The author asks the founder to send details because the next question involves private team or account information.
Why it matters: Continue privately, reference the invitation, stay within the requested scope, and avoid adding the person to an automated sequence.
Representative: a like with no question
The author reacts positively to the answer but does not ask for more information or contact.
Why it matters: Treat the interaction as complete. A reaction confirms receipt, not consent for a direct message or repeated follow-up.
Representative: important information changes
The founder previously gave a factual limitation, and a product update now changes that answer while the buyer's evaluation is visibly still active.
Why it matters: One concise correction can be useful. Disclose that the product changed and avoid using the update to restart a closed conversation.
Use explicit follow-up states
Track public question, private invitation, decision active, decision closed, no response, research only, and do not contact. Advance only when the state supplies a clear reason.
Write stopping rules before outreach begins
Treat silence, a closed choice, a declined invitation, poor fit, or a community restriction as an end state. Do not rely on individual judgment after several nudges.
Capture learning without extending contact
Record the objection, requirement, decision rule, and outcome in aggregate. The team can improve messaging and product knowledge without asking the buyer for another interaction.
Keep public-conversation follow-up selective, visible, and easy to end.
ReplyRadar supports manual review and reply pacing so founders can learn from conversations without turning every interaction into an outreach sequence.
Should a founder DM someone after replying to their public post?
Only when the person invites private contact or the next requested step requires private information. A useful public reply alone does not grant permission for a direct message.
How many times should a founder follow up after a community reply?
Use the buyer's active questions or explicit invitations rather than a fixed sequence. If there is no response or new decision-relevant information, stop.
Is a like or profile view a follow-up invitation?
Not by itself. Passive engagement can show that the answer was seen, but it does not clearly request private contact or another sales message.