Skip to content

Internal Devs — Kat / Brian / Lucas

Who this is for: SavvyDealer internal team building AI-native tools alongside Adam.

Your work complements Adam's portfolio. These pages are placeholders until you share repo URLs — please drop them to Adam so he can fill in.

Kat — AI Notes Tool + AI Slides Tool

AI Notes Tool

Related existing work: dealerpulse

dealerpulse is SavvyDealer's current notes + action-items system — Next.js, Yjs collaborative notes, Freshdesk webhook sync. Before building a parallel notes tool, read its 1-pager. Options:

  1. Extend dealerpulse — add your AI layer (summarization, entity extraction, action-item inference) as a module of the existing app.
  2. Replace dealerpulse — if your design supersedes it, propose a migration path with Adam.
  3. Complement dealerpulse — if your notes tool serves a different use case (e.g., meeting transcription vs. dealer-call recap), define the seam clearly.

Option 3 is the default; option 1 and 2 both require Adam sign-off.

Your repo: placeholder — Kat, send Adam the URL.

AI Slides Tool

No direct overlap in Adam's portfolio — this is a new slot.

Your repo: placeholder — Kat, send Adam the URL.

When you write the 1-pager, lean on: - stock-image-project for OEM jellybeans, brand guides (don't fabricate brand assets) - media for asset storage - Adam's persona design philosophy (conclusion-first, not journey-first, 20-min-call framing) — if slides are generated for dealer reviews, match that cadence

Hard rule: no vendor-filler vocabulary in generated slides ("optimize / leverage / move the needle" etc. — Adam mocks this on calls).

Brian — Google Ads AI Work

Related existing work: ppc-assistant

ppc-assistant is SavvyDealer's existing Google Ads campaign builder + analyzer (Python/Typer CLI, pip-installable). It already:

  • Supports 7 ad platforms
  • Has config files for negatives, ad copy, bidding
  • Produces budget projections
  • Codifies the SavvyDealer PPC playbook

Your work should extend ppc-assistant, not rebuild it. If you're building an AI layer on top of Google Ads, it belongs inside this repo or as a companion service that consumes its outputs.

Before starting, read: 1. ppc-assistant 1-pager 2. The repo's CLI + config file structure — this is the playbook you're extending

Your repo: placeholder — Brian, send Adam the URL. If your work is a new module inside ppc-assistant, note that here instead.

Lucas — AI Form Pages

Related existing work: No direct 1:1 in Adam's portfolio. Adjacent:

Hard rules (carry over from Adam's patterns):

  • Form spam protection via Cloudflare Turnstile (see reference_cloudflare_account.md in memory — Adam has the account + widget patterns)
  • SMS verification where lead quality matters (pop-coupons pattern)
  • No secrets in committed files (.env or Secret Manager only)
  • Validate + log form submissions — never silently drop (see feedback no_silent_workarounds)

Your repo: placeholder — Lucas, send Adam the URL.

How your work shows up in this portfolio

Once your repos are shared:

  1. Adam (or you, with write access) adds your repo to the section 9 table in the inventory.
  2. We create a 1-pager for each project using the template in contributing.
  3. Cross-link integrations — if your AI notes tool ships, update dealerpulse integrations section; if Brian's work lands inside ppc-assistant, update that 1-pager.
  1. This page.
  2. The 1-pager for your closest related SavvyDealer tool (dealerpulse / ppc-assistant / Sell-Us-Your-Car).
  3. The Inventory "What NOT to duplicate" section — make sure your scope doesn't overlap something else.
  4. Adam's hard rules: no vendor-filler vocab, no fabricated OEM logos, secrets in .env only, never scrape Sheets for inventory (Savvy API is canonical).

Questions: Adam (support@savvydealer.com).