A practical guide for platform engineers to manage vendor pitches efficiently at KubeCon.

Context and Why It Matters

KubeCon pitches are inevitable but manageable. Poor handling wastes time, creates decision fatigue, and distracts from technical learning. A structured approach reduces noise and surfaces actionable insights.

Actionable Workflow

1. Pre-Event Prep

   • Define Goals: List 2-3 technical pain points (e.g., “improve CI/CD throughput”, “simplify cluster lifecycle”).
   • Filter Targets: Use the KubeCon schedule/app to identify vendors aligned with your goals. Prioritize demos over sales pitches.
   • Block Time: Allocate 20% of your schedule to pitches; use the rest for sessions and networking.

2. During the Pitch

   • Ask Diagnostic Questions:
     • “How does this integrate with existing tooling like ArgoCD/Flux?”
     • “What’s your support model for air-gapped deployments?”
     • “Can you demo failure recovery, not just happy path?”
   • Take Structured Notes: Use a template (see Policy Example below) to capture key details.

3. Post-Event Triage

   • Score Vendors: Rate based on relevance, maturity, and fit (1-5 scale).
   • Share Summary: Brief your team with a 1-page memo highlighting top candidates and red flags.

4. Follow-Up

   • Request Trials: For top vendors, ask for sandbox access or a PoC plan.
   • Negotiate: Use notes to push back on pricing or scope (“Your demo lacked X, which we need”).

Concrete Policy Example

Pitch Evaluation Template

- Vendor: [Name]  
- Contact: [Name/Email]  
- Core Value: [1-sentence problem solved]  
- Tech Fit: [Integration points with existing stack]  
- Red Flags: [Immature features, vendor lock-in risks]  
- Next Steps: [Trial request, architecture review]  

Tooling

• CRM Lite: Use HubSpot or Notion to track vendor contacts and notes.
• Time Blocking: Google Calendar with 15-minute buffers between pitches.
• Decision Matrix: Google Sheets with weighted criteria (cost, support, ease of use).

Tradeoff: Rigidity vs. Serendipity

A strict workflow risks missing unexpected tools. Mitigation: Allocate 10% of pitch time to “wildcard” vendors recommended by peers.

Troubleshooting Common Failures

• Symptom: Overloaded with demos.
  Fix: Use a shared calendar; delegate pitches to team members with overlapping interests.
• Symptom: Vendors dominate time.
  Fix: Pre-send a “scope document” outlining your needs and time limits.
• Symptom: Post-event analysis paralysis.
  Fix: Use the scoring matrix to limit follow-ups to top 2 vendors.

Final Check

If a pitch doesn’t align with pre-defined goals or reveals critical gaps in 10 minutes, politely exit. Your time is better spent on sessions or hands-on labs.

Source thread: Going to KubeCon. Anyone mastered the art of getting pitched at all day yet?