stone-lead

byNeev Khoreja

This Product Requirements Document (PRD) is the final, comprehensive blueprint for **LeadFlow Ultra**. It integrates deep scraping, automated website auditing, and high-conversion outreach tools into a high-end, minimalist interface designed for professional agency use. --- ## **Product Requirements Document: LeadFlow Ultra** **Project Name:** LeadFlow Ultra **Proprietor:** Webora **Design Ethos:** Dark, Achromatic, Command-Driven (Anti-AI Aesthetic) --- ### **1. Executive Summary** LeadFlow Ultra is a specialized lead extraction and auditing engine built to identify and convert "digitally struggling" businesses. By combining Google Maps data with real-time website performance audits, the platform provides Webora with a ranked list of high-intent prospects who lack a professional web presence or have underperforming digital assets. --- ### **2. Core Functional Requirements** #### **2.1. "Exhaustive" Lead Scraping (Apify Integration)** * **Deep Scrape:** Utilize the **Apify Google Maps Scraper** to bypass the 120-result limit, crawling specific coordinates or subdivision zones to find *all* matching businesses. * **Data Fields:** Capture Business Name, `place_id`, Phone, Physical Address, Website URL, Rating, Review Count, and Category. #### **2.2. Intelligent Lead Vault & Deduplication** * **Primary Key Persistence:** Use the Google `place_id` as the unique identifier in Supabase to prevent duplicate records. * **UPSERT Logic:** If a business is found in a new search, the system must update its rating or website status rather than creating a second entry. #### **2.3. Automated Website Audit (PageSpeed Engine)** * **Health Check:** For any business with an existing URL, the system triggers the **Google PageSpeed Insights API** to generate a **Webora Score** (0–100) based on Performance, SEO, and Mobile-friendliness. * **Status Indicators:** * **Missing:** No website found. * **Critical (< 50):** Outdated, slow, or broken site. * **Suboptimal (50–80):** Needs refinement. #### **2.4. AI-Powered Personalized Outreach** * **Generate Pitch Button:** A dedicated action within the Lead Drawer that synthesizes Google Maps data (e.g., "You have a great 4.5 rating!") and Audit data (e.g., "But your site takes 6 seconds to load") into a concise pitch. * **Language Toggle:** Option to generate the message in professional **English** or conversational **Hinglish** to suit the local Mumbai/Kalyan market. * **Copy to Clipboard:** A "One-Click Copy" button immediately following the message generation for quick pasting into WhatsApp, Email, or DM. --- ### **3. User Interface (UI) & Design** #### **3.1. Aesthetic Guidelines** * **Palette:** Pure Black (`#000000`) background with `Slate-900` surfaces and `Slate-800` borders (1px solid). * **Typography:** **Geist Sans** for interface text; **Geist Mono** for all data points, ratings, and code snippets. * **Anti-AI Polish:** Avoid large rounded corners, gradients, or heavy shadows. The UI should feel like a high-end developer tool (e.g., Linear or Vercel) rather than a generic SaaS. #### **3.2. Dashboard & Navigation** * **Command Palette:** `Cmd + K` functionality to filter by "No Website" or "Low Ratings". * **Lead Drawer:** A sliding side-panel (no pop-up modals) that displays the full audit logs and the **Outreach Module**. * **Search History Sidebar:** A persistent record of all past keyword/location combinations to re-run or review. --- ### **4. Technical Stack & Database Schema** * **Frontend:** React (Vite) + Tailwind CSS + Lucide Icons. * **Backend:** Supabase (Auth & PostgreSQL). * **Intelligence:** OpenAI/Claude API for pitch generation; Google PageSpeed API for audits. #### **Database Schema (SQL):** ```sql -- Leads Table CREATE TABLE leads ( place_id TEXT PRIMARY KEY, name TEXT NOT NULL, category TEXT, maps_rating DECIMAL(2,1), reviews_count INTEGER, website_url TEXT, webora_score INTEGER, -- 0 to 100 audit_data JSONB, -- Stores specific LCP, SEO, and Speed metrics last_contacted_at TIMESTAMP WITH TIME ZONE, created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() ); -- Search Logs Table CREATE TABLE searches ( id UUID PRIMARY KEY DEFAULT uuid_generate_v4(), keyword TEXT, location TEXT, leads_count INTEGER, created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW() ); ``` --- ### **5. Roadmap & Success Metrics** * **Phase 1 (The Engine):** Connect Apify to Supabase with `place_id` deduplication. * **Phase 2 (The Auditor):** Integrate Google PageSpeed API to calculate the Webora Score. * **Phase 3 (The Closer):** Implement the Lead Drawer with the AI Pitch Generator and Copy-to-Clipboard functionality. * **Success Metric:** Time-to-lead (how quickly an agency can find a qualified prospect and send a message). --- ### **Final Instruction for Coding Tools:** > "Build LeadFlow Ultra using React and Supabase. The UI must be pure black with 1px slate borders. Sorting must default to 'Maps Rating: Ascending.' For every lead, provide a 'Lead Drawer' containing a 'Generate Pitch' button that creates a customized improvement plan for the business, followed by a 'Copy' button."

Landing
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document
Page 1 of 7

System Requirements Document: stone-lead

1. Introduction

The stone-lead project is a comprehensive lead-generation and auditing platform designed specifically for agency owners who create websites for businesses. By leveraging advanced scraping, auditing, and AI-powered outreach tools, stone-lead empowers agencies to identify high-potential leads, streamline their outreach process, and track conversions effectively. This document outlines the system requirements for the development and deployment of the platform.

2. System Overview

stone-lead integrates multiple functionalities into a unified platform to help agencies discover businesses with outdated or missing websites, audit their digital presence, and generate personalized pitches to convert them into clients. The platform also includes features for tracking lead statuses, scheduling follow-ups, and managing client relationships post-conversion.

The system will be tailored for the Indian market, with support for English and Hinglish communication, timezone alignment (IST), and locale-specific defaults. The platform will be accessible via a web interface, with a mobile-friendly design for on-the-go access.

3. Functional Requirements

Page 2 of 7

Core Functionalities

  • As a User, I should be able to scrape exhaustive business data from Google Maps using specific coordinates or keywords.
  • As a User, I should be able to view detailed lead information, including business name, address, website status, ratings, and reviews.
  • As a User, I should be able to audit a business’s website using Google PageSpeed Insights and generate a Webora Score (0–100).
  • As a User, I should be able to generate AI-powered personalized outreach messages in English or Hinglish.
  • As a User, I should be able to copy the generated outreach message with a single click.

Extended Features

  • As a User, I should be able to track the status of each lead (e.g., Contacted, In Negotiation, Closed – Won, Closed – Lost).
  • As a User, I should be able to schedule follow-up reminders for leads.
  • As a User, I should be able to view an analytics dashboard showing metrics like outreach success rate, most profitable lead categories, and time-to-close.
  • As a User, I should be able to export lead lists and sync them with CRM tools like HubSpot or Pipedrive.
  • As a User, I should be able to manage converted leads in a "Client" section with project timelines and status updates.
  • As an Admin, I should be able to manage user accounts and permissions.
  • As an Admin, I should be able to configure API keys for integrations (e.g., Google Maps, PageSpeed Insights, OpenAI).

4. User Personas

Page 3 of 7

1. Agency Owner

  • Description: A business owner who creates websites for other businesses and needs a steady stream of high-quality leads.
  • Goals:
    • Identify businesses with outdated or missing websites.
    • Streamline outreach and conversion processes.
    • Track lead statuses and follow-ups.
  • Pain Points:
    • Difficulty finding qualified leads.
    • Time-consuming manual outreach.
    • Lack of tools for tracking conversions.

2. Sales Representative

  • Description: A team member responsible for contacting leads and closing deals.
  • Goals:
    • Access detailed lead information quickly.
    • Generate personalized outreach messages.
    • Track follow-up schedules and lead statuses.
  • Pain Points:
    • Inefficient lead management.
    • Lack of personalized messaging tools.

5. Visuals Colors and Theme

Page 4 of 7

Color Palette

  • primary: #1E4E8C (Deep Blue)
  • primary_light: #5A8CCF (Light Blue)
  • secondary: #F15A24 (Vibrant Orange)
  • accent: #00C49A (Emerald Green)
  • highlight: #FFC107 (Golden Amber)
  • bg: #F4F4F9 (Light Gray)
  • surface: rgba(255, 255, 255, 0.9)
  • text: #1C1C1C (Dark Charcoal)
  • text_muted: #6C757D (Muted Gray)
  • border: rgba(0, 0, 0, 0.1)

6. Signature Design Concept

Interactive Lead Galaxy

The homepage of stone-lead will feature an Interactive Lead Galaxy, where each lead is represented as a glowing star within a 3D galaxy. Users can:

  • Hover over stars to view a quick summary of the lead (e.g., business name, rating, website status).
  • Click on a star to zoom in and open the detailed Lead Drawer, which includes audit logs and outreach tools.
  • Drag the galaxy to explore different clusters of leads, categorized by location or industry.

The galaxy will be built using @react-three/fiber and @react-three/drei for 3D rendering, with smooth animations powered by gsap. The stars will subtly change colors based on lead status (e.g., green for "Contacted", orange for "In Negotiation", red for "Closed – Lost").

7. Interaction Model & Motion Direction

Page 5 of 7

Landing Page Interaction Model

  • Type: Parallax
  • Details: The landing page will feature layered depth effects, with the Interactive Lead Galaxy as the centerpiece. Scrolling will reveal additional sections, such as the analytics dashboard and client management tools, with smooth transitions.

Internal Pages Interaction Model

  • Type: Animated
  • Details: Internal pages like the dashboard and lead management sections will include hover transitions, scroll-triggered reveals, and spring physics for interactive elements.

8. Non-Functional Requirements

  • Performance: The platform must load within 2 seconds on a 4G connection.
  • Scalability: Support up to 10,000 active users and 1 million leads.
  • Security: Implement role-based access control and encrypt sensitive data.
  • Localization: Support English and Hinglish for outreach messages.
  • Accessibility: Meet WCAG 2.1 AA standards.

9. Tech Stack

Frontend

  • React for Web
  • Tailwind CSS
  • @react-three/fiber + @react-three/drei
  • gsap for animations
Page 6 of 7

Backend

  • Python
  • FastAPI

Database

  • MySQL for relational data
  • MongoDB for NoSQL data
  • Alembic for migrations

AI Models

  • GPT 5.4 for user-friendly responses
  • Claude 4.6 Opas for coding-related tasks
  • Google Nano Banana for image generation

AI Tools

  • Langchain
  • Litellm for LLM routing

Orchestration

  • Docker
  • Kubernetes
Page 7 of 7

10. Assumptions and Constraints

  • The platform will primarily target the Indian market.
  • Users will have basic technical proficiency.
  • The system will rely on third-party APIs (e.g., Google Maps, PageSpeed Insights).

11. Glossary

  • Lead Drawer: A side panel displaying detailed information about a lead.
  • Webora Score: A score (0–100) indicating the health of a business’s website.
  • Interactive Lead Galaxy: A 3D visualization of leads on the homepage.
Landing design preview
Login: Sign In
Dashboard: View Overview
Users: Manage Accounts
Users: Edit Permissions
Settings: Configure APIs
Settings: Manage Integrations
Analytics: View Platform Stats
Analytics: Export Reports
Clients: View All Clients
Clients: Update Status