Stakeholder Profiles.

What Matters to Kush

• Outcomes, not tickets. When Kush speaks, Krishna shuts up. He operates at strategic level — skills, memory, self-improving agents, agent chaining vision.
• Risk mitigation. Cyber security background. Core question: "Is this vendor going to blow up in my face?"
• Deprioritized A.6 and A.10 (Jun 22) in favor of SOC for AI. He sets portfolio priority.

Key Decisions Made

• Defined "institutional knowledge" concept for agents (May 7)
• Defined deployment model, memory framework, agent chaining vision (May 7)
• SOC for AI takes priority over Vitals Dashboard (Jun 22)

Engagement Rules

• Schedule through Tony. Expect long lead time on calendar.
• Show outcomes, not features. Video evidence + live URLs.
• Don't surface ticket-level detail — that's Krishna's world.

What Matters to Krishna

• Operational metrics: MTTD, MTTR, FP/TP rates, time-per-alert (21 min → 5 min target).
• A.6 Vitals Dashboard was his #1 priority before Kush deprioritized it for SOC for AI.
• Agent latency: Raised concern about Kindo agents at 14-min median vs Swimlane's 6-min. Target: 8 minutes.
• Won't give requirements directly — routes to Adelina (back office, currently on maternity leave).

How to Engage

• Tony sends questionnaire + sprint cadence visual directly.
• Krishna routes questionnaire to the right person per agent.
• May be invited to Sprint 1 demo depending on PoC quality (Tony decides).
• San Francisco portfolio meeting (late Aug) is on his turf — prepare accordingly.

Why Nathan Matters

• "Eyes and ears for Kush" — if Nathan flags a problem, Kush hears it immediately.
• "Equally if not more important" than Krishna for deployment success (Kush's words).
• Critical for first 5–7 client deployments alongside Harish.
• Only person who really sees platform issues as they happen in production.

Engagement Approach

• Tony's program-level interaction — biweekly with Charlie, Zun, Matthew Lew.
• Don't bypass him. If Nathan is unhappy, Kush knows before you do.
• Show him production readiness, not concepts.

Why Zun Matters

• Key program-level voice — Tony specifically named him for the new program-level interaction.
• Can speak to what's technically feasible and what their team actually needs.
• Charlie noted Zun could build a basic discovery agent quickly — he understands the tech.
• Currently the engineering contact for agent design sessions.

Engagement Approach

• Technical peer of Charlie. Speak in engineering terms.
• Include in agent design sprint sessions (Option 1 method).
• His input validates feasibility before committing scope.

Why Matthew Matters

• Key program-level voice — Tony named him alongside Nate and Zun.
• SDM perspective: operational delivery, timelines, resource allocation.
• Bridges gap between engineering decisions and delivery execution.

Engagement Approach

• Include in program-level interactions with Charlie.
• Delivery-oriented — speak to timelines, milestones, blockers.

Role

• Krishna's requirements person — delivery and quality.
• Would normally be the one to fill out detailed agent requirements questionnaires.
• Currently on maternity leave — questionnaire routing must go through Krishna → Zun/Rahul instead.

Impact on Sprint

• Her absence means requirements may be slower or less detailed.
• Zun and Rahul are the fallback contacts for technical requirements.

Role

• Leads the threat monitoring function — owns the SOC analyst workflow that agents A.1–A.5 automate.
• Primary SME for SOC for AI Discovery Agent requirements.
• Best contact for understanding current analyst workflows, alert triage, and operational pain points.

Engagement Approach

• Agent Design Sprint sessions (Option 1) — walk through how analysts do the job today.
• Can validate whether the SOC for AI agent output matches real operational needs.

Role

• India-based, driving go-to-market for Cyber Digital Analyst.
• Likely Tony's Channel Enablement contact.
• Connects the agent work to commercial rollout and client-facing positioning.

Role

• Client deployment lead alongside Nathan for the first 5–7 production deployments.
• Named directly by Kush as critical for initial rollout.

Role

• SDM and client delivery leader for HP — the first Dedicated MSS (Fortune 100) production deployment.
• HP deployment is happening now and is the proof point for the Dedicated MSS model.

Role

• Already moved firewall provisioning to Kindo at an insurance company — existing proof point.
• Demonstrates cross-service-line adoption potential beyond D&RaaS.