Idea Details

```markdown
# Master Coding Prompt for Construction/Real Estate CRM MVP

This prompt outlines the requirements for building an MVP CRM specifically tailored for the construction and real estate industries. The focus is on addressing the identified market gaps:

*   Failure to follow up with customers/leads
*   Difficulty in maintaining historical property data for performance analysis
*   No proper system for sales and marketing
*   Lack of real-time updates on properties and inventory
*   Need for customization in construction CRM to fit specific workflows

## Tech Stack

*   **Backend:** Python (Flask) - chosen for rapid development, ease of use, and extensive libraries.
*   **Frontend:** React.js - for a dynamic and responsive user interface.
*   **Database:** PostgreSQL - robust, reliable, and suitable for complex data relationships.
*   **ORM:** SQLAlchemy (Python) - to interact with the database in a Pythonic way.
*   **API:** RESTful API (Flask)
*   **Deployment:** Docker (optional, but recommended for consistency)

## Core Features (Based on USPs)

1.  **Automated Follow-Up & Lead Nurturing:**
    *   **Lead Management:** Capture lead information (name, contact details, property interest, source).  Allow manual entry and import from CSV.
    *   **Automated Workflows:** Define workflows based on lead stage (e.g., New Lead, Qualified Lead, Proposal Sent).  Triggers actions like email sending, task creation, and status updates.
    *   **Email Integration:** Integrate with an email provider (e.g., SendGrid, Mailgun) to send automated emails.
    *   **Reminder System:**  Create tasks and reminders for follow-up calls, meetings, and other activities.  Notifications via email and in-app.

2.  **Dynamic Historical Property Performance Analytics:**
    *   **Property Data:** Store detailed information about properties (address, purchase date, purchase price, square footage, rental income, maintenance costs, property type, status (active, sold, etc.)). Allow property tagging (e.g., 'luxury', 'new development', 'commercial').
    *   **Financial Tracking:**  Record income and expenses associated with each property. 
    *   **Reporting:** Generate reports on property performance metrics (ROI, occupancy rate, gross profit, net profit) over specified time periods.
    *   **Data Visualization:**  Display data in charts and graphs (e.g., line charts showing revenue trends, bar charts comparing property performance).

3.  **End-to-End Sales & Marketing Automation:**
    *   **Sales Pipeline:**  Define sales stages (e.g., Initial Contact, Site Visit, Proposal, Contract Negotiation, Closed Won/Lost).
    *   **Opportunity Management:** Track potential deals (property interested in, estimated value, probability of closing).
    *   **Marketing Campaigns:** Create and manage email marketing campaigns. Segment leads based on demographics and property interest.
    *   **Construction CRM Customization:** Allow administrators to define custom fields and workflows to tailor the CRM to specific construction processes (e.g., permitting stages, inspection schedules).

## Database Schema (PostgreSQL)

```sql
-- Leads Table
CREATE TABLE leads (
    id SERIAL PRIMARY KEY,
    first_name VARCHAR(255),
    last_name VARCHAR(255),
    email VARCHAR(255) UNIQUE NOT NULL,
    phone VARCHAR(20),
    property_interest TEXT, -- Description of what properties they're interested in.
    source VARCHAR(255), -- Where did they hear about us?
    status VARCHAR(255) DEFAULT 'New Lead', -- Lead Status
    created_at TIMESTAMP DEFAULT NOW(),
    updated_at TIMESTAMP DEFAULT NOW()
);

-- Properties Table
CREATE TABLE properties (
    id SERIAL PRIMARY KEY,
    address VARCHAR(255) UNIQUE NOT NULL,
    purchase_date DATE,
    purchase_price DECIMAL(15, 2),
    square_footage INTEGER,
    rental_income DECIMAL(15, 2),
    maintenance_costs DECIMAL(15, 2),
    property_type VARCHAR(255),
    status VARCHAR(255), -- e.g., 'Active', 'Sold', 'Under Renovation'
    created_at TIMESTAMP DEFAULT NOW(),
    updated_at TIMESTAMP DEFAULT NOW()
);

-- Property Financials Table
CREATE TABLE property_financials (
  id SERIAL PRIMARY KEY,
  property_id INTEGER REFERENCES properties(id) ON DELETE CASCADE,
  date DATE,
  income DECIMAL(15, 2),
  expenses DECIMAL(15, 2),
  notes TEXT,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

-- Tasks Table (for follow-up, reminders, etc.)
CREATE TABLE tasks (
    id SERIAL PRIMARY KEY,
    lead_id INTEGER REFERENCES leads(id) ON DELETE CASCADE,
    property_id INTEGER REFERENCES properties(id) ON DELETE CASCADE,
    description TEXT,
    due_date DATE,
    completed BOOLEAN DEFAULT FALSE,
    created_at TIMESTAMP DEFAULT NOW(),
    updated_at TIMESTAMP DEFAULT NOW()
);

-- Opportunities Table
CREATE TABLE opportunities (
  id SERIAL PRIMARY KEY,
  lead_id INTEGER REFERENCES leads(id) ON DELETE CASCADE,
  property_id INTEGER REFERENCES properties(id) ON DELETE CASCADE,
  stage VARCHAR(255), -- Sales stage (e.g., 'Initial Contact', 'Proposal Sent')
  estimated_value DECIMAL(15, 2),
  probability DECIMAL(5, 2), -- Probability of closing (0-1)
  closing_date DATE,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

-- Campaigns Table
CREATE TABLE campaigns (
  id SERIAL PRIMARY KEY,
  name VARCHAR(255),
  description TEXT,
  start_date DATE,
  end_date DATE,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

-- Lead_Campaigns Table (many to many relationship between Leads and Campaigns)
CREATE TABLE lead_campaigns (
  lead_id INTEGER REFERENCES leads(id) ON DELETE CASCADE,
  campaign_id INTEGER REFERENCES campaigns(id) ON DELETE CASCADE,
  PRIMARY KEY (lead_id, campaign_id)
);
```

## Key UI/UX Elements

*   **Dashboard:**  Overview of key metrics (number of leads, property performance, open opportunities, upcoming tasks).
*   **Lead Management Page:**  List of leads with search, filtering, and sorting capabilities.  Ability to view lead details, add notes, and create tasks.
*   **Property Management Page:** List of properties with search, filtering, and sorting. View property details, financials, and associated tasks.
*   **Reporting Page:**  Generate and view reports on property performance and sales activity.  Download reports in PDF or CSV format.
*   **Sales Pipeline View:** Visual representation of the sales pipeline, showing opportunities at each stage.
*   **Drag-and-Drop Functionality:** Where appropriate, allow drag-and-drop interaction (e.g., moving opportunities between sales stages).
*   **Responsive Design:** Ensure the application is accessible on desktops, tablets, and mobile devices.

## API Endpoints (Examples)

*   `GET /leads`:  Get all leads.
*   `POST /leads`:  Create a new lead.
*   `GET /leads/{id}`:  Get a specific lead.
*   `PUT /leads/{id}`:  Update a lead.
*   `DELETE /leads/{id}`:  Delete a lead.
*   `GET /properties`: Get all properties.
*   `POST /properties`: Create a new property.
*   `GET /properties/{id}`: Get a specific property.
*   `PUT /properties/{id}`: Update a property.
*   `DELETE /properties/{id}`: Delete a property.
*   `GET /reports/property_performance`: Generate a property performance report.

## MVP Scope

This MVP should focus on the core features outlined above.  Prioritize functionality over aesthetics initially.  Aim for a functional and user-friendly interface, but don't spend excessive time on pixel-perfect design.  Consider prioritizing one key USP (e.g. Automated Follow-up) and building that out fully before implementing the others. 

## Further Considerations

*   **Authentication and Authorization:** Implement a secure authentication system (e.g., using Flask-Login or similar). Consider role-based access control (RBAC).
*   **Error Handling:** Implement proper error handling and logging.
*   **Testing:** Write unit tests to ensure code quality.
*   **Documentation:** Document the API and database schema.

This prompt provides a solid foundation for building the MVP. Further refinement and adjustments may be necessary as development progresses.
```