From f29b2457af3d06fcaa08f226ecc1f99fc853b141 Mon Sep 17 00:00:00 2001 From: ippadmin Date: Mon, 10 Aug 2026 23:16:59 -0400 Subject: [PATCH] =?UTF-8?q?Initial:=20competitive=20landscape=20research?= =?UTF-8?q?=20pipeline=20=E2=80=94=20methodology,=20tracking,=20Batch=2000?= =?UTF-8?q?1=20dispatched?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CHANGELOG.md | 9 ++++ METHODOLOGY.md | 112 +++++++++++++++++++++++++++++++++++++++++++++++++ README.md | 57 +++++++++++++++++++++++++ 3 files changed, 178 insertions(+) create mode 100644 CHANGELOG.md create mode 100644 METHODOLOGY.md create mode 100644 README.md diff --git a/CHANGELOG.md b/CHANGELOG.md new file mode 100644 index 0000000..ad884d6 --- /dev/null +++ b/CHANGELOG.md @@ -0,0 +1,9 @@ +# Changelog + +## 2026-08-10 — Initial Pipeline Setup + +### Added +- Project folder, README, METHODOLOGY.md, COST-TRACKING.md created +- Gitea repo: git.itpropartner.com/ippadmin/competitive-landscape-research +- Research Batch 001 dispatched: 20 sites across 3 parallel teams +- Products analyzed: IntelSight, TransitPin, VentureBuilt, VerdictTank, HotNow, DRE diff --git a/METHODOLOGY.md b/METHODOLOGY.md new file mode 100644 index 0000000..ce4649c --- /dev/null +++ b/METHODOLOGY.md @@ -0,0 +1,112 @@ +# Research Methodology + +## Dispatch Architecture + +### Team Composition +Each batch is split across 3 parallel research teams, each covering 3-8 sites: +- **Team Alpha:** Marketing/landing optimization + scraping/monitoring tools +- **Team Bravo:** Micro-SaaS platforms + social/content tools +- **Team Charlie:** Career/local discovery + document tools (typically highest priority due to HotNow competitive overlap) + +### Model Selection +- Default: deepseek-v4-pro (cost-effective, strong at structured analysis) +- Premium: Claude Sonnet 5 for mission-critical competitive analysis (e.g., Locale-NYC vs HotNow) +- Fallback: deepseek-v4-flash for high-volume scraping passes + +### Dispatch Pattern +``` +delegate_task(tasks=[ + {goal: "...", context: "...", role: "orchestrator"}, + {goal: "...", context: "...", role: "orchestrator"}, + {goal: "...", context: "...", role: "orchestrator"} +]) +``` + +Each team subagent is an orchestrator — they can spawn their own leaf subagents for individual site scraping. This keeps context windows manageable and enables parallel site analysis. + +## Site Analysis Protocol + +### Per-Site Mandatory Extraction +1. **Core product/service** — What do they actually sell? (not what their tagline says) +2. **Pricing model** — Free tier? Monthly? Per-seat? Enterprise? +3. **Key features** — The 3-5 things that define the product +4. **UI/UX patterns** — Layout decisions, card designs, search patterns, filter approaches +5. **USP (Unique Selling Proposition)** — What's their "one thing"? +6. **Target audience** — Who is this for? (evidence from copy, not assumption) +7. **Tech stack indicators** — Framework hints, JS libraries, hosting clues +8. **Polish rating (1-5)** — Landing page quality, copy clarity, conversion strategy + +### Competitive Comparison Dimensions +When comparing a target site to an ITPP product, evaluate across: +- Feature completeness +- UX/UI polish +- Monetization strategy +- Data pipeline (how do they get their content?) +- Mobile readiness +- Conversion funnel +- Brand voice and positioning + +## Cross-Reference Protocol + +### Feature Mapping +Every extracted feature is mapped to at least one ITPP product with: +- **What:** The specific feature (e.g., "their tiered pricing table with hover comparison") +- **From:** Source site +- **To:** Target ITPP product +- **Why:** Reason this feature would improve the product +- **Effort:** Low / Medium / High implementation estimate +- **Impact:** 1-5 rating of expected user impact + +### Priority Tiers +- **P0 (Ship This Week):** 1-2 day features that close obvious gaps +- **P1 (Next Sprint):** 3-7 day features that add significant value +- **P2 (Roadmap):** Features requiring refactoring or new infrastructure +- **P3 (Nice to Have):** "Eventually" features with marginal impact + +## New Product Identification + +### Signal Detection +A new product opportunity exists when: +- 3+ sites in a batch cluster around the same problem +- A site solves a problem in one vertical that doesn't exist in another +- A "pick-and-shovel" opportunity emerges (tools for the toolmakers) +- A local version of a city-specific app is viable (e.g., Locale-NYC → HotNow Savannah) + +### Evaluation Criteria +- Market size estimate (rough) +- Competition density +- Our unique advantage +- MVP scope and timeline +- AI cost for ongoing operation +- Domain availability + +## Cost Tracking + +### Per-Batch Cost Attribution +``` +Research Batch 001: + Team Alpha: $X.XX (deepseek-v4-pro, N tool calls) + Team Bravo: $X.XX (deepseek-v4-pro, N tool calls) + Team Charlie: $X.XX (deepseek-v4-pro, N tool calls) + Integration: $X.XX (deepseek-v4-pro, N tool calls) + Total: $X.XX +``` + +Tracked via dedicated LiteLLM virtual key `competitive-research-prod` on admin-ai. + +### Historical Cost Baseline +| Batch | Date | Total Cost | Sites | Cost/Site | Notes | +|---|---|---|---|---|---| +| 001 | 2026-08-10 | TBD | 20 | TBD | Initial batch | + +## Report Template + +Each batch produces a master report at `research/NNN-slug.md`: +1. Executive Summary (1 paragraph) +2. Site-by-Site Breakdown (summary table) +3. Feature Extraction Matrix (sortable table) +4. Product Enhancement Recommendations (grouped by product, prioritized) +5. New Product Opportunities (concept cards) +6. Risk Flags & Warnings +7. Cost Summary +8. Next Batch Queue (sites flagged for future analysis) diff --git a/README.md b/README.md new file mode 100644 index 0000000..0ed28fc --- /dev/null +++ b/README.md @@ -0,0 +1,57 @@ +# Competitive Landscape Research Pipeline + +Systematic competitive analysis pipeline — scrape target sites, extract features, cross-reference against ITPP products, and identify new product opportunities. Designed as a repeatable research operation. + +**Status:** LIVE +**Owner:** Germaine Brown / Sho'Nuff +**Created:** 2026-08-10 + +## Access + +| Resource | URL | Access | +|---|---|---| +| Git Repo | https://git.itpropartner.com/ippadmin/competitive-landscape-research | ippadmin (read/write) | +| AI Costs | admin-ai key: `competitive-research-prod` | TBD | + +## Purpose + +When Germaine identifies a batch of competitor/adjacent sites, this pipeline: +1. Scrapes and deeply analyzes every site +2. Extracts features, UI patterns, pricing models, and UX decisions +3. Cross-references findings against ITPP products (IntelSight, HotNow, VerdictTank, TransitPin, VentureBuilt, DRE) +4. Identifies new product opportunities from common themes +5. Produces a structured, searchable report + +## Pipeline Architecture + +``` +Research Batch (user provides URLs) + │ + ├─ Team Alpha (3-7 sites) ──┐ + ├─ Team Bravo (3-7 sites) ──┤ Parallel scraping + analysis + └─ Team Charlie (3-7 sites)─┘ + │ + ▼ +Integration & Synthesis (master report) + │ + ├─ Feature Extraction Matrix + ├─ Product Enhancement Recommendations + ├─ New Product Opportunities + └─ Risk Flags & Cost Summary +``` + +## Research Batches + +| Batch ID | Date | Sites | Researchers | Products Analyzed | Report | +|---|---|---|---|---|---| +| 001 | 2026-08-10 | 20 sites | Alpha, Bravo, Charlie | 6 products | research/001-aug10.md | + +## Methodology + +See [METHODOLOGY.md](METHODOLOGY.md) for the full research protocol. + +Key principles: +- Every site gets a full page extraction + browser inspection +- Features are rated on replicability and mapped to specific ITPP products +- New product ideas must cite which sites inspired them +- AI costs tracked per-research-batch via dedicated LiteLLM key