# How founder requests work

> Ask founders for numbers, documents and explanations during diligence, review each answer, and record accepted answers on the deal's claims and facts.

Source: https://delsivo.com/help/founder-requests/how-founder-requests-work · Updated 2026-11-06

## Key takeaways

- A request is a set of questions you send a founder from a deal, built from a template you can adjust.
- The founder answers on your portal, can hand a section to a teammate, and can send answers in parts if you allow it.
- Your team reviews each answer, accepts it or sends it back with a note.
- An accepted answer can be recorded on a claim or as a company fact. Conflicts show before anything changes.

During diligence you need the same things from most companies: revenue by month, customer counts, the cap table, legal and security basics. Founder requests turn those into questions with a due date, answered on your portal.

1. **Build the questions** in a template, with amounts, dates, rows and follow-ups. See [Build a request form](/help/founder-requests/building-a-form).
2. **Send** from the deal, with a due date and reminders. A person always sends. See [Send a request to a founder](/help/founder-requests/sending-a-request).
3. **The founder answers** on your portal. They can ask a teammate to answer a section, and send answers in parts if you allowed it.
4. **Review** each answer: accept it or send it back with a note. See [Review a founder's answers](/help/founder-requests/reviewing-answers).
5. **Record on the deal**: an accepted answer can support or contradict a claim, or become a company fact. The deck's value stays beside it.

For what each state means, see [Request states and reminders](/help/founder-requests/request-states-and-reminders).