GETTING STARTED WITH UNDERLYING

Bring Underlying into your deal workflow.

Start with a demo of source review, Findings, and IC drafting. Then agree the source pack, memo format, review roles, and commercial scope for your team.

Before the pilot

Agree the test before sharing a file.

The scope, commercial terms, data handling, and measures are set out in a written proposal before work begins.

01 / SOURCE

An approved pack

One authorized live, anonymized, or controlled pack. Security and data handling are approved before files are shared.

02 / PEOPLE & OUTPUT

A named review job

A named analyst and reviewer, an agreed memo structure, and someone who will judge the result.

03 / COMMERCIAL

Written terms

The fee, duration, included work, and support cadence are specified before kickoff.

04 / SUCCESS

An agreed baseline

Define acceptance criteria and how analyst effort, review effort, and memo usability will be assessed.

The pilot path

One review job. Three clear stages.

Each stage has a decision gate. The firm retains ownership of its evidence and investment judgment.

01 DEFINE

Choose the review job.

Map how the source pack becomes IC material today. Agree the pack, memo sections, named users, baseline, acceptance criteria, and data handling before any files are shared.

Firm: authorize the pack and name the analyst and reviewer.

Underlying: propose the bounded workflow and written scope.

02 RUN

Work through the evidence.

Configure the agreed workflow and work with the named team on the pack, its findings and open questions, and a memo draft for human review.

Firm: prepare, challenge, and review the material.

Underlying: configure the workflow and provide agreed support.

03 EVALUATE

Judge the result.

Compare observed preparation and review effort, source traceability, rework, and memo usability with the agreed baseline. Record where the workflow helped and where it did not.

Firm: decide whether the result is useful for its IC process.

Underlying: document the observations and limitations.

What you receive

A memo draft, its evidence, and a measured result.

Acceptance is based on the agreed review job and what the team observes, not a claim that every firm workflow is already supported.

THE DRAFT01

An IC memo to review

A DOCX working draft in the agreed section structure. The named reviewer checks its claims, source references, formatting, and usefulness against the pilot criteria.

A draft for human judgment, not an approved investment conclusion.

THE RECORD02

Evidence behind the draft

The findings, cited sources, qualifications, and open questions used in the agreed memo scope, available to the named team for review.

Citation granularity and source access are tested on the selected pack.

THE EVALUATION03

A decision on whether it helped

A comparison of observed analyst work, senior review, rework, and output usability against the baseline agreed at kickoff.

The report includes limitations and work that still needed people.

How value is reported

Record baseline and observed active hours for analysts and reviewers separately, plus rework and memo usability. Released hours are capacity; they are not automatically cash savings.

Pilot fit

A useful test needs a real review job.

We shape the pilot around a decision the firm already needs to make. If a prerequisite is missing, we agree a narrower test or address it before kickoff.

Test it when

  • An approved pack, or controlled equivalent, can test the review job.
  • A named analyst and senior reviewer can participate.
  • The memo format and decision consumer are known.

Rescope it when

  • Data rights or security requirements have not been cleared.
  • The requested output or integration falls outside the agreed scope.
  • The test expects AI to approve an investment conclusion.

See Underlying in your deal workflow.

See how source review, Findings, and a cited IC draft fit your team’s workflow. We’ll discuss your memo format, review process, and setup requirements.