WEBIT

byManan Punamiya

## Product Overview Build a full-stack SaaS web application called **WEBIT**. It is a platform for agencies/freelancers to: 1. Find real local business leads (via Google Maps). 2. Automatically generate a full AI-built website for each lead. 3. Publish that website live and connect a custom domain — all in a few clicks. 4. Track revenue, generate invoices, and view business analytics. Target scale: must support **500,000–1,000,000+ registered users** and concurrent traffic without degradation. Design the architecture for horizontal scaling from day one (not a prototype-only build). --- ## Tech Stack Requirements - **Frontend:** Next.js (React) + Tailwind CSS, fully responsive, SSR where needed for SEO on public-facing generated sites. - **Backend:** Node.js (NestJS or Express) or equivalent, structured as modular services (auth, leads, website-generator, finance). - **Database:** PostgreSQL (primary relational data: users, leads, invoices) + Redis (caching, rate limiting, job queues). - **Queue/Workers:** Background job queue (e.g., BullMQ) for async tasks like AI website generation, since these are slow operations and shouldn't block the request. - **File/Asset storage:** Object storage (S3-compatible) for generated site assets, images, invoice PDFs. - **Auth:** JWT-based auth with refresh tokens, email/password + OAuth (Google login), role-based access (admin/user). - **Hosting/Infra:** Containerized (Docker), deployable behind a load balancer, auto-scaling groups, CDN for static/generated site delivery. - **APIs to integrate:** - Google Maps Places API (lead discovery) — I will provide the API key. - An LLM API (e.g., Anthropic Claude API) for AI website copy/content/layout generation. - Domain/DNS provider API (e.g., Namecheap, Cloudflare, or Vercel Domains API) for one-click domain connection. - Payment gateway (Stripe/Razorpay) for invoicing and payment collection. --- ## Page-by-Page Specification (5 core pages after login) ### 1. Dashboard (home page after login) - Summary cards: total leads found, websites generated, websites published, total revenue, active clients. - Recent activity feed (e.g., "Website generated for XYZ Cafe", "Invoice #123 paid"). - Quick-action buttons: "Find New Leads", "Generate Website", "Create Invoice". - Simple charts: leads over time, revenue over time. ### 2. Lead Finder - Search form: business category/keyword + location (city/area/radius) → calls Google Maps Places API. - Results table: business name, address, phone, website (if any), rating, category. - Filters: "no website" (highest value leads), rating range, category. - Save lead to "My Leads" list; bulk-select and bulk-save. - Pagination/infinite scroll to handle large result sets without lag. ### 3. Website Generator - Select a saved lead → click "Generate Website" → triggers async AI job (show progress/loading state, don't block UI). - AI generates: homepage copy, about section, services/products, contact section, image suggestions, based on the business's Google Maps data (name, category, reviews, address). - Live preview of generated site inside the page (iframe or embedded renderer). - Actions per generated site: Edit content, Regenerate, **Publish** (deploys to a subdomain instantly), **Connect Custom Domain** (DNS setup flow), Delete. - Grid/list view of all generated websites with status (Draft / Published / Domain Connected). ### 4. Finance - Revenue overview: total earned, pending payments, this month vs last month, simple line/bar chart. - Invoice creation: select client/lead, add line items, tax, due date → generate PDF invoice → send via email or shareable link. - Invoice list with status (Paid / Unpaid / Overdue) and payment tracking. - Basic analytics: revenue by client, by month, top-earning websites/services. ### 5. Settings - Profile & account settings (name, email, password, avatar). - API key management (user's own Google Maps key, if self-serve). - Domain/DNS provider connection settings. - Billing/subscription plan for the platform itself (if this is a paid SaaS). - Team/member management (if multi-user accounts are needed). - Notification preferences. --- ## Non-Functional Requirements (must be explicit, not skipped) - **Scalability:** design DB schema with indexing on frequently queried fields (user_id, lead_id, status). Use pagination everywhere — never load unbounded lists. - **Async processing:** website generation and domain connection must be background jobs with status polling/webhooks, not synchronous blocking calls. - **Rate limiting:** protect Google Maps and LLM API usage per user to control cost and avoid abuse. - **Security:** hashed passwords (bcrypt/argon2), input validation, HTTPS everywhere, RBAC on all endpoints, secrets in environment variables (never hardcoded). - **Error handling:** graceful failure states in UI for failed API calls (e.g., Maps quota exceeded, AI generation failed) with retry options. - **Clean architecture:** clear separation between frontend, backend API, and worker processes; documented REST or GraphQL API layer. --- ## Deliverables Expected - Fully working frontend (5 pages + login/signup/onboarding flow) with clean, modern, professional UI. - Backend API with the modules described above. - Database schema (users, leads, generated_websites, invoices, domains). - Auth flow (signup, login, password reset, session handling). - Placeholder/mock integration points clearly marked where I need to plug in my own API keys (Google Maps, LLM, domain provider, payment gateway).

LandingUsersSignupLogin
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document

WEBIT System Requirements Document

Introduction

The purpose of this document is to outline the system requirements for the WEBIT project, a full-stack SaaS web application designed for agencies and freelancers. WEBIT aims to streamline the process of finding local business leads, generating AI-built websites, and managing business analytics.

System Overview

WEBIT is a platform that allows users to:

  1. Discover real local business leads using Google Maps.
  2. Automatically generate a full AI-built website for each lead.
  3. Publish the website live and connect a custom domain with minimal effort.
  4. Track revenue, generate invoices, and view business analytics.

The system is designed to support a large user base and handle concurrent traffic efficiently. It is built with scalability in mind, ensuring that the architecture can grow horizontally as needed.

Page 1 of 6

Functional Requirements as Story Points

  • As a User, I should be able to find local business leads using Google Maps.
  • As a User, I should be able to automatically generate a website for each lead using AI.
  • As a User, I should be able to publish a generated website and connect it to a custom domain.
  • As a User, I should be able to track revenue and generate invoices.
  • As a User, I should be able to view business analytics.
  • As a User, I should be able to manage my profile and account settings.
  • As a User, I should be able to manage API keys for integration with external services.
  • As a User, I should be able to manage billing and subscription plans.
  • As a User, I should be able to manage team members if multi-user accounts are needed.
  • As a User, I should be able to set notification preferences.

User Personas

  • Agency Owner: Uses the platform to find leads and generate websites for clients.
  • Freelancer: Utilizes the platform to expand their client base and streamline website creation.
  • Admin: Manages platform settings, user accounts, and oversees system operations.
Page 2 of 6

Core User Flows

  1. Lead Discovery:

    • User searches for business leads using Google Maps.
    • User filters results and saves leads to "My Leads" list.
  2. Website Generation:

    • User selects a lead and initiates website generation.
    • AI generates website content based on lead data.
    • User previews, edits, and publishes the website.
  3. Revenue and Invoicing:

    • User views revenue overview and generates invoices.
    • User tracks invoice status and manages payments.
  4. Account Management:

    • User updates profile settings and manages API keys.
    • User configures billing and subscription plans.

Visuals Colors and Theme

  • primary: #1E40AF (Indigo)
  • primary_light: #3B82F6 (Light Blue)
  • secondary: #F59E0B (Amber)
  • accent: #EF4444 (Red)
  • highlight: #10B981 (Green)
  • bg: #F3F4F6 (Light Gray)
  • surface: #FFFFFF (White)
  • text: #111827 (Dark Gray)
  • text_muted: #6B7280 (Gray)
  • border: #D1D5DB (Light Gray)
Page 3 of 6

Signature Design Concept

Interactive Business Map Experience

The homepage will feature an interactive map where users can visually explore business leads. As users hover over different areas, business details will dynamically appear, providing a seamless exploration experience. Clicking on a business will initiate the website generation process. This map will be built using motion/react for smooth transitions and interactions.

Landing Hero Motion Brief

The landing page will feature a dynamic illustration of a business ecosystem. As users scroll, elements like business icons, website previews, and analytics charts will animate into view, telling the story of how WEBIT transforms leads into live websites. The animation will loop every 10 seconds, using motion/react for fluid motion and responsiveness.

Interaction Model & Motion Direction

  • Interaction Model: Animated
  • The landing page will feature moderate scroll-triggered reveals and hover transitions to enhance user engagement.
  • Internal pages will maintain a static interaction model for clarity and ease of use.
Page 4 of 6

Non-Functional Requirements

  • Scalability: Ensure the database schema is optimized with indexing and pagination.
  • Async Processing: Use background jobs for website generation and domain connection.
  • Rate Limiting: Implement rate limiting for API usage to control costs.
  • Security: Use hashed passwords, input validation, HTTPS, and RBAC.
  • Error Handling: Provide graceful failure states with retry options.
  • Clean Architecture: Maintain separation between frontend, backend, and worker processes.

Tech Stack

  • Frontend: Next.js (React) + Tailwind CSS
  • Backend: Node.js (NestJS or Express)
  • Database: PostgreSQL + Redis
  • Queue/Workers: BullMQ
  • File/Asset Storage: S3-compatible object storage
  • Auth: JWT-based with OAuth
  • Hosting/Infra: Docker, load balancer, CDN
  • APIs: Google Maps Places API, LLM API, Domain/DNS provider API, Payment gateway
Page 5 of 6

Assumptions and Constraints

  • The system must support up to 1,000,000+ users.
  • The architecture must be designed for horizontal scaling.
  • Placeholder/mock integration points will be provided for API keys.

Glossary

  • AI: Artificial Intelligence
  • API: Application Programming Interface
  • JWT: JSON Web Token
  • RBAC: Role-Based Access Control
  • SaaS: Software as a Service
  • SSR: Server-Side Rendering

This document outlines the comprehensive requirements for the WEBIT project, ensuring that all aspects of the system are clearly defined and ready for development.

Page 6 of 6
Landing design preview
Landing: View Info
Login: Sign In
Admin Dashboard: View System Stats
Admin Dashboard: Manage Users
Users: Edit User
Users: Suspend Account
Admin Dashboard: Monitor Jobs
Settings: Configure Platform
Settings: Manage Billing Plans
Settings: Manage Rate Limits
Settings: Manage Team Members
Settings: Set Notifications
Landing design preview
Landing: View Info
Login: Sign In
Admin Dashboard: View System Stats
Admin Dashboard: Manage Users
Users: Edit User
Users: Suspend Account
Admin Dashboard: Monitor Jobs
Settings: Configure Platform
Settings: Manage Billing Plans
Settings: Manage Rate Limits
Settings: Manage Team Members
Settings: Set Notifications