MVP CRM System Development
Budget: $750 – $1,500 USD
Software Requirements Specification (SRS)
MVP CRM System
Project Name: RiskOptiks CRM – MVP
Platform: Bubble.io
Document Version: 1.0
Prepared By: Waqar Ahmad
Date: 10 Feb 2026
Budget: $1000
1. Introduction
1.1 Purpose
This document defines the requirements for the Minimum Viable Product (MVP) version of the RiskOptiks CRM system.
The MVP focuses only on the following priority areas requested by the client:
1. Home Page
2. Client Page
3. Supplier Page
4. Support Cases
5. Opportunities
The objective is to deliver a working MVP that allows early internal use and validation while staying within the agreed MVP budget.
1.2 Scope
The MVP will include:
● Core data pages for Clients, Suppliers, Support Cases, and Opportunities
● Basic create, view, edit, and delete functionality
● Simple linking between records – please explain what you mean by simple?
● Search and list views
● Minimal automation – please explain a bit about what minimal automation will be?
2. Pages in Scope (Priority Order)
Priority Page
1 Client
2 Supplier
3 Support Cases
4 Opportunities
3. Functional Requirements
3.1 Client Page
3.1.1 Description
Stores and manages enterprise client accounts.
3.1.2 Features
● Create, view, edit, and delete client records
● Display client list with search
● View a client profile
● Show linked:
○ Suppliers
○ Support Cases
○ Opportunities
3.1.3 Fields
● Account Name
● RO_ID
● Country
● Industry
● Status
● Account Manager (user relationship)
● Client Success Manager (user relationship)
● Client Health (option set: Green, Amber, Red, Grey)
● Client Health Details (text, multi-line)
● Account Status (option set: Active, Pending, Prospect, Lead)
● Key Contact (relationship to Contact entity)
3.2 Supplier Page
3.2.1 Description
Stores suppliers linked to a Client.
3.2.2 Features
● Create, view, edit, and delete supplier records
● Require each supplier to be linked to a Client – not required
● Display supplier list with search
● View supplier profile
● Show related Support Cases
3.2.3 Fields
● Account Name
● RO_ID
● Status
● Email
● Phone
● Related Client – not required
● Account Status (option set: Active, Inactive, Pending, Registered, Unregistered)
● Primary Contact (relationship to Contact entity)
● Phone (text)
● Email (email)
● Related support cases
3.3 Support Cases Page
3.3.1 Description
Tracks support requests from Clients or Suppliers.
3.3.2 Features
● Create cases manually – future consideration by creating a case when support email is emailed.
● Auto-generate a case number
● Link case to Client or Supplier
● Assign a case owner
● Update status and priority
● Add notes
● Close cases
● List view with filters and search
● Basic email notification on assignment
3.3.3 Fields
● Case Number
● Linked Client or Supplier
● Subject
● Priority
● Status
● Notes
● Assigned User
● Primary Contact (relationship to Contact entity)
● Phone (text)
● Email (email)
● Time/Date of Case Open (date & time, auto-generated)
● Time/Date of Case Closed (date & time)
● Case Type (option set: Billing, Technical Query, General Query, Account Issue, Product Feedback, Bug Report, Feature Request)
● Case Status (option set: New, Waiting on Client, Waiting on RO, Waiting on Supplier, In Progress, Resolved, Closed)
● Subject/Title
3.4 Opportunities Page
3.4.1 Description
Tracks potential sales opportunities for Clients.
3.4.2 Features
● Create and edit opportunities
● Link opportunity to a Client
● Update stage
● Record amount and close date
● Mark opportunities as Won or Lost
● List view with search
3.4.3 Fields
● Opportunity Name
● Client
● Stage – option set: Prospect, Demonstrate Value, Define Scope, Agree on Launch, Document Plan and Requirements, Execute Mailing, Closed Won, Closed Lost)
● Amount
● Close Date
● Notes
● Forecast Category (option set: Pipeline, Best Case, Commit, Closed)
● Type (option set: Existing Business, New Business)
● Country (option set)
● Opportunity Owner (user relationship)
● Created Date (date, auto-generated)
4. Non-Functional Requirements
The MVP will include:
● Standard login system
● Navigation menu
● Desktop-friendly layout
● Mobile Responsiveness
● Basic data validation
● Performance optimization
5. Delivery Timeline
Phase Duration
Database & Base Setup 1 week
Client & Supplier Pages 1 week
Support Cases 4–5 days
Opportunities 3–4 days
Testing & Handover 2–3 days
Estimated Total: 3–4 weeks
6. Future Phases (Post-MVP)
Future phases may include:
● Campaign management
● Dashboards & reporting
● Integrations with RiskOptiks platform
● Advanced permissions
● Automation workflows
● Contracts and contacts
● Compliance and audit tools
These will be scoped and priced separately.
MVP CRM System
Project Name: RiskOptiks CRM – MVP
Platform: Bubble.io
Document Version: 1.0
Prepared By: Waqar Ahmad
Date: 10 Feb 2026
Budget: $1000
1. Introduction
1.1 Purpose
This document defines the requirements for the Minimum Viable Product (MVP) version of the RiskOptiks CRM system.
The MVP focuses only on the following priority areas requested by the client:
1. Home Page
2. Client Page
3. Supplier Page
4. Support Cases
5. Opportunities
The objective is to deliver a working MVP that allows early internal use and validation while staying within the agreed MVP budget.
1.2 Scope
The MVP will include:
● Core data pages for Clients, Suppliers, Support Cases, and Opportunities
● Basic create, view, edit, and delete functionality
● Simple linking between records – please explain what you mean by simple?
● Search and list views
● Minimal automation – please explain a bit about what minimal automation will be?
2. Pages in Scope (Priority Order)
Priority Page
1 Client
2 Supplier
3 Support Cases
4 Opportunities
3. Functional Requirements
3.1 Client Page
3.1.1 Description
Stores and manages enterprise client accounts.
3.1.2 Features
● Create, view, edit, and delete client records
● Display client list with search
● View a client profile
● Show linked:
○ Suppliers
○ Support Cases
○ Opportunities
3.1.3 Fields
● Account Name
● RO_ID
● Country
● Industry
● Status
● Account Manager (user relationship)
● Client Success Manager (user relationship)
● Client Health (option set: Green, Amber, Red, Grey)
● Client Health Details (text, multi-line)
● Account Status (option set: Active, Pending, Prospect, Lead)
● Key Contact (relationship to Contact entity)
3.2 Supplier Page
3.2.1 Description
Stores suppliers linked to a Client.
3.2.2 Features
● Create, view, edit, and delete supplier records
● Require each supplier to be linked to a Client – not required
● Display supplier list with search
● View supplier profile
● Show related Support Cases
3.2.3 Fields
● Account Name
● RO_ID
● Status
● Phone
● Related Client – not required
● Account Status (option set: Active, Inactive, Pending, Registered, Unregistered)
● Primary Contact (relationship to Contact entity)
● Phone (text)
● Email (email)
● Related support cases
3.3 Support Cases Page
3.3.1 Description
Tracks support requests from Clients or Suppliers.
3.3.2 Features
● Create cases manually – future consideration by creating a case when support email is emailed.
● Auto-generate a case number
● Link case to Client or Supplier
● Assign a case owner
● Update status and priority
● Add notes
● Close cases
● List view with filters and search
● Basic email notification on assignment
3.3.3 Fields
● Case Number
● Linked Client or Supplier
● Subject
● Priority
● Status
● Notes
● Assigned User
● Primary Contact (relationship to Contact entity)
● Phone (text)
● Email (email)
● Time/Date of Case Open (date & time, auto-generated)
● Time/Date of Case Closed (date & time)
● Case Type (option set: Billing, Technical Query, General Query, Account Issue, Product Feedback, Bug Report, Feature Request)
● Case Status (option set: New, Waiting on Client, Waiting on RO, Waiting on Supplier, In Progress, Resolved, Closed)
● Subject/Title
3.4 Opportunities Page
3.4.1 Description
Tracks potential sales opportunities for Clients.
3.4.2 Features
● Create and edit opportunities
● Link opportunity to a Client
● Update stage
● Record amount and close date
● Mark opportunities as Won or Lost
● List view with search
3.4.3 Fields
● Opportunity Name
● Client
● Stage – option set: Prospect, Demonstrate Value, Define Scope, Agree on Launch, Document Plan and Requirements, Execute Mailing, Closed Won, Closed Lost)
● Amount
● Close Date
● Notes
● Forecast Category (option set: Pipeline, Best Case, Commit, Closed)
● Type (option set: Existing Business, New Business)
● Country (option set)
● Opportunity Owner (user relationship)
● Created Date (date, auto-generated)
4. Non-Functional Requirements
The MVP will include:
● Standard login system
● Navigation menu
● Desktop-friendly layout
● Mobile Responsiveness
● Basic data validation
● Performance optimization
5. Delivery Timeline
Phase Duration
Database & Base Setup 1 week
Client & Supplier Pages 1 week
Support Cases 4–5 days
Opportunities 3–4 days
Testing & Handover 2–3 days
Estimated Total: 3–4 weeks
6. Future Phases (Post-MVP)
Future phases may include:
● Campaign management
● Dashboards & reporting
● Integrations with RiskOptiks platform
● Advanced permissions
● Automation workflows
● Contracts and contacts
● Compliance and audit tools
These will be scoped and priced separately.