tidal-estimate

byRajesh Reddy Guthikonda

Estimate follow-up tracker Remodelers, HVAC installers, roofers, photographers, cleaning companies Small service businesses routinely send quotes and then fail to follow up consistently; this is revenue leakage rather than a “nice-to-have.” Import leads/quotes, automate follow-ups, track reasons for lost deals, and show recovered pipeline; $59–199/month

LandingAuthenticationDashboard
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document
Page 1 of 6

System Requirements Document for Tidal-Estimate

1. Introduction

Tidal-Estimate is a SaaS solution designed to help small service businesses, such as remodelers, HVAC installers, roofers, photographers, and cleaning companies, manage and automate follow-ups on leads and quotes. This tool aims to reduce revenue leakage by ensuring consistent engagement with potential clients and tracking reasons for lost deals.

2. System Overview

Page 2 of 6

2a. Product Interpretation and Delivery Boundary

  • Domain Descriptors:

    • Lead and Quote Management: The product focuses on importing leads and quotes to streamline follow-up processes.
    • Follow-up Automation: Automating follow-ups to ensure consistent engagement with potential clients.
    • Deal Tracking and Analysis: Tracking reasons for lost deals and visualizing recovered pipeline to optimize sales strategies.
  • Product Being Built:

    • A SaaS platform that allows small service businesses to import leads/quotes, automate follow-ups, track reasons for lost deals, and display recovered pipeline.
  • Excluded Assumptions:

    • Generic CRM features
    • In-app billing or payment processing
  • Access:

    • Application-owned identity is required for secure access to the platform.
  • Behavior Contracts:

    • Import Leads and Quotes: Service Business Owner uploads or syncs lead data, resulting in leads and quotes being imported into the system.
    • Automate Follow-ups: Scheduled follow-up times trigger automated follow-up messages to be sent.
    • Track Reasons for Lost Deals: When a deal is marked as lost, the reason is recorded.
    • Show Recovered Pipeline: Accessing the pipeline dashboard displays a visual representation of the recovered pipeline.
Page 3 of 6

2b. Source Content Inventory

No explicit content sources were provided.

2c. Page Content and Component Coverage

  • Landing Page:

    • Orientation for new users
    • Overview of features and benefits
    • Call-to-action for sign-up
  • Authentication Page:

    • Sign-up, login, and session management
    • Error handling for failed login attempts
  • Dashboard:

    • Import leads/quotes interface
    • Automated follow-up scheduling and tracking
    • Visualization of recovered pipeline
    • Interface for tracking reasons for lost deals

3. Functional Requirements as Story Points

  • As a Service Business Owner, I should be able to import leads and quotes to streamline my follow-up processes. explicit
  • As a Service Business Owner, I should be able to automate follow-ups to ensure consistent engagement with potential clients. required_inference
  • As a Service Business Owner, I should be able to track reasons for lost deals to optimize my sales strategies. required_inference
  • As a Service Business Owner, I should be able to view a visual representation of my recovered pipeline. required_inference
  • As a Service Business Owner, I should be able to sign up, log in, and manage my session to securely access my dashboard and workflows. required_inference
Page 4 of 6

4. User Personas

  • Service Business Owner: The primary user responsible for managing leads and follow-ups. This persona includes remodelers, HVAC installers, roofers, photographers, and cleaning companies.

5. Core User Flows

  1. Landing Page to Authentication:

    • User visits the Landing page.
    • User is oriented with the product features and benefits.
    • User clicks on the sign-up call-to-action.
  2. Authentication to Dashboard:

    • User signs up or logs in through the Authentication page.
    • Upon successful authentication, the user is redirected to the Dashboard.
  3. Dashboard Operations:

    • User imports leads and quotes.
    • User schedules and automates follow-ups.
    • User tracks reasons for lost deals.
    • User views the recovered pipeline visualization.
Page 5 of 6

6. Visuals Colors and Theme

[Default — not specified by user]

  • Primary: #007BFF (Blue)
  • Primary Light: #66B2FF (Light Blue)
  • Secondary: #6C757D (Gray)
  • Accent: #28A745 (Green)
  • Highlight: #FFC107 (Yellow)
  • Background: #F8F9FA (Light Gray)
  • Surface: #FFFFFF (White)
  • Text: #212529 (Dark Gray)
  • Text Muted: #6C757D (Muted Gray)
  • Border: #DEE2E6 (Light Gray)

7. Signature Design Concept

The Dashboard page will feature a clean and intuitive design, focusing on clarity and ease of use. The primary color (blue) will be used for key action buttons and highlights, while the secondary color (gray) will provide a neutral backdrop for text and data. The accent color (green) will be used sparingly to draw attention to important notifications or actions, such as successful imports or follow-ups.

8. Interaction Model & Motion Direction

  • Dashboard: Animated with moderate scroll-triggered reveals and hover transitions to enhance user interaction without overwhelming the user.
  • Landing Page: Animated with a restrained 2D Hero motion to engage users upon entry.
Page 6 of 6

9. Non-Functional Requirements

No additional non-functional requirements were inferred.

10. Tech Stack

  • Frontend: React for Web
  • Backend: Python with FastAPI
  • Database: MySQL or MariaDB, using Alembic for migrations
  • Local Orchestration: Docker and docker-compose

11. Assumptions and Constraints

  • The system will not include generic CRM features or in-app billing.
  • Persistent identity is required for secure access to the platform.

12. Glossary

  • Lead: A potential client or customer.
  • Quote: A formal statement of the estimated cost for a service.
  • Pipeline: The process of managing and tracking sales prospects.
  • Follow-up: The act of contacting a lead or client after an initial interaction.
Landing design preview
Landing: View product features and sign-up call-to-action
Authentication: Sign up or log in
Dashboard: Workspace ready for lead and follow-up operations
Dashboard: Upload or sync lead data
Dashboard: Configure follow-up schedule and templates
Dashboard: Scheduled follow-up time reached
Notification System: Send automated follow-up message
Dashboard: Mark deal as lost and record reason
Dashboard: View recovered pipeline visualization
Dashboard: Failed import notification
Dashboard: Follow-up not sent
Dashboard: Reason not recorded
Dashboard: Pipeline not displayed
Landing design preview
Landing: View product features and sign-up call-to-action
Authentication: Sign up or log in
Dashboard: Workspace ready for lead and follow-up operations
Dashboard: Upload or sync lead data
Dashboard: Configure follow-up schedule and templates
Dashboard: Scheduled follow-up time reached
Notification System: Send automated follow-up message
Dashboard: Mark deal as lost and record reason
Dashboard: View recovered pipeline visualization
Dashboard: Failed import notification
Dashboard: Follow-up not sent
Dashboard: Reason not recorded
Dashboard: Pipeline not displayed