Skip to content
Delsivo
Use case

Come back to a passed deal with its full history

Pass reasons, deck versions and claims stay on the record, so a returning company is compared with what you knew instead of starting from zero.

How it works

Short answer: To revisit passed startups well, you need to know why you passed and what has changed since. In Delsivo, a pass is a person's decision with a recorded reason, earlier decks and claims stay on the deal, and a new deck becomes a new version whose citations sit beside the old ones. A Revisit stage with milestones and reminders is planned for a later release.

Key takeaways

  • Pass reasons, deck versions, claims and fit runs stay on the deal record (Pilot).
  • A returning founder is suggested as a possible duplicate, and an analyst confirms the merge.
  • Re-running the rubric on a new deck creates a new run beside the old one, so you can compare.
  • Milestones and reminders for revisiting are planned for later. Your retention settings decide how long anything is kept.

Planned feature: not in Delsivo yet, and details may change before it ships.

Why passed deals get lost

Most passes are not a no forever. They are not yet: too early, round too small, a claim that couldn't be checked. Months later the company comes back, or a partner hears about it again, and nobody can find the original deck or remember the reason. The fund either repeats the first review or, worse, passes again for a reason that no longer holds.

What stays on the record after a pass

What a passed deal keeps, by release
ItemWhat is keptRelease
DecksEvery version, with the original filePilot
Extracted factsEach with its slide citation and any founder correctionPilot
ClaimsEach with its label, sources and earlier statementsPilot
Fit reportEvery run and the rubric version it usedPilot
The passWho passed, when and the reasonPilot
InterviewTranscript with timestamps, under your retention settingsFirst release

When the founder applies again

  1. 1The new application arrives and Delsivo suggests it may match the earlier deal, by company domain and founder identity.
  2. 2An analyst confirms the match, and the new submission joins the existing record.
  3. 3The new deck becomes a new version. Citations to the old deck keep working.
  4. 4Re-run the rubric. The new run sits beside the old one, so you see which criteria changed result.
  5. 5Compare claims: where the founder's numbers changed, both statements are on the record with their sources.

How to revisit passed startups on purpose

Waiting for founders to come back only catches the ones who do. Planned for a later release, a Revisit stage lets you note the milestone that would change your mind, such as paid conversion of pilots or a lead investor, and set a reminder to look again. Until then, write that milestone into the pass reason, so whoever reopens the deal knows what to look for.

Founder data and retention

Your fund is the controller of the data founders submit, and Delsivo processes it on your behalf. Funds set retention for decks, recordings and transcripts, and deletion removes previews, search indexes and derived copies. If your retention deletes a passed deal's deck after six months, there will be nothing to revisit, so choose retention with that in mind and say so in your notice to founders.

FAQ

Questions about revisit passed startups

They should. Your fund is the controller of founder data and sets the notice founders see. Delsivo supports your retention settings and founders' requests to delete their data.

Yes. Both versions are kept with their citations, and re-running the rubric shows which criteria changed result. Claims that changed keep both statements.

Not yet. Revisit tracking with milestones and reminders is planned for a later release.
Design partner pilots

Review your next deals with the evidence in one place

We set up your branded portal and thesis rubric with you, calibrate on your historical deals, then run live intake beside your current process.

Talk to us