System Requirements Document (SRD)

Project Name: verdant-hi

1. Introduction

The verdant-hi project is a versatile service management application designed to cater to all kinds of service industries. It aims to streamline operations by enabling users to create and manage requests, quotes, jobs, and invoices efficiently. With support for multiple roles, the system ensures dynamic collaboration between admins, service providers, and customers.

This document outlines the system requirements for verdant-hi, ensuring clarity and alignment with the project's goals.

2. System Overview

verdant-hi is a web and mobile application that provides a comprehensive platform for service management. It is designed to be adaptable across various industries, such as plumbing, IT services, cleaning, and more. The system supports multiple user roles, including admins, service providers, and customers, to facilitate seamless interaction and task management.

Key features include:

• Request creation and tracking
• Quote generation and approval
• Job assignment and monitoring
• Invoice generation and payment processing

The system is built with scalability and user-friendliness in mind, ensuring it can grow alongside the needs of its users.

3. Functional Requirements

As story points:

• As Admin I should be able to manage user roles, including assigning multiple roles to a single user.
• As Admin I should be able to oversee all requests, quotes, jobs, and invoices.
• As Service Provider I should be able to view and accept job assignments.
• As Service Provider I should be able to generate quotes for customer requests.
• As Customer I should be able to create service requests.
• As Customer I should be able to view quotes and approve them.
• As Customer I should be able to track job progress and receive invoices.

4. User Personas

Admin

• Responsibilities: Manage user roles, oversee system operations, ensure smooth workflows.
• Access: Full access to all system features.

Service Provider

• Responsibilities: Handle job assignments, generate quotes, update job statuses.
• Access: Limited access to jobs, quotes, and invoices related to their assignments.

Customer

• Responsibilities: Create service requests, approve quotes, track job progress, and process invoices.
• Access: Limited access to their own requests, quotes, jobs, and invoices.

5. Visuals Colors and Theme

Color Palette

The verdant-hi project will use a fresh and professional color palette inspired by nature and growth, reflecting the versatility and dynamism of service industries:

• Background: #F5F9F6 (Soft Mint Green)
• Surface: #E8F0E6 (Light Sage Green)
• Text: #2E3B32 (Deep Forest Green)
• Accent: #FFD700 (Golden Yellow)
• Muted Tones: #A9B8A6 (Muted Olive Green)

6. Signature Design Concept

Concept: Interactive Service Ecosystem

The homepage of verdant-hi will feature an interactive ecosystem map that visually represents the service management workflow.

Details:

• Visual Layout: A dynamic map with interconnected nodes representing Requests, Quotes, Jobs, and Invoices.
• Animations: Nodes will pulse gently to indicate activity, and connections between nodes will light up when hovered over.
• User Interaction: Clicking on a node will zoom into its details, allowing users to interact with the specific feature (e.g., view requests or manage quotes).
• Color Shifts: The map's colors will subtly shift based on the time of day, transitioning from warm tones in the morning to cooler tones at night.
• Micro-Interactions: Hovering over a node will display a tooltip with quick stats (e.g., "5 pending requests").

This bold and engaging design will make the homepage memorable and intuitive, ensuring users feel immersed in the service management process.

7. Non-Functional Requirements

• Scalability: The system must support a growing number of users and service requests without performance degradation.
• Localization: The application will support locale-specific defaults for India, including currency (INR) and timezone (IST).
• Security: Implement robust authentication and authorization mechanisms to protect user data.
• Performance: Ensure response times are under 2 seconds for all major operations.

8. Tech Stack

Frontend

• React for Web
• React Native for Mobile App

Backend

• Python
• FastAPI

Database

• MySQL or MariaDB (preferred for RDBMS, with Alembic for migrations)
• MongoDB for NoSQL storage

AI Models

• GPT 5.4 for user-friendly responses
• Claude 4.6 Opas for academic or coding work
• Gemini 3.1 Pro for friendly responses
• Google Nano Banana for image generation

AI Tools

• Litellm for LLM Routing
• Langchain

Orchestration

• Docker and docker-compose for local orchestration
• Kubernetes for server-side orchestration

9. Assumptions and Constraints

Assumptions

• Users will have access to stable internet connections.
• The system will primarily be used in India, with support for INR and IST.
• Users will have basic familiarity with service management workflows.

Constraints

• The system must comply with Indian data protection regulations.
• The application must be optimized for both web and mobile platforms.

10. Glossary

• Request: A service inquiry initiated by a customer.
• Quote: A cost estimate provided by a service provider for a specific request.
• Job: A service task assigned to a service provider.
• Invoice: A payment document generated after job completion.
• Admin: A user role responsible for managing the system and user permissions.
• Service Provider: A user role responsible for fulfilling service requests.
• Customer: A user role responsible for initiating service requests and approving quotes.