Key takeaways
- Start from templates for revenue quality, product, security, customers, cap table, legal and follow-up questions (Pilot).
- Every request has one of seven states, so outstanding items are visible without chasing email threads.
- Reminders go only for items still outstanding, and a request sent by mistake can be revoked.
- Files are scanned for malware before preview or extraction, and suspicious files stay quarantined.
Planned feature: not in Delsivo yet, and details may change before it ships.
Where diligence request lists go wrong
Most funds keep the list in a spreadsheet and send it by email. The founder replies to some items in the thread, uploads others to a shared folder, and answers a few on a call. A week later nobody is sure what is outstanding, two people have asked for the same cap table, and the latest version of the customer list lives in someone's downloads folder.
For the founder it is worse: a long list with no sense of what matters most, reminders about things already sent, and no single place to see what is left.
Request templates and field types
| What | Includes | Release |
|---|---|---|
| Templates | Revenue quality, product, security, customers, cap table, legal, follow-up | Pilot |
| Basic fields | Text, number, select, file, required questions | Pilot |
| Richer fields | Currency, dates, URLs, repeating rows | First release |
| Conditional logic | Show a question only when an earlier answer calls for it | First release |
| Preview and versions | See the form as the founder will, and keep earlier versions | First release |
| Section assignees | The founder assigns a section to a teammate, such as a CFO | First release |
The seven request states
- Draft: being prepared by your team, not visible to the founder.
- Sent: approved by a person and delivered through your portal.
- In progress: the founder has started and can save and come back.
- Submitted: answers and files are in, waiting for your review.
- Changes requested: your team asked for a correction or a missing file.
- Complete: accepted by your team.
- Expired: the deadline passed without a submission.
Reminders go only for items that are still outstanding, and you can revoke a request at any time.
How due diligence request list management works in Delsivo
- 1Pick a template, or start from the unknowns and disputed claims on the deal, and edit the questions.
- 2A partner approves the request, and it goes to the founder through your branded portal.
- 3The founder answers, uploads files and saves progress as they go.
- 4Each upload is scanned, versioned and linked to the item it answers. Downloads use short-lived links issued after a permission check.
- 5An analyst reviews each item and accepts it or asks for changes, with a note the founder can see.
- 6Accepted documents can corroborate claims on the deal, cited by file and page.
From requests to a data room in the first release
In the first release, requests feed a data room with fixed folders: Corporate, Financials, Customers, Product and IP, Security, People and Round Documents. Each item moves through Requested, Uploaded, In review, Accepted or Changes requested. Rooms add file previews, questions on a single file, named guests with expiry, a preview and download policy, watermarks, NDA acknowledgement and an activity log.
In the pilot, file requests already arrive in upload slots, so moving to a room later doesn't mean asking founders for everything again.