# B2B DECISION FORENSICS™ — ANALYSIS OUTPUT ## Deal: HR Tech | 3,500-person Manufacturing Co. | $180K ACV | Post-Demo Stall --- ## {DECISION BRIEF — 30-Second Readout} **Stall Classification:** {EXECUTION-GAP} trending toward {STRUCTURAL} if unresolved within 7–10 days. **Diagnosis:** The VP HR champion is almost certainly not stalling on conviction — she's stalling on *internal coordination*. Her "looking great, will share with team" message signals she's carrying the deal forward but has hit real friction inside the organization before coming back to you. The 11-day silence is a distribution problem, not a rejection signal. However, three of the four stakeholders have materially different epistemic systems, none of which were fully addressed in the demo, and the champion may be unable to translate your value proposition into their respective frames without explicit help. **Highest-Friction Role:** Head of IT Security. One-strike rule + prior breach incident = the highest burden-of-proof requirement in the buying committee, and the one most likely to create a quiet veto. **Reframing Leverage:** CFO and Plant Managers are reachable via evidence repackaging (TCO model, training-load benchmarks). Security is a gating condition, not a persuasion target — compliance documentation must close that lane entirely before the champion can move. **Priority Discovery Questions before next call:** 1. What specific stakeholders has the VP HR shared materials with, and what feedback has she received? 2. Has IT Security received the SOC2 Type II report and pen test results yet — or are they waiting? 3. Has a formal evaluation timeline or committee meeting been scheduled? --- ## {PHASE 1} — STAKEHOLDER EPISTEMIC MAP --- ### Stakeholder 1: VP HR — Champion **Justification Framework:** `EMPIRICAL` (primary) + `PRECEDENT` (secondary) **Behavioral Signal:** Cited employee NPS data as a metric baseline; referenced peer-company HR transformations as social proof; asked detailed integration questions signaling she has mentally committed to implementation feasibility. **Confidence:** HIGH (3 clear signals) **Tags:** {E} NPS data citation | {E} Peer-company references | {E} Integration question depth **Gatekeeper (who validates truth FOR her):** HR peer network and her own data dashboards. She needs peer-company case studies with comparable firmographics (manufacturing, 2,000–5,000 employees) and ideally a reference call with a counterpart HR leader who can speak to the rollout experience — not just the outcome. **Role-in-Deal:** Champion + Sponsor hybrid. She carries internal advocacy and has access to the economic buyer, but is likely not herself the economic buyer. **Note:** Her silence is the central diagnostic signal. The most probable explanation is that she shared the demo with one or more stakeholders and received pushback she was not prepared to answer. {H} She may be waiting to solve that before re-engaging with you, rather than asking for help — a common champion behavior in mid-market manufacturing cultures where showing vendor dependency is perceived as weakness. --- ### Stakeholder 2: CFO **Justification Framework:** `EMPIRICAL` (primary) + `PROCEDURAL` (secondary) **Behavioral Signal:** TCO 3-year model request indicates she thinks in capitalized cost, depreciation, and total commitment — not annual subscription line items. Vendor financial stability request signals this is a real buying concern in her frame, not a negotiating tactic. Prior SaaS over-run reference is a `PRECEDENT` negative signal — she has been burned by hidden costs before and is calibrating skepticism accordingly. **Confidence:** HIGH (3 clear signals) **Tags:** {E} TCO 3-year request | {E} Vendor stability docs | {E} Prior SaaS over-run reference **Gatekeeper (who validates truth FOR her):** Finance peer network, board-level precedent, and — critically — her own prior experience with SaaS sprawl. Your vendor financial docs will be cross-checked against public or semi-public information (Crunchbase, LinkedIn headcount trends, funding rounds). A CFO at a manufacturing firm at this ACV will not trust a one-pager; she wants audited figures or credible third-party signals. **Role-in-Deal:** Economic Buyer or co-Economic Buyer. She can kill this deal with silence or delay. She does not appear to be a blocker by disposition, but her `PROCEDURAL` secondary frame means she will not approve without a defined process artifact — specifically a TCO model in a format she can own and present to her own stakeholders. **{G}:** Has the TCO model been delivered? In what format — PDF, spreadsheet, call? If not delivered, this is the highest-urgency execution gap in the deal. --- ### Stakeholder 3: Head of IT Security **Justification Framework:** `PRECEDENT` (primary) + `PROCEDURAL` (secondary) **Behavioral Signal:** SOC2 + pen test request is standard, but the prior vendor breach citation and explicit "one-strike rule" language indicates this is not a routine checkbox — it is a genuine risk-weighted veto posture. He has personally experienced the consequences of trusting a vendor on security grounds and was wrong. His epistemic frame is structured around falsification: *you must prove absence of risk*, not presence of quality. **Confidence:** HIGH (3 signals; all pointing in the same direction) **Tags:** {E} SOC2 + pen test request | {E} Prior breach incident reference | {E} "One-strike rule" — explicit veto language **Gatekeeper (who validates truth FOR him):** His own technical review process, third-party security auditors, and — most importantly — his own judgment. He does not trust vendor-provided materials at face value. He will want to review the SOC2 Type II report directly (not a summary), and ideally wants a technical call with your security team, not a sales engineer. **Role-in-Deal:** Blocker / Technical Gatekeeper. He is not persuadable through narrative or business case. This lane must be closed through compliance documentation only. If the SOC2 and pen test results have not been delivered directly to him (not routed through the champion), this is a structural gap that explains the stall. **Critical:** Do not route security materials through the VP HR champion. That will be read as an attempt to manage his access to information, which will confirm his skepticism. --- ### Stakeholder 4: Plant Managers (collective) **Justification Framework:** `NARRATIVE` (primary) + `PRECEDENT` (secondary) **Behavioral Signal:** Floor-staff training time concern signals they are thinking in operational capacity — shift coverage, floor disruption, throughput impact. Prior tech rollout failures cited as precedent. They are not evaluating the HR platform; they are evaluating what it will cost *them* operationally during implementation. **Confidence:** MEDIUM (2 signals — specific behavior cited but limited individual differentiation) **Tags:** {E} Training time concern | {E} Failed prior rollout reference | {H} Likely consulted by VP HR as political buy-in, not formal evaluators **Gatekeeper (who validates truth FOR them):** Peer plant managers who have gone through similar deployments. A brief one-page case study showing training time metrics from a comparable manufacturing facility (e.g., "onboarding to productivity: 2.5 hours per employee, no shift disruption required") would outperform any feature deck. **Role-in-Deal:** End Users / Informal Influencers. They likely have a soft veto via the VP HR (she will not proceed if she believes plant adoption will fail), but they are not formal committee members. Their resistance is operationally, not strategically, motivated — and therefore addressable with specific evidence. **{G}:** How many plant managers are involved in the evaluation? Is their input formally solicited or informally consulted by the champion? --- ## {PHASE 2} — STALL POINT DIAGNOSTIC **Stall Classification:** {EXECUTION-GAP} with one potential {STRUCTURAL} thread **Primary Explanation:** The VP HR champion has shared the demo internally and is managing stakeholder feedback that she does not currently have the materials to resolve. This is an execution gap — the deal is not misaligned; the champion is undersupplied. **Secondary Risk:** If the Head of IT Security has not received compliance documentation directly and formally, the stall will convert to {STRUCTURAL} because his veto posture does not respond to indirect reassurance. A security hold-up in manufacturing IT — especially post a prior breach — can extend indefinitely without direct engagement. --- ### Burden-of-Proof Asymmetry | Stakeholder A | Approve threshold | Stakeholder B | Delay/block threshold | Conflict | |---|---|---|---|---| | VP HR | Peer-company precedent + integration feasibility | Head of IT Security | Full compliance documentation reviewed directly | Champion cannot close IT Security lane herself — she doesn't speak his language | | VP HR | Business case (NPS improvement, transformation) | CFO | 3-year TCO model in structured format | Champion may not have finance fluency to close CFO lane without a financial artifact | | CFO | Defined cost commitments | Plant Managers | Operational capacity concerns | Low structural conflict, but CFO approval without plant-manager buy-in creates a signed contract with poor adoption risk | **Hidden Conflict:** The VP HR champion is almost certainly trying to synthesize these four incompatible epistemic frames into a single internal pitch — and failing. She is not going to ask you for help with this unless you make it easy and non-exposing for her to do so. Her silence is self-reliance under pressure. --- ### {G} List — Discovery Questions for Next Call 1. "When you shared the demo with your team, what was the most common question or concern that came up?" *(Maps which stakeholder is causing the friction)* 2. "Has IT Security had a chance to review the SOC2 documentation directly — or would it be helpful for me to send it to them separately?" *(Unblocks security lane without forcing the champion to admit she hasn't managed it)* 3. "For the CFO's team, was the TCO model in the format they needed — spreadsheet or something else?" *(Diagnoses whether the financial artifact landed)* 4. "What would need to be true for you to feel ready to set a next step with the full committee?" *(Surfaces her internal map of what's blocking her)* --- ## {PHASE 3} — ACCEPTANCE THRESHOLD MAPPING --- **VP HR / Champion** - Type: Precedent + Empirical - Source: A peer HR leader at a comparable manufacturing firm (2,000–5,000 employees), ideally one who managed a similar implementation - Form: Reference call, 30 minutes — not a written case study alone - Volume: 1 reference with strong firmographic match outperforms 3 generic ones - Threshold: "I spoke with the HR Director at [comparable company] and she told me their training rollout took X weeks with Y disruption to floor operations." **CFO** - Type: Empirical + Procedural - Source: Your finance team, delivered in a native CFO format - Form: Editable Excel or Google Sheets TCO model — not a PDF she can't manipulate — plus a one-page vendor financial summary (ARR growth trend, customer retention rate, funding status or profitability signal) - Volume: One well-structured model she can own and present internally - Threshold: "I have a 3-year model I can run myself, and I have reviewed the vendor's financial stability documentation." - ⚠ Specificity note: The model must show Year 1 implementation costs (including internal IT time), Year 2–3 normalized costs, and a clearly labeled line for "assumed hidden costs / change management" — because her prior SaaS over-run experience means she will mentally add a buffer anyway. If you don't name it, she'll inflate it. **Head of IT Security** - Type: Procedural (only — he does not respond to narrative or business case framing) - Source: Your security/compliance team directly to him - Form: SOC2 Type II full report + pen test executive summary + a 30-minute technical call between your security lead and him — not a sales call - Volume: Full documentation, no summaries - Threshold: "I reviewed the SOC2 Type II report, spoke with their security team, and my questions were answered without deflection." - ⚠ Critical constraint: Do not send materials through the champion. Send directly. Offer the technical call explicitly. If he declines the call, that is a positive signal — it means the documentation was sufficient. **Plant Managers** - Type: Narrative + Precedent - Source: One comparable manufacturing deployment, expressed in operational terms - Form: A single-page "Implementation Impact Sheet" — not a feature sheet — showing: average time-to-productivity per employee, training format (self-service vs. facilitated), shift disruption metrics, and a 2-sentence quote from a plant manager or floor supervisor at the reference company - Volume: One example, high firmographic match - Threshold: "We've seen that a plant like ours can do this in X hours per employee without pulling people off the floor." --- ## {PHASE 4} — PER-STAKEHOLDER REFRAMING *Focusing on the two highest-friction roles: Head of IT Security and CFO* --- ### Head of IT Security — Reframing **4.1 Source Frame → Destination Frame** | | Source Frame (current) | Destination Frame (reframed) | |---|---|---| | Positioning | "Our platform is secure and compliant" | "Our security posture is independently verifiable — here is what you need to review it yourself" | | Evidence type | Vendor-asserted quality claims | Third-party audited documentation with direct access | | Interaction model | Champion-mediated | Direct security-to-security channel | | Burden | You must trust us | You can verify us without trusting us | **Content unchanged:** Feature set, pricing, timeline, integrations — none of these change. Only the channel and framing of the security conversation changes. **4.2 Non-Distortion Check** - ✓ Pricing claims unchanged - ✓ Capability claims unchanged - ✓ Timeline commitments unchanged - ✓ Risk caveats preserved — if there are any known SOC2 exceptions or findings, they must be disclosed in the report, not minimized - ✓ Competitive comparison honest - **Reframe passes.** **4.3 Champion Playbook for IT Security Lane** What the champion needs from you: - **Document:** SOC2 Type II full report + pen test summary, formatted for direct delivery (not routed through her) - **Ask:** "Would it be helpful if I sent these directly to your Head of IT Security so you don't have to be in the middle of a technical conversation?" — this relieves her of a lane she can't close - **Anticipated objection:** "Our security team has a lot of questions" → Response: "We'd welcome a 30-minute technical call between our security lead and yours — no sales people in the room." - **What NOT to send:** A marketing one-pager on "enterprise security" or a security FAQ. He will read this as avoidance. --- ### CFO — Reframing **4.1 Source Frame → Destination Frame** | | Source Frame (current) | Destination Frame (reframed) | |---|---|---| | Positioning | "$180K ACV investment in HR transformation" | "Here is the 3-year cost structure you can model yourself, including the variables you'll want to stress-test" | | Evidence type | Vendor-provided ROI projections | Editable model the CFO owns and controls | | Risk framing | Upside-led ("here's what you gain") | Cost-contained ("here's what you know vs. what is variable") | | Implicit message | Trust our numbers | Verify our numbers | **Content unchanged:** ACV, implementation timeline, scope — none change. Only the format and ownership model of the financial artifact changes. **4.2 Non-Distortion Check** - ✓ Pricing claims unchanged — the model must reflect actual ACV, not a discounted scenario - ✓ Capability claims unchanged - ✓ Timeline commitments unchanged - ✓ Risk caveats preserved — if implementation has variable cost components (e.g., data migration, custom integrations), these must appear as labeled line items in the model, not be absorbed into a flat "implementation fee" - ✓ Competitive comparison honest - **Reframe passes.** **4.3 Champion Playbook for CFO Lane** What the champion needs from you: - **Document:** Editable TCO spreadsheet + 1-page vendor financial summary - **Audience map:** She will show this to the CFO directly; she may not be in the room when the CFO reviews it — so the model must be self-explanatory - **Anticipated objection from CFO:** "What happens if we need more integrations than scoped?" → The model should have a labeled row: "Additional integration costs (variable, see scope assumptions)" with a reference to the SOW - **What NOT to send:** A PDF ROI deck with pre-calculated returns. The CFO wants a model she can break, not one she has to trust. --- **4.4 REFUSED MOVES — Minimum 2** 1. **Escalating above the champion to the CFO or CHRO directly.** Tempting given the 11-day silence, but bypassing the VP HR at this stage would signal distrust in her champion role and damage the relationship permanently. She is still the primary path to close. 2. **Manufacturing a deadline.** "Our Q2 pricing expires on [date]" or any variant — not recommended. The CFO and Head of IT Security are both empirically-oriented and will read this as pressure theater. The CFO has seen SaaS vendors use this tactic before; it will lower her trust in your commercial integrity. 3. **Sending a "just checking in" email without a specific value artifact.** A content-free follow-up after 11 days of silence will be interpreted as pipeline anxiety. Every outreach must deliver something: a TCO model, a security document, a reference contact, a case study — not a nudge. 4. **Framing security compliance as a competitive differentiator in messaging to the Head of IT Security.** He does not care that you're more secure than a competitor. He cares whether you are secure enough. Comparative framing activates skepticism in his epistemic system. --- ## {REFUSED INFERENCES — Minimum 2} 1. **"The champion has lost enthusiasm for the deal."** Considered and rejected. The behavioral evidence — NPS data citations, peer-company research, detailed integration questions — indicates a highly engaged champion who has done significant pre-work. Eleven days of silence following a "looking great, will share with team" message is more consistent with internal coordination difficulty than fading interest. Inferring lost enthusiasm would lead to premature escalation that could damage the champion relationship. 2. **"The CFO is the primary blocker."** Considered and rejected. The CFO's requests (TCO model, vendor stability docs) are procedurally standard for a $180K ACV decision at a manufacturing firm — they are not signals of resistance. She has a high burden-of-proof requirement, but there is no behavioral evidence of active opposition. Treating her as a blocker would lead to defensive over-explanation rather than simply delivering the financial artifact she asked for. 3. **"Plant managers are irrelevant to the buying decision."** Considered and partially rejected. They are not formal evaluators, but in a manufacturing environment, a VP HR will not advance a platform she believes will face adoption failure on the floor. Their informal veto via the champion is real, even if their formal role in the decision is limited. --- ## {HONESTY NOTES} - **Synthesis tags:** {MONNA-Analysis-2026} - **Tag distribution:** {E}: 12 | {H}: 2 | {G}: 4 - **Within-stakeholder variance disclaimer:** Plant managers are treated as a collective based on limited behavioral input. Individual plant manager variance could be significant; the {G} question about how many are involved and how formally is material to Phase 3 threshold design. - **Confidence ceiling:** The central diagnosis (champion undersupplied, IT Security lane unclosed) rests on high-{E} behavioral signals. The 11-day silence interpretation as "coordination difficulty" rather than disengagement is {H}-tagged and should be tested on the next call via the discovery questions in Phase 2. --- ## {VERIFICATION CHECK} - ✅ Every stakeholder has framework + behavioral citation - ✅ Stall classification is specific: execution-gap with IT Security structural risk - ✅ Acceptance thresholds are specific (editable TCO model, SOC2 Type II direct delivery, peer reference call with firmographic match) - ✅ Reframing passes non-distortion check for both high-friction roles - ✅ REFUSED MOVES list has 4 entries (minimum 2 met) - ✅ {G} list has discovery questions, not invented answers - ✅ No manipulation tactics recommended