LeadsRadar (Webless Business Tracker) is an elite, responsive full-stack B2B outreach workspace built using React, Vite, Tailwind CSS, Express, and Google Cloud Firestore. It is designed specifically to help sales departments, independent agencies, and business development officers discover high-potential offline businesses in the USA, United Kingdom, Germany, and Canada that do not currently have an active website.
By scanning and identifying these businesses, LeadsRadar crafts hyper-targeted sales scripts, generates intelligent competitive SWOT matrices, manages direct communication channels, and tracks follow-up pipeline progression in a unified dashboard.
- Multi-Country Filters: Discover small businesses across USA, United Kingdom, Germany, and Canada with support for custom country queries.
- Smart Niche Profiling: Instantly filter prospects by popular niches like Plumbing, Roofing, Dentists, Auto Mechanics, Bakeries, Hair Salons, or Local Restaurants.
- Status Timeline Synchronizer: Real-time cloud progress synchronizer with Firebase Firestore databases.
- Multi-Select Bulk Manager: Toggle precise check selections on multiple leads to update pipeline statuses simultaneously or batch-disenroll records.
- Dynamic Spreadsheet Export: Export bulk-selected accounts instantly into structured CSV ledger files ready for immediate importing into any standard CRM.
- Color-Coded Pipeline Stages: Visually coordinate leads by tracking progress through six distinct, high-contrast statuses:
🆕 New Prospect📞 Contacted✉️ Pitch Sent🤝 Negotiating🎉 Account Won🛑 Disqualified
- Mini-Map Layout Previews: Features an embedded geo-location preview map container right inside the details view, highlighting the business's current location relative to landmarks.
- Navigation Links: One-click shortcuts directly into Google Maps for route mapping and physical outreach planning.
- Custom Labeled Tags: Label leads with custom categorized hashtags such as
#high-priority,#follow-up, or#warm. - Smart Palette Highlighting: Tags are color-coded depending on keyword importance to allow busy field reps to quickly prioritize high-value targets.
- Gemini Outreach Engine: Powered by advanced server-side Gemini models to instantly generate dedicated phone pitches and professional email drafts.
- SWOT Competitive Matrix: Live generation of competitive analysis (Strengths, Weaknesses, Opportunities, Threats) to immediately arm sales reps with actionable talking points.
- Direct Desktop Mail Integration: Direct Compose Email launcher buttons that generate a
mailto:link populated with pre-filled subjects and email bodies, launching directly in the user's desktop or mobile email client.
- Frontend: React (v18+) with Vite, Styled via Tailwind CSS
- Backend: Express Server Integration
- Database: Cloud Firestore Databases (Firebase SDK)
- AI Engine:
@google/genaiTypeScript SDK (utilizing Gemini models) - Icon Set: Lucide React
- Maps: Standard Map Embed APIs with OpenStreetMap geometry configuration
Make sure you have Node.js installed on your machine. Be sure to configure .env variables accordingly.
# .env.example
GEMINI_API_KEY=your_gemini_api_key_here
FIREBASE_PROJECT_ID=your_firebase_project_id_here-
Install necessary workspace dependencies:
npm install
-
Run the local development server:
npm run dev
-
Build the server-side bundled scripts and client site for production deployment:
npm run build
-
Launch production server:
npm run start
LeadsRadar now defaults to fail-closed production behavior. Configure NODE_ENV=production, an HTTPS APP_URL, GEMINI_API_KEY, FIREBASE_SERVICE_ACCOUNT, and ENCRYPTION_KEY with at least 32 UTF-8 bytes. MoonPay billing additionally requires MOONPAY_PUBLISHABLE_KEY, MOONPAY_SECRET_KEY, MOONPAY_WEBHOOK_SECRET, and TREASURY_WALLET_ADDRESS; set MOONPAY_ENVIRONMENT=sandbox locally and production in production. Optional pricing/currency values are MOONPAY_BASE_CURRENCY_CODE, MOONPAY_CURRENCY_CODE, MOONPAY_MONTHLY_AMOUNT, and MOONPAY_YEARLY_AMOUNT. See docs/production-operations.md for the complete environment contract, MoonPay signed checkout and webhook setup, credential-storage model, incident checks, and rollback procedure. For a safe local provider test, follow docs/moonpay-sandbox-testing.md.
All protected API calls require a verified Firebase ID token. Pro access and subscription state are server-authoritative and are never granted from browser localStorage or a client-controlled Firestore write. Gmail tokens are encrypted and stored outside the client-readable profile document. Discovery responses expose grounding citations when available; synthetic or unverified fallbacks are labeled and should not be treated as verified business data.
The weekly scan planner is a manual browser-session workflow, not a persistent background scheduler. A durable scheduler requires a separately authenticated job runner and queue.
Grounded lead discovery enforces the daily search allowance on the server, using the verified Firebase UID, UTC calendar day, and the subscription tier stored by the server. Free and Pro limits are not controlled by browser localStorage. The generic Express IP rate limiter is an abuse-control layer and is intentionally separate from product entitlement.
Provider failures do not create verified business facts. Missing contact fields remain explicit, LinkedIn/social enrichment falls back to an unverified empty state, and synthetic development data is labeled as synthetic. Before release, follow docs/production-operations.md and security_spec.md. No Firebase rules, MoonPay configuration, credential rotation, database migration, or cloud deployment is performed by this workflow.
Use MOONPAY_ENVIRONMENT=sandbox with MoonPay test keys only. The browser opens the official MoonPay overlay through @moonpay/moonpay-js; Pro activation is still controlled by the signed webhook and server-created order. See docs/moonpay-sandbox-testing.md for the complete local workflow.
Use the locked dependency and production validation workflow before release:
npm ci --ignore-scripts
npm run lint
npm test
npm run build
npm run audit
git diff --checkThe repository includes a GitHub Actions workflow at .github/workflows/ci.yml that runs these quality gates on pushes and pull requests.