EBR Builder

I am preparing a QBR/EBR contribution for [COMPANY NAME], a [INDUSTRY] company. Step 1 -- Check connected sources first: If you have access to any of the following, search them before going to public sources: - My email or calendar for recent conversations, meeting notes, or follow-ups related to [COMPANY NAME] - Any shared drives, folders, or CRM records I have access to that contain account notes, call recordings, or customer documents for this account - Any Slack or Teams channels related to this account Step 2 -- Fill gaps with public research: For anything not covered by internal sources, use publicly available information: recent earnings calls, press releases, LinkedIn posts from their leadership, news coverage, job postings (which often signal priorities), or their own website. Based on everything you find, identify their top 2-3 business priorities right now that a CTO, VP Engineering, or technical executive would care about: reliability, developer productivity, platform consolidation, compliance, cost reduction, AI adoption, or similar. For each priority, give me: - A one-sentence summary of the priority in the customer's own language where possible - The signal that indicates this is top of mind (internal note, earnings quote, job posting, news item) - How an observability or monitoring solution could connect to it Additional context I am providing: [PASTE ANY NOTES FROM DISCOVERY OR PREVIOUS MEETINGS]

I need to write 2-3 value win statements for a QBR/EBR with [COMPANY NAME]. Step 1 -- Check connected sources first: Before using my notes below, search any sources you have access to: - My email or calendar for messages from [COMPANY NAME] contacts that mention outcomes, results, or feedback - Any CRM records, account notes, or shared folders for this account that might contain usage data, support tickets resolved, or success metrics - Any call recordings or transcripts where they described what improved If you find specific metrics or quotes from the customer themselves, prioritize those -- they are far more credible than our own claims. Step 2 -- Use my notes to fill any gaps: [PASTE YOUR NOTES -- rough bullet points, Salesforce activity log, call notes, anything] For each win, write: - Headline: one sentence, business outcome first, metric included where possible (e.g. "P1 incident MTTR reduced by 64% since Payments team deployment") - Supporting detail: 1-2 sentences explaining what changed, for which team, and why it matters to the business Write for a VP or CTO audience. Avoid product feature names and technical jargon. Every sentence should answer "so what?" from a business perspective.

I am building an expansion narrative for a QBR/EBR with [COMPANY NAME]. Step 1 -- Check connected sources first: Search any sources you have access to before relying on what I provide below: - My email, calendar, or meeting notes for conversations where [COMPANY NAME] contacts mentioned gaps, frustrations, future plans, or things they wish were in place - Any CRM records or account documents that describe their environment, roadmap, or strategic initiatives - Any previous QBR or EBR notes or slide decks for this account that might show what was discussed before If you find specific quotes from the customer about where they want to go or what is missing, use those. A recommendation grounded in their own words lands very differently than one that comes only from our side. Step 2 -- Use the context I am providing: - Their current maturity level: [e.g. Core Deployed -- Payments team fully instrumented, Infrastructure not started] - What is working well: [PASTE VALUE WINS] - Their stated business priorities: [PASTE PRIORITIES] - Expansion opportunity I am considering: [DESCRIBE WHAT YOU WANT TO SUGGEST] Write: 1. One sentence describing the expansion from the customer's perspective -- what gap it closes, not what product we would sell 2. Two to three sentences explaining why this maps to the priorities they have stated, using their language where possible Write it as a technical recommendation from a trusted advisor. No upsell language.