PE fund with advisory boards, partner-led

We examined AI claims with investors

The investment team at a partner-led PE fund and its advisory boards wanted to better assess technical AI claims in portfolio companies and potential investments.

IndustryFinancial Services
ServicesAI Workshops, Technical Due Diligence

AI promises left operations and effort unexplained

AI features appeared increasingly in pitch decks and portfolio reports. Demonstrations showed successful results but rarely explained the underlying workflow. The investment team could not tell how much manual preparation was needed or who corrected faulty results.

Advisory board meetings also often lacked a shared standard. People used technical terms differently. A model integration could appear to be proprietary technology, while existing process knowledge was barely described. Participants wanted to test business assumptions without having to assess every technical detail themselves.

The workshop had to produce verifiable follow-up questions

Our task was to guide the investment team and advisory boards through assessing AI claims using concrete documents. The goal was a shared review framework for management conversations and technical due diligence. Participants needed to recognize which claims already had evidence, which evidence was missing and when to commission a specialist review.

Product claims became specific review assignments

  • The framework separated features from production evidence

    Participants recorded what an AI feature should do, who uses it and what evidence exists of production use.

  • Questions connected technology to economics

    We added questions about data rights, integrations, manual rework and running costs. Each question related to an assumption in the business model.

  • Red flags prompted relevant evidence requests

    For selected demonstrations without failure cases or for unclear dependencies, we formulated specific follow-up questions. A red flag remained a reason to investigate without prejudging the result.

  • DD assignments used clear language

    The team recorded which business question a technical review should answer and which decision depended on it. This allowed the assignment to be scoped precisely.

Participants switched roles to examine claims

Before the workshop, we collected sanitized excerpts from typical pitch decks and management documents. During the session, participants alternated between management and reviewer roles. This required both sides to explain claims about data, quality and operations clearly.

We initially let a convincing demonstration stand on its own, then added a failure case. This revealed which information had been missing from the first impression. The group asked about handovers to staff, the extent of necessary corrections and updates to the underlying knowledge.

When discussing proprietary technology, we distinguished model access, the data foundation, integration and process knowledge. This helped participants ask more precisely about dependencies and reuse. A model integration received scrutiny before being treated as either unremarkable or a technical advantage.

At the end, the investment team and advisory boards each worked through a complete review assignment. We removed questions whose answers would not change a decision and sharpened the rest. Owners incorporated the framework into their existing templates for management conversations and DD preparation.

Investors and boards could name the missing evidence

The investment team and advisory boards had shared terminology and specific questions for AI claims. When preparing conversations, they could distinguish claims, evidence and outstanding reviews. They could commission deeper technical work around an economically relevant question. The workshop provided a usable framework for further assessments.

Follow-up questions need a link to the investment thesis

  • Ask for an explanation of failure cases

    The response to an incorrect result shows which manual work and responsibilities remain in operations.

  • Ask about the data rights in use

    A working demonstration does not yet prove that the necessary data can be used for the intended purpose over time.

  • Commission reviews that inform decisions

    Define which assumption in the investment thesis needs to be confirmed or disproved before collecting technical details.

A first conversation takes 30 minutes.

We discuss which AI claims your investment team and advisory boards want to examine more closely.