Portfolio Analytics Platform (MVP)

What This Product Is

Portfolio Analytics Platform is a web-based SaaS MVP for analyzing multi-asset property portfolios. It helps users move from raw financial entries at the asset level to decision-ready portfolio insights in a single dashboard.

This is a practical analytics product, not a spreadsheet replacement UI. It is designed to make performance interpretation faster, clearer, and more consistent across multiple assets.

Why It Exists (Business Problem)

Teams managing multiple properties often track numbers asset by asset, but make decisions at the portfolio level. This creates a gap:

• Data is entered locally per asset
• Decisions are made globally across the portfolio
• Comparisons and trends are hard to maintain consistently

The platform closes that gap by standardizing financial input, computing consistent KPIs, and aggregating results from each asset into a portfolio-wide view.

Who It Is For

• Portfolio owners and operators managing multiple assets
• Analysts who need structured periodic performance views
• Teams that want a clear MVP foundation before automation/integrations

Core Concepts (Plain-Language Definitions)

• Portfolio: A container grouping multiple assets under one owner. It represents the level where strategic decisions are usually made.
• Asset: A single property/investment unit inside a portfolio. It is the primary level of financial data entry.
• Financial Data (Manual Input): Period-based income and cost entries entered by users for each asset.
• Financial Period: A defined time window (for example a month) with a start and end date used to organize financial records.
• KPI / Financial Metric: A computed indicator that summarizes performance (for example cash flow behavior, cost burden, or coverage quality).
• Aggregation (Asset -> Portfolio): The process of combining metrics and totals from individual assets to produce portfolio-level insight.
• Dashboard and Analytics Views: Product screens that present KPIs, summaries, and trends so users can interpret performance quickly.

How the Product Works Conceptually

1. A user logs into their private account workspace.
2. The user creates one or more portfolios.
3. Inside each portfolio, the user adds assets.
4. For each asset, the user enters financial records by period.
5. The calculation engine computes asset-level metrics from those records.
6. Portfolio-level analytics are generated by aggregating all asset outputs in that portfolio.
7. Dashboard views present totals, KPI cards, trend visuals, and comparative tables.

This flow ensures every portfolio insight is traceable back to asset-level inputs.

Major Product Features

1) Account-Based Data Isolation

Each user sees only their own portfolios, assets, and records. This supports a real SaaS usage model where data privacy is mandatory.

2) Structured Manual Financial Input

Users enter periodized financial data per asset. This gives consistent, auditable inputs and avoids ad hoc data shape differences.

3) Asset Analytics

Each asset has its own KPI summary and period trend view. This helps identify which assets are driving or weakening overall results.

4) Portfolio Analytics

The platform aggregates all assets in a portfolio into one consolidated performance view. This supports prioritization and allocation decisions.

5) Dashboard Experience

Users get a concise overview of portfolio count, asset count, income behavior, and cash-flow direction, with drill-down into details.

6) Demo Data Loader

A logged-in user can load realistic sample data directly from the UI to explore the product behavior without admin/shell access.

KPI Logic: What Each Metric Means

The MVP focuses on practical, interpretable metrics built from manually entered period records.

• Total Revenue

  • Represents core income from operations.
  • Business value: shows gross earning capacity.
  • Inputs: revenue fields across periods.
  • Applies to: asset and portfolio.

• Total Other Income

  • Represents non-core but relevant income entries.
  • Business value: captures additional income sources.
  • Inputs: other income fields across periods.
  • Applies to: asset and portfolio.

• Total Income

  • Represents full income picture (core + other).
  • Business value: baseline for cost and margin interpretation.
  • Inputs: revenue plus other income.
  • Applies to: asset and portfolio.

• Total Operating Expenses

  • Represents recurring costs of operating the asset.
  • Business value: indicates operational burden.
  • Inputs: operating expense entries across periods.
  • Applies to: asset and portfolio.

• Total Capital Expenditures

  • Represents investment spending on asset improvements.
  • Business value: highlights reinvestment intensity and cash impact.
  • Inputs: capital expenditure entries across periods.
  • Applies to: asset and portfolio.

• Total Debt Service

  • Represents financing obligations over the selected records.
  • Business value: shows fixed financing pressure.
  • Inputs: debt service entries across periods.
  • Applies to: asset and portfolio.

• Net Operating Income (NOI)

  • Represents income after operating costs, before financing/capital impacts.
  • Business value: core operating performance indicator.
  • Inputs: total income and operating expenses.
  • Applies to: asset and portfolio.

• Net Cash Flow

  • Represents cash result after operating costs, debt service, and capital spending.
  • Business value: indicates practical cash outcome over time.
  • Inputs: NOI, debt service, and capital expenditures.
  • Applies to: asset and portfolio.

• Operating Expense Ratio

  • Represents how much of income is consumed by operating costs.
  • Business value: helps compare efficiency between assets.
  • Inputs: operating expenses relative to income.
  • Applies to: asset and portfolio.

• Debt Service Coverage Ratio (DSCR)

  • Represents ability of operating performance to cover debt obligations.
  • Business value: financing resilience indicator.
  • Inputs: NOI relative to debt service.
  • Applies to: asset and portfolio.

Asset-Level vs Portfolio-Level Insight

• Asset-level analytics explain local performance and identify outliers.
• Portfolio-level analytics reveal consolidated exposure and overall direction.

The system first computes metrics at asset level, then aggregates those results to portfolio level. This sequencing preserves interpretability and makes portfolio totals explainable.

Dashboard and Analytics Views

• Portfolio Dashboard: cross-portfolio summary cards and comparative rows.
• Portfolio Detail View: consolidated KPIs for one portfolio plus asset list.
• Asset Detail View: KPI summary, period trend chart, and period record table.

These views support a top-down workflow: overview -> portfolio -> asset -> period record.

High-Level Technical Overview

The MVP uses a layered architecture:

• Database layer stores users, portfolios, assets, and financial period records.
• Application layer manages workflows, validation, and access control.
• Calculation engine computes metrics in a dedicated domain layer, isolated from presentation concerns.
• Web UI layer presents dashboards and forms for non-technical users.

Why this structure matters:

• Business logic stays testable and reliable.
• Data ownership/security rules are enforced consistently.
• UI can evolve without rewriting calculation logic.
• Future capabilities (automation, integrations, advanced analytics) can be added on top of stable boundaries.

MVP Scope Boundaries

Phase 1 intentionally focuses on:

• Authentication
• Manual asset-level input
• Asset and portfolio analytics
• Responsive dashboard UX

Not included in this phase:

• External API integrations
• Automated data ingestion
• Advanced forecasting/reporting modules

Additional Project Documentation

• Metric definitions: METRICS_IMPLEMENTED.md
• Render deployment guide: DEPLOY_RENDER.md
• Delivery roadmap: IMPLEMENTATION_ROADMAP.md