Partner Talk Track Kit

🔍 Uncovering an Observability Use Case — Without Mentioning Any Vendor

This talk track is designed for your partner to use before any product enters the conversation. The goal is to uncover real pain around monitoring and observability so you can earn the right to propose a solution. No product names, no vendor pitches — just good questions that surface problems worth solving.

The Opening Frame (30 seconds)

"We work with a lot of engineering teams, and one pattern keeps coming up: the tools they use to monitor their systems end up creating as much work as they save. I'm not here to pitch you anything — I'd just like to understand how your team handles observability today. If there's a better way to do it, great. If not, you've lost nothing."

💬 Discovery Question Bank

Choose 3–4 questions based on what you know about the account. Start broad, then go deep on whatever draws the strongest reaction.

1. Visibility & Coverage

Goal: understand how complete their monitoring picture actually is.

• "When something goes wrong in production, what's the first thing your on-call engineer does? Where do they go to start diagnosing?"
• "How many different tools does your team check during a typical incident? Are they all in one place, or are people switching between tabs and systems?"
• "Do you have a single view of your infrastructure health right now — or is that picture spread across multiple tools?"
• "Are there parts of your stack you'd say you're flying blind on — things you know you should be monitoring but haven't gotten to yet?"

2. Cost & Complexity

Goal: surface the hidden tax of running monitoring infrastructure.

• "How many engineers are involved in keeping your monitoring stack healthy — not using it, but maintaining it? Upgrades, storage, plugins, scaling?"
• "If those engineers weren't doing that work, what would they be building instead?"
• "Have your monitoring costs surprised you in the last year? Any unexpected spikes in storage, ingestion, or licensing?"
• "What percentage of your infrastructure budget goes toward the tools that watch the rest of the infrastructure?"

3. Incident Response & Speed

Goal: quantify the pain of slow diagnosis and resolution.

• "Think about your last major incident. How long did it take to go from 'something's wrong' to 'here's the root cause'? What slowed that down?"
• "When an alert fires, does your team trust it? Or is alert fatigue a real thing?"
• "Can your engineers correlate a metric spike with the corresponding log entries and traces — or does that require manual detective work?"
• "How much of your incident response time is spent gathering data versus analyzing it?"

4. Scale & Future State

Goal: understand where they're headed and whether current tools will break.

• "As your infrastructure grows, how confident are you that your current monitoring will scale with it?"
• "Are you adopting Kubernetes, microservices, or serverless? Has that changed what you need from monitoring?"
• "If you were building your monitoring stack from scratch today, what would you do differently?"
• "What's the one thing about your current setup that frustrates your team the most?"

5. Security & Governance

Goal: surface compliance and access control gaps.

• "Who has access to your monitoring dashboards today? Is that controlled centrally, or is it more ad hoc?"
• "If an auditor asked you to show who changed what in your monitoring configuration last quarter, could you produce that?"
• "Do you have any compliance requirements — SOC 2, HIPAA, PCI — that affect how you handle monitoring data?"

🎯 Signals to Listen For

These responses indicate real pain worth pursuing. When you hear them, go deeper — don't rush to a solution.

🌉 Bridging to a Deeper Conversation

Once you've uncovered pain, use one of these bridges to transition to a follow-up meeting. Still no vendor name needed — just the promise of a relevant conversation.

"Based on what you've described — [reflect their specific pain back to them] — it sounds like there are some meaningful gains on the table. We work with a platform that addresses exactly this. Would it be worth 30 minutes for us to walk through what a better setup could look like for your team, side by side with what you have today?"

"That's really helpful context. I think there's a conversation worth having about how teams in your position are solving this — without ripping out what's working. Can we schedule a short session with one of our solutions architects to explore it?"

🚀 Opening Hook — From OSS to Cloud

Use this when the account already runs Grafana OSS or is new to Grafana entirely.

"Your team already chose Grafana — and for good reason. But most OSS deployments eventually hit a ceiling: the engineers running the stack are spending more time maintaining observability than actually using it. We're seeing teams reclaim that time by letting Grafana Cloud handle the undifferentiated work — upgrades, HA, scaling, plugin management — so they can focus on the things that actually move the business forward."

🎯 Three Pain Seeds

Pick the one that best fits the account based on your discovery conversation.

1. The Hidden Cost Angle

Best for accounts with growing infrastructure

"Here's the question we keep hearing from teams like yours: how many engineers are dedicated to maintaining your observability stack? Not using it — maintaining it. Upgrades, scaling storage, troubleshooting compatibility issues. Those are hours that aren't going toward building features your customers actually see. If that number is more than zero, it's worth a conversation."

2. The Security & Governance Angle

Best for regulated industries or enterprises

"Open-source Grafana is powerful, but it wasn't built for enterprise security out of the box. No SAML, no RBAC, no data source permissions. As your team scales and compliance requirements tighten, that gap becomes a real operational risk. Grafana Cloud includes all of that — SSO, role-based access, audit logging — without requiring a separate Enterprise license."

3. The "What You're Missing" Angle

Best for teams that think OSS is "good enough"

"OSS gives you the building blocks, and that's solid. But Cloud unlocks capabilities that don't exist in the open-source version: AI-powered root cause analysis with Grafana Assistant, integrated SLO management, Adaptive Telemetry to control costs, turnkey observability for Kubernetes and applications, and incident response workflows — all connected. Teams that have been on OSS for years are often surprised by how much the managed platform has evolved beyond what they know."

🤝 Bridge to Discovery Meeting

"We're not asking you to rip anything out. The product is the same core — your dashboards, your alerts, your queries all carry over. What we'd love is 30 minutes to walk through what your current stack looks like and show you specifically where Cloud would save your team time and unlock capabilities you don't have today. No commitment — just a side-by-side."

📊 Proof Points

Anonymized and approved for external use.

🛡️ Objection Handling

✉️ Suggested Email Opener

For your partner to send after a discovery conversation or cold:

💡 Tips for Your Partner