Crozer Health — outreach play (Snowflake AE vs Uttam cold)
Last updated: 2026-03-30
Lead metadata (co-sell & owners)
| Field | Value |
|---|---|
| Co-selling with a partner? | Yes |
| Partner | Snowflake |
| Partner AE / contact name | [Add name + email from AE] |
| Partner SE or specialist (if any) | [Optional] |
| Brainforge owner | Uttam |
| CRM / Linear | [Link or ID] |
Use this block on every lead play so direct vs co-sell motion and partner sponsor are explicit. Blank template: ../_templates/lead-play-template.md.
Account research
How to refresh: Run Exa MCP (neural search tools as configured in Cursor) or WebSearch for Crozer Health, Crozer Health bankruptcy, Crozer Health Snowflake, Delaware County Crozer, and relevant titles (CIO, chief analytics, digital). Summarize only sourced facts; re-check within 30 days of outreach.
Research snapshot (as of 2026-03-30) — public sources; confirm with Snowflake AE before leaning on narrative
| Theme | Notes | Sources (examples) |
|---|---|---|
| System status | Public reporting through early 2026 describes financial distress, bankruptcy filing (Jan 2025) context, hospital closures (e.g. remaining hospitals closed spring 2025 per press), and county-level response (disaster declaration later lifted Feb 2026). | e.g. Philly Tribune — Penn Medicine / Delco funding delay closure; Delco Times — Crozer closure impact |
| Community / care displacement | Coverage of behavioral health / recovery volume shifts and FQHC load (e.g. ChesPenn) after Crozer exits. | e.g. Delco Today — ChesPenn; Delco Today — MVP Recovery |
| Implication for GTM | Do not pitch as a stable “four-hospital system” without AE confirmation. Ask the AE: which entity / which leader / which Snowflake workload (successor org, county, health plan, or retained IT) this intro targets. Adjust proof points to data continuity, migration, analytics for public-health or network partners if that matches reality. | — |
| One true sentence (only after AE confirms angle) | [Fill once you know whether the meeting is e.g. residual IT, RCM, affiliated network, or different account shell.] |
Context (Brainforge): Partner-sourced opportunity via Snowflake AE. Brainforge is a Snowflake + Fivetran partner; healthcare proof: operational EMR/journey work (Hyp Access), HIPAA-governed multi-site analytics (Ellie), intake + data foundation (MIDI), embedded data + experimentation (Eden). Full write-ups: ../../sunstone/CASE_STUDIES_MIDI_EDEN_HYPACCESS.md.
Recommendation
| Path | When to use |
|---|---|
| A. Warm intro from Snowflake AE | Default. Highest reply rate, honors partner motion, aligns to whatever Snowflake workload the AE is pursuing (EDW, new subject areas, Cortex, consumption). |
| B. Uttam cold | Parallel multi-thread after AE agrees to intro (different buyer), or if intro stalls 10–14 days and you have a named data/digital leader + verified email. Use Snowflake + healthcare compliance as credibility, not as “we know your stack” unless research confirms Snowflake. |
Do not lead cold email with a long case-study list. One proof line + one specific question beats three paragraphs.
Path A — Warm intro (Snowflake AE)
1) What to ask the AE (short note / call)
Use this so the intro is anchored to a workload, not a generic “meet a consultant”:
- Who at Crozer owns Snowflake (platform owner / enterprise analytics / IT)? Any digital / access / marketing analytics leader they co-sell with?
- Is the hook net-new Snowflake, expansion (new marts / Cortex / AI), or services around existing footprint?
- Can they cc both a data/platform contact and a digital or ops contact if two threads exist?
- Preferred format: email intro or Slack intro (shared partner/customer channel, group DM, or @-mention in an existing thread)—not “you should reach out” cold so Uttam can reply same day on-thread.
2) Forwardable blurb for the AE (email or Slack)
Use email for formal first touch; use Slack when you already collaborate with the AE in a Snowflake or account Slack (faster loop, same substance).
Email — Option 1 — Platform / analytics (default)
Subject: Intro: Crozer ⟷ Brainforge (Snowflake partner)
[Crozer contact name] — wanted to introduce Uttam Kumaran, CEO of Brainforge. They’re a Snowflake and Fivetran partner we work with on the services side: data platform, modeling, and analytics for complex organizations, including healthcare (HIPAA-aware pipelines, EMR-adjacent and operational analytics, multi-site footprints).
Uttam — [Crozer name] is [title / one line of context AE gives you].
I’ll let you two find time; happy to join a first call if useful.
Email — Option 2 — Digital access / intake / journey
Add one sentence before “I’ll let you two”:
They’ve done similar work mapping patient journey and intake data alongside EMR workflows—not theory, operational integration and reporting foundations.
Email — Option 3 — AI / Cortex / “modern analytics”
Add:
Brainforge also helps teams get governed data ready for analytics and AI use cases on Snowflake so pilots don’t die on bad semantics or compliance boundaries.
Slack — short variants (paste in thread; @ prospect + @ Uttam)
Slack — Platform / analytics (default)
@[Crozer] @[Uttam] — quick intro per our Snowflake thread. Uttam runs Brainforge (Snowflake + Fivetran partner): data platform, modeling, analytics—lots of healthcare (HIPAA-aware pipes, EMR-adjacent + ops analytics, multi-site). @[Crozer] — [title / one line from AE]. I’ll let you two grab time; ping me if you want me on a first call.Slack — Digital / intake angle (append one line):
They’ve also mapped patient journey + intake alongside EMR—not slideware, operational data + reporting.
Slack — AI / Cortex angle (append one line):
Strong on governed data for analytics + AI on Snowflake so pilots don’t die on semantics/compliance.
(AE fills @[Crozer], title/context; use real Slack handles.)
(AE should fill [Crozer name], title, and one line of context for email variants.)
3) Uttam — first reply on the intro thread (within 24h)
Keep it short; mutual-intro playbook: honor introducer, move fast, one clear CTA. Same copy works for email or Slack—trim sign-off if Slack norms are tighter.
[AE name] — thanks for making the intro.
[Crozer name] — good to meet you. We’re Brainforge’s team for data platform, analytics, and AI-ready foundations; we’re partnered with Snowflake and spend a lot of time in healthcare where HIPAA and source-system reality (EMR, scheduling, ops) matter as much as the warehouse.
If you’re open to it, I’d propose 20 minutes to hear what you’re trying to solve this half (Snowflake roadmap, a specific domain—access, ops, marketing analytics—or an AI pilot), and we can see if our build + embed model fits.
Here’s my calendar: [link] — or send a couple of times that work and I’ll move things around.
Adjust “this half” if AE gave you a sharper hook (e.g. “Cortex evaluation,” “new mart for X”).
Path B — Uttam cold (if no intro or multi-thread)
ICP titles to prioritize: VP / Director Data & Analytics, Chief Data Officer, Digital / Patient Access, CIO office (platform), or whoever Snowflake account team names.
Email 1 — pattern interrupt + Snowflake + healthcare
Subject options (pick one):
Snowflake + Crozer — quick introData platform work (healthcare / Snowflake partner)15m — analytics foundations (partner w/ Snowflake)
Body:
[Name],
I’m Uttam — I run Brainforge. We’re a Snowflake services partner and work with healthcare orgs where analytics has to respect HIPAA and messy EMR / ops reality—not just dashboards.
I’m reaching out because [one specific line from research: initiative, hire, event, 10-K theme, LinkedIn post — do not fabricate].
If you’re the right person for Snowflake roadmap or analytics foundations, worth 15 minutes? If not, who owns that on your side?
— Uttam
Brainforge | [calendar link]
Email 2 — bump (day 4–5)
[Name],
Brief bump — sent a note about Snowflake-side analytics / data foundation work in healthcare.
Still the right person, or should I be talking to someone on enterprise data / IT?
— Uttam
Email 3 — value + exit (day 10–12)
[Name],
Last note from me. We’ve helped health systems and clinic networks with governed pipelines, patient journey / ops data alongside EMR, and multi-site analytics—happy to share a 2-minute overview if timing’s wrong for a call.
If not a fit, no worries.
— Uttam
LinkedIn (optional, same week as Email 1)
- Connection note (300 chars max):
Uttam — Brainforge CEO. Snowflake partner; healthcare data platform + HIPAA-aware analytics. Saw [specific]; open to connect. - Follow-up DM after accept: one sentence + calendar, no pitch deck.
Case study one-liners (for calls / AE — not all in one email)
| Reference | One line |
|---|---|
| Hyp Access | EMR-centric patient journey and SOP ↔ system alignment; operational/clinical data visibility. |
| Ellie | Hundreds of sites, HIPAA, Azure-anchored pipelines, call + Amplitude attribution—governed marketing analytics. |
| MIDI | Intake / funnel analytics, Mixpanel, custom EMR + commercial telemetry, HIPAA-aware foundation. |
| Eden | Embedded data team, intake + experimentation, Customer.io / edge—high-velocity digital care (use if digital buyer). |
Execution checklist
- Confirm with AE: which legal entity / leader this intro targets (given public reporting on system stress — do not assume classic IDN pitch).
- Confirm with AE: intro vs. name-only, target buyer, and Snowflake angle.
- Research Crozer: one true sentence for cold or for AE context (public news, job post, conference).
- Log touchpoints in CRM; if Linear used for partner opps, link ticket.
- After first meeting: create or update
knowledge/sales/agents/feedback-sessions/icp-analysis-2026-03-30-crozer-snowflake-ae.md(or add a short outcome note here).
Related
- Lead play template:
../_templates/lead-play-template.md - Cursor skill:
.cursor/skills/lead-play/SKILL.md(research + grill pass) - Case studies:
../../../../gtm/sales/leads/sunstone/CASE_STUDIES_MIDI_EDEN_HYPACCESS.md - Snowflake partner context:
../../../../gtm/sales/partners/snowflake/transcripts/2026-02-26_account_map_brainforge_snowflake_e657fda9.md - Mutual intro patterns:
knowledge/sales/agents/playbooks/mutual-intro-playbook.md - Cold patterns:
knowledge/sales/agents/playbooks/cold-outbound-playbook.md