Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature- Prospect System #3731

Open
2 of 3 tasks
Ayush8923 opened this issue Oct 18, 2024 · 1 comment
Open
2 of 3 tasks

Feature- Prospect System #3731

Ayush8923 opened this issue Oct 18, 2024 · 1 comment
Assignees

Comments

@Ayush8923
Copy link
Member

Ayush8923 commented Oct 18, 2024

Problem Statement
Currently, there is no system in place to track pre-sales activities, and everything is being tracked manually. This process makes it difficult to monitor the status of proposals sent to various organizations and to see which proposals are still ongoing. This manual tracking can lead to inefficiencies, missed opportunities, and a lack of clear visibility.

Objective
We need a streamlined system to manage pre-sales efforts. The goal is to create a Pre-Sales Dashboard that allows users to view and track all proposals sent to potential clients. This dashboard will provide clarity on the status of each proposal, helping the team stay organized and informed about ongoing deals.

Proposed Solution
To address the need for pre-sales tracking, we propose making the following enhancements to the current sales module:

  1. UI for Adding New Prospects
  2. Prospect Dashboard
  3. Editing and Updating Prospects

Action Items

  • Create the UI for the Add New Prospect form, ensuring all fields listed in the spreadsheet are included.
  • Design and implement the Prospect Dashboard to display active prospects and relevant columns.
  • Enable users to update the prospect details and change their details as needed.
@Ayush8923 Ayush8923 self-assigned this Oct 18, 2024
@GauravGusain98 GauravGusain98 changed the title Feature- Pre-Sales System Feature- Prospect System Oct 18, 2024
@Ayush8923
Copy link
Member Author

Here is the Database Structure of the Prospect Flow.


1. Prospect Table

This table contains the general information about each prospect.

Column Name Data Type Description
id INT Primary Key
organization_name VARCHAR Name of the organization
poc VARCHAR Point of contact (POC)
proposal_sent_date DATE Date the proposal was sent
domain VARCHAR Domain of the organization
customer_type VARCHAR Type of customer (e.g., new, existing)
budget DECIMAL Budget for the project
status ENUM Status of the prospect (e.g., in-progress, won)
introductory_call DATE Date of the introductory call
last_followup_date DATE Date the last follow-up was sent
rfp_link VARCHAR Link to the RFP document
proposal_link VARCHAR Link to the proposal document

2. Prospect Followup Responses Table

Tracks the follow-up responses from users regarding each prospect.

Column Name Data Type Description
id INT Primary Key
followup_response TEXT Response details
user_id INT Foreign Key (references users table)
prospect_id INT Foreign Key (references prospects table)
created_at TIMESTAMP Timestamp when the response was created

3. Prospect Comments Table

Store comments related to each prospect.

Column Name Data Type Description
id INT Primary Key
comment TEXT Comment text
user_id INT Foreign Key (references users table)
prospect_id INT Foreign Key (references prospects table)
created_at TIMESTAMP Timestamp when the comment was made

4. Prospect Insights Table

Records insights and learnings about each prospect.

Column Name Data Type Description
id INT Primary Key
insight_learning TEXT Insight/learning from the prospect
user_id INT Foreign Key (references users table)
prospect_id INT Foreign Key (references prospects table)
created_at TIMESTAMP Timestamp when the insight was created

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant