Reporting

Reporting is Foundaro's cross-module health dashboard. It aggregates data from Capital, Exit, People, and Partnerships workspaces and surfaces conversion rates, cycle times, overdue risk, response rates, and leakage patterns in a single view — without requiring you to open each module individually.

The module is built around the idea that operational health across multiple workspaces is nearly impossible to track when every module is viewed in isolation. Reports surfaces early warning signals that only become visible when data is compared side by side.

Overview

The Reporting overview loads your current workspace data and builds a consolidated snapshot. If some workspace stores are still loading on first visit, Reporting falls back to a lightweight direct query so the view is never empty.

Stat bar — Five aggregate metrics across all your workspaces:

• Conversion rate — The percentage of pipeline entities that have advanced beyond the earliest stage. A low conversion rate across the board indicates that pipeline is coming in but not progressing.
• Cycle time — The median number of days entities are spending in your pipelines before reaching a terminal stage. Long cycle times may indicate decision-making friction or neglected follow-up.
• Overdue risk — The percentage of pipeline entities whose expected close or resolution date has passed without a status update. High overdue risk means pipeline hygiene is slipping.
• Response rate — The percentage of outreach or meeting activities that have a recorded response or outcome. A low response rate may indicate that contact activity is not being logged or that follow-up is not happening.
• Leakage hotspot — The stage or workspace type where the highest proportion of pipeline is stalling without advancing. This is where to investigate first.

Tips:

• Look at overdue risk and leakage hotspot first — these are the signals most likely to indicate a problem that is actively getting worse, not just one that is already visible.
• The stat bar aggregates across all workspaces. A strong aggregate can mask a specific workspace that is dragging. Drill into the module health section to check.
• These metrics are directional indicators. A low conversion rate in Capital during a bear market is different from the same rate in a hot market — always interpret in context.

Module Health

Module health shows a card for each active workspace type — Capital, Exit, People, Partnerships — with workspace-level metrics and trend indicators.

Per-module metrics:

• Health score — A composite score (0–100) based on pipeline activity, engagement recency, and completion rates specific to that module's entity types.
• Trend — Improving, stable, or slipping. Trend reflects whether the health score has moved up or down over the recent period.
• Workspace count — How many workspaces of this type are active.
• Key metric — A module-specific headline stat: active investors for Capital, qualified buyers for Exit, open roles for People, active partners for Partnerships.
• Risk flags — Module-specific operational warnings, such as investors with no recent contact, buyers with overdue diligence, roles with no funnel activity, or partnerships past renewal date.

Trend interpretation:

• Improving — The workspace is gaining activity, coverage, or engagement compared to the prior period.
• Stable — Activity and coverage are holding steady.
• Slipping — Engagement, activity, or coverage has declined. A slipping trend warrants investigation even if the absolute health score looks acceptable.

Tips:

• Module health trends matter more than snapshots — a workspace with a slipping trend needs investigation even if the current score is not alarming.
• Risk flags in the module health cards are the most actionable outputs from the Reporting view. They identify specific entities or patterns that need attention, not just abstract score movements.
• A stable trend across all modules in a growth period is not a good sign — it means the workspaces are not gaining momentum along with the business.

Risk Analysis

Risk analysis surfaces the specific entities across your workspaces that are contributing most to overdue risk and leakage. Rather than just showing an aggregate percentage, it identifies which contacts, investors, buyers, or partners are the underlying causes.

Stale risk entries — Entities that have not had a status change, meeting, or activity log entry within the risk threshold for their module type. These are the records most likely to go cold or be forgotten.

Risk status labels:

• High — The entity is overdue and has no recent activity. Immediate follow-up is recommended.
• Watch — The entity is approaching the risk threshold but has not yet crossed it. This is the window to re-engage before the situation becomes high.
• Healthy — The entity has recent activity and is within expected cycle time.

Tips:

• High-risk entries should be reviewed weekly — these are the deals, investors, or relationships most at risk of going cold.
• Watch entries are an opportunity to act before a situation escalates. A brief re-engagement when a record is at watch status is far easier than recovering from high risk.
• Use stale risk analysis before outreach sprints to prioritise who to contact first based on urgency rather than recency or personal familiarity.

Workspace Comparison

Workspace comparison shows your individual workspaces ranked by health score within each module type. It makes visible which specific workspaces are driving aggregate performance and which are pulling it down.

Comparison view per module:

• Each workspace is listed with its health score, trend, key metric, and most recent activity date.
• Workspaces are sorted by health score, with the strongest performing first.
• Slipping workspaces are highlighted to make underperforming areas easy to identify.

Tips:

• Use workspace comparison to identify the specific workspaces that need attention rather than treating all workspaces of a given type equally.
• A workspace with a low health score and a recent activity date may just need more time. A workspace with a low score and a stale activity date is more concerning.
• Healthy workspaces can be useful benchmarks — if one Capital workspace has strong engagement and conversion and another does not, compare the approaches being used in each.

See also: Automations guide — push renewal risk, blocked tasks, and stalled partnerships directly into the Reporting layer via automated rules.