Skip to content

Dealer CRM (Productized SaaS)

Repo: savvydealer-adam/dealer-crm · Path: C:/Users/adam/dealer-crm · Owner: Adam Status: Active dev · % Done: 50 · Last commit: 2026-03-10 Deployed: Cloud Run (not yet public)

What it is

The next-gen, multi-tenant CRM SaaS that dealers use themselves — distinct from the internal ai-crm that SavvyDealer uses to run the agency. This one is a product we sell.

Why it exists

Dealers asked for a lightweight, AI-native CRM without the VinSolutions/Reynolds overhead. Rather than retrofit the internal agency CRM for external sale, Dealer CRM was started clean with multi-tenancy, Gemini AI, and dealer-centric workflows from day one.

How it works

Stack: React + Vite + TS (client), Express + TS (server), Drizzle ORM, Postgres, Google GenAI SDK (@google/genai), Cloud Run. - Multi-tenant from the ground up — tenant isolation baked into schema - AI Command Center with Gemini-powered natural-language processing (added 2026-03-10) - client/ — Radix UI component library, TanStack Query, forms with react-hook-form + Zod - server/ — Express API - script/build.ts — custom build orchestrator - Vitest for tests

What's done

  • Core schema + auth + multi-tenant scaffolding
  • Dealership/contact/lead CRUD
  • AI Command Center (natural-language queries, actions) via Gemini
  • Docker/Cloud Run deploy target

What's next

  • Harden multi-tenancy (row-level security, tenant admin UX)
  • Billing/subscription layer for external customers
  • Import tools (pull from common dealer CRMs)
  • Sales + onboarding flow — this is productized, so signup/trial matters
  • Not yet differentiated from ai-crm in the public roadmap — need a clear product page on www.savvydealer.com

Where the code lives

  • Client entry: client/src/App.tsx
  • Server entry: server/index.ts
  • Schema: shared/schema.ts
  • Build: script/build.ts, Dockerfile, cloudbuild.yaml
  • Tests: vitest.config.ts

Integrations

  • Gemini API — AI Command Center
  • Dealer CRM is NOT the internal agency CRM — it does not share a DB with ai-crm
  • Future: webhooks out to dealer's existing tooling (DMS, marketing, etc.)

Don't rebuild this — extend it

This is the ONE productized CRM for external dealers. Any dealer-facing CRM feature belongs here, not in ai-crm. Keep the agency data model (ai-crm) separate from the product data model (dealer-crm).