Kiran CRM System Requirements Document

1. Introduction

Kiran CRM is a Micro SaaS solution designed to serve local businesses such as salons, clinics, coaching centers, agencies, and small shops. The primary objective of Kiran CRM is to facilitate faster replies, efficient lead tracking, and increased sales without the need for additional staff. This document outlines the system requirements for developing a production-ready CRM platform with a modern design inspired by Linear, Notion, and Vercel.

2. System Overview

Kiran CRM will provide a comprehensive suite of tools for managing customer interactions via WhatsApp. The system will include features such as user authentication, a dashboard, Stripe subscriptions, and analytics. The platform will be responsive, support dark mode, and include robust error handling and loading states.

3. Functional Requirements as Story Points

• As a User, I should be able to access a beautiful landing page to understand the product offerings.
• As a User, I should be able to log in using Google or Email for authentication.
• As an Admin, I should be able to manage user accounts through an admin dashboard.
• As a User, I should be able to subscribe to services using Stripe for payments.
• As a User, I should be able to view and interact with a responsive dashboard.
• As a User, I should be able to switch between light and dark modes for better accessibility.
• As a User, I should be able to update my settings in the user settings page.
• As a User, I should be able to view billing information on a dedicated billing page.
• As a User, I should be able to access analytics to track performance and sales.
• As a User, I should be able to navigate a pricing page to understand different subscription tiers.
• As a Developer, I should be able to access REST APIs for integration and development purposes.
• As a User, I should experience seamless error handling and loading states for a smooth user experience.

4. User Personas

• Admin: Manages user accounts and oversees the CRM operations.
• User: Local business owners or staff who interact with customers and manage leads.

5. Core User Flows

• User visits the landing page -> User logs in via Google/Email -> User accesses the dashboard -> User manages leads and customer interactions -> User views analytics -> User updates settings or billing information.
• Admin logs in -> Admin accesses the admin dashboard -> Admin manages user accounts and subscriptions.

6. Visuals Colors and Theme

• primary: #0070f3 (dominant brand color)
• primary_light: #3291ff (lighter tint for hover states)
• secondary: #1c1c1e (supporting color for neutral elements)
• accent: #ff4081 (emphasis color for CTAs and active states)
• highlight: #f5a623 (color for hover states and notifications)
• bg: #ffffff (page background color)
• surface: #f7f7f7 (card/panel background)
• text: #333333 (primary text/heading color)
• text_muted: #888888 (softer color for secondary text)
• border: #eaeaea (subtle accessible border color)

7. Signature Design Concept

Interactive Workflow Animation

The landing page will feature an interactive workflow animation that visually represents the CRM process. Users will see a dynamic illustration of a customer inquiry coming in through WhatsApp, being processed by the CRM, and resulting in a successful sale. This animation will be built using motion/react for smooth transitions and interactions. Users can hover over different stages to see detailed tooltips explaining each step.

LANDING HERO MOTION BRIEF

The hero section will depict a customer's message entering the CRM system, transforming into a lead, and culminating in a sale. The animation will loop every 10 seconds, with each stage clearly illustrated. Users can interact by clicking on stages to reveal more information. The animation will be responsive and will settle into a static state with reduced motion for accessibility.

8. Interaction Model & Motion Direction

• Interaction Model: Animated
• The landing page will feature moderate scroll-triggered reveals and hover transitions. Interactive elements will have spring physics for a polished feel. Internal pages will maintain a static layout for clarity.

9. Non-Functional Requirements

• The system must be highly responsive and support various devices and screen sizes.
• The platform should ensure data security and privacy, especially for user authentication and payment processing.
• The system should be scalable to accommodate growing user bases and data volumes.

10. Tech Stack

• Frontend: React for Web
• Backend: Python with FastAPI
• Database: MySQL or MariaDB
• AI Models: Not applicable
• AI Tools: Not applicable
• Local Orchestration: Docker, docker-compose
• Server-side Orchestration: Kubernetes

11. Assumptions and Constraints

• The system will primarily serve local businesses in India, considering locale-specific defaults such as currency (INR) and timezone (IST).
• The platform will integrate with WhatsApp for customer interactions.
• The design will be inspired by modern SaaS platforms like Linear, Notion, and Vercel.

12. Glossary

• CRM: Customer Relationship Management
• SaaS: Software as a Service
• REST API: Representational State Transfer Application Programming Interface
• Stripe: A payment processing platform
• Responsive Design: Design that adapts to different screen sizes and devices
• Dark Mode: A color scheme that uses light-colored text and icons on a dark background

This document serves as a comprehensive guide for developing Kiran CRM, ensuring all functional and non-functional requirements are met for a successful product launch.