# Ghosted After The Demo > Works out why a prospect went quiet after a good call and what to send now, by reading the actual thread and call notes rather than assuming they got busy. Use when a promising deal stops replying, or when several deals go silent at the same stage. - Skill: `mardab96/ghosted-after-the-demo` (Agent Skill) - Install (CLI): `npx skillmds@latest add mardab96/ghosted-after-the-demo` - Raw SKILL.md: https://api.skillmd.com/api/skills/mardab96/ghosted-after-the-demo/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: mardab96 (https://skillmd.com/u/mardab96) - Updated: 2026-09-21 - Page: https://skillmd.com/skills/mardab96/ghosted-after-the-demo --- # Ghosted After the Demo ## Use this skill when The call went well, everyone said the right things, and then nothing. This is the most common and least examined failure in B2B selling. The default explanation is that they got busy, which is comfortable, occasionally true, and almost never the whole story. Silence after a good call usually means something was left unresolved in the call itself, and it was audible at the time. Two versions of this skill's job: work out what actually happened, and write the message that has a chance of restarting it. ## Required input - The email thread, pasted, including your own messages. - What was said on the call. Notes or transcript, whichever exists. - How long the silence has run, and how many times you have followed up. Helpful: - who attended the call and who did not - what the agreed next step was, and who owned it - whether pricing was discussed and how it landed - whether this pattern repeats across other deals ## Analysis workflow 1. Find the exact moment the tone changed. Read the thread in order and mark where enthusiasm turned into logistics, or where a question went unanswered. 2. Check whether a real next step existed. "I will send something over" and "we will get back to you" are not next steps, and a deal with no owned next step goes quiet by default rather than by decision. 3. Check who was in the room against who needs to approve. A great call with someone who cannot buy is the single most common cause of this silence, and it feels like progress right up until it stops. 4. Look for the unasked question. Price, timing, incumbent contract, internal politics: whichever of these went unmentioned in a call where it obviously mattered is usually the reason. 5. Count your own follow-ups and read their tone. Three messages that each say "just checking in" have taught them that ignoring you has no cost. 6. Classify the silence honestly into one of: no authority, no budget cycle, no urgency, unspoken objection, lost to an incumbent, or genuinely busy. State the confidence. 7. Write one message that fits the diagnosis, and decide whether this deal should be worked or closed. ## Decision rules - Never write another "just checking in". If the message contains no new information and asks nothing answerable, it makes the silence more likely, not less. - A message that gives the recipient an easy, face-saving way to say no outperforms one that asks for a yes. "Should I close this out?" gets replies that "any thoughts?" never will. - If the call had no economic buyer in the room, the follow-up goes to the person who was there, asking for access, not for a decision. - After three unanswered follow-ups, the honest move is a closing message, not a fourth attempt. - One ghosted deal is a deal. Five ghosted deals at the same stage is a process, and the process sits upstream of any email you can write, so stop rewriting messages and route it to `discovery-call-gap-analysis`. ## Output format ### What likely happened The classification, with the evidence from the thread or notes that supports it, and a confidence level. ### What was missing from the call The specific question that should have been asked and was not. ### The message Ready to send. Short. With a one-line note on why it is built this way. ### If they reply The two likely replies and what to do with each. ### If they do not When to send the closing message, and what it says. ### Verdict `work it` / `close it out` / `park it with a date` ## Practical example The thread shows a strong call on the ninth, a same-day thank-you with a proposal attached, and then three follow-ups over five weeks, each some variant of checking in. Reading the notes, pricing never came up on the call, and the attendee was a marketing manager at a company where the budget for this sits with a director who was not invited. The diagnosis is not that they got busy. It is that the proposal reached someone who could not approve it, and nobody has said a number out loud yet. The message goes to the manager, does not chase the proposal, and asks one thing: whether the director needs to see it and what they usually want to know. It offers to close the file if the timing is wrong. ## Guardrails - Do not send anything on the user's behalf. - Do not use manufactured urgency, fake deadlines or invented scarcity to restart a conversation. - Do not guess at internal politics and present it as fact. Mark inference as inference. - Do not recommend a fourth follow-up because the deal is wanted. Wanting it is not evidence it is alive. - Do not read a single ghosted deal as a pattern. One deal is one deal.