Key takeaways
- Each claim holds the assertion, metric definition, period, amount, units, source links, owner and state.
- Claims come from the deck, forms, interviews, the data room and analysts' own notes.
- When a new source contradicts an old one, both are kept, and a verification task can be created.
- AI suggests claims and changes. An analyst accepts, edits or dismisses each one.
Planned feature: not in Delsivo yet, and details may change before it ships.
Why a startup claims tracker matters
Partners often read a summary without knowing which numbers have been checked. "$40k MRR" might come from a slide, a call, or a bank statement in the data room. It might be gross or net, this month or an average. When the claim is a line in a memo, that context is gone.
The tracker keeps it. Every material statement becomes a record you can open, with the source it came from and the label that says how far it has been verified.
What a claim record holds
| Field | Example |
|---|---|
| Assertion | Monthly recurring revenue of $40k |
| Metric definition | Net of refunds, subscription revenue only |
| Period | September |
| Amount and units | 40,000 USD per month |
| Sources | Deck v2, slide 8; revenue form answer; analyst check |
| Owner | The analyst responsible for checking it |
| State | Founder reported, Corroborated, Disputed or Unresolved |
A worked example: 20 customers or 12 pilots
- 1The deck says "20 enterprise customers" on slide 7. Delsivo suggests a claim, labelled Founder reported, citing that slide.
- 2Later, the founder clarifies that 12 of the 20 are unpaid pilots.
- 3Delsivo suggests a second claim from that statement. The first is not overwritten. Both stay, each with its own source.
- 4A verification task is created for the analyst: confirm how many accounts pay.
- 5The analyst requests a customer list through a founder information request, checks it and marks the paid-customer claim Corroborated.
- 6The approved correction carries into future briefs, so nobody repeats the original figure by mistake.
This is the example from the product requirements, and it shows the rule: earlier statements are kept, not erased, when the facts change.
Where claims come from
AI suggestions are labelled and look different from findings an analyst has checked. Nothing becomes part of the record until someone accepts it.
- Deck facts with slide citations, each with a verbatim quote.
- Answers to forms and requests.
- Interview answers, with timestamped excerpts, once interviews arrive in the first release.
- Files in the data room, cited by version and page in later releases.
- An analyst's own notes from a call or reference check.
Who works on claims
Each claim has an owner, usually the analyst on the deal. Partners can filter the tracker to see what is still unverified before a meeting. Founders don't see claim states. They see the questions and requests your team chooses to send them. The full set of labels is explained on evidence labels.