# Executive Dossier: David Park ## Quick-Reference Card --- ### Visitor Snapshot | Field | Detail | |-------|--------| | **Name** | David Park | | **Title** | SVP Technology | | **Company** | Apex Financial Group | | **Industry** | Financial Services | | **Company Revenue** | $11.6B | | **Employees** | 42,000 | | **Headquarters** | New York, NY | | **Account Tier** | Strategic | | **Account Health** | 62/100 (Declining) | --- ### Relationship Summary | Field | Detail | |-------|--------| | **VVIP Tier** | Gold | | **SAB Member Since** | Q1 2023 (3+ years) | | **SAB Board** | Strategic Technology Advisory Board | | **SAB Attendance (TTM)** | 3/4 (75%) | | **Executive Sponsor** | James Kim, VP Financial Services | | **Sponsor Last Touchpoint** | Jan 2026 (QBR attendance) | | **Engagement Score** | 68/100 | | **Relationship Stage** | Trusted (at risk -- declining) | | **Role in Buying Center** | Economic Buyer | | **Contract Value** | $2.9M ARR | | **Contract Renewal** | June 30, 2026 | --- ### Top 3 Strategic Priorities 1. **Hybrid Cloud Migration Recovery** -- Led the SAB discussion on migration reality gaps. Apex's core banking migration to OpenShift failed in January 2026, causing 6 hours of staging downtime and a rollback. David is publicly frustrated and quoted the failure as setting Apex "back three months." Needs a credible remediation plan before renewal. 2. **Platform Consolidation & Reliability** -- Apex runs three different internal platforms because teams never agreed on standards. David wants consolidation before investing further. Uptime and reliability are non-negotiable requirements given his trading floor background. 3. **Security Automation for Financial Compliance** -- CISO Karen Wu is exploring Ansible for SOC modernization. This represents an independent value track less affected by the migration failure. Potential $650K opportunity if the security org champions internally. --- ### Communication Style Profile | Dimension | Guidance | |-----------|----------| | **Style** | Concise and metrics-driven. Does not tolerate marketing fluff. | | **Technical Depth** | Deep -- former Goldman Sachs infrastructure lead. Will test presenters. | | **Format Preference** | Architecture diagrams over slides. Distributes agendas 48 hours in advance. | | **Meeting Preference** | Afternoon briefings (1:00-1:30 PM start). Never before 11 AM. Mornings reserved for trading floor oversight. | | **Communication Channel** | Phone first, then in-person. Does not respond well to long emails. | | **What Works** | Candid acknowledgment of problems, ROI data, competitor benchmarks, concrete timelines, architecture diagrams. Let him drive with questions. | | **What Doesn't Work** | Marketing language, overselling, glossing over the migration failure, vague commitments, sending junior presenters. | > **Critical behavioral note:** David is highly competitive and brings his own data. He will make pointed comparisons with competitor offerings. Be prepared for direct challenges. He respects expertise but will test every presenter in the room. --- ### Critical Flags | Priority | Flag | Detail | |----------|------|--------| | **CRITICAL** | Failed Migration | Jan 2026: Core banking workload migration to OpenShift failed. 6-hour staging downtime. Rollback required. Root cause: insufficient pre-migration assessment for stateful workloads. David escalated to executive level. Trust damaged. | | **CRITICAL** | Contract Renewal at Risk | $2.9M ARR renewal June 30, 2026 -- less than 3 months away. Account health declining (62/100). Renewal decision likely influenced by migration recovery. | | **CRITICAL** | Competitor Threat | Azure is actively pitching to Apex. Azure presenting to Apex board imminently. David is evaluating three vendors for AI governance tooling. Competitive displacement risk is real. | | **HIGH** | Engagement Score Declining | Score dropped to 68/100. Frustration with migration failure is the primary driver. David's team (Marcus Thompson, VP Core Banking Engineering) is skeptical. | | **MEDIUM** | Support Friction | Ansible playbook performance issue (ESC-4610) took 11 days to resolve. Neutral satisfaction. Compounds the migration frustration. | --- ### Active Pipeline | Opportunity | Stage | Value | Close Date | Notes | |-------------|-------|-------|------------|-------| | Hybrid Cloud Expansion -- Trading Platform | Negotiation | $2.1M | June 30, 2026 | Tied to contract renewal. Azure competing. At risk. | | Security Automation -- SOC Modernization | Discovery | $650K | Q3 2026 | CISO Karen Wu championing. Independent track. | **Total pipeline at risk**: $2.75M (plus $2.9M ARR renewal) --- ### Products Deployed - Red Hat Enterprise Linux - OpenShift Container Platform - Ansible Automation Platform - Red Hat Advanced Cluster Security --- ### Key Account Contacts | Name | Title | Engagement | Notes | |------|-------|-----------|-------| | **David Park** | SVP Technology | 68/100 | Economic buyer. Frustrated. Primary relationship. | | **Karen Wu** | CISO | 55/100 | Independent champion in security org. Less affected by migration failure. | | **Marcus Thompson** | VP Core Banking Engineering | 41/100 | Most impacted by migration failure. Currently skeptical. Must win back for renewal. | --- ### Recent Support History | Date | Severity | Summary | Outcome | |------|----------|---------|---------| | Jan 14, 2026 | P2 | OpenShift migration failure -- core banking workloads | Negative. Executive escalation. "Set us back three months." | | Feb 20, 2026 | P3 | Ansible playbook performance degradation | Neutral. Resolved in 11 days (slower than expected). | Support relationship is strained. Two incidents in two months, both contributing to declining sentiment. --- ### Competitive Intelligence | Competitor | Activity | Risk Level | |------------|----------|------------| | **Microsoft Azure** | Actively pitching hybrid cloud and AI to Apex leadership. Board presentation scheduled. | HIGH | | **Multiple vendors** | David evaluating 3 vendors for AI governance tooling. We may not be one of them. | MEDIUM | > **Competitive context:** Azure's pitch will emphasize managed services and reduced operational burden -- directly targeting the migration failure narrative. Our counter-positioning must focus on remediation credibility, open-source flexibility, and total cost analysis. --- ### Recommended Approach **Address the migration failure head-on in the first 10 minutes.** David respects candor and will lose patience if we try to deflect. Open with accountability, present the root cause analysis, and deliver a concrete recovery plan with a timeline. **Key messages:** 1. Own the migration failure -- present the completed RCA and specific remediation steps 2. Deliver a revised migration plan with risk mitigation for stateful workloads 3. Provide competitive differentiation data vs. Azure (TCO analysis, open-source flexibility, financial services references) 4. Present ROI benchmarks from comparable financial services migrations 5. Advance the security automation track with Karen Wu as an independent value proof point **Relationship goal:** Stabilize the relationship from Declining to Stable. Rebuild enough confidence to secure the $2.9M renewal and protect the $2.1M expansion deal. **Do not attempt to upsell or introduce new products.** This briefing is about recovery, accountability, and retention. --- *Compiled from: CRM (Salesforce), VVIP Roster, SAB Meeting Notes, Support Escalation Logs* *Data freshness: CRM export 2026-03-28 | VVIP roster 2026-03-15 | Support logs current* *Risk assessment: HIGH -- briefing is retention-critical* *Next refresh: Automated pre-briefing (T-24h)*