📄 Lightning Lesson resource

Build plan: Market Research Agent

An AI agent that does market research for solo founders — the plan we vibe-coded live. Hand it to your own coding agent and build it yourself.

This is the build plan from the July 30 Lightning Lesson, “Live Build: Ship an AI Agent on Kimi K3.” In that hour we started from an empty folder and vibe-coded the whole thing live on Claude Code running Kimi K3 — the model wrote this spec, then built against it while everyone watched.

What's below is the plan itself, unedited. It's a plan, not a finished product — and that's the useful part. Everything a coding agent needs to build this is written down: the stack, the architecture, the report structure, the agent flow, the file layout, the decisions and why they were made. Download the raw markdown, drop it into Claude Code, Cursor, or whatever you use, and tell it to build. Or just read it as a worked example of what an agent-ready spec looks like.

  Download the plan (.md)

Free, no signup. 6 KB of markdown — paste it straight into your agent.

Context

Build a local demo of an AI agent that helps solo founders discover their next product idea. The founder describes their situation in natural language; the agent conducts one-shot market research via web search and delivers an interactive dashboard report.

Requirements Summary

Aspect Decision
Frontend React SPA (Vite)
Backend FastAPI (Python)
User Input Natural language prompt
Data Sources Web search (DuckDuckGo, no API key), social signals via search
Output Interactive dashboard with collapsible sections
Research Style One-shot (~30-60s), parallel sub-searches + LLM synthesis
LLM Kimi K3 via Moonshot Anthropic-compatible endpoint

Architecture

┌─────────────┐     POST /research     ┌─────────────┐
│  React SPA  │ ─────────────────────► │  FastAPI    │
│  (Vite)     │                        │  Backend    │
│             │ ◄── JSON Report ────── │             │
└─────────────┘                        └──────┬──────┘
                                              │
                       ┌──────────────────────┼──────────────────────┐
                       ▼                      ▼                      ▼
                ┌─────────────┐       ┌─────────────┐       ┌─────────────┐
                │ DuckDuckGo  │       │ DuckDuckGo  │       │ DuckDuckGo  │
                │ Trends      │       │ Competitors │       │ Pain Points │
                └─────────────┘       └─────────────┘       └─────────────┘
                       │                      │                      │
                       └──────────────────────┼──────────────────────┘
                                              ▼
                                       ┌─────────────┐
                                       │  Kimi K3    │
                                       │  Synthesis  │
                                       └─────────────┘

← scroll the diagram sideways

Report Structure (Dashboard Sections)

  1. Executive Summary — Top-level takeaways and recommended focus areas
  2. Industry Trends — What's growing, declining, or emerging in the space
  3. Competitor Landscape — Key players, funding stage, positioning
  4. Existing Products — Products solving related problems, with feature summaries
  5. Pain Points & Limitations — What users complain about (from social signals)
  6. Market Gaps & Opportunities — Unserved niches or under-served segments
  7. Recommended Next Steps — Actionable ideas for the founder to validate

Research Agent Flow

  1. Query Decomposition — LLM breaks the founder's prompt into 3-5 parallel search queries
  2. Parallel Search — Each query runs through DuckDuckGo independently
  3. Result Aggregation — Deduplicate and rank results by relevance
  4. Synthesis Pass — LLM analyzes aggregated data and produces structured report JSON
  5. Response — Backend returns structured JSON; frontend renders interactive dashboard

Tech Stack Details

Backend (backend/)

Frontend (frontend/)

Critical Design Decisions

  1. DuckDuckGo over paid APIs — Zero API keys needed for demo. Can swap to Serper.dev/Tavily later.
  2. No database — Research sessions stored in-memory. Simple for demo; add SQLite if history is needed.
  3. Streaming response — FastAPI streams partial results so the dashboard populates incrementally (better UX for 30-60s wait).
  4. One-shot vs. multi-turn — Strictly one-shot. No follow-up questions from the agent to keep it fast.

Verification Plan

  1. Start backend: cd backend && uvicorn main:app --reload
  2. Start frontend: cd frontend && npm run dev
  3. Open http://localhost:5173, enter a prompt like:
    “I'm a solo developer with $50k budget, interested in B2B SaaS for the construction industry. I have React and Python skills.”
  4. Verify dashboard renders with all 7 sections populated.
  5. Verify research completes in under 60 seconds.

Open Questions

  Download the plan (.md)
Free community

Come build with us

You just watched someone build an agent in an hour. The hard part was never that hour — it's the next one, on your own, when the thing won't run and there's nobody to ask. That's what AI Superpower is for: a free community of people shipping AI products in public, posting the broken parts along with the wins. I'm in there most days. If you take this plan and build something with it, come show us — honestly, that's the best reason there is to join.