fiery-build

bySAGUTURU SAI RAKESH

Build a production-ready MVP for a micro SaaS called Scrabio-style Lead Finder. PRODUCT GOAL Create a Chrome extension + lightweight SaaS backend for agencies that want to find businesses or contractors currently running ads, extract lead details, qualify them, and export them for outreach. CORE PROBLEM SEO agencies, SMMA agencies, freelancers, and lead-gen agencies struggle to find prospects that both: 1. have budget, and 2. are actively spending on marketing. A Reddit founder described a Chrome extension that scrapes businesses and contractors currently running ads and said agencies use it because these companies are more likely to pay for services; the founder reported 10 customers paying $49.99/month, roughly $500 MRR [web:11]. TARGET USERS - SEO agencies - SMMA agencies - freelance marketers - local lead-gen operators - cold email agencies - sales prospecting teams targeting local businesses MAIN USE CASE A user opens a supported source page, clicks the extension, scrapes visible businesses running ads, enriches the data, filters leads, saves selected leads to a dashboard, and exports CSV for outreach. BUILD SCOPE Build: 1. Chrome extension (Manifest V3) 2. Web app dashboard 3. Auth 4. Stripe subscription integration 5. Lead storage 6. CSV export 7. Simple usage limits by plan 8. Clean onboarding 9. Basic admin analytics DO NOT build a fake demo. Build a real MVP architecture with modular code, clear folders, and working flows. TECH STACK Frontend: - Next.js latest stable - TypeScript - Tailwind CSS - shadcn/ui or equivalent clean component system Extension: - Chrome Extension Manifest V3 - TypeScript - React for popup UI - content scripts for scraping - background service worker - message passing between popup/content/background Backend: - Next.js API routes or separate Node backend - PostgreSQL with Prisma ORM - Supabase or Neon acceptable for DB hosting - Clerk or NextAuth for authentication - Stripe for billing - Redis optional for rate limits / job queue INFRASTRUCTURE - Use environment variables - Modular services - Clean README - Database schema - Seed script - Deployment-ready structure PRODUCT NAME Use placeholder brand name: AdProspector POSITIONING “Find businesses already spending on ads.” KEY FEATURES 1. Chrome Extension Scraper - Detect and scrape lead data from supported pages - Extract: - business name - website - phone number - email if visible - category - city/state/country if available - ad platform/source page - source URL - timestamp scraped - Show scrape progress - Let user select/deselect leads before saving - Prevent duplicates - Handle pagination where possible - Show errors gracefully 2. Lead Qualification For each lead, generate fields: - has website: yes/no - website quality score: simple heuristic - has email: yes/no - has phone: yes/no - ad-active flag: yes - niche/category - local business / contractor / ecommerce / service - lead score from 0–100 - suggested pitch angle 3. Dashboard - login/signup - onboarding flow - leads table - filters by niche, location, has phone, has email, source, date - sort by lead score - save notes - mark status: - new - contacted - replied - booked - closed - bulk select - bulk export CSV - search leads - usage meter by subscription plan 4. Subscription Billing Plans: - Starter: $49/month, 500 leads/month - Growth: $99/month, 2500 leads/month - Agency: $199/month, 10000 leads/month Features: - Stripe checkout - customer portal - plan enforcement - free trial optional - webhook handling - billing status in DB 5. Admin - total users - active subscriptions - leads scraped today - MRR estimate - churned users - popular categories - top source pages 6. Outreach Helper For each lead, generate: - one cold email opener - one one-line personalized pitch - one offer suggestion Use rule-based templates first, optional AI provider later. SUPPORTED SOURCES Design the scraper system as adapter-based so new sources can be added easily. Create mock adapters for: - Google search result pages with ad indicators - Google Maps/business listings where ads/sponsored results appear - directory/listing pages - search pages for local service businesses IMPORTANT: Do not hardcode one fragile scraper only. Create a provider/adapter architecture like: - BaseScraper - GoogleSearchAdsScraper - GoogleMapsSponsoredScraper - DirectoryScraper Each adapter should expose: - canHandle(url) - scrape() - normalizeLead() DATA MODEL Create database models such as: - User - Organization - Subscription - Lead - LeadSource - ScrapeSession - UsageEvent - Note - ExportJob - ApiKey optional - AuditLog optional LEAD MODEL FIELDS - id - userId / orgId - businessName - contactName nullable - email nullable - phone nullable - website nullable - category nullable - city nullable - state nullable - country nullable - sourceType - sourceUrl - adPlatform nullable - adDetected boolean - score integer - pitchAngle nullable - status enum - notes - rawData JSON - createdAt - updatedAt SCORING LOGIC Create a simple transparent scoring engine: - +30 if running ads - +15 if website exists - +10 if phone exists - +15 if email exists - +10 if niche is high-value service - +10 if multiple locations - +10 if weak website and strong need for agency help - cap at 100 UI REQUIREMENTS Style: - modern SaaS - minimal - high trust - fast - not overly flashy Pages: - landing page - pricing page - login/signup - onboarding - app dashboard - lead detail drawer/modal - billing settings - help/docs Sections on landing page: - hero with strong problem statement - how it works - sample lead table screenshot mock - who it is for - pricing - FAQ - CTA LANDING PAGE COPY DIRECTION Headline ideas: - Find businesses already spending on ads - Stop cold prospecting random businesses - Discover high-intent local leads for your agency Subheadline: - Scrape, qualify, and export ad-active business leads in minutes CHROME EXTENSION UX Popup should include: - current page supported/not supported - scrape button - progress bar - result count - preview list - save selected leads - open dashboard button Options page: - API connection status - account plan - monthly usage - supported sources - help If scraping unsupported page: - show helpful explanation and supported source list SECURITY - sanitize scraped data - validate API input with Zod - auth guard protected routes - secure Stripe webhooks - rate limit write-heavy endpoints - no secrets in extension bundle - extension authenticates with user token securely - encrypt sensitive tokens if stored LEGAL / COMPLIANCE Add a disclaimer area in settings and docs: - user is responsible for complying with platform terms, privacy law, and outreach regulations - tool only assists with data collection from visible pages - support opt-out and deletion of stored lead records Do not present the product as bypassing any platform restrictions. ANALYTICS Track: - scrape started - scrape completed - leads saved - export generated - subscription created - subscription canceled - dashboard visit - onboarding completed ONBOARDING FLOW Step 1: what type of agency are you? - SEO - SMMA - Web design - Cold email - Lead gen Step 2: target niches Step 3: target geographies Step 4: install extension Step 5: scrape first leads DELIVERABLES I want the output to include: 1. Full folder structure 2. All key source files 3. Database schema 4. Extension manifest 5. Example scraper adapters 6. API routes 7. Landing page 8. Dashboard UI 9. Stripe integration skeleton 10. README with setup instructions 11. Seed/demo data 12. Clean comments where needed OUTPUT FORMAT Return: 1. project architecture overview 2. folder tree 3. important implementation notes 4. then generate the code files CODE QUALITY - production-minded - strongly typed - reusable - minimal duplication - clear naming - no pseudo-code unless clearly marked TODO - use realistic mock data only where external scraping cannot be run in this environment MVP PRIORITY ORDER Phase 1: - auth - extension scaffold - scrape adapters - save leads - dashboard table - CSV export - starter billing Phase 2: - lead scoring - outreach helper - analytics - team/org support Phase 3: - enrichment integrations - AI personalization - CRM integrations SUCCESS CRITERIA A paying user should be able to: - install extension - scrape supported pages - save leads - view them in dashboard - export CSV - stay within plan limits - pay monthly BONUS FEATURES IF TIME ALLOWS - duplicate domain detection - email verification integration hook - webhook to push leads into Google Sheets / Airtable / HubSpot - team seats - saved searches - niche presets like dentists, roofers, lawyers, med spas, plumbers Also provide: - 10 alternative product names - 5 pricing experiments - 7 cold outreach angles agencies can use with scraped leads - 10 SEO keywords to target for content marketing