Key takeaways
- Planned for a later release. Passing with a recorded reason is part of the core deal lifecycle.
- Milestones are written at the time of the pass, in plain words.
- Founder updates are compared to those milestones, and alerts link to what changed.
- Reopening keeps the original decision. Nothing reopens on its own.
Planned feature: not in Delsivo yet, and details may change before it ships.
How to track passed deals without losing the history
A pass is a decision with a reason, not a deletion. The deal keeps its deck versions, claims, interview and requests, and the pass rationale sits on the record with who decided and when. The suggested lifecycle has two side states, Passed and Revisit, and authorised users can reopen a passed deal without rewriting the original decision.
Writing revisit milestones
Milestones are the specific evidence that would make the deal worth another look. Good ones are measurable and tied to the reason you passed.
| Pass reason | Revisit milestone |
|---|---|
| Pilots not converting | Three pilot customers converted to paid contracts |
| Too early for our cheque | A priced round led by another investor |
| Single founder, no technical lead | A technical cofounder or senior hire joins |
| Thesis mismatch on geography | Revenue from a market in our thesis |
From founder update to a reopened deal
- 1A founder sends an update through your portal, or an analyst adds one.
- 2Delsivo compares it to the recorded milestones and suggests which, if any, look met, citing the update.
- 3An alert reaches the deal owner with a link to the underlying change.
- 4The owner reviews the evidence and decides whether to move the deal to Revisit or reopen it.
- 5The reopening is logged with its own reason. The first pass decision is kept as it was.
What the later design leaves out
- No automatic reopening, and no message to the founder without approval.
- No scraping of founders' social posts. Updates come through your portal or your team.
- Pass emails stay written and approved by your team.