← Back to home
Playbook Design · FareHarbor

The Go-to-Green Playbook

Silent accounts don't churn all at once. They drift. I built a systematic, repeatable process to re-engage at-risk enterprise accounts before silence becomes a decision, and gave every AM on the team a shared framework to do it with.

Scope
Mid Market and Enterprise
Output
10-day sprint · Multi-thread framework · Manager review cadence
Skills
Playbook design · Change management · Coaching · Process systems

The problem with silence

When an account goes quiet, everyone had a different approach. Call 1 person here, email 1 person there. It was sporadic. Disorganized. I built this playbook to fix that.

As a manager, I watched AMs get stuck in this pattern. They'd make a few attempts, not hear back, and quietly deprioritize the account. By the time anyone flagged it as at-risk, months had passed. I wanted to give the team something more structured, a process that removed the guesswork and raised the floor on what a re-engagement attempt actually looked like.

We are not trying to "check in." We are trying to create value that is difficult to ignore.

What "Red" means

The playbook starts with a clear definition of when to use it. Accounts are flagged Red if any of the following are true:

Red, initiate immediately
  • Engagement score below 10
  • No response after 3+ attempts across 2+ channels
  • No live conversation in 45 to 60 days
  • Declining or stagnant usage
  • Key stakeholder is no longer active or unknown
Green, exit criteria
  • A meeting has occurred
  • A clear next step is defined
  • Multiple stakeholders are engaged
  • Ongoing communication is established

The 10-day sprint

Once an account is flagged Red, the AM follows a structured 10-day engagement sequence. No skipping steps. No defaulting to a single contact. The design forces multi-threading, channel variety, and escalating intensity across the sprint.

2-Week Engagement Sprint Follow sequence exactly · Do not skip steps
Day 1
Launch multi-threaded outreach
Insight-led email to primary contact + 1–2 additional stakeholders. Goal: start 2–3 parallel conversations.
Day 2
Social and light follow-up
View all stakeholder profiles, engage with recent activity, send connection requests. Tailored email to any remaining key stakeholder.
LinkedIn
Day 3
Call layer begins
Call primary contact and one secondary stakeholder. Voicemail if no answer, reference the insight, not the follow-up.
Calls
Day 4
Expand stakeholder coverage
Reach out to 1–2 additional contacts, active dashboard users, manager/director permissions, or contacts found on their website. Goal: 3–5 total contacts.
LinkedIn
Day 5
Value drop across all contacts
Send value-driven message to all engaged stakeholders: benchmark data, a specific insight, or a quick win they can act on.
Calls
Days 6–8
Sustained multi-channel pressure
Continue rotating through calls, email, and LinkedIn across all identified stakeholders. No single-threading. Day 7 brings in leadership, a manager or director sends a fresh perspective directly to key contacts.
CallsLinkedInManager Involvement
Day 9
New angle on same hypothesis
Reframe the core insight through a different lens, risk, missed opportunity, or industry trend. Send to all key stakeholders.
Day 10
Pattern interrupt
Short, direct message. Acknowledge the lack of response. Ask if timing or priority is off. Final call attempt to primary contact.
Calls

What makes it work

The playbook isn't just a sequence, it's a forcing function. It requires real prep before any outreach begins. The AM must be able to answer specific questions: what does this customer care about right now? What insight can I bring that they don't already have? No prep, no outreach. "Checking in" is explicitly not allowed.

It also mandates multi-threading. Single-contact relationships are one of the most common failure modes in enterprise CS, when that contact goes dark or leaves the company, the relationship disappears with them. The sprint builds breadth by design, requiring contact with 3–5 stakeholders across different roles before the sequence is complete.

Common failure modes this playbook eliminates
Generic "checking in" messages with no insight
Giving up after 2 or 3 attempts
Single-threaded relationships with one contact
Leading with product instead of outcomes
Weak or unclear calls to action
No manager visibility until the account is already lost
0 → 1
A structured, team-wide playbook for re-engaging at-risk accounts. Every AM follows the same high-quality process. Managers have weekly visibility. Silence now has a response.

Why I built it

The best CS teams don't just react to churn, they have a system for catching drift before it becomes a decision. I built this because I kept watching good AMs lose winnable accounts not from bad relationships, but from letting silence go unanswered too long.

A repeatable playbook means the quality of the re-engagement attempt doesn't depend on how motivated someone feels that week. It sets the floor high and makes the expectation explicit: silence is a signal, and we have a process for answering it.

Next

LiverMan, what I build outside of work →