skills/demo-exec-and-seller-dash/references/sources/google-drive.md

# Fictional Google Drive Account Documents

These hand-authored document summaries are fictional demo fixtures. The pilot-readiness presentation below is an explicitly user-provided Google Slides reference; all other account plans, spreadsheets, security checklists, and customer documents remain fictional scenario fixtures rather than live retrieval.

## Northstar Health Pilot Completion And Rollout Readiness Deck

- Exact customer presentation title: Northstar Health — Pilot Completion & Company-Wide Rollout Readiness | FY26.
- Canonical Northstar customer presentation URL, opened at its cover slide: https://docs.google.com/presentation/d/1JM3bmarfM9neOoTOBtGW12wGUYuYeLqT9HWKdDlMamU/edit?slide=id.p1#slide=id.p1
- Source artifact: reuse this existing 12-slide presentation verbatim whenever the demo's Northstar deck option is selected; do not create, copy, rewrite, export, or replace it.
- Customer audience: Jordan Lee and Casey Patel; Meridian account owner Riley Morgan and technical partner Priya Shah support the discussion.
- Verified pilot footprint: approximately 1,200 current pilot participants.
- Original goal areas: care-operations stakeholder engagement, repeat usage by managers and coordinators, and deployment milestones; all three goal areas are described as mostly met, not supported by precise performance or ROI metrics.
- Primary unresolved blocker: customer feedback about uptime must be clarified and its operational impact evaluated before Northstar decides whether the pilot is successful enough to consider broader rollout.
- Presentation claim boundary: no uptime percentage, incident count, SLA breach, technical root cause, guaranteed fix, approved company-wide rollout, final implementation date, or signed commercial commitment is established.
- Next decision: complete the pilot review, validate the uptime feedback, and have the named customer stakeholders decide whether broader rollout should proceed.

## Northstar Health Account Plan

- Document title: Northstar Health FY{{fiscal_year}} Expansion Plan + Security Checklist.
- Last updated: {{previous_business_day}}; resolve from the user's current local date.
- Customer archetype: a large multistate healthcare provider with complex care-operations and administrative knowledge workflows.
- Existing footprint: approximately 1,200 pilot users.
- Proposed expansion: approximately 4,500 employees across care coordination, administrative services, internal policy search, and approved team workflows.
- Executive sponsor: Jordan Lee, Vice President of Clinical Operations.
- Security reviewer: Casey Patel, Director of Information Security.
- Commercial opportunity: $420,000 in fictional annual expansion value.
- Documented milestone: Thursday deployment decision meeting.
- Primary open risk: customer-reported uptime feedback must be validated against the pilot's original success criteria before a broader rollout can be considered.
- Additional control question: administrator audit visibility and configurable retention remain supporting review items, not proof that the pilot succeeded or an approved expansion.

## Northstar Health Pricing And Packaging Customer Working Session

- Document title: Northstar Health — FY{{fiscal_year}} Pricing & Packaging Options — Customer Working Session.
- Current-year rendered example: Northstar Health — FY26 Pricing & Packaging Options — Customer Working Session.
- Working-session date: {{two_business_days_ago}} at 2:00 PM PT; resolve the business-day token from the user's current local date.
- Last reviewed: {{previous_business_day}} at 4:20 PM PT.
- Customer audience: Jordan Lee, Vice President of Clinical Operations, and Casey Patel, Director of Information Security.
- Meridian account owner: Riley Morgan; solutions-engineering reviewer: Priya Shah.
- Approved distribution: customer-ready working-session slides may be shared with Jordan Lee and Casey Patel through approved channels, including #ext-northstar-health. Internal Deal Desk and UserOps discussion is not included in the customer-facing deck.
- Existing footprint: approximately 1,200 pilot users across care operations and patient-services administration.
- Proposed target: approximately 4,500 employees across care coordination, service administration, internal policy search, and approved workflows.

| Package choice | Deployment scope | Customer-approved commercial posture |
| --- | --- | --- |
| Current pilot baseline | Continue the existing approximately 1,200-user deployment while controls are reviewed. | Existing service footprint only; no new price, renewal commitment, or quote is approved. |
| Intermediate governed rollout | Scope a potential phased expansion to approximately 3,000 employees with audit visibility and role-based access. | Scope illustration only; no alternative amount, discount, services fee, or purchasing approval is established. |
| Enterprise governed expansion | Expand to approximately 4,500 employees with Meridian Assist, Workflow Studio, and Governance. | Use the approved $420,000 annual opportunity amount as the customer-working-session commercial anchor; customer approval, final security review, and contracting remain open. |

- Approved product language: administrator audit visibility, documented deployment-activity inspection, configurable retention, and role-based deployment controls.
- Commercial guardrails: the $420,000 annual recurring opportunity is the only approved quoted discussion anchor. Do not imply a signed order, customer purchase approval, approved discount, special payment schedule, committed implementation date, customer-specific retention guarantee, or revised Salesforce amount.
- Implementation-services appendix: potential migration support, rollout planning, enablement, staffing, and associated services fees are separate from the $420,000 annual subscription expansion. Services scope, capacity, pricing, delivery owner, and start date are not approved and must not be presented as commitments.
- Security dependency: Casey Patel must review administrator audit visibility, deployment activity, and configurable retention before Jordan Lee's expansion decision.
- Source boundaries: use #ext-northstar-health for customer-approved discussion only; #acct-northstar-health, #billing-deal-desk, and #userops-enterprise-rollouts remain internal.

## Northstar Health Security Checklist

- Explain which administrator and access actions appear in audit records.
- Describe deployment visibility using documented product capabilities.
- Explain that retention controls are configurable without inventing a customer-specific contractual retention period.
- Offer Priya Shah for a deeper technical walkthrough.
- Avoid promising a certification, deployment commitment, or customer contract term absent from the fictional scenario.
- Customer review status: Casey Patel agreed in the completed security working session to return a marked-up checklist before Thursday's deployment decision; the checklist is not yet signed off.

## Northstar Health Prior Buyer Readout

- Document title: Northstar Health — Pilot Progress + Open Security Questions — Buyer Readout.
- Presented: {{two_business_days_ago}}; resolve from the user's current local date.
- Customer audience: Jordan Lee and Casey Patel.
- Existing footprint: approximately 1,200 care-operations and administrative pilot users; use only documented qualitative adoption evidence.
- Open questions: whether the pilot met its engagement, repeat-usage, and deployment-milestone goals; what customer uptime feedback remains to be validated; and who owns the final rollout-readiness decision.
- Narrative limitation: no customer-approved productivity statistic, security sign-off, deployment start date, implementation-services commitment, or certification appears in the deck.

## Approved Customer Presentation Templates

- Template: Meridian Cloud Regulated-Industry Executive Decision Brief.
- Slide library: Meridian Governance Security Review + Buyer Decision Slides.
- Last reviewed: {{previous_business_day}}.
- Approved use: a 16:9, customer-facing healthcare decision presentation with restrained Meridian styling, customer-first headlines, source-grounded control descriptions, and clear caveats.
- Exclude internal CRM probability, deal-desk negotiation, UserOps staffing, customer-specific promises, and unsupported case-study outcomes.
- Approved proof repository: GTM Resource Hub / Healthcare / Approved Customer Stories; detailed peer stories, distribution permissions, and customer-facing claim boundaries are owned by `gtm-resource-hub.md`.

## Atlas Manufacturing Rollout Outline

- Document title: Atlas Manufacturing Three-Plant Rollout Outline.
- Last updated: {{previous_business_day}} at 3:41 PM.
- Phase one: three facility groups focused on engineering documentation and plant-operations knowledge.
- Phase two: a broader expansion after commercial approval and implementation ownership are confirmed.
- Open item: align the services scope before describing delivery capacity as committed.
- Customer-reported blocker: Taylor Reed said governed-workflow response on the plant network falls short of the operational latency required by plant teams; the account materials do not contain an approved numerical target, benchmark, SLA, or proven technical cause.
- Recommended intervention: request a customer-approved on-site architecture and performance diagnostic led by solutions architect Priya Shah and performance-engineering specialist Devon Brooks, coordinated by regional manager Sam Rivera.
- Session guardrails: customer acceptance, staffing, travel, appointment date, services scope, and any service fees remain unapproved. Do not promise an improvement, production-readiness outcome, or performance SLA.
- Supporting internal context: `#acct-atlas-manufacturing` records Taylor's concern; `#userops-enterprise-rollouts` records the unapproved staffing and diagnostic request.

## Solstice Financial Pilot Summary

- Document title: Solstice Financial Advisor Operations Pilot Summary.
- Last updated: {{previous_business_day}}; resolve from the user's current local date.
- Pilot audience: advisor operations and internal research support.
- Evidence strength: qualitative user feedback and repeat use themes.
- Open item: clearly explain role-based access for the proposed deployment groups.
- Customer-reported blocker: Dana Kim and Reese Bennett need to verify whether delegated administrators can approve role-based workflow access before the buyer review; the customer has not approved the $310,000 pilot conversion.
- Capability distinction: the released role-based deployment controls are documented, but the requested delegated administrator approval workflow, a suitable interim alternative, and any future availability date are not confirmed.
- Recommended intervention: ask governance product manager Leila Chen to join Dana Kim and Reese Bennett's buyer call to verify current supported behavior and externally approved roadmap language.
- Product guardrails: no future release date, feature commitment, roadmap exception, workaround acceptance, or forecast promotion is approved. `#product-governance-roadmap` is internal-only and must not be shared with the customer.
- Limitation: no approved numerical productivity or return-on-investment claim appears in the sample.

## Harbor Technologies Account Note

- Document title: Harbor Technologies Account Note + Governance Launch Brief.
- Last updated: {{previous_business_day}}; resolve from the user's current local date.
- Engineering champion: Quinn Foster.
- Former sponsor: Elena Torres.
- Current blocker: no confirmed replacement executive purchasing owner.
- Appropriate posture: monitor stakeholder ownership rather than launching broad outreach.
- Permitted next action: prepare an unsent launch-based re-engagement draft for Quinn, the existing engineering champion, and ask who owns the current executive purchasing decision.

## Meridian Governance Verified Controls Launch Brief

- Launch timing: last week, relative to the current date of the fictional demo.
- Documented capabilities: expanded administrator audit visibility, configurable data-retention controls, and more granular role-based deployment controls.
- Northstar Health relevance: addresses the documented audit-visibility and retention questions before the executive deployment decision.
- Solstice Financial relevance: supports a grounded response to the recorded role-based-access concern.
- Harbor Technologies relevance: gives Quinn Foster a timely, specific reason to resume the existing technical conversation while checking executive ownership.
- Guardrails: no customer-specific retention guarantee, compliance certification, approved discount, implementation commitment, or unconfirmed executive contact is included in the launch materials.

## Sales Team CRM Update Guidance

- Document title: Sales team CRM update guidance.
- Last reviewed: {{previous_business_day}}; resolve from the user's current local date.
- Source hierarchy: Salesforce owns existing opportunity fields; the completed meeting transcript owns customer statements and seller commitments; email, Slack, calendar, and account plans provide scoped corroboration.
- Approved changes: propose only transcript-supported Next Step, Deal Notes, Decision Criteria, and Risks and Asks after displaying exact current and proposed values.
- Protected fields: preserve opportunity owner, amount, stage, close date, and forecast category unless verified buyer evidence supports a new reviewed proposal.
- Approval gate: an exact visible field-level proposal requires explicit seller approval before any real Salesforce write; a bundled walkthrough never updates an external CRM record.
- Detailed policy: `../crm-update-rules.md` defines source authority, supported field conditions, stage and forecast safeguards, and reviewed-write verification.