Snowflake CRM tech stack

Snowflake CRM is not a product pitch — it’s the ops layer I built when Beehiiv’s utility rate dropped below 10%. These tools cover data, deliverability, first-party analytics, background work, and build throughput without a separate API shop or multi-tenant auth tax. Full scored reviews live in the playbook; this page is the short map. For why I built it and what I’m learning, see Snowflake CRM.

Supabase

What it does in Snowflake CRM

• Single hub for content, workflows, CRM records, and subscriber data
• Edge functions instead of a standalone API layer
• One hard-coded UUID — egocentric permissioning, no multi-user RLS abstraction
• Webhooks from Postmark and other services land here first

Monthly cost: free tier

Playbook: Supabase review → (full score coming soon) · Semantic search: pgvector on connections and transcript chunks today — dedicated vector DB is Pinecone (live scored review; on deck for deeper Steven OS2 integration)

Postmark

What it does in Snowflake CRM

• Outbound newsletter and automation sends across multiple domains without wrecking reputation
• Dynamic templates — not locked into Beehiiv-style blocks
• Open, click, and bounce analytics via webhooks back into Supabase
• Selective email escalation into additional webhooks when a message needs routing

Monthly cost: ~$14

Playbook: Postmark review → (live scored review) · peer: Resend

PostHog

What it does in Snowflake CRM

• First-party cookies on my domains — tracking I control and disclose in privacy/terms
• Session capture across content, booking, and gated surfaces before anyone logs in
• identify on login with CRM subscribers.id — anonymous page history backfills onto the same person
• Engine edge function pulls PostHog activity into Connections for prep-before-meetings
• Closes the loop with Postmark click tokens — email click → site behavior on one timeline

Monthly cost: free tier (generous at hobby scale)

Playbook: PostHog review → (live scored review)

Inngest

What it does in Snowflake CRM

• Staggered, multi-worker email delivery — not one big CRON blast
• Lead-magnet signup → automation sequence (the Beehiiv feature I thought would be hardest to replace)
• Retries, concurrency, and job history without building my own queue
• Fan-out for anything that shouldn’t block the UI or an edge function

Monthly cost: usage-based (hobby-scale)

Playbook: Inngest review → (live scored review)

Cursor

What it does in Snowflake CRM

• Vibe-coding the architecture — about three hours a day for four days to first usable stack
• MCP bench wired into Supabase, Postmark, and the rest so ideas ship across the whole instance
• Screenshot-and-roadmap workflow: Beehiiv and Calendly features marked up, redacted, rebuilt
• Token-cost estimate before committing — then another month integrating Astro and four sub-apps

Monthly cost: tokens (variable)

Playbook: Cursor review → (live scored review)

Also on the card: ImprovMX (~$8/mo) for multi-domain aliases into Gmail and outbound SMTP — mail routing, not the CRM core. Calendly replacement (BookTime — booking + CRM tags) was the hardest migration: Vibecoding Calendly? Really? → · stack context in Snowflake CRM.