Check whether a response was actually expected
Review what happened at the end of the meeting or submission. Did the recipient promise review, request a sample, give a date, or merely accept information? Check whether you used the correct channel and supplied the requested material. A missing attachment or an incomplete portal submission is different from a commercial rejection.
Do not infer commitment from polite language. If the company says it reviews submissions quarterly, align with that process. If a person referred you elsewhere, follow the referral appropriately rather than repeatedly contacting the original person. Good follow-up starts with accurate interpretation of the last explicit agreement.
Write a message that advances the decision
A practical structure is context, relevant update, and question. For example, identify the product and meeting date, state that the requested packaging dimensions are now confirmed, and ask whether the recipient wants the revised sheet for the next review. Keep the message understandable without opening several attachments.
Avoid invented urgency, guilt, or unsupported claims that competitors are interested. Do not send large files unrequested. If nothing has changed, a brief status question may be appropriate, but repeated messages saying only checking in add little. A real update should reduce the recipient's uncertainty, not merely remind them that you are waiting.
Use a small tracking system
Track recipient, role, submission route, material version, last contact, promised next step, and next review date. Suppose 12 pitches produce four explicit declines, three requests for more detail, and five unanswered submissions. Your actionable pipeline is the three requests, while the five unknowns require clarification rather than being counted as interested prospects.
This accounting prevents inflated forecasts. It also reveals patterns: one channel may produce no response because it is inappropriate, while another reaches the actual category reviewer. Measure progress by concrete next steps and completed evaluations, not by the number of messages sent.
Know when to close the loop
Choose a reasonable bounded sequence based on the recipient's stated process and relationship. There is no universal number of days or messages that guarantees a reply. After appropriate attempts, send a courteous closing note if useful and mark the prospect inactive until new evidence or an invitation justifies contact.
Use the time recovered to improve the product evidence or approach better-fit prospects. If multiple recipients ask the same unresolved question, solve it. If nobody understands the benefit, revise the presentation. Follow-up cannot compensate indefinitely for weak fit, missing evidence, or an offer that does not address the recipient's business.
Separate a useful update from an attempt to restart the pitch
A useful update addresses a question the recipient raised or changes the basis for evaluation. Examples include a corrected dimension, a completed test, a clarified cost assumption, or a now-available sample. A redesigned logo or a larger social follower count may be irrelevant to the decision. Before sending, write one sentence explaining why the information matters to this specific recipient.
If the contact declined, respect the stated reason. Reapproaching can make sense when that reason has materially changed, but the message should acknowledge the prior decision and explain the new fact. Do not behave as though the earlier exchange never occurred. If the company declines unsolicited ideas altogether, further persuasion may simply waste time and ignore its process.
Keep an inactive-prospect category distinct from rejected and active. Inactive means there is no current agreed action; it does not imply hostility or hidden interest. Review that category only when meaningful new evidence exists or the recipient invited a later contact. This prevents a founder from spending most of the week maintaining imaginary opportunities. The resulting time can be directed toward customers and prospects whose actions provide clearer information about the invention's prospects.
Before sending a final follow-up, verify the contact details and any automatic reply or stated absence already received. A routing problem should not be interpreted as commercial disinterest. Keep the tone factual and the requested action small enough to answer. If the recipient responds with a clear decline, update the record immediately so another team member does not continue the sequence. A simple shared status field prevents duplicate outreach and preserves a more professional relationship for any genuinely relevant future development.
Decision checklist
- Was a reply or review actually promised?
- Does the new message resolve a relevant uncertainty?
- Are pipeline stages based on explicit actions?
- Is there a bounded point at which effort moves elsewhere?