Skip to content

deanpeters/Product-Manager-Skills / plugins/pm-deliver/skills/eol-internal-enablement

eol-internal-enablement

Verified

Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement. Use when customer-facing teams must be ready before customers hear.

FileKindSize
SKILL.mdskill md12.3 KB
examples/sample-industrial.mdmarkdown9.6 KB
examples/sample.mdmarkdown7.1 KB
template.mdmarkdown5.9 KB

examples/sample.md

View on GitHub
# EOL Internal Enablement Example — SaaS

**Product:** Fieldlight Classic Dispatch
**Level:** 2 — Standard
**Context:** ~800 accounts, $2.4M ARR, annual contracts. Replaced by Fieldlight Next Scheduling.
EOS March 1, EOE June 1, EOM October 1, EOL December 31, 2026. ~30 accounts use custom dispatch
rules that don't carry over — the known gap.

---

```markdown
## EOL Internal Enablement Pack: Fieldlight Classic Dispatch

**Level**: 2 -- Standard
**Materials included**: Support FAQ, sales talking points, objection
handling, escalation playbook
**Announcement target date**: March 1, 2026
**Enablement must be complete by**: February 20, 2026

---

### 1. Support FAQ

#### What is happening?
- Q: Is Fieldlight going away?
- A: No. Classic Dispatch is being retired December 31, 2026. Everything
  else in Fieldlight continues, and Next Scheduling replaces Classic.

- Q: Why are you retiring it?
- A: Classic recalculates routes once overnight and can't respond to
  changes during the day. Next reoptimizes as the day happens.

#### What does this mean for me?
- Q: Will my dispatch board stop working?
- A: Not until December 31, 2026. Everything works normally until then.

- Q: Do I have to do anything right now?
- A: No. The migration wizard opens March 1 and takes about 20 minutes
  for most accounts.

#### What are my options?
- Q: Can I stay on Classic?
- A: Not past December 31, 2026. Next is the path forward, and we'll
  migrate your rules automatically with your approval.

- Q: How long does migration take?
- A: About 20 minutes for standard setups. Accounts with custom dispatch
  rules need a 1-on-1 session -- we'll reach out first.

#### What about my data?
- Q: Do I lose my dispatch history?
- A: No. History migrates to Next. Anything you want outside Fieldlight
  can be exported until December 31, 2026.

- Q: How long do you keep my data after EOL?
- A: Exports remain available 90 days past December 31, 2026.

#### What about my contract?
- Q: I'm paying for Classic -- do I get a refund?
- A: Your subscription covers the platform, and Next is included at no
  additional cost. Nothing changes on your invoice.

- Q: My renewal is after the EOL date. What happens?
- A: You'll renew on Next. Your account manager will walk through it
  before renewal.

#### When does support end?
- Q: When do you stop fixing Classic bugs?
- A: October 1, 2026. Security patches continue through December 31.

- Q: When does Classic actually stop working?
- A: December 31, 2026.

#### Escalation path
- Level 1: Support team -- standard questions, migration how-to
- Level 2: Priya (Support Lead) -- frustrated customers, repeat contacts
- Level 3: Marcus (VP CS) -- churn threats, custom-rule accounts
- Executive: Dana (CPO) -- top 20 accounts, press, legal language

---

### 2. Sales Talking Points

#### Positioning the Transition
- Frame: Consolidating scheduling into one product
- Avoid: "Sunsetting," "deprecating," "low usage"
- Lead with: Schedules that adapt during the day

#### Product Comparison

| Capability | Classic Dispatch | Next Scheduling |
|---|---|---|
| Drag-and-drop assignment | Yes | Yes |
| Technician skill matching | Yes | Yes |
| Daily route view | Yes | Yes |
| Mid-day reoptimization | No | Yes |
| Live customer arrival windows | No | Yes |
| Overtime warnings | No | Yes |
| Custom dispatch rules | Yes | Partial -- common patterns
  supported; complex rules need rebuild. Full parity targeted Q3 2026 |
| v1 dispatch API | Yes | Replaced by v2 -- migration guide published |

#### Pipeline Impact Guidance
- Deals in progress: quote Next only, effective immediately
- Renewals pending: renew on Next, no price change
- Bundled pricing: no change, Next included
- New prospects asking: Classic is retiring, Next is the product

#### Competitive Response
- If a competitor raises our EOL: we announced ten months ahead with
  automated migration and free 1-on-1 support
- If asked "what else are you killing?": nothing else is scheduled;
  this is a consolidation, not a retrenchment

---

### 3. Objection Handling

#### "We just renewed last quarter."
- Acknowledge: That's fair -- you renewed expecting continuity
- Reframe: Your subscription covers the platform, and Next is included
  at no extra cost. You're not paying twice
- Offer: Priority migration slot and a 1-on-1 session (approved for all
  renewals since October)

#### "Next doesn't support our custom dispatch rules."
- Acknowledge: Correct, and I won't pretend otherwise. Complex rules
  need a rebuild
- Reframe: Common patterns are supported today, and full parity is
  targeted for Q3 2026 -- ahead of the December date
- Offer: A 1-on-1 rebuild session with our team doing the work, plus
  early access to the parity release (approved for all 30 accounts)

#### "We're going to look at alternatives."
- Acknowledge: That's a reasonable reaction to being asked to change
- Reframe: Switching platforms means retraining on everything, not just
  the dispatch board. Migrating to Next keeps your history, integrations,
  and technician records intact
- Offer: A call with the product team on the Next roadmap, and I'll
  personally run your migration (approved: exec call for accounts over
  $25K ARR)

#### "Why should we trust Next won't be next?"
- Acknowledge: That's the right question to ask
- Reframe: Next is where all our scheduling engineering goes now --
  this consolidation is what makes that commitment real. And how we're
  handling this transition is the honest evidence: ten months' notice,
  automated migration, no price increase
- Offer: Written confirmation that Next is our long-term scheduling
  platform (approved language from Legal)

#### "Can we get an extension past December?"
- Acknowledge: I understand the timing is hard
- Reframe: December 31 is firm -- the infrastructure Classic runs on is
  being decommissioned
- Offer: Migration support on your schedule any time before then, plus
  a dedicated slot in Q4 if you need to be last (no date extensions --
  do not offer one)

---

### Assumptions to Validate
- Assumes Q3 2026 custom-rule parity date holds
- Assumes Finance approved the exec-call threshold at $25K ARR
- Objections 3 and 5 are predicted, not yet heard from customers
```

---

## What to notice

- **The comparison table names two real gaps.** Custom dispatch rules and the v1 API are listed as
  gaps with workarounds and a parity date. A rep who leads with a concession keeps credibility for
  the eight rows above it.
- **Every offer states its approval.** "(approved for all 30 accounts)," "(approved: exec call for
  accounts over $25K ARR)." A rep knows exactly what they can commit without checking.
- **One objection ends by forbidding an offer.** "No date extensions — do not offer one" is as
  important as the offers themselves. Without it, a sympathetic rep invents one.
- **The escalation ladder has human names.** Priya, Marcus, Dana. "Support Lead" is a role; a rep
  at 4pm on a Friday needs a person.
- **The trust objection gets the strongest reframe.** The answer isn't a promise about Next — it's
  pointing at how *this* transition is being handled. That's the only evidence a customer can
  actually check.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall