# Private equity

Source: https://www.trypascal.io/solutions/private-equity

Carry the investment thesis into the work.

Keep diligence findings, investment assumptions, and operating priorities connected. Give each claim a source, each open question an owner, and each initiative a basis for review.

## Who this is for

For deal teams, operating partners, and portfolio leaders

## The thesis should survive the handoff.

An investment conclusion depends on a model version, a diligence answer, and assumptions about the business. When those pieces separate, the next team has to reconstruct the case. Pascal keeps the claim, evidence, and open work together from deal preparation to the initiatives management chooses to pursue.

Tomorrow’s deal call needs a consistent account of operating performance. The deck, model, diligence tracker, and legal notes tell different parts of the story.

In the deal Workroom, a revenue bridge discrepancy, five open diligence questions, and two disclosure holds become a preparation brief. Pascal organizes the questions for the internal team and prepares a separate client draft, keeping each audience’s information distinct.

## Workflow

### Underwrite

State: source. Connect investment claims to their sources, assumptions, sensitivities, and open questions.

### Seal

State: source. Record the approved investment decision, source revisions, conditions, and disclosure limits.

### Accept

State: approval. Let company management review each proposed handoff and decide what it will own.

### Rebuild

State: proposal. Turn accepted priorities into defined initiatives, required software changes, and named responsibilities.

### Operate

State: effect. Run approved initiatives under company access rules, review requirements, and operating limits.

### Realize

State: receipt. Ask company finance to distinguish observed improvement from validated financial benefit.

### Compound

State: receipt. Carry approved lessons and reusable practices into the next initiative while preserving company boundaries.

## Result and action boundary

The team has an internal agenda with five questions and named owners, plus a client draft that excludes the two restricted disclosures. Reviewers can resolve the gaps before the call and decide what is ready to share. Both briefs remain drafts.

A prepared brief is not an approved disclosure. After close, portfolio-company management remains responsible for operating decisions and finance remains responsible for validating benefits. Sponsor oversight does not grant direct authority over company systems.

## Start and expand

Begin with one investment claim or value-creation initiative. Agree on its sources, assumptions, company owner, permitted actions, and the operating and financial observations that will determine whether it worked.

After diligence, connect an accepted investment claim to a company-owned initiative. Carry forward the source and assumptions, establish the operating baseline, and review the result with management and Finance. Each portfolio company keeps its own access and decision boundaries.

## Related products

- [Bedrock](https://www.trypascal.io/platform/bedrock)
- [Ontology](https://www.trypascal.io/platform/ontology)
- [Workrooms](https://www.trypascal.io/platform/workrooms)
- [Context Graph](https://www.trypascal.io/platform/context-graph)
- [Compass](https://www.trypascal.io/platform/compass)
- [Atlas](https://www.trypascal.io/platform/atlas)
- [Workflows](https://www.trypascal.io/platform/workflows)
- [Work Surfaces](https://www.trypascal.io/platform/work-surfaces)

## Next step

[Discuss your workflow](https://www.trypascal.io/contact)