Follow Up When a Technology Buyer Ghosts After a Proposal

A buyer requests a proposal, receives one, and then sends no reply for three weeks. Silence invites stories. A seller might assume a competitor won, budget disappeared, or interest faded. Guesswork produces weak follow up. Start instead with the decision behind the proposal request. The buyer asked for help weighing something. Refer to the choice and ask a question with room for an honest answer.

Review your own record before sending a message. Find the problem discussed during discovery, people expected to join a choice, timing mentioned by the buyer, and any unresolved concern. Do not use the proposal attachment as a substitute for this review. If notes say a sponsor wanted to decide whether to replace manual purchase approval during the current quarter, use those words. A note grounded in a buyer’s original purpose feels different from a routine chase.

Keep the message short. State the decision in one sentence. Then offer an easy path for reply. For example: “When you requested the proposal, you were weighing manual approval work this quarter. Has priority changed, or is part of the proposal hard to evaluate?” This question does not accuse anyone of ignoring you. A buyer has language for a stalled project, confusing scope, a changed date, or a choice to stop.

Avoid putting “checking in” at the center of an email. Those words ask a buyer to work without explaining why a reply matters. Repeated requests for review time create more pressure for a person already handling internal work. Your note should reduce pressure and clarify a next step. Offer only paths you are ready to honor, such as clarifying scope, revisiting timing, or closing an active evaluation. Each path permits a reply without a defense of the delay.

Do not offer a price change, new feature, extension, or deadline unless your team has authority and a genuine reason. Do not claim urgency for a buyer. A proposal does not give a seller control of someone else’s calendar. Your role is to learn where evaluation stands and organize a useful conversation when a buyer wants one. Careful limits make a follow up more credible.

Consider a fictional example. Evan, an account executive, sent a proposal to Lila, a finance operations sponsor, on April 4. During an earlier call, Lila said her group wanted fewer exchanges around purchase approvals before a June planning meeting. Evan receives no response by April 25. He reviews notes and finds one unresolved concern. Lila was unsure whether regional managers needed a separate approval path. He uses this concern instead of sending a generic reminder.

Evan writes: “Lila, our April 4 proposal covered purchase approval review. You were weighing separate regional manager paths before June planning. Has your timing changed, or would a short scope discussion help? We are ready to clarify scope, revisit timing, or close this evaluation for now.” The note is direct. Evan does not fill space with reasons his own team wants a meeting. He gives Lila a small number of useful responses.

Suppose Lila replies, “Still reviewing.” Treat this as a beginning, neither a win nor a rejection. Ask one question connected to the decision. Evan replies, “Which part needs review before your group chooses a path: regional manager approval, rollout sequence, or another concern?” He names options from prior discussion while leaving room for a different answer. A long list of questions would turn a small reply into fresh work for Lila.

Suppose Lila says internal agreement is missing. Ask who needs a useful discussion and what choice sits between them. She might say procurement wants more detail while operations wants a simpler process. Evan should not decide who is right. He asks whether a 25 minute session focused on regional approval would help both groups examine the same scope. If Lila agrees, Evan confirms a meeting purpose in writing: decide whether regional managers follow a standard path or need a separate review.

If timing changed, accept an answer without hiding punishment inside persistence. Evan might reply, “Thank you for letting me know. What date would make a later check back useful, if any?” The final words matter. Lila might prefer to close evaluation. Record her answer accurately. A future date must come from a buyer, not an internal forecast. When Evan contacts her later, he refers to the agreed date and original decision instead of starting discovery again.

If a buyer asks to close evaluation, make closure easy. A brief response protects the relationship better than an argument. Evan writes, “Understood. I will close our active evaluation. If purchase approval becomes a priority again, please reach out and we will begin with regional path questions.” This response does not promise a future result or force a meeting. Evan records Lila’s reason if she provides one. He does not add an invented loss reason for reporting convenience.

Silence sometimes follows a proposal because the document hides a hard choice. A buyer might not know which scope option fits, who needs approval, or why a cost line appears. Your follow up should surface one choice. Before writing, read the proposal from a buyer’s position. Mark places where a reader needs an assumption. Select the assumption closest to the original decision. Then ask about the choice in plain language.

Keep follow up timing intentional. After a first note, allow time for a reply. Do not send a message every day. When a later contact has a reason, record both date and decision context. A second note should add a useful prompt rather than repeat the first. Evan might mention regional approval and ask whether Lila wants a one page scope comparison. He sends material only after Lila requests a comparison or agrees such a comparison would help.

Before your next quiet proposal, run a short practice with a fictional sponsor. A colleague replies, “We are still reviewing.” Repeat the discovery decision in one sentence. Ask one narrow question about the blocker. Do not offer a discount or an invented deadline. Read your question aloud. An honest answer should feel easier than replying to “Any updates?” Remove excess language until the buyer sees one clear choice.

On April 26, Lila writes, “Regional approval is holding us up.” Evan sends a calendar option for a 25 minute scope discussion with Lila and her operations lead. His invitation names one outcome: decide which approval path belongs in a revised proposal. Before the meeting, Evan prepares one page with two labeled scope options, marks unresolved items, and leaves the decision for Lila’s group.