Know which claims are verified before the partner meeting
Every material claim keeps its definition, period, units and sources, and one of four labels: founder reported, corroborated, disputed or unresolved.
- Claim tracker and labels Pilot
- Research and Ask This Deal First release
A claim from slide 4 of the deck, 20 enterprise customers, is founder reported. In the interview at 07:42 the founder says 12 of them are unpaid pilots. Both statements are kept with their sources, the claim is marked Disputed, and a task to check paid contracts is assigned to Sam Okafor.
A number is only useful with its definition, period and source
“20 customers” means little until you know who counts as a customer, as of when, and where it was said. Every claim in Delsivo keeps those fields.
| Field | What it holds | Example |
|---|---|---|
| Assertion | What was claimed, in plain words | 20 enterprise customers |
| Metric and definition | What is being counted, and how | Enterprise customers: signed broker accounts |
| Period | When the number applies | As of September 2026 |
| Amount and units | The value and what it is measured in | 20, customers |
| Sources | Every place the claim appears, each a link to the exact spot | Deck v1, slide 4; interview, 07:42 |
| Owner | Who on your team is responsible for checking it | Sam Okafor |
| Evidence label | Where the claim stands now | Disputed |
Four labels, and the text is always shown
Colour is never the only signal. Each label says where a claim stands today, and changes only when a person agrees.
- Founder reported
Stated by the founder in the deck, a form or the interview, not yet checked.
- Corroborated
Backed by a document, a data room file or an analyst's check.
- Disputed
Two sources disagree. Both versions are kept and cited.
- Unresolved
Not enough evidence either way yet. It becomes a question or a task.
The deck says 20 customers. The interview says 12 are unpaid pilots.
Neither statement is thrown away. Both stay with their sources, the claim is marked Disputed, and someone is asked to check.
20 enterprise customers
Disputed- Metric
- Enterprise customers
- Period
- Sep 2026
- Units
- Customers
12 of the 20 are unpaid pilots
Disputed- Metric
- Paying customers
- Period
- Nov 2026
- Units
- Customers
8 customers on paid annual contracts
Corroborated- Period
- Nov 2026
- Units
- Customers
Sample deal. Names and numbers are made up.
- 1
The deck claim is extracted
Slide 4 says 20 enterprise customers. It is recorded as Founder reported, with the quote.
- 2
The interview adds a detail
At 07:42 the founder says 12 of them are unpaid pilots. AI suggests a claim update, citing the timestamp.
- 3
An analyst accepts the update
The claim becomes Disputed. Both statements stay, each with its source.
- 4
A task is created
Ask for the paid contracts. The request goes to the founder through your portal.
- 5
The document arrives
Eight paid contracts in the room corroborate a new claim. The history keeps every step.
Every claim links to the exact spot it came from
A citation opens the slide, the moment in the recording, the form answer or the page of the document. A quote that can't be found in its source is dropped.
Deck slide
Deck version and slide, with the exact quote.
Deck v2 · Slide 4Interview answer
The answer and its start time in the recording.
Interview · 07:42Form answer
The request, the question and the founder's answer.
Revenue quality · Q2Room document
The folder, the file version and the page.
Financials / revenue.xlsx p. 2Web page
The address and the date it was read, for research findings.
Read 4 Nov 2026Analyst check
Who checked what, when, and the note they left.
Checked by S. Okafor
AI suggests claims and updates. Analysts decide what is true enough.
Suggestions sit on lilac with their label until someone accepts them. Accepted corrections carry into later briefs, so the same mistake doesn't come back.
AI suggests, with a citation
- Extracts claims from decks, forms and interviews, each with its source
- Suggests updates when a new source changes a number
- Flags when two sources disagree
- Suggests the question or request that would settle it
People decide, with a reason
- Accepting, editing or dismissing each suggested claim
- Changing a label to Corroborated or Disputed
- Assigning and closing verification tasks
- What goes in front of the partners
Research findings and questions about the deal, with citations
Two first-release features build on the same evidence record.
- First release
Cited research
Market, competitor and funding research with the address and date of every source. Findings are marked public, founder reported or analyst verified.
- First release
Ask This Deal
Ask a question about one deal and get an answer from its deck, interview, forms, room and research, with a citation per sentence.
- First release
Corrections carry forward
An accepted correction is used in later briefs and call preparation, and the earlier version stays in the history.
- First release
Permission-aware answers
Search and AI answers use the same permission check as pages, so a restricted file never leaks through a summary.
Ask This Deal
How many customers pay today, and what is the source?
Illustration of a planned feature, with sample data.
Questions about claims
Walk into partner meetings knowing what was checked
Design partner pilots start with deals you have already reviewed, so you can judge the extraction, the fit reports and the citations against what you know.