agentleFS
Sign inStart free
Frontal-soFrontal-so/outbound-skills/skills/bridgebound-history-16/SKILL.md

bridgebound-history-16

Skill8 starsChanged 4 months agoMITView on GitHub

16 history-based Bridgebound triggers from Flip The Script - Demo Pipeline, Closed-Lost, Executive Churn, Email Engagement, and Reciprocity. Use when re-engaging past prospects, reactivating closed-lost deals, or building win-back campaigns.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

Create a free account to mount
Files
SKILL.md

BRIDGEBOUND Category II: Based on History (16 Triggers)

Demo Pipeline (3 Triggers)

  1. Requested a Demo But Didn't Schedule One - Demo request abandonment
  2. Agreed to a Demo & No-Showed - No-show follow-up
  3. Prospects Who "Abandoned the Chat" - Chat abandonment

Closed-Lost (5 Triggers)

  1. Demoed in the Past (Ghosted or Went Dark) - Ghosted prospects
  2. Went with a Competitor & Up on Renewal - Competitor renewal timing
  3. You Messed Up (Ex. Objection of No Budget) - Past objection resolution
  4. Didn't Hit ICC (Size) - Company grew into ICP
  5. Didn't Hit ICC (Criteria that DQs) - Criteria changed

Executive Churn / UserGems (3 Triggers)

  1. Customers Who Went to Another Company - Champion tracking
  2. Customers Who Changed Roles Internally - Internal moves
  3. Prospective Company New Hires, Who Never Used Your Product - New decision makers

Email Engagement (3 Triggers)

  1. Opened Prospecting Emails - Email openers
  2. Opened Prospecting Emails (Aggressively) - Multiple opens
  3. Received an OOO to Prospecting Emails - OOO responses (timing intel)

Reciprocity (2 Triggers)

  1. Companies that Sold You THEIR Product (Tit for Tat) - Vendor relationships
  2. Competitors of Your Current Customers - Competitive intelligence

Re-Engagement Template

Subject: since we last talked

{{firstName}},

When we talked in {{month}}, you mentioned {{objection}}.

Since then, we've {{improvement}}.

Worth another look?

Timing Considerations

Trigger TypeOptimal Timing
No-showSame day + 2 days later
Ghosted30-60 days later
Competitor renewal90 days before renewal
Champion job changeDays 14-45 in new role

Combines with

SkillWhy
cold-email-templates-34Re-engagement templates (#31-34)
buying-signals-6Champion tracking (signal #1)
clay-enrichment-9stepTrack job changes in Clay
cold-call-scriptsNo-show phone script

Example prompts

Create a win-back campaign for closed-lost deals from 6 months ago.
How do I track when competitors' customers are up for renewal?
Write a sequence for trigger #9 (Customers Who Went to Another Company).

Part of Frontal — free, open GTM skills for your AI agent. Browse the library →

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free