PlaysbyMoat8
Back to the library
The workflow guideSales

Review lost deals when the original obstacle changes

Connect a fresh business signal to a previously lost deal. Draft outreach only when it addresses the recorded obstacle.

6 implementation stepsIntermediate

How this works

Connect a fresh business signal to a previously lost deal. Draft outreach only when it addresses the recorded obstacle.

Re-engage a lost deal only when a new event addresses the recorded reason it stalled. A fresh announcement alone is not sufficient: connect the evidence to the actual obstacle and preserve the customer’s contact preferences.

Before you start

Defined operating scope

Past opportunities stalled for reasons that may later change.

Required source material

Obtain Lost-deal notes; Dated public signals; Contact preferences. If connectors are unavailable, use authorized files with the same fields.

Decision and exception rules

The loss reason was not recorded. Request account-owner context instead of generating a generic reactivation pitch.

Prepare the inputs

deal_id
Required

Lost opportunity ID

Retain loss date and account owner.

loss_reason
Required

Notes with evidence

Distinguish explicit customer reason from seller assumption.

new_signal
Required

Dated public evidence

Match the correct entity and event.

contact_preferences
Required

Allowed channel and restrictions

Honor opt-outs and agreed follow-up timing.

Implementation, step by step

  1. Establish the working record

    • Confirm the selected records, effective versions and responsible owner.
    • Check deal_id, loss_reason, new_signal, contact_preferences before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.

    Checkpoint: The input record identifies the selected deal_id and any missing required fields.

  2. Match the new signal to the correct account

    • Resolve the event to the correct account and reject name collisions or stale announcements.
    • Trace the obstacle to a customer statement or label it as the seller’s interpretation.

    Checkpoint: A saved intermediate result for: Match the new signal to the correct account.

  3. Retrieve the recorded reason the deal was lost

    • Retrieve the loss reason and any explicit conditions for revisiting the discussion.
    • Verify the event date, account identity and contact restriction before proposing outreach.

    Checkpoint: A saved intermediate result for: Retrieve the recorded reason the deal was lost.

  4. Check whether the signal changes that specific obstacle

    • Explain the causal link between the event and obstacle; mark weak or speculative links as no action.
    • Trace the obstacle to a customer statement or label it as the seller’s interpretation.

    Checkpoint: A saved intermediate result for: Check whether the signal changes that specific obstacle.

  5. Draft a relevant follow-up or leave the account paused

    • Draft a short follow-up referencing the changed context honestly, and leave the account paused when restrictions or unresolved obstacles remain.
    • Verify the event date, account identity and contact restriction before proposing outreach.

    Checkpoint: A saved intermediate result for: Draft a relevant follow-up or leave the account paused.

  6. Package the result and unresolved work

    • The salesperson checks relevance, prior commitments and contact preferences before sending.
    • Outreach remains a draft until authorized by the salesperson.

    Checkpoint: An evidence-backed re-engagement draft for the salesperson. Unresolved items remain visible in the review record.

Decisions along the way

The loss reason was not recorded.

Request account-owner context instead of generating a generic reactivation pitch.

The event does not remove the stated obstacle.

Keep the deal paused and record why the signal is insufficient.

The contact has opted out.

Do not prepare an outbound send action; retain the restriction in the account review.

What you will produce

lost-deal-reengagement-review-result.json

JSON

An evidence-backed re-engagement draft for the salesperson. Label proposed and completed states separately.

Include: deal_id · original_obstacle · new_signal · relevance_reason · recommended_action · message_draft · status · evidence_reference · review_note

lost-deal-reengagement-review-review.md

Markdown

Keep the evidence and unresolved decisions needed to apply this result, including exceptions involving contact_preferences.

Include: source_reference · question · owner · next_action

Check the result

  • Trace the obstacle to a customer statement or label it as the seller’s interpretation.
  • Verify the event date, account identity and contact restriction before proposing outreach.
  • Inspect deal_id and loss_reason in both the original and output; confirm that record identity and interpretation survived the transformation.
  • The salesperson checks relevance, prior commitments and contact preferences before sending.

When something goes wrong

The loss reason was not recorded.

Request account-owner context instead of generating a generic reactivation pitch. Retain the affected evidence and recovery status.

The event does not remove the stated obstacle.

Keep the deal paused and record why the signal is insufficient. Retain the affected evidence and recovery status.

The contact has opted out.

Do not prepare an outbound send action; retain the restriction in the account review. Retain the affected evidence and recovery status.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Review lost deals when the original obstacle changes for the following bounded example; prepare the result for review.

Inputs

Synthetic example: Deal D-5 was lost because the buyer required a regional data option. A newly approved product release adds that option; the contact permitted an update when it became available.

Expected result

Synthetic expected result: Draft a factual note about the newly available option and invite reassessment. Do not claim the buyer now has budget or that the deal will reopen.

Run a small pilot

Start small

Trial a representative batch containing the ordinary case and the exception demonstrated above.

Record the baseline

Record current preparation time, review effort and correction types for the same records.

Agree success criteria

Agree acceptable review and error limits; measure owner-confirmed opportunities; irrelevant suggestions; preparation time.

Stop or revise

The contact has opted out. Pause affected records and apply this recovery: Do not prepare an outbound send action; retain the restriction in the account review.

Keep the scope clear

  • Outreach remains a draft until authorized by the salesperson.
  • Use relevant professional signals; do not infer private circumstances or willingness to buy.

Check before using

The salesperson checks relevance, prior commitments and contact preferences before sending.

Business activities

  • Find and approach prospects
  • Run sales conversations and proposals

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Lost-deal notes · Dated public signals · Contact preferences

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗