With Dealflow Review, users can filter deals by stage, industry, fundraising amount, or other custom criteria, and then customize the presentation layout using default or custom fields. Components such as documents, notes, and deal metrics can also be added to the presentation, ensuring that the team has all the relevant information in one place. This makes pipeline reviews faster, more structured, and better aligned with the fund’s priorities.
The clients can also save templates of their reviews to be used at their preferred cadence.
Key use cases
1. Monday Review
- Purpose: Prepare the weekly pipeline review with a clear, structured overview of deals in the fund’s pipeline.
- Example: Every Monday, partners and analysts review the deals currently in the pipeline. Using Dealflow Review, they generate a presentation showing deals in specific stages or sectors, with all relevant metrics and documents attached, enabling focused discussions on progress and next steps.
2. Business Metrics Evaluation
- Purpose: Quickly evaluate key metrics for each company according to your fund’s priorities.
- Example: Partners want to see which metrics are most relevant for their investment thesis. Dealflow Review allows them to create a presentation highlighting revenue growth, ARR, churn, or any custom KPIs, making it easy to spot trends or outliers across deals.
3. High-Priority Deals
- Purpose: Identify and discuss the deals that should be prioritized due to promise or urgency.
- Example: The team wants to focus on deals with the largest fundraising rounds or those requiring immediate attention. Dealflow Review lets them filter for high-priority deals and assemble presentations with notes, documents, and custom metrics to guide decision-making.
4. Investment Committee
- Purpose: Facilitate final decision-making before investment by consolidating all relevant information for IC members.
- Example: Before an Investment Committee meeting, the team generates a presentation showing only the deals under consideration, with full metrics, documents, notes, and custom fields. Only IC members provide feedback or commentary, ensuring structured, focused discussions.
Metrics
The product team should define success metrics for launch (e.g., adoption, engagement).
The above will also be used to measure the success of these initiatives.
Next Steps
- Finalize and schedule launch announcement (email + in‑app).
- Schedule the four post‑launch use case emails above (1 per week or bi‑weekly, or cadence TBD).
- Post‑launch: track adoption & gather client success stories if possible.
- Analyze results internally, and validate the project or adapt it if needed.