Ask founders once, and keep every answer with its file
Follow-up forms and file requests go out through your portal. Uploads are scanned, versioned and filed, and guests see only what you share, until it expires.
- Basic forms and file requests Pilot
- Conditional forms and full rooms First release
A revenue quality request goes to the founder. She answers that some customers prepay, so a follow-up question about revenue recognition appears. She uploads a revenue schedule, which lands in the Financials folder and moves from Uploaded to In review to Accepted. A bank statement that failed the malware scan stays quarantined.
Sample data. The fund, founder, company and numbers are made up.
Ask once, from a template, through your portal
Requests go to the founder on your branded portal, with a due date. Every message to a founder is approved by someone on your team first.
Revenue quality
Revenue by customer, contract terms, prepayments and how revenue is recognised.
Customers
Customer list, contracts, pilots and references you may contact.
Product
Architecture, roadmap, usage data and what is built versus planned.
Security
Security practices, incidents, certifications held or planned, data handling.
Cap table
Current ownership, option pool, convertible instruments and the round on offer.
Legal
Incorporation, IP assignment, material contracts and disputes.
Follow-up
Free-form questions after a call or an interview.
What forms can do, by release
| Pilot | First release | |
|---|---|---|
| Field types | Text, number, select, file, required | Adds currency, dates, web addresses and repeating rows |
| Conditional questions | Not yet | Show a question only when an earlier answer needs it |
| Versions | One form per request | Templates are versioned, so a sent request never changes under the founder |
| Preview | Not yet | See exactly what the founder will see before sending |
| Sections and delegation | One founder answers | Assign sections to teammates, and founders can delegate to a colleague |
A conditional question in practice: “Do any customers prepay annually?” If the founder answers yes, the form asks “How is prepaid revenue recognised?”. If no, the question never appears.
Always know what is outstanding
Each request has one state, on its own track, separate from the deal's stage. A request can be outstanding while the deal sits in Screening.
- Draft
- Being written by your team. The founder sees nothing yet.
- Sent
- Approved and sent through your portal, with a due date.
- In progress
- The founder has started answering or uploading.
- Submitted
- The founder has sent everything asked for.
- Changes requested
- Your team asked for a correction or a missing item.
- Complete
- Accepted by your team.
- Expired
- Past its date, or revoked. No more uploads are accepted.
Seven folders, and every item has a state
Uploads land in the folder they belong to. Your team moves each item from Requested to Accepted, or asks for changes.
- Corporate
- Financials
- Customers
- Product and IP
- Security
- People
- Round Documents
Item states
- Requested
- Uploaded
- In review
- Accepted
- Changes requested
- A checklist per folder shows what is still missing.
- Replacing a file adds a version; earlier versions stay.
- Previews open in the browser after the scan, without downloading.
- Questions can be asked on a single file, and the answer stays with it.
Full rooms: First release
Every file is scanned before anyone opens it
Data rooms hold the most sensitive documents a startup has. Delsivo treats every upload as untrusted until it is checked.
- Pilot
Scan and quarantine
Malware scanning runs before preview, extraction or indexing. A file that fails stays quarantined, nobody can open it, and staff are alerted.
- Pilot
Private, encrypted storage
Files sit in private storage, encrypted at rest, under your fund's own prefix.
- Pilot
Short-lived links
Downloads and previews use signed links that expire quickly, issued only after a permission check.
- Pilot
Versions
A replacement is a new version of the same item. Citations keep pointing at the version they came from.
- Pilot
Scoped file requests
Each request says where its files go, so uploads arrive filed instead of in an email thread.
- Pilot
Revocation
Revoke a request or a guest at any time. Open links stop working.
Share with named guests, until access expires
Co-investors, experts and committee members see only what you share, and you see what they opened.
- First release
Named guests with expiry
Invite a person by email to chosen folders or files, until a date you set.
- First release
Preview or download
Choose per guest whether files can be downloaded or only previewed.
- First release
Watermark
Guest previews carry the watermark text you set for that share.
- First release
NDA acknowledgement
Ask guests to acknowledge your terms before the room opens.
- First release
File-level questions
Questions and answers attached to a single file, visible to the people who can see that file.
- First release
Activity log
Every view, download and share, with who and when.
What arrives when
Requests and file collection start in the pilot. The room itself arrives in the first release.
- Pilot
- Basic forms: text, number, select, file, required
- Scoped file requests and upload slots
- Request states and reminders for outstanding items
- Scanning, quarantine, versions and short-lived links
- First release
- Versioned, conditional forms with preview
- Sections, assignees and delegation
- Rooms with seven folders and item states
- Guests, watermark, NDA acknowledgement, activity log
- Later
- Frozen committee packets built from room documents
- Portfolio handoff after closing
- CRM import and export
Questions about requests and rooms
Collect diligence through your own portal
In a pilot, follow-up forms and file requests go to founders on your branded portal, and every answer stays with the deal.