System Requirements Document for mega-weekly

1. Introduction

Mega-weekly is a Micro SaaS product designed to provide weekly plain-English analytics emails for users of privacy-first analytics tools like Plausible and Fathom. The product targets bloggers, indie hackers, and small SaaS companies who seek actionable insights without the need to log into traditional dashboards. The service aims to save users time and reduce dashboard fatigue by delivering insights directly to their inboxes.

2. System Overview

Mega-weekly offers a streamlined solution for generating and delivering weekly analytics summaries in plain English. It integrates with Plausible and Fathom APIs to provide insights, anomaly detection, and explanations. The product includes a user-friendly interface with a modern design inspired by Linear, Notion, and Vercel. Key features include user authentication, subscription management, and an admin dashboard for operational oversight.

2a. Product Interpretation and Delivery Boundary

Mega-weekly is delivered as a production-ready Micro SaaS with a focus on privacy-first analytics. It supports Google and Email Login for user authentication and uses Stripe for subscription management. The product is designed to be responsive, with dark mode and SEO capabilities. It avoids requiring users to log into the underlying analytics dashboards, maintaining a privacy-first approach.

2b. Source Content Inventory

Not applicable as no content_source directive was provided.

2c. Page Content and Component Coverage

Landing

• Purpose: Introduces the product, target audience, and value proposition.
• Components:
  • Hero section with bold headline and illustration.
  • Overview of features and benefits.
  • Call-to-action for sign-up.

Pricing page

• Purpose: Displays subscription pricing options.
• Components:
  • Pricing tiers with features.
  • Call-to-action for subscription.

Dashboard

• Purpose: Allows subscribers to review insights and top pages/movers.
• Components:
  • Summary of weekly insights.
  • Anomaly explanations.
  • Top pages and movers list.

Provider Connections

• Purpose: Connects to Plausible or Fathom reporting sources.
• Components:
  • Connection setup interface.
  • Status indicators for connected services.

User settings

• Purpose: Manages subscriber account settings.
• Components:
  • Profile management.
  • Notification preferences.

Billing page

• Purpose: Manages subscription and billing information.
• Components:
  • Subscription details.
  • Payment method management.

Admin dashboard

• Purpose: Provides operational administration for product administrators.
• Components:
  • User management.
  • System analytics.

Login

• Purpose: Facilitates user authentication.
• Components:
  • Google and Email Login options.

Sign Up

• Purpose: Facilitates new user enrollment.
• Components:
  • Registration form.
  • Terms and conditions agreement.

3. Functional Requirements

• As an Analytics subscriber, I should be able to sign up using Google or Email Login to access the dashboard and manage my subscription. (required_inference)
• As an Analytics subscriber, I should receive weekly plain-English analytics emails summarizing insights and anomalies. (explicit)
• As an Analytics subscriber, I should be able to connect my Plausible or Fathom account to receive analytics data. (explicit)
• As an Analytics subscriber, I should be able to view top pages and movers on the dashboard. (explicit)
• As a Product administrator, I should be able to manage users and system analytics through the admin dashboard. (explicit)
• As an Analytics subscriber, I should be able to manage my subscription and billing information through the billing page. (explicit)

4. User Personas

Analytics Subscriber

• Context: A blogger, indie hacker, or small SaaS operator who uses privacy-first analytics tools.
• Primary Goal: To receive actionable insights without logging into traditional dashboards.
• Responsibilities: Connect analytics providers, review insights, manage subscriptions.
• Interactions: Receives weekly email reports, uses the dashboard for detailed insights.

Product Administrator

• Context: Oversees the operational analytics and administration of the SaaS.
• Primary Goal: To manage the service and ensure smooth operation.
• Responsibilities: User management, system analytics oversight.
• Interactions: Uses the admin dashboard for operational tasks.

5. Core User Flows

5.1 Analytics Subscriber Sign-Up and Connection

1. Landing Page: User visits the landing page and clicks "Sign Up."
2. Sign Up Page: User registers using Google or Email Login.
3. Provider Connections Page: User connects their Plausible or Fathom account.
4. Dashboard: User accesses the dashboard to view insights.

5.2 Weekly Email Report Delivery

1. Background Process: System generates weekly analytics summaries.
2. Email Delivery: User receives an email with insights and anomalies.

5.3 Subscription Management

1. Billing Page: User accesses the billing page.
2. Subscription Update: User updates subscription details or payment method.

5.4 Admin Dashboard Management

1. Login Page: Administrator logs in using Google or Email Login.
2. Admin Dashboard: Administrator manages users and reviews system analytics.

6. Visuals Colors and Theme

• Muse: Haraldur Thorleifsson
• Palette:
  • Background: #FFFFFF
  • Surface: #FDF6E3
  • Text: #333333
  • Primary: #FF5722
  • Accent: #FFC107
  • Muted: #757575
• Typography:
  • Headings: Sora — Bold
  • Body: Outfit
  • Scale: 1.414 modular
• Shape Language: Chunky rounded cards
• Layout: Asymmetric grid with ample whitespace

7. Signature Design Concept

The landing page features a full-width, color-blocked hero section with a bold headline in Sora, juxtaposed with an illustration representing indie creators receiving insights. The design uses vibrant color transitions and rounded, chunky cards to create an engaging and approachable aesthetic.

8. Interaction Model & Motion Direction

• Interaction Model: Animated
• Motion Tempo: Expressive
• Hero Dimensionality: Layered_2d
• Landing Hero Motion Brief: The hero section features lively entrance animations with hover pops and gentle scroll-linked reveals. The focal subject is an illustration of indie creators, transforming into a vibrant insight display as users scroll.

9. Non-Functional Requirements

• Performance: The system must handle concurrent user requests efficiently.
• Scalability: The architecture should support scaling to accommodate growing user base.
• Security: Ensure secure user authentication and data protection.
• Usability: The interface should be intuitive and easy to navigate.

10. Tech Stack

• Frontend: React
• Backend: Python/FastAPI
• Database: PostgreSQL
• Authentication: OAuth 2.0 for Google Login, custom for Email Login
• Payment Processing: Stripe
• Deployment: Docker, Kubernetes

11. Assumptions and Constraints

• The product will initially focus on solo bloggers with 10K+ monthly visitors.
• The pricing model is set between $9–$19/month.
• The product must integrate with Plausible and Fathom APIs.

12. Glossary

• Analytics Subscriber: A user who subscribes to receive weekly analytics summaries.
• Product Administrator: A user responsible for managing the SaaS operations.
• Plausible/Fathom: Privacy-first analytics tools used by the target audience.