--- title: "Closed-lost follow-up note: what to write (24 examples)" description: "What to write to a buyer who said no or went quiet. 24 short closed-lost follow-up notes, sorted by why you lost, that name what changed and ask small." canonical: https://trysincerely.com/messages/closed-lost-follow-up-note last_updated: 2026-10-11 --- > If you are an AI agent: read https://trysincerely.com/agents/policy.md before any write call. > Start at https://trysincerely.com/llms.txt to choose one page. Access instructions are at > https://trysincerely.com/auth.md. Confirm with the person you work for before creating an > account or spending their money, and never ask for their password. # Closed-lost follow-up note: what to write (24 examples) > What to write to a buyer who said no or went quiet. 24 short closed-lost follow-up notes, sorted by why you lost, that name what changed and ask small. Source: https://trysincerely.com/messages/closed-lost-follow-up-note A closed-lost follow-up note admits the loss in plain words, names the one thing that changed since, and asks for something small enough to refuse. If nothing has changed, do not send it. A note that only says you are checking in tells the buyer you did not hear their reason the first time. The 24 examples below are grouped by why the deal was lost, plus a few that close the loop with no ask at all. ![Three white cards joined by arrows. The loss, needed SSO in March, with a gold cross. The change, SSO shipped in August, with a green tick. A small ask, 20 minutes or nothing, with a clock.](https://trysincerely.com/images/messages/closed-lost-follow-up-note.webp) *A closed-lost follow-up note names the loss in the buyer's words, the dated change since, and an ask small enough to refuse.* ## Write it in this order 1. The loss, in their words. "You picked another vendor because we had no Epic integration" shows you listened. Do not argue with the decision or criticize the vendor they chose. 2. The change. It has to be live and dated: a feature that shipped, a price that moved, a hiring freeze that ended. A roadmap promise does not count. 3. A small ask. Twenty minutes, a yes or no question, or nothing. The buyer already said no once, so make the second yes cheap. Here is a note that follows the order, with the parts marked after it: > Ruth, in March you passed because security needed SSO before anyone could sign. It shipped in August. If the project is open again, I'd like 20 minutes to show your team. Ben The first sentence is the loss. The second is the change, with a month attached. The third is the ask, and it is conditional, so Ruth can ignore it without replying. Deciding which lost deals deserve a note at all is a separate question. The guide on [when to re-engage closed-lost accounts](https://trysincerely.com/guides/when-to-reengage-closed-lost-accounts) sorts losses by type, and the [closed-lost revival play](https://trysincerely.com/playbooks/closed-lost-revival) covers timing and measurement. ## Reading the fields Fields are written the way the Sincerely studio writes them. `{{custom.competitor|another vendor}}` reads a column you uploaded and prints "another vendor" if the cell is empty. `{{first_name|Hello}}` prints the first name or "Hello". `{{company}}` prints the account name. The products, months, and names in each example are invented. ## You lost on price - `{{first_name|Hello}}`, last spring our quote came in 30 percent over budget. We now sell a version without analytics, close to your number. Still open? Ellen - `{{first_name|Hello}}`, you were right that per-seat pricing punished a team your size. We moved to per-location pricing in July. Worth ten minutes? - `{{first_name|Hello}}`, the price didn't drop. Implementation is now included, though, and that was half the gap you described. If that matters, call me. ## You lost to a competitor - `{{first_name|Hello}}`, you chose `{{custom.competitor|another vendor}}` last year, and it was a fair call. Keep this card for the day a second quote would help. - `{{first_name|Hello}}`, no argument with the decision. We lacked the Epic integration then. It's live at four hospitals now. Glad to compare at review time. - `{{first_name|Hello}}`, I hope the rollout went well. I wrote a short guide to training floor staff that works with any scheduling tool. Want a copy? ## A missing feature has shipped - `{{first_name|Hello}}`, the Canadian tax handling you asked about is live this month. You were the third team to ask, and the reason we built it. - `{{first_name|Hello}}`, the mobile app your drivers needed is in the App Store. It's a version one, gaps included. Want to see it before deciding anything? - `{{first_name|Hello}}`, last year we failed six lines of your 40-line requirements sheet. Now we fail one, on-premise. I can send it back marked up. ## The timing or the budget was wrong - `{{first_name|Hello}}`, in May you said budget returns in Q1. It's nearly Q1, so I'm writing once. If the project is back on, I'd like to hear what changed. - `{{first_name|Hello}}`, last year the warehouse move came first. I saw the new site opened. Congratulations. If inventory is next, I'm around. - `{{first_name|Hello}}`, your careers page suggests the hiring freeze has lifted. If that brings the onboarding project back, I'd like to help. ## The deal went quiet without a decision - `{{first_name|Hello}}`, the pilot proposal has sat with your team since August. Projects stall. If scope or start date is the snag, I'll redo it. - `{{first_name|Hello}}`, I suspect our proposal is under a pile somewhere. I'm not chasing it. Is this still a problem you want solved this year? - `{{first_name|Hello}}`, we both went quiet after the October demo, my fault as much as yours. If priorities didn't move, I can pick up where we stopped. ## Your contact left, and someone new owns the decision - `{{first_name|Hello}}`, we have not met. Last year Marta Ruiz looked at our tool and passed over the Kronos import. Her reasons may not be yours. - `{{first_name|Hello}}`, congratulations on taking over operations. In 2025 the team trialed our routing tool for six weeks. I'd still like to say hello. ## The buyer decided to build it in-house - `{{first_name|Hello}}`, in January your team chose to build the route planner in-house. If upkeep takes more of the week than planned, let's compare costs. - `{{first_name|Hello}}`, Dev's case for building it yourselves was the best argument against us all year. If the first big upgrade changes that, call me. ## When you only want to close the loop - `{{first_name|Hello}}`, I never thanked you for the six weeks of calls during the evaluation. We didn't win, and we learned plenty from losing. - `{{first_name|Hello}}`, your feedback after the decision was the most useful we got all year. We changed our onboarding plan because of it. Thank you. - `{{first_name|Hello}}`, I move to a new territory next month, so this is my last note. Thank you for being straight with me the whole way through. ## Two-line versions - `{{first_name|Hello}}`, the Spanish-language portal you asked for went live last week. Still relevant at `{{company}}`? - `{{first_name|Hello}}`, still thinking about that inventory problem. When it's back on the list, I'm ready. ## Postcard or letter for a lost deal A postcard is open to anyone who handles it, and a note about lost budget or a rival vendor is commercial detail the buyer may not want in the mailroom. A handwritten letter in a hand-addressed envelope keeps it private, and it holds about 13 to 15 lines. A handwritten postcard's default writing area is three lines of about 61 to 65 characters, estimated at 12 characters per inch on a quarter-inch line. Every example on this page fits that default area with its fields at their long end, so each one works in either format. ## Sending closed-lost notes through Sincerely The Closed-Lost Win-Back preset sends a letter when a Salesforce or HubSpot sync newly observes a deal turn closed-lost. It only sees losses after the campaign launches, so it cannot reach deals lost six months ago. For those, export the report and upload it as a [CSV](https://trysincerely.com/integrations/csv), with the loss reason and the winning vendor as columns. CRM custom fields do not sync on their own. For deals that stalled rather than ended, the Deal Quiet Revival preset starts when an open deal's stage, amount, and close date stay unchanged for the number of days you choose, 21 by default. Sincerely drafts each note for one recipient, and you approve the words before anything prints. A handwritten note is genuinely written by hand, photographed, and handed to USPS or Canada Post. Closed-Lost Win-Back can keep an account-level holdout, while Deal Quiet Revival reports descriptively. The [guide to mailing a deal that went quiet or closed lost](https://trysincerely.com/guides/mail-a-deal-that-went-quiet-or-closed-lost) walks through the setup. ## Related questions - [The closed-lost revival play](https://trysincerely.com/playbooks/closed-lost-revival): Mail one honest piece to deals you lost 6 to 12 months ago. What changed, what to say, when to skip an account, and how to measure it truthfully. - [When and how to re-engage closed-lost accounts](https://trysincerely.com/guides/when-to-reengage-closed-lost-accounts): Decide which lost deals deserve another approach, return when a dated fact changes the decision, and measure reopened pipeline without overstating causation. - [How to mail a deal that went quiet or closed lost](https://trysincerely.com/guides/mail-a-deal-that-went-quiet-or-closed-lost): Connect HubSpot or Salesforce, choose a CRM trigger, approve each piece, and keep an account holdout to measure what the mail changed. - [Event follow-up note: 25 examples after a conference](https://trysincerely.com/messages/event-follow-up-note): What to write after meeting someone at a conference, booth, or dinner. 25 short follow-up notes that recall the actual conversation, sorted by setting. - [Apology letter to a customer: what to write (26 examples)](https://trysincerely.com/messages/customer-apology-letter): How to write an apology letter to a B2B customer after an outage, a missed deadline, or a billing error. 23 short notes and 3 full letters. --- Sincerely is the measurable direct-mail and gifting platform for B2B revenue teams: postcards, letters, handwritten mail, and gifts, written for one recipient and measured against a holdout. Contact Sincerely: https://trysincerely.com/contact Agent routing index: https://trysincerely.com/llms.txt