All skills
deanpeters avatar

/eol-internal-enablement

@d025768

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.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/eol-internal-enablement

This session only. Nothing lands on disk.

examplessample-industrial.md

≈2.5k tokens on demand. Your agent reads this file only when SKILL.md points to it.

EOL Internal Enablement Example — Industrial

Product: NFA-200 series retrofit controller (Northfield Automation) Level: 3 — Heavy Context: ~120 installations, 8 channel partners, service contracts through 2028, UL 508A and CE certified. NFA-500 is the successor but needs a different mounting bracket — every migration is a scoped site visit. This is an End-of-Sale announcement with no EOL date.

What makes this Level 3: field service techs and channel partners are customer-facing here, not just Sales and Support. The pack has to arm four audiences, and the wrong word about certification creates a compliance problem rather than an unhappy call.


## EOL Internal Enablement Pack: NFA-200 Series Retrofit Controller

**Level**: 3 -- Heavy
**Materials included**: Support FAQ, sales talking points, objection
handling, escalation playbook, channel partner brief, training outline
**Announcement target date**: March 31, 2026
**Enablement must be complete by**: March 13, 2026 (partners briefed
by March 6)

---

### 1. Support and Field Service FAQ

#### What is happening?
- Q: Is the NFA-200 being discontinued?
- A: It's going end-of-sale March 31, 2027. Installed units keep
  running and stay under service through your agreement.

- Q: When does my controller stop working?
- A: It doesn't. We are not setting an end-of-life date and we will
  never remotely disable an installed unit.

#### What does this mean for me?
- Q: Does this affect my running line?
- A: No. Service, parts, and support continue under your existing
  agreement.

- Q: Can I still buy more NFA-200 units?
- A: Through March 31, 2027. After that, the NFA-500 is the product.

#### What are my options?
- Q: Do I have to switch to the NFA-500?
- A: Not until your service agreement ends. When you're ready, we'll
  scope the retrofit with you at no charge.

- Q: Is the NFA-500 a drop-in replacement?
- A: No. It uses a different mounting standard and panel depth. Every
  migration is a scoped site visit -- budget it as a project.

#### What about my data?
- Q: What happens to controller telemetry and logs?
- A: Retained through end of service, December 31, 2028. We'll export
  your records on request at any time.

#### What about my contract?
- Q: Is my service agreement still valid?
- A: Yes, to its full stated term, including agreements running into
  2028. Contact your account manager for written confirmation.

- Q: Can I renew my service agreement?
- A: Renewals stop December 31, 2027. Existing terms are honored past
  that date.

#### What about certification?
- Q: Does this affect our UL or CE compliance?
- A: No. Installed NFA-200 units retain UL 508A and CE marking. This
  status change does not affect your compliance posture.

- Q: We run a validated process -- what do we need?
- A: We'll supply a change-control documentation package for your
  quality records. Request it from your account manager.

#### When does support end?
- Q: When do firmware updates stop?
- A: Non-safety updates stop December 31, 2028. Safety-related updates
  continue to end of service.

- Q: When does service end?
- A: December 31, 2028, or your agreement end date if later.

#### Escalation path
- Level 1: Field service desk -- standard questions, parts orders
- Level 2: Ravi (Service Manager) -- site-specific concerns, scheduling
- Level 3: Elena (VP Service) -- contract disputes, escalated accounts
- Executive: Tom (COO) -- top 10 accounts, regulatory inquiries, press

---

### 2. Sales Talking Points

#### Positioning the Transition
- Frame: Consolidating manufacturing onto one platform
- Avoid: "Obsolete," "unsupported," "end of life"
- Lead with: Your installed units are not affected

#### Product Comparison

| Capability | NFA-200 | NFA-500 |
|---|---|---|
| Safety interlock behavior | Yes | Yes -- equivalent |
| Ladder-logic compatibility | Yes | Yes |
| Field-serviceable design | Yes | Yes |
| Modular I/O expansion | Fixed | Yes |
| Remote diagnostics | No | Yes |
| Firmware updates without site visit | No | Yes |
| Mounting compatibility | -- | No -- different bracket and panel
  depth; site visit required per unit |
| Spare parts availability | Through Dec 2028 | Current |

#### Pipeline Impact Guidance
- Deals in progress: honor open NFA-200 quotes to March 31, 2027
- Planned expansions: raise last-time-buy now, not in 2027
- Multi-site standardization: move to NFA-500 or plan mixed fleet
- New prospects asking: quote NFA-500 only

#### Competitive Response
- If a competitor raises our EOS: we committed to service through 2028
  and set no shutdown date
- If asked about the mounting change: confirm it directly, then offer
  the free retrofit assessment

---

### 3. Objection Handling

#### "We standardized on the NFA-200 across six sites."
- Acknowledge: That's a real investment and this complicates it
- Reframe: Nothing installed is affected, and last-time-buy runs to
  March 2027 -- you can complete planned sites on the 200
- Offer: Last-time-buy quantities reserved at current pricing, plus a
  free multi-site retrofit roadmap (approved: reservations to March 2027)

#### "The NFA-500 doesn't fit our panels."
- Acknowledge: Correct. Different bracket and panel depth. I won't
  soften that
- Reframe: It's a scoped site visit, not a swap -- which is exactly why
  we're not setting an EOL date. You retrofit on your schedule
- Offer: Free site assessment with per-site cost and downtime window,
  whether or not you commit (approved for all installations)

#### "We just signed a three-year service agreement."
- Acknowledge: And we'll honor every month of it
- Reframe: The agreement covers service, parts, and safety updates to
  its full term. End-of-sale doesn't touch it
- Offer: Written confirmation of your end date from Legal (approved --
  standard letter available)

#### "Are we going to fail an audit over this?"
- Acknowledge: A fair concern with certified equipment
- Reframe: UL 508A and CE marking remain valid on installed units.
  End-of-sale is a commercial status, not a certification change
- Offer: Change-control documentation package for your quality records
  (approved -- Regulatory supplies within 10 business days)

#### "Will you brick our controllers like other vendors have?"
- Acknowledge: That's happened in this industry and the concern is earned
- Reframe: We have set no end-of-life date and will never remotely
  disable an installed unit. That's in the customer notice in writing
- Offer: Point them to the written commitment in the announcement
  (approved -- quote it directly)

#### "Can you extend spare parts past 2028?"
- Acknowledge: I understand you're planning past that
- Reframe: Parts are committed through December 2028. Beyond that we
  can't commit, because component supply is outside our control
- Offer: Quarterly parts-stock levels published so you can plan, plus a
  final buy option in 2028 (do not promise parts past 2028)

---

### 4. Channel Partner Brief

#### What partners need to know
- Last-time-buy window closes March 31, 2027
- Inventory buyback available through June 2027
- Service and warranty obligations unchanged
- Partners briefed March 6, public notice March 31

#### What partners can tell their customers
- Installed units are unaffected and stay serviced
- No end-of-life date has been set
- NFA-500 requires a site-specific retrofit
- Free retrofit assessments available now

#### What partners should NOT do
- Do not quote an end-of-life or shutdown date
- Do not promise NFA-500 drop-in compatibility
- Do not commit parts availability past December 2028
- Do not discount to clear inventory before buyback terms

---

### 5. Training Session Outline

- Duration: 90 minutes
- Audience: Sales, field service, account management, channel partners
  (separate session)
- Format: Presentation plus role-play

Agenda:
- [5 min] Why end-of-sale and not end-of-life
- [10 min] Phase walkthrough and what each date means
- [15 min] FAQ review, certification section emphasized
- [20 min] Objection role-play: bricking, mounting, audit concerns
- [10 min] Escalation paths and regulatory referral rules
- [10 min] Channel-specific: buyback, last-time-buy, forbidden claims
- [10 min] Open questions

---

### Assumptions to Validate
- Assumes Legal approved the standard confirmation letter
- Assumes inventory buyback terms are final with Finance
- Assumes Regulatory can meet the 10-business-day documentation SLA
- Assumes no service agreements extend past December 2028

What to notice

  • The FAQ gains a section the SaaS version doesn't have. "What about certification?" sits between contract and support questions because in a regulated context it drives real call volume — and a wrong answer creates a compliance problem, not just an unhappy customer.
  • Two objections end with an explicit prohibition. "Do not promise parts past 2028" and the partner brief's forbidden-claims list. At Level 3 the damage from an invented commitment is contractual, so the pack forbids as clearly as it authorizes.
  • The bricking objection is answered by pointing at the written notice. The strongest response isn't a talking point, it's a quotable sentence the company already published. Enablement works best when it points at commitments rather than generating new ones.
  • Partners are briefed 25 days before the public notice. March 6 versus March 31, stated in the header. Resellers with their own customer relationships need the lead time to prepare their own conversations.
  • Training allocates 20 minutes to role-play. The longest block. Reading objection handlers silently doesn't build the reflex — and "will you brick our controllers" is a question you want a rep to have already answered out loud once.

Source: SKILL.md on GitHub

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill is a documentation and planning tool for generating internal enablement materials during product transitions. No malicious patterns, data exfiltration risks, or code execution vulnerabilities were detected.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at d025768. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 2 months ago
argument-hint
[product being sunset, replacement, and key dates]
type
component
theme
eol-transition
Other metadata
intent
Generate the internal enablement materials customer-facing teams need before an EOL announcement goes out: a support FAQ, sales comparison talking points, objection-handling scripts using Acknowledge-Reframe-Offer, and an escalation playbook. Right-sized so a feature deprecation gets a one-page support note while a major sunset gets a full role-specific enablement pack.
best_for
[
  "Arming Support and Sales before the announcement, not five minutes after it",
  "Turning predictable EOL objections into honest, non-defensive responses",
  "Giving escalations a named path before the churn-risk calls start"
]
scenarios
[
  "We announce the sunset in three weeks and Support has nothing — what do they need?",
  "Sales keeps getting ambushed on our EOL; build them talking points and objection handling"
]
estimated_time
25-45 min

README badge

README badge for deanpeters/product-manager-skills/eol-internal-enablement