Skip to content

Savvy Batch Analyst Prompts

Repo: internal · Path: C:/Users/adam/savvy-batch-analyst-prompts/ · Owner: Adam Status: Active dev · % Done: 70 · Last commit: 2026-04-10 Deployed: not deployed (prompt/spec package)

What it is

A multi-analyst persona prompt system (v4, markdown + observational) that plugs into Ray Nawara's SavvyDealerDataWarehouse Rails Multi AI Agent Performance Analysis pipeline to produce weekly dealer performance reviews.

Why it exists

Dealer performance calls are the core SavvyDealer deliverable. Adam currently loses 12-28% of every 20-minute call navigating reports live. The personas must replace Adam on the call (not assist him) by pre-assembling conclusions, flagging cross-source data issues, and carrying continuity from the last call — so the live time is spent on dealer concerns, not report navigation.

How it works

Five prompts feed Ray's existing Rails pipeline: four persona analysts run in parallel via ConsultPersonaJob, then SynthesizeOpinionsJob emits the executive summary.

  • Four-role responsibility matrix: Sales (Inv→VDP + Shown→Sold), BDC (set rate + show-rate honesty check), Marketing (approx. cost per inventory-page visitor + total lead volume), Inventory (real-photo % + description %, with hybrid fallback).
  • v4 is markdown + observational — personas state what the numbers show and what the pattern means; they do NOT prescribe actions. Dealer GM decides.
  • Design philosophy: dealer trust lifecycle (skepticism 0-90d → establishing 90-180d → trusted 180+d, resets on new manager), 20-min call target, conclusion-first not journey-first, personas should REPLACE Adam not assist him.
  • Calibrated against a real Spinach call corpus (152 meetings, 1,912 events, 69 friction signals) — 11 patches applied to v4 based on findings (Google Ads #1 topic, CRM #1 friction source, "wrong data" = 47.8% of friction).
  • Totals first, segments on-demand. Prior-period benchmarks sufficient for default runs; trailing avg / peer set deferred to deep-dive mode.

What's done

  • 5 v4 prompts drafted and Spinach-calibrated (sales_analyst_v4.md, bdc_analyst_v4.md, google_ads_analyst_v4.md, inventory_analyst_v4.md, executive_synthesizer_v4.md).
  • PHASE2_WAREHOUSE_WORK.md — ordered warehouse data-gap worklist (Inv→VDP, approx CPIV, store_benchmarks, real_photo_pct/description_pct wiring, trailing avg, peer set, segments, etc.).
  • CASE_FOR_CHANGE.md — 30-min code ask to make synthesizer editable as an AiPromptTemplate, plus JSON-appendix hybrid option.
  • README_FOR_RAY.md handoff doc mapping each prompt to its Rails persona_* template.
  • SPINACH_CALIBRATION_NOTE.md with findings and patches.
  • Zip delivered to Ray: C:/Users/adam/Downloads/savvy-persona-system-v4-for-ray.zip.

What's next

  • v5 shift from analysis reports to pre-call briefs (conclusion-first, dealer-lifecycle-tagged, continuity from last Spinach recap).
  • Deploy v4 into /settings/ai_prompts GUI (batch edit vs. migration — Adam's call).
  • CASE_FOR_CHANGE item 1 green light before v4 synthesizer adoption.
  • Resolve BDC set-rate denominator (Ray's appointments / good_leads vs. v3 appointments / contacted).
  • Phase 2 warehouse work — sequence is Ray's call.

Where the code/content lives

  • C:/Users/adam/savvy-batch-analyst-prompts/sales_analyst_v4.md
  • C:/Users/adam/savvy-batch-analyst-prompts/bdc_analyst_v4.md
  • C:/Users/adam/savvy-batch-analyst-prompts/google_ads_analyst_v4.md
  • C:/Users/adam/savvy-batch-analyst-prompts/inventory_analyst_v4.md
  • C:/Users/adam/savvy-batch-analyst-prompts/executive_synthesizer_v4.md
  • C:/Users/adam/savvy-batch-analyst-prompts/PHASE2_WAREHOUSE_WORK.md
  • C:/Users/adam/savvy-batch-analyst-prompts/CASE_FOR_CHANGE.md
  • C:/Users/adam/savvy-batch-analyst-prompts/README_FOR_RAY.md
  • C:/Users/adam/savvy-batch-analyst-prompts/SPINACH_CALIBRATION_NOTE.md
  • v3 files retained for historical reference.

Integrations

Consumes ConsultationMetricsService payload (Lead performance, Google Ads, Facebook Ads, GA4, CallRail, inventory) from SavvyDealerDataWarehouse. Emits markdown into Rails Turbo Stream opinion rendering — no code changes required for four of five prompts. Spinach corpus drives calibration. Downstream consumer of persona output: dealer-facing batch reports and executive call briefs.

Don't rebuild this — extend it

v4 is the deployable markdown/observational handoff; evolve toward v5 pre-call briefs and deploy via Ray's AiPromptTemplate GUI rather than building a parallel persona system.