skills/demo-exec-and-seller-dash/references/northstar-followup-meeting.md

# Fictional Northstar Health Meeting Follow-Up

This transcript, goals, participants, CRM values, and proposed updates are fictional demonstration data. No live call recording, Salesforce opportunity, calendar event, customer email, or account document was accessed.

## Meeting Record

- **Meeting:** Northstar Health Expansion & Security Review.
- **Date:** {{two_business_days_ago}}; resolve from the current demo date.
- **Related decision checkpoint:** {{next_thursday}}.
- **Opportunity:** Northstar Health — FY{{fiscal_year}} Governed Workflow Expansion.
- **Current CRM owner:** Riley Morgan.
- **Current amount:** $420,000.
- **Current stage:** Security review.
- **Current forecast category:** Best Case.
- **Current close date:** {{next_thursday}}.
- **Attendees:** Riley Morgan, Strategic Enterprise Account Executive; Jordan Lee, Vice President of Clinical Operations; Casey Patel, Director of Information Security; Priya Shah, Solutions Engineer.
- **Primary meeting goal:** Determine whether Northstar's 1,200-user pilot met its original engagement, repeat-usage, and deployment-milestone goals and clarify customer uptime feedback before considering a broader rollout.
- **Secondary meeting goals:** confirm the executive buying sponsor, identify the customer-feedback validation owner, cover supporting control questions, and leave with a dated seller/customer next step.

## Reviewed Source Context

- **CRM: Salesforce:** the existing Northstar Opportunity establishes the exact record, Riley Morgan as owner, $420,000 amount, Security review stage, {{next_thursday}} close date, Best Case forecast, and current Next Step.
- **Call notes: Granola:** the selected completed meeting transcript establishes what Jordan Lee, Casey Patel, Riley Morgan, and Priya Shah actually said and agreed.
- **Email: Gmail:** Jordan Lee's pilot-scorecard request, customer uptime concern, and decision timing provide customer-side corroboration without establishing final pilot, rollout, or security approval.
- **Customer-shared and internal communication: Slack:** `#ext-northstar-health` captures Jordan Lee's customer-visible request; internal-only `#acct-northstar-health`, `#billing-deal-desk`, and `#userops-enterprise-rollouts` separately confirm specialist support, the approved $420,000 commercial anchor, and unapproved implementation capacity. Never expose internal channel messages to customer participants.
- **Team guidance and commercial documents: Google Drive:** the existing `Northstar Health — Pilot Completion & Company-Wide Rollout Readiness | FY26` presentation, `Sales team CRM update guidance`, `crm-update-rules.md`, and the separate Northstar pricing deck document original pilot goals, open customer feedback, exact-field review, protected opportunity values, and unapproved services.

## Condensed Transcript

**Riley Morgan:** Our goal today is to review whether the 1,200-user pilot met its original engagement, repeat-usage, and deployment goals and understand the customer uptime feedback before discussing a broader rollout.

**Jordan Lee:** The pilot's engagement, repeat usage, and deployment milestones are mostly where we wanted them, but our team still has uptime feedback that needs to be understood before we can decide whether a broader rollout makes sense.

**Casey Patel:** I want to understand the uptime concern our users raised and what it means operationally. I also need to review administrator audit visibility and retention. I am not approving a rollout or signing off today.

**Priya Shah:** I can review the existing pilot-readiness deck, help clarify the customer-reported uptime concern, and walk through the documented controls. We should not infer a technical cause, uptime percentage, SLA breach, guaranteed fix, or contractual retention promise.

**Riley Morgan:** I'll send the existing pilot scorecard and coordinate a review of the customer uptime feedback with Priya by next Thursday. Casey, can you and Jordan Lee review those findings before the deployment decision?

**Casey Patel:** Yes. We can review the pilot criteria, the reported customer feedback, and the supporting controls before Jordan Lee's decision meeting. I am not confirming pilot success or final approval until that review happens.

**Jordan Lee:** That works. The potential broader scope is roughly 4,500 employees, but do not change the commercial proposal or imply the rollout is approved until the pilot-readiness questions are resolved.

## Grounded Outcome

- **Business outcome:** Northstar remains interested in expanding from 1,200 pilot users to approximately 4,500 employees.
- **Economic/business sponsor:** Jordan Lee is the confirmed executive sponsor; the transcript does not establish a new contract signer or purchasing approver.
- **Decision criteria:** the original engagement, repeat-usage, and deployment milestones must be reviewed, customer uptime feedback and observed impact must be clarified, and supporting administrator controls must be validated.
- **Confirmed customer action:** Jordan Lee and Casey Patel will review the pilot scorecard and reported uptime concern before the deployment decision.
- **Confirmed seller action:** Riley Morgan will share the existing pilot-readiness presentation; Priya Shah will support customer-feedback and controls validation.
- **Remaining blocker:** customer uptime feedback remains unresolved; pilot success, rollout approval, and security sign-off have not been confirmed.
- **Commercial values:** $420,000 opportunity value and the existing close date remain unchanged.
- **Prohibited inferences:** do not claim an uptime percentage, outage or incident count, SLA breach, technical root cause, guaranteed fix, compliance certification, agreed retention period, signed expansion, confirmed implementation date, final approval, or a committed forecast.

## Salesforce-Ready Next Step

- Attendees: Jordan Lee (VP, Clinical Operations); Casey Patel (Director, Information Security); Riley Morgan; Priya Shah
- Takeaways: the existing 1,200-user pilot's original goals are mostly met, but the proposed 4,500-user expansion requires customer uptime feedback and supporting controls to be validated.
- Next steps: Riley Morgan to share the existing pilot-readiness presentation by {{next_thursday}}; Jordan Lee, Casey Patel, and Priya Shah to review the customer feedback before the deployment decision.

## Proposed Review-Only Salesforce Changes

| Field | Current value | Proposed value | Source and rationale |
| --- | --- | --- | --- |
| Next Step | Validate pilot success and open uptime feedback before the decision meeting. | Riley Morgan to share the existing pilot scorecard and review reported uptime feedback with Jordan Lee, Casey Patel, and Priya Shah before {{next_thursday}}. | Transcript: Riley Morgan and the customer participants explicitly agreed on the owner, action, and checkpoint. |
| Deal Notes | Pilot-readiness and uptime questions pending before expansion decision. | Engagement, repeat usage, and deployment milestones are mostly met; broader rollout remains contingent on clarifying customer-reported uptime feedback, with Priya Shah supporting validation. | Transcript: Jordan Lee and Casey described the original goals and unresolved concern; Priya offered technical support. |
| Decision Criteria & Purchase Process | Pilot success and Security review required. | Validate the original pilot goals, customer-reported uptime feedback and observed impact, and supporting administrator controls before the executive deployment decision. | Transcript: the customer identified the original success criteria, open feedback, and required review process. |
| Risks and Asks | Customer uptime feedback pending validation. | Pilot success and rollout approval remain open until Riley and Priya clarify the reported uptime concern with Jordan Lee and Casey Patel. | Transcript and account-team Slack identify the blocker and available specialist without establishing an incident or technical cause. |

Keep **Stage = Security review**, **Amount = $420,000**, **Close date = {{next_thursday}}**, **Forecast category = Best Case**, and the existing account owner unchanged. A real write requires the exact opportunity, confirmed supported fields, explicit user approval, and verification after the approved update.