# Executive Dossier: Ziggy Stardust-Chen ## Quick-Reference Card --- ### Visitor Snapshot | Field | Detail | |-------|--------| | **Name** | Ziggy Stardust-Chen | | **Title** | VP Platform Engineering | | **Company** | Quantum Pretzel Corp | | **Industry** | FinTech / Crypto | | **Company Revenue** | $890M | | **Employees** | 4,200 | | **Headquarters** | Miami, FL | | **Account Tier** | Strategic (at risk) | | **Account Health** | 55/100 (Declining) | --- ### Relationship Summary | Field | Detail | |-------|--------| | **VVIP Tier** | Silver | | **SAB Member Since** | Q1 2024 (stepped down Q4 2025) | | **SAB Board** | Alumni -- Financial Services Advisory Board | | **SAB Attendance (TTM)** | 1/3 (declining before departure) | | **Executive Sponsor** | Aisha Patel, Director Strategic Accounts | | **Sponsor Last Touchpoint** | Feb 2026 (Defensive call -- renewal risk) | | **Engagement Score** | 55/100 (declining) | | **Relationship Stage** | Trusted -> at risk of Favorable (downgraded) | | **Role in Buying Center** | Economic Buyer | | **Contract Value** | $1.4M ARR | | **Contract Renewal** | May 15, 2026 (CRITICAL -- 2 months out) | --- ### Top 3 Strategic Priorities 1. **Platform Reliability for 24/7 Crypto Trading** -- Quantum Pretzel runs a crypto trading platform with zero tolerance for downtime. Any incident has direct revenue impact (roughly $120K per minute during peak volume). Ziggy is under constant pressure from the trading desk and the board. 2. **Cost Optimization Under Board Pressure** -- Crypto market volatility has squeezed margins. Board has mandated a 15% infrastructure cost reduction. Ziggy is actively evaluating vendor consolidation and exploring cheaper alternatives. This is the primary driver of the renewal risk. 3. **Reduced Vendor Dependency** -- Ziggy has publicly stated in SAB meetings that "too many eggs in one basket" is a strategic risk. Interested in multi-vendor architectures and escape hatches. AWS is actively courting them with this narrative. --- ### Communication Style Profile | Dimension | Guidance | |-----------|----------| | **Style** | Blunt, remote-first, zero tolerance for corporate jargon | | **Technical Depth** | High -- hands-on engineer who still commits code | | **Format Preference** | Async-first, video calls if needed, casual dress | | **Meeting Preference** | No meetings before noon (night owl), prefers afternoons | | **Communication Channel** | Signal, Matrix, or email. NOT Slack. | | **What Works** | Direct language, honest acknowledgment of failures, remote options | | **What Doesn't Work** | Corporate speak, morning meetings, performative account management | --- ### Critical Flags | Priority | Flag | Detail | |----------|------|--------| | **HIGH** | Contract Renewal Risk | $1.4M ARR renewal May 15, 2026. 2 months out. Ziggy has not committed to renew. Aisha's Feb defensive call did not get a commitment. | | **HIGH** | Competitive Threat | AWS Solution Architect embedded at Quantum Pretzel for 3 weeks. Working on a migration proposal. This is a full-court press from AWS. | | **HIGH** | Departed SAB | Ziggy left SAB in Q4 2025 citing 2 undelivered commitments (platform cost calculator, multi-vendor reference architecture). Stated reason was "loss of trust." | | **OPPORTUNITY** | Re-engagement Signal | In the Feb defensive call, Ziggy hinted at returning to SAB "if we demonstrate accountability." This is the retention opening. | --- ### Active Pipeline | Opportunity | Stage | Value | Close Date | Notes | |-------------|-------|-------|------------|-------| | Contract Renewal | Negotiation | $1.4M | May 15, 2026 | At risk. Competitive pressure from AWS. Ziggy has not committed. | | Platform Reliability Tier Upgrade | Discovery | $340K | Q3 2026 | Paused pending renewal decision. Contingent on trust rebuild. | **Total pipeline at risk**: $1.74M --- ### Products Deployed - OpenShift Container Platform - Red Hat Enterprise Linux - Ansible Automation Platform - OpenShift Data Foundation --- ### Recent Support History | Date | Severity | Summary | Outcome | |------|----------|---------|---------| | Mar 03, 2026 | P2 | OpenShift etcd latency during high trading volume | Resolved in 4 days. Ziggy noted "slow response" in ticket comments. | | Jan 18, 2026 | P2 | Storage performance degradation | Resolved. Customer tone in tickets has become more terse. | Support relationship is strained. Ziggy's team is filing more tickets and less satisfied with response times. --- ### Recommended Approach **Lead with direct, unvarnished acknowledgment of the dropped commitments.** No spin, no soft pedaling. Open the briefing with: "We owe you an apology. Here are the two things we promised that we did not deliver. Here is what we have done about it. Here is our concrete plan to prevent this in the future." **Key messages:** 1. Present concrete remediation for both dropped commitments (platform cost calculator and multi-vendor reference architecture) -- completed or in-flight 2. Present a clear retention offer with specific accountability structure (e.g., named executive owner with monthly check-ins) 3. Offer a SAB re-invitation with a guaranteed charter for follow-through 4. Address cost optimization directly with a credible pricing conversation, not a sales pitch 5. Do not bring anyone from account management or sales enablement to this briefing. Engineers and executives only. **Hard rules for this briefing:** - ZERO corporate speak. No "partnership journey," no "value realization," no "strategic alignment." - Remote attendance must be offered. Ziggy may not travel. - Afternoon start time. Ziggy does not do mornings. - Direct accountability -- name the person who owns each commitment going forward. **Relationship goal:** Save the $1.4M renewal by demonstrating accountability. Secure at minimum a renewal intent letter by end of briefing. Stretch goal: return to SAB and unlock the $340K tier upgrade. --- *Compiled from: CRM (Salesforce), VVIP Roster, SAB Alumni Notes, Renewal Risk Analysis, Engagement History* *Data freshness: CRM export 2026-04-08 | VVIP roster 2026-03-15 | Renewal risk updated 2026-04-01* *Next refresh: Automated pre-briefing (T-24h)*