Key takeaways
- Planned for a later release.
- Four parts: waiting for review, stale requests, pipeline changes and partner actions.
- Every line links to the deal or the change behind it.
- Revisit alerts for passed deals appear here too.
Planned feature: not in Delsivo yet, and details may change before it ships.
What goes into the weekly partner pipeline brief
| Part | Example line |
|---|---|
| Waiting for review | Four deals screened this week with no reviewer assigned |
| Stale requests | Financials request to a fintech deal unanswered for 12 days |
| Pipeline changes | Two deals moved to Diligence, one passed with its reason |
| Partner actions | Three founder follow-ups waiting for your approval |
| Revisit alerts | A passed deal reports a milestone you recorded |
Example lines are illustrative, not data from any fund.
Why every line links to its source
Partners often see summaries without knowing which claims behind them were checked. The brief is designed the other way round: a line is a pointer, and the deal holds the evidence, with its labels from the claim tracker. If a line is drafted by AI, it is marked as such and any figure in it cites where it came from.
How the brief is put together
- 1Each week Delsivo gathers stage history, request states, approvals waiting and revisit alerts for the partner's deals.
- 2It drafts the brief, grouped by the four parts, with a link on each line.
- 3The brief arrives by email and in the workspace. Email is a notification channel, not an integration.
- 4The partner opens any line to act in the deal itself.
What partners can tune
- Which deals count: their own, their team's or the whole fund, within their permissions.
- What counts as stale, for example no founder reply in 7 or 14 days.
- Whether the brief also goes out mid-week when approvals are waiting.
These settings are part of the later design and may change after pilots. Pipeline reporting by stage, owner and intake source is a separate reporting view.