Discover
Search local businesses by area and category. The discovery service uses Overture data or clearly marked fictional fixtures in local development; preliminary classifications are not verification.
Working product / Internal tool
Mossy Prospect
From prospect to project
The agency problem
Scattered steps slow useful work
Finding a local business, checking what is true, keeping a pipeline current and preparing a relevant next step often happen in separate tools. Mossy Prospect brings those stages into one operator-led workflow.
The product idea
Keep the facts and the work connected
The product links discovery records to reviewed facts, saved prospects, outreach drafts and website project records. A person remains responsible for verification, messaging and publication decisions.
The workflow
Find, check, follow through
Verify
Review source-backed business facts and website audit findings before relying on them. Unknown or stale information stays visible as such.
Pipeline
Save prospects and manage their status in a workspace pipeline, with structured records behind the board.
Prepare outreach
Generate an operator-review draft from approved facts and operational context. The AI path is configuration-dependent; drafts are never described as sent.
From prospect to project
A saved prospect can be associated with a website record. Operators can build a structured draft or attach a prebuilt static website ZIP of up to 25 MB, then review an immutable version and private preview.
The interface
A real working interface
The login and discovery captures avoid real prospect names. The silent walkthrough below shows location search and map interaction; prospect result rows and details have been cropped out.
The interface / Video
Discovery map walkthrough
A cropped excerpt from the local working product. The source recording stays outside the site.
Engineering & delivery
An operator-led system
Next.js and React provide the workspace UI. A Python FastAPI discovery service queries bounded Overture data. Supabase stores workspace and prospect records with access controls. A persistent worker handles longer-running jobs. Static source ZIPs enter a checked build and version workflow before private preview.
My role
Product direction, workflow design and implementation across the web interface, discovery integration and site delivery path.
Built with
Next.js 16 · React 19 · TypeScript · Python · FastAPI · DuckDB · Supabase · worker jobs
Current status
Current status
Working internal product. The repository contains tested discovery, review, pipeline, source ZIP import and preview flows. Git URL cloning was not found in the inspected implementation. Generated websites require editing, quality checks and human approval; automatic production-ready output is not claimed.
Your project / Next step
Have a workflow that needs to become a useful product?
Tell us where the handoffs break down. We can start with a focused task or discuss a larger build.
Discuss a small task ↗Start a project