Skip to content

RV Research

Repo: savvydealer-adam/rv-research · Path: C:/Users/adam/rv-research · Owner: Adam Status: Active dev · % Done: 50 · Last commit: 2026-04-06 Deployed: not deployed (research + prototype workspace)

What it is

Market research + data model prototype for SavvyDealer's expansion into the RV dealer website market. Includes competitive landscape, inventory pipeline analysis, OEM data strategy, VIN decoding research, and prototype scrapers.

Why it exists

Before committing platform build effort, we need a clear picture of the RV market, who the website competitors are, how inventory flows, and what the canonical data model should look like. This is the "think before we build" workspace — rv-catalog is the "build".

How it works

Python — mixed backend prototypes + research markdown. - Research docs: market overview, competitive landscape, inventory pipeline, OEM data, VIN decoding, gap analysis, priority roadmap - Prototype APIs (opus_api.py, claw_api.py) comparing model output quality - Prototype SQLite DBs (rv_inventory.db, rv_knowledge_base.db) - stlrv.net fresh scrape reseeded 2026-04-06 (74 units, 1125 images) - Model comparison test (Claude Opus vs Claw Code local)

What's done

  • Full market research brief (RV-DEALER-WEBSITE-RESEARCH.md)
  • JSON schema drafts for RV models / floorplans
  • Opus vs Claw Code VIN decoder + model catalog comparison
  • stlrv.net scrape baseline

What's next

  • Migrate validated schema into rv-catalog (production)
  • Wind this repo down to research-only once rv-catalog picks up the scraping
  • Archive prototype APIs

Where the code lives

  • RV-DEALER-WEBSITE-RESEARCH.md — canonical market brief
  • MODEL-COMPARISON-TEST.md — Opus vs Claw Code results
  • opus_*.py / claw_*.py — prototype implementations
  • backend/ + frontend/ — prototype app
  • scripts/ — scrape scripts

Integrations

  • Feeds rv-catalog (schema + scraper patterns migrate there)
  • Informs stl-rv-website build decisions
  • Shares rv_inventory.db with stlrv.net scrape pipeline

Don't rebuild this — extend it

When the schema or a scraper pattern is production-ready, port it into rv-catalog — don't keep iterating in the research repo.