Meetings

Deals move in conversations, and most of what is decided in them never reaches the deal record. Meetings attaches that conversation to the deal it was about.

Questions this workflow answers

• What was actually said about this deal, and by whom?
• Which claims from that call are worth acting on?
• What did we agree to do, and did it get tracked anywhere?

Recording and processing

Upload a recording to a deal and it is transcribed, then processed into a meeting record. Processing takes time proportional to the recording, and the record shows its own progress rather than leaving you guessing.

The transcript is searchable and stays attached to the deal, so a question six weeks later resolves against what was said instead of what someone remembers.

Claims

Processing extracts claims: specific, checkable statements made in the meeting. A broker asserting a market rent, a seller describing a roof's remaining life, a partner committing to a follow-up.

Claims are proposals, not facts. Each one is presented for a person to confirm, reject, or promote. That distinction is deliberate: a transcript is evidence of what was said, which is not the same as evidence that it is true, and the deal record should not blur the two.

A confirmed claim can become a task on the deal or feed the Diligence risk register as something to verify.

The brief

A meeting brief summarizes a call against the deal it belongs to, so the record is readable without replaying the conversation.

Voice notes

Separately from recorded meetings, the AI assistant can take notes while you think out loud about a deal. Those notes land in the deal's notebook and are visible on the deal Overview. See Deal overview.

Privacy

Recordings and transcripts are deal-scoped and follow the same isolation as the rest of the deal's data. See Data isolation and How EQUIRE processes AI data.