Skip to content

India Website / Marketing Team — Start Here

Who this is for: The development and marketing team building dealer websites, landing pages, marketing materials, and demos for SavvyDealer clients.

Your mission overlap with Adam's portfolio: Adam has built three distinct dealer-site strategies, template libraries, OEM brand assets, and the marketing/demo site itself. You should plug into these, not rebuild them.

Before you build a new dealer site or landing page, check which strategy fits. Extend over rebuild.


The three dealer-site strategies

Strategy When to use Tool
#1 — Full migration Client has an existing WP site to lift-and-shift wp-migration-factory — website.savvydealer.ai
#2 — Demo builds Prospecting or new builds — full template-generated site savvy-demo — demo.savvydealer.com
#3 — Single-page embeds Client platform handles chrome; we paste a page savvy-page-builder — paste-ready HTML w/ CSS prefixing

Don't propose a fourth strategy without talking to Adam. One of these three almost always fits.


Live sites and active clients

Site Purpose 1-pager
www.savvydealer.com / dev.savvydealer.com Main marketing site cloud-savvydealer-website
savvy-autos.com Auto marketplace content hub competing w/ Car & Driver savvy-autos
ata-website (Auto Team America) Client site ata-website
St. Pete Mitsubishi — Sell Us Your Car Mitsubishi rebrand of Sell-Us-Your-Car template stpetemitsubishi-sellyourcar
STL RV RV dealer demo (React + FastAPI) stl-rv-website
Gables Motorsports Powersports DealerSpike replacement demo gables-motorsports
savvydealer-static Static content + blog (51 pages + 26 posts) savvydealer-static
Thayer Family Dealerships 7 demo templates see Thayer build in memory

Shared assets — use these, don't source new ones

  • stock-image-project — licensed image catalog + OEM jellybeans + 12 brand guides
  • media — asset management / CDN
  • VCP-Image-Editor — vehicle photo editor
  • Facebook ad builder / Image Collage Pro — facebook.savvydealer.com (separate tool, ad-specific)

Hard rules (Adam will reject PRs that violate these):

  • Never fabricate OEM logos or brand assets. Source from the OEM website only.
  • Never use vendor-filler vocabulary in dealer-facing copy: "optimize / leverage / best practices / move the needle" etc. Adam mocks this on client calls.
  • Never scrape Google Sheets for inventory. Use the Savvy APIsellingPrice is authoritative.

Inventory / pricing on dealer sites

If a site needs vehicle inventory:

  1. Read from Savvy API — canonical.
  2. For RV: rv-catalog inventory API.
  3. For powersports: powersports-data.

Incentives / leases / window stickers — don't build these per-site. Consume: - lease-scraper - incentive-matcher - nissan-stickers (pattern extends to other brands)


Landing-page patterns (Sell Us Your Car, conversion pages)

For Lucas's AI form pages work — coordinate with Adam and Lucas first; Lucas is also a collaborator on bobweaver-collision.


Deployment

All SavvyDealer websites deploy to Cloud Run in GCP project savvydealer-website. - Prod: master branch → cloudbuild.yaml → prod service - Dev: dev branch → cloudbuild-dev.yaml → dev service

Never create a new Cloud Run service without checking for an existing one first. Always ask Adam before creating one.


  1. This page.
  2. wp-migration-factory, savvy-demo, savvy-page-builder — understand the three strategies.
  3. cloud-savvydealer-website — the main marketing site.
  4. stock-image-project + media — your asset library.
  5. savvy-autos — content strategy pattern.
  6. The full Inventory "What NOT to duplicate" section.

Questions: Adam (support@savvydealer.com).