Prompt Details
Model
(claude-4-5-sonnet)
Token size
3,152
Example input
[INITIATIVE_DESCRIPTION]: Migrating our flagship enterprise SaaS product from a perpetual license model to a subscription-based pricing model over the next two quarters. This affects revenue recognition, sales compensation, customer contracts, and product roadmap priorities.
[KEY_STAKEHOLDERS]: CEO, CFO, VP of Sales, VP of Product, VP of Customer Success, Head of Finance Operations, Top 3 enterprise customer accounts (by ARR), Sales team (40 reps on commission)
[ORG_TYPE]: corporate
[TIME_HORIZON]: 6 months, with go/no-go decision at next board meeting in 8 weeks
[OUTPUT_DEPTH]: full-playbook
Example output
# Force Field Analysis: Perpetual → Subscription Model Migration
---
## STEP 0 — DECISION BRIEF
**FIELD STATE:** VOLATILE
**RECOMMENDATION:** GO AFTER {CFO operational alignment + Sales compensation redesign}
**CONFIDENCE:** MEDIUM
**BIGGEST ASSUMPTION:** That the Top 3 enterprise accounts will accept contract renegotiation without triggering churn or triggering MFN (most-favored-nation) clauses that cascade pricing risk across the book of business.
**TIME-CRITICAL ACTION (next 7 days):** The CFO must privately commission a revenue recognition bridge model (ASC 606 perpetual → ratable) before the board meeting is framed. If the CFO presents to the board without this model, the narrative defaults to "revenue dip in Q1" and the board will kill the initiative on optics alone. Schedule that session this week.
---
## STEP 1 — LIFE SPACE MAPPING
### Visible Stakeholders
---
**CEO**
| Field | Detail |
|---|---|
| STATED POSITION | "We need to shift to subscription — it's the industry direction" |
| PERCEIVED SELF-INTEREST | Higher valuation multiple (ARR commands 8–12× vs. perpetual 2–4×), board confidence, competitive narrative |
| IDENTITY THREAT | LOW — CEO's identity is tied to strategic vision; this initiative *is* a CEO-level call. Risk is being seen as late to the shift, not wrong for doing it |
| VALENCE | +4 |
| ROLE | DECISION-MAKER |
| INFLUENCE WEIGHT | 5 |
---
**CFO**
| Field | Detail |
|---|---|
| STATED POSITION | "Subscription is the right direction. We need to plan the transition carefully." |
| PERCEIVED SELF-INTEREST | Cleaner revenue predictability long-term; but near-term: revenue dip under ratable recognition will surface in quarterly numbers *on their watch* |
| IDENTITY THREAT | **HIGH AND HIDDEN.** The CFO's professional identity is built on financial control and predictability. A model transition that introduces a "trough year" implies they failed to architect a resilient revenue model earlier. They will not say this — they will say "timing" and "operational readiness." Hear those words as identity protection, not operational concern. |
| VALENCE | +1 (stated), −2 (operational) |
| ROLE | DECISION-MAKER + GATEKEEPER |
| INFLUENCE WEIGHT | 5 |
> **This is the central paradox of the field.** The CFO is the most technically capable champion AND the most operationally restraining force. They can build the model that unlocks the board — or the model that kills the timeline. How you engage them determines everything downstream.
---
**VP of Sales**
| Field | Detail |
|---|---|
| STATED POSITION | "I support the strategic direction but we need to get compensation right first" |
| PERCEIVED SELF-INTEREST | Commission structure entirely built on ACV (annual contract value) of perpetual deals; subscription ACV is lower in year one even if LTV is higher. 40 reps follow their wallet — if comp isn't solved, the VP loses the team |
| IDENTITY THREAT | **CRITICAL.** The VP of Sales has built their entire organization, hiring profile, playbook, and personal brand around closing large perpetual deals. Enterprise sales is a specific skill set and identity. Subscription sales requires different motion (land-and-expand, lower initial close, multi-year nurture). This isn't just a comp change — it implies their team may be the wrong team. They will hear this initiative as "you're obsolete." |
| VALENCE | −3 |
| ROLE | INFLUENCER + GATEKEEPER (controls field access to 40 reps) |
| INFLUENCE WEIGHT | 4 |
---
**VP of Product**
| Field | Detail |
|---|---|
| STATED POSITION | "Subscription unlocks the roadmap investments we've been trying to justify" |
| PERCEIVED SELF-INTEREST | Predictable revenue = predictable R&D budget. Subscription also justifies product-led growth investments the VP has been lobbying for |
| IDENTITY THREAT | LOW-MEDIUM. Risk is being asked to reprioritize the roadmap for packaging/tier work (which feels like plumbing) over feature development (which feels like vision) |
| VALENCE | +3 |
| ROLE | INFLUENCER |
| INFLUENCE WEIGHT | 3 |
---
**VP of Customer Success**
| Field | Detail |
|---|---|
| STATED POSITION | "We're supportive but worried about how customers will react to forced migration" |
| PERCEIVED SELF-INTEREST | Renewal rates become the primary KPI of the business under subscription — CS becomes more powerful. But forced migration conversations are brutal, and CS absorbs the customer anger |
| IDENTITY THREAT | MEDIUM. If churn spikes during migration, CS owns the failure narrative even if the decision was made above them. They fear being handed a grenade and told to hold it. |
| VALENCE | +1 |
| ROLE | INFLUENCER + AFFECTED |
| INFLUENCE WEIGHT | 3 |
---
**Head of Finance Operations**
| Field | Detail |
|---|---|
| STATED POSITION | "There are significant systems changes required — billing, rev rec, reporting" |
| PERCEIVED SELF-INTEREST | Carries operational execution risk for a transformation they didn't design and can't fully control |
| IDENTITY THREAT | MEDIUM. If billing systems fail during migration, it's a Finance Ops failure. They are being handed execution risk for a strategic decision. |
| VALENCE | −2 |
| ROLE | GATEKEEPER (controls systems readiness timeline) |
| INFLUENCE WEIGHT | 3 |
---
**Top 3 Enterprise Accounts (by ARR)**
| Field | Detail |
|---|---|
| STATED POSITION | Varies by account — likely ranging from "we'd prefer to stay on perpetual" to cautious openness |
| PERCEIVED SELF-INTEREST | Perpetual licenses = predictable capex, no renewal risk, no price escalation. Subscription = opex reclassification (may be favorable) but perceived loss of control |
| IDENTITY THREAT | LOW individually, but their procurement leads have internal political capital tied to the contract structures they negotiated. Renegotiation implies they got a worse deal going forward |
| VALENCE | −1 to +1 (account-dependent) |
| ROLE | GHOST (in internal meetings) / DECISION-MAKER (for their own contracts) |
| INFLUENCE WEIGHT | 4 (churn risk is a veto-equivalent in board conversations) |
---
**Sales Team (40 reps)**
| Field | Detail |
|---|---|
| STATED POSITION | Quiet — waiting to see what comp looks like |
| PERCEIVED SELF-INTEREST | Near-term income protection. Subscription year-one ACV is structurally lower; reps fear a de facto pay cut regardless of how leadership frames it |
| IDENTITY THREAT | HIGH AND DIFFUSE. Enterprise reps define themselves by deal size. A $500K perpetual close is a career moment. A $50K ARR subscription start is not — even if the 5-year LTV is higher. Their professional identity, peer status, and hiring market value are all tied to perpetual deal size |
| VALENCE | −3 |
| ROLE | AFFECTED + EXECUTION-CRITICAL |
| INFLUENCE WEIGHT | 3 (collective) |
---
### Ghost Stakeholders — Surfaced
**Board of Directors**
| Field | Detail |
|---|---|
| IDENTITY THREAT | Board members who championed the *current* model in prior strategy sessions will experience the migration as an implicit critique of their prior judgment |
| VALENCE | +2 (strategically) / −1 (if presented without trough mitigation) |
| ROLE | GHOST → DECISION-MAKER at week 8 |
| INFLUENCE WEIGHT | 5 |
**Audit Committee (subset of Board)**
Specifically relevant because ASC 606 revenue recognition changes will require disclosure. The Audit Committee will scrutinize the revenue recognition methodology change independently of the CEO's strategic narrative. They are a parallel approval path that most change plans ignore until it's too late.
**External Auditors**
Any change in revenue recognition methodology triggers auditor involvement. Their timeline is not the company's timeline. If not engaged early, they become a hard blocker at the worst moment — during the Change phase.
**Investors / Analysts (if public or pre-IPO)**
Perpetual-to-subscription transitions are well-understood by SaaS-literate investors as a value-creating move — but they create a "rule of 40" dip year that triggers sell signals from less sophisticated holders. If this company has any secondary market or investor reporting obligations, this is a ghost force.
**Legal / General Counsel**
Customer contracts under perpetual model may contain evergreen clauses, MFN provisions, or upgrade rights. Legal is not on the stakeholder list but will become a hard gatekeeper the moment customer contract renegotiation begins.
**HR / Compensation Team**
The VP of Sales cannot redesign comp alone. HR owns the compensation framework and may have constraints (equity vesting, employment contract terms) that aren't visible to the sales org.
---
## STEP 2 — FORCE FIELD ANALYSIS WITH FEEDBACK COUPLING
### Driving Forces
| Force | Source | Magnitude | Stability | Coupling |
|---|---|---|---|---|
| Valuation multiple arbitrage (ARR > perpetual) | CEO, Board | 5 | ENTRENCHED | Strengthens CFO's long-term case; weakens board resistance |
| Competitive positioning (market moving to subscription) | CEO, VP Product | 4 | SHIFTING (accelerating) | Strengthens urgency framing; weakens "wait and see" restraint |
| Predictable revenue / R&D budget stability | CFO (strategic), VP Product | 4 | ENTRENCHED | Strengthens Finance Ops readiness case once modeled |
| CS strategic elevation (renewals become core KPI) | VP CS | 3 | FRAGILE (conditional on churn not spiking) | Can flip to restraining if early migrations go badly |
| Product roadmap unlock (PLG investment justification) | VP Product | 3 | SHIFTING | Strengthens VP Product as active champion |
**Σ Driving = 19**
---
### Restraining Forces
| Force | Source | Magnitude | Stability | Coupling |
|---|---|---|---|---|
| Revenue recognition trough (CFO operational resistance) | CFO, Head of Finance Ops | 5 | ENTRENCHED | Weakens board confidence; weakens Sales motivation if bonus pool shrinks |
| Sales compensation disruption (rep income risk) | VP Sales, 40 reps | 5 | ENTRENCHED | Directly coupled to execution speed; if unresolved, weakens VP CS (reps will undersell renewals) |
| Customer contract complexity / churn risk | Top 3 accounts, Legal | 4 | SHIFTING | Weakens board confidence; can trigger MFN cascade |
| Systems/operational readiness (billing, reporting) | Head of Finance Ops | 3 | SHIFTING (improvable) | Weakens CFO's operational confidence; creates delay risk |
| Board optics on near-term revenue dip | Board, CFO | 3 | FRAGILE (frame-dependent) | Central pivot point — can be flipped by the right revenue bridge narrative |
| Sales team identity / deal-size prestige loss | 40 reps, VP Sales | 3 | ENTRENCHED | Weakens execution quality even if comp is technically solved |
**Σ Restraining = 23**
---
### Net Force Calculation
- **Σ Driving = 19**
- **Σ Restraining = 23**
- **Net Vector = −4**
- **Field State: VOLATILE** — The net is negative, but several restraining forces are FRAGILE or SHIFTING, meaning targeted intervention can flip the field without requiring massive force increases. This is not a stuck field — it's a field with solvable blockers.
---
### Lewin's Leverage: Top 3 Restraining Forces by (Magnitude × Removability)
| Restraining Force | Magnitude | Removability | Priority Score | Why |
|---|---|---|---|---|
| Revenue recognition trough (CFO operational) | 5 | HIGH (solvable with modeling) | **25** | One well-constructed financial model changes CFO valence from −2 to +2 |
| Sales compensation disruption | 5 | MEDIUM (requires design + HR process) | **20** | Solvable but takes 4–6 weeks; must start now |
| Board optics on revenue dip | 3 | HIGH (frame-dependent) | **18** | Entirely a narrative problem, solvable once CFO model exists |
> These three forces are coupled. Solve the CFO financial model → the board optics problem dissolves → the CFO becomes a champion rather than a brake. The sales compensation problem runs in parallel and cannot wait for the CFO resolution.
---
### Feedback Loops
**Loop 1 — The CFO Flywheel (Virtuous if activated)**
CFO model built → Board narrative shifts from "dip" to "investment" → Board approves → CFO becomes public champion → Finance Ops gets mandate and resources → Systems readiness accelerates → Operational resistance weakens
**Loop 2 — The Sales Spiral (Vicious if unresolved)**
Comp redesign delayed → Reps sandbagging pipeline (holding perpetual deals to close under current model) → Q2 revenue artificially inflated (perpetual), Q3 cliff → CFO concerns validated → Board delays → VP Sales vindicated in resistance → Initiative stalls
**Loop 3 — The Customer Signal Loop (Balancing)**
If any Top 3 account churns during migration → Board treats it as market validation of risk → Restraining forces spike across the field → Even strong driving forces can't compensate. This loop auto-corrects the initiative toward caution. It is not inherently bad — it is telling you to sequence customer conversations *after* comp and board alignment, not before.
---
## STEP 3 — TOPOLOGICAL FIELD STRUCTURE
### Regions
**Region A — Strategic Leadership (High valence, high authority)**
Members: CEO, VP Product
Shared life space: They perceive the change as directionally correct and are willing to absorb transition costs for long-term positioning. They speak in competitive and strategic terms. They are frustrated by operational resistance they read as risk-aversion.
**Region B — Financial Control (Mixed valence, execution authority)**
Members: CFO, Head of Finance Operations, Audit Committee (ghost)
Shared life space: They process every change through the lens of what could go wrong on paper and in systems. They are not anti-change — they are anti-surprise. The revenue recognition trough isn't a strategic objection; it's a failure of imagination about how to present the story. Give them the model and they flip.
**Region C — Revenue Execution (Negative valence, execution-critical)**
Members: VP Sales, 40 Sales Reps, HR (ghost)
Shared life space: Their professional identity and income are inseparably tied to the current model. They do not experience this as a strategic shift — they experience it as a threat to their livelihood and professional worth. No amount of strategic framing reaches them. Only concrete comp design does.
**Region D — Customer Relationship (External, veto-equivalent)**
Members: Top 3 Enterprise Accounts, Legal (ghost)
Shared life space: They signed contracts based on assumptions that are now changing. Their concern is not ideological — it's contractual and political (internal procurement politics). They need a value narrative written for their CFO and procurement lead, not their technical buyer.
---
### Barriers
**Hard Barriers:**
- Region B → Region C: Finance doesn't set comp. Even if CFO supports the model, HR and the VP Sales own compensation redesign. There is no direct path from financial model approval to rep behavior change.
- Region D (external accounts) → Internal field: Customer feedback doesn't enter the internal discussion unless CS or VP Sales carries it in. Currently, that channel is controlled by Region C, which has a conflict of interest.
**Soft Barriers:**
- CFO → VP Sales: Historical tension between finance's desire for predictable revenue and sales' desire for flexibility in deal structures. If CFO is the messenger on comp changes, it will be read as finance dictating to sales.
- Region A → Region C: CEO and VP Product live in a strategic register that feels tone-deaf to reps who are worried about their mortgage payment. Direct communication from Region A to Region C will be heard as "we don't understand your world."
**Information Barriers:**
- The 40 sales reps have no visibility into the valuation multiple argument. They don't know (or care) that ARR trades at 10× and perpetual at 3×. This isn't stupidity — it's a different life space. Information that matters in Region A is noise in Region C.
- The board has no visibility into the customer contract complexity risk. They will approve this initiative with incomplete information unless someone (Legal, VP CS) briefs them on the MFN/cascade risk before week 8.
---
### Locomotion Paths
**To shift CFO from +1 (strategic) / −2 (operational) to +3 (active champion):**
Path = CEO → CFO (private session, revenue bridge model pre-built by an external SaaS CFO advisor or IB comparable)
Barrier = CFO must not be handed a model they didn't build. They will find holes in it and protect those holes as professional identity. The fix: CEO frames the session as "I need your expertise to build this," not "here's the model, does it work?" CFO must author the solution, not approve it.
**To shift VP Sales from −3 to −1 (workable neutrality):**
Path = CEO → VP Sales (1-on-1, before any group sessions) → VP Sales designs comp framework → HR validates → VP Sales presents to reps as their own solution
Barrier = VP Sales will not accept a comp model designed by Finance or HR. They will experience it as further evidence that their world is being managed away. The VP Sales must be the architect of the new comp structure, with constraints given, not prescribed.
Reframe: "You're not losing your model — you're getting ahead of where every enterprise SaaS company is going, and you're going to be the leader who figured out how to run this motion."
**To shift Top 3 Enterprise Accounts from −1 to +1:**
Path = VP CS (primary) + CEO (optional executive sponsorship call) → Account-specific value narrative
Barrier = These accounts cannot hear about this from their sales rep. The sales rep has a conflict of interest (their comp is changing) and the account knows it. VP CS is the trusted relationship owner here.
**To shift Board from +2 (strategic) to +4 (active mandate):**
Path = CFO (once converted) → Board pre-read → CEO presentation
Barrier = If CFO hasn't been converted before the board deck is written, the board will receive two conflicting signals (CEO strategic enthusiasm + CFO operational caution) and default to CFO's concern. CFO alignment is a prerequisite for board alignment, not a parallel track.
---
## STEP 4 — TEMPORAL DYNAMICS
### Known Triggers
| Trigger | Estimated Date | Forces Strengthened | Forces Weakened | Net Δ |
|---|---|---|---|---|
| Board meeting (go/no-go) | Week 8 | Board mandate (if aligned) / Board veto (if not) | Ambiguity / stalling | +5 or −5 |
| Q2 pipeline close | Week 6–8 | Sales sandbagging risk peaks here | Sales resistance | −3 if comp unresolved |
| External auditor engagement | Should be Week 2–3; risk if delayed to Week 6+ | Audit confidence | Finance Ops restraint | +2 if early, −4 if late |
| Sales comp redesign completion | Target Week 5 | VP Sales valence, rep execution | Region C resistance | +4 |
| First customer migration pilot | Month 4–5 | CS confidence, proof of concept | Customer churn fear | +3 or −5 (binary) |
| Contract review (Legal) | Should begin Week 1–2 | Legal readiness | MFN cascade risk | +2 if early |
---
### Critical Windows
**Most movable window:** Weeks 2–5. The field is currently in negative equilibrium but several key actors (CFO, VP Sales) are not yet entrenched in *public* opposition. Once the board meeting narrative forms (week 6–7), positions will harden.
**Field locks:** Week 7 (board pre-read distribution). After the board narrative is set, CFO and VP Sales will calibrate their public positions to the board framing. Changing their minds after that point requires a board-level reversal, which carries political cost.
**Point of no return:** If Q2 closes under current model with a strong pipeline (which sandbagging could artificially create), the CFO will have a "see, perpetual is working fine" data point. This is the single most dangerous outcome. The point of no return is approximately Week 8 if the field hasn't moved.
---
## STEP 5 — UNFREEZE → CHANGE → REFREEZE
### UNFREEZE PHASE (Weeks 1–6, ~35% of horizon)
**Goal:** Make the current model feel unsustainable — not wrong in isolation, but wrong relative to where the market is going and what the company needs.
**Tactics:**
1. CEO commissions a competitive positioning brief (3 slides): "What happens to our valuation, hiring, and customer acquisition cost in 18 months if we stay perpetual while competitors complete their transitions?" This is not propaganda — it is an honest stress test of the *status quo*, which is what Lewin meant by unfreezing.
2. CFO privately builds the revenue bridge model (see Step 7 sequencing). Converts CFO from brake to builder.
3. VP Sales gets a private 1-on-1 with CEO: not to sell the change, but to acknowledge the identity threat explicitly. "I know this changes what you've built. I want to build the new model *with* you, not hand it to you."
4. Legal and external auditors are quietly engaged to scope the contract and recognition complexity (removes the ghost blocker risk before it surfaces publicly).
**Exit Gate:** CFO valence moves to +3. VP Sales valence moves to −1. Restraining force sum drops below 18 (from 23). Legal has completed initial contract review with no showstopper findings.
---
### CHANGE PHASE (Weeks 5–16, ~50% of horizon)
**Goal:** Move from "this could work" to "this is happening."
**Tactics:**
1. Board meeting (Week 8) with CFO as co-presenter of the financial model. CEO presents strategy; CFO presents the bridge model as *their own work*. This is not theater — it is accurate. They built it.
2. VP Sales presents new comp framework to sales team — authored by VP Sales, validated by HR and CFO. Reps need to hear this from their leader, not from HR.
3. VP CS begins tiered customer communication: top 3 accounts get executive conversations first, before any broad announcement.
4. First customer migration pilot with a cooperative mid-tier account (not top 3 — too high-risk for a pilot). Use this to build CS muscle before the high-stakes accounts.
**Exit Gate:** Net force vector reaches +5. No critical stakeholder below −1. At least 1 of top 3 accounts has signed new subscription contract. Sales team has not experienced material attrition.
---
### REFREEZE PHASE (Weeks 16–24, ~30% of horizon)
**Goal:** Lock in the new equilibrium so the field doesn't revert.
**Tactics:**
1. Rev rec methodology formally documented and auditor-signed. This makes regression structurally difficult.
2. Comp plan for Year 2 published early — reps need to see that subscription isn't a one-year experiment.
3. First NRR (Net Revenue Retention) dashboard published company-wide. This is a ritual act: it signals that the organization measures itself differently now.
4. CEO publicly celebrates first "expansion ARR" win (a customer who upsold within subscription model). New identity anchor: we are an ARR company.
**Exit Gate:** Field survives the first bad quarter (there will be one — ratable recognition will show a revenue dip) without the board reversing course. If it survives that shock, the refreeze is complete.
---
## STEP 6 — COMMUNICATION PLAYBOOK
### Region B — CFO and Finance Operations
| Element | Content |
|---|---|
| **KEY MESSAGE** | "You are the architect of a model that makes this company more fundable, more predictable, and harder to attack — not the person who managed a revenue dip." |
| **EVIDENCE THAT MOVES THEM** | Comparable SaaS transitions with auditor-approved rev rec bridges. Show them the methodology, not just the outcome. CFOs trust process. |
| **CHANNEL** | 1-on-1 with CEO, followed by private working session with external SaaS finance advisor |
| **MESSENGER** | CEO (for mandate) + external advisor (for technical credibility — CFO will trust a peer more than their own CEO on a technical question) |
| **TIMING** | Unfreeze phase, Week 1–2 |
| **WHAT TO AVOID** | Never say "the revenue dip is temporary." That framing puts the CFO in the position of defending a dip. Instead: "the bridge model shows how we communicate this as planned investment, not underperformance." |
---
### Region C — VP Sales and Sales Team
| Element | Content |
|---|---|
| **KEY MESSAGE (VP Sales)** | "The leaders who figured out subscription sales are running the most valuable SaaS companies in the world right now. You have the chance to be that leader here." |
| **KEY MESSAGE (Reps)** | "Your deal size isn't shrinking — your account value is growing, and we're redesigning your comp so you get credit for the full value you create." |
| **EVIDENCE THAT MOVES THEM** | Show 3 examples of enterprise AEs at companies that made this transition and what happened to their OTE over 3 years. Peer data beats executive narrative every time. |
| **CHANNEL** | VP Sales: 1-on-1 with CEO. Reps: VP Sales town hall (reps will not believe this from anyone but their direct leader) |
| **MESSENGER** | CEO → VP Sales. VP Sales → reps. Do not skip the chain. |
| **TIMING** | VP Sales: Unfreeze, Week 2–3. Reps: Change phase, after comp framework is complete (Week 5–6) |
| **WHAT TO AVOID** | Never frame this as "the market is moving this direction." Reps hear: "your skills are becoming obsolete." Never show the Year 1 ACV comparison without the LTV and NRR story alongside it. |
---
### Region A — CEO and VP Product
| Element | Content |
|---|---|
| **KEY MESSAGE** | "The initiative is right. The sequencing is the risk. Your job for the next 6 weeks is to build the field, not announce the change." |
| **EVIDENCE THAT MOVES THEM** | The force field itself — specifically the Loop 2 sales spiral risk. Region A tends to underestimate execution drag. |
| **CHANNEL** | Private strategic alignment session |
| **MESSENGER** | This document (or a skilled change strategist delivering it) |
| **TIMING** | Now — before any public framing |
| **WHAT TO AVOID** | The temptation to announce the initiative broadly to "build momentum." Premature announcements harden positions before stakeholders have been worked. In a corporate field, announcement is not momentum — it's a forcing function that removes your maneuvering room. |
---
### Region D — Top 3 Enterprise Accounts
| Element | Content |
|---|---|
| **KEY MESSAGE** | "We're not changing your product or your relationship — we're giving you a contract structure that gives you more flexibility, not less, and we want to design your migration together." |
| **EVIDENCE THAT MOVES THEM** | Opex vs. capex reclassification benefit (real for many enterprise procurement teams). Contractual protections (price caps, rollback provisions in transition period). Reference from a peer company who made the move. |
| **CHANNEL** | Executive 1-on-1 (VP CS + CEO optional). Not an email. Not a CSM call. |
| **MESSENGER** | VP CS (trusted relationship) + CEO (signal of seriousness) |
| **TIMING** | Change phase, after internal alignment complete — not before |
| **WHAT TO AVOID** | Do not mention what other customers are doing or paying. MFN clauses are triggered by perceived inequity. Treat each account as if they are the only one in the conversation. |
---
## STEP 7 — CRITICAL PATH & SEQUENCING
### First Domino: The CFO
The CFO must move before anyone else — not because they have the most positive valence, but because they are simultaneously a gatekeeper AND a ghost force multiplier. A CFO who is publicly ambiguous at the board meeting will torpedo the initiative regardless of CEO enthusiasm. A CFO who co-presents the financial model is a 5× force multiplier on board confidence.
**Conversation Sequence:**
1. **Week 1: CEO → CFO (private)** — "I need you to build the model that makes this work. Not to validate mine — to build yours." Frame as authorship, not approval.
2. **Week 2: CEO → VP Sales (private, before any group session)** — Acknowledge identity threat directly. Offer VP Sales authorship of comp redesign. Set constraints, not prescriptions.
3. **Week 2–3: Legal + External Auditors engaged quietly** — Scope the contract complexity and rev rec methodology. Remove ghost blockers before they surface publicly.
4. **Week 3–4: CFO → Head of Finance Ops** — Once CFO is converted, Finance Ops resistance becomes resolvable. CFO gives mandate and resources.
5. **Week 4–5: VP Sales + HR design comp framework** — VP Sales authors, HR validates, CFO approves the financial model against it.
6. **Week 5: VP CS briefed on customer migration sequencing** — Identify lowest-risk pilot account. Brief VP CS on messaging framework.
7. **Week 6–7: Board pre-read (CFO + CEO co-authored)** — Revenue bridge model, comp framework summary, customer migration plan. No surprises at the board meeting.
8. **Week 8: Board meeting** — GO decision with CFO as co-presenter.
9. **Weeks 9–12: VP Sales town hall on comp** — Only after board approval. Not before.
10. **Weeks 12–16: Customer migration conversations begin** — Top 3 accounts get CEO/VP CS executive conversations. Pilot with mid-tier account starts.
---
### Biggest Blocker: VP Sales
**Force vector:** −3
**Identity threat:** "This initiative implies I've been running the wrong playbook and my team may be the wrong team."
**The ONE intervention:** CEO private conversation in Week 2 that offers VP Sales authorship of the new sales motion. Not consultation — authorship. "You are the person who will write the enterprise subscription playbook for this company. No one else has your relationships and your team. The question isn't whether we do this — it's whether you lead it." This is not manipulation. It is accurate. The VP Sales *is* the right person to lead this — if they choose to.
---
### Tipping Point
The field flips irreversibly when the following conditions are simultaneously true:
- CFO valence ≥ +3 (active champion)
- VP Sales valence ≥ 0 (neutral, not blocking)
- Board has issued formal mandate
- At least 1 top-3 account has signed subscription contract
At that point, the social proof dynamics shift. The remaining resistors (individual reps, Head of Finance Ops) no longer have a legitimate coalition to anchor to. The field has moved.
Estimated net force at tipping point: **+6 to +8**, which is above the MOVING threshold and stable enough to survive one adverse event.
---
## STEP 8 — SENSITIVITY ANALYSIS
| Assumption | If Wrong, What Changes | Confidence |
|---|---|---|
| Top 3 accounts will accept migration without triggering MFN clauses | MFN cascade could reprice 20–40% of ARR downward simultaneously. This is a GO → NO-GO flip. | LOW-MEDIUM |
| CFO can be converted through authorship framing | If CFO's resistance is political (they briefed the board against this already), no framing fixes it — requires CEO to manage the relationship directly, potentially including personnel conversation | MEDIUM |
| VP Sales accepts authorship offer | If VP Sales reads the offer as patronizing or has already decided to leave over this, the 40 reps will receive no trusted messenger for comp changes. Execution collapses. | MEDIUM |
| External auditors can approve rev rec methodology within timeline | Auditors have their own timeline. If they require a restatement review or find a complexity in existing contracts, they can delay the board approval regardless of internal alignment | MEDIUM |
| Sales sandbagging doesn't create a false Q2 perpetual peak | If reps hold deals to close under perpetual model and Q2 looks strong, the CFO will have a legitimate "the current model is performing" argument. This is the most underestimated risk. | LOW-MEDIUM |
| First customer pilot doesn't churn | If the pilot account churns, it becomes a board-level narrative anchor ("customer rejected the model") that is very difficult to overcome | MEDIUM |
---
### The Pivot Question
**Which single assumption, if wrong, flips GO to NO-GO?**
**The MFN / contract cascade assumption.**
If the Top 3 enterprise accounts have MFN clauses and a forced migration triggers them, the company faces simultaneous repricing risk across its highest-ARR customers at the exact moment its revenue recognition model is in transition. The combination of ratable revenue recognition starting (reducing recognized revenue) AND MFN-triggered price reductions on existing ARR would create a financial picture no board could approve. This scenario warrants a dedicated legal review in Week 1–2, before any other work proceeds.
---
### Confidence Interval on Net Force
| Scenario | Conditions | Net Force |
|---|---|---|
| **Best case** | CFO converted, comp solved, no MFN issues, VP Sales leads the motion | **+9** |
| **Expected case** | CFO partially converted, comp framework complete but imperfect, 1 of 3 accounts resistant | **+3 to +5** |
| **Worst case** | CFO publicly ambiguous, VP Sales resigns or goes passive-resistant, MFN issue surfaces at board | **−7 to −9** |
**Assessment:** This is a fragile field. The best case and worst case are both plausible. The expected case is slightly positive but not robust. This is not a situation where you can afford to skip the sequencing — the difference between best and worst case is entirely determined by whether the Week 1–5 groundwork is done correctly. The initiative is sound. The execution risk is high.
> **Final note on the corporate calibration:** In a corporate field, politics > logic and CYA dynamics are real. The CFO's operational resistance is not irrational — it is *rational self-protection* in a world where quarterly numbers are career outcomes. The VP Sales' resistance is not obstruction — it is *accurate threat perception*. The correct response to both is not to argue them out of their position but to redesign their position so that their self-interest and the initiative's success are the same thing. That is the entire job of the change strategist here.
By purchasing this prompt, you agree to our terms of service
CLAUDE-4-5-SONNET
✅ Built on Lewin's Field Theory and Force Field Analysis — a documented academic framework, not a generic 2x2 matrix
✅ Surfaces ghost stakeholders (board members, regulators, predecessors) that visible-only analysis misses
✅ Distinguishes stated position from perceived self-interest from identity threat — the third layer is where most change initiatives die
✅ Models feedback loops between stakeholders so you see second-order effects before they hit you
✅ Includes sensitivity analysis with a pivo
...more
Updated 2 weeks ago
- Reviews for this prompt (1)
