Private equity · Evidence to decision

Build a value case.
Then challenge it.

An operating partner workspace for deciding what belongs in the first 100 days. Trace the evidence, separate earnings from cash, and revisit the plan when the facts change.

A portfolio project by Alex Hines. Progress Software public research with a separate constructed operating exercise. No company engagement or realized savings claimed.

01
Trace the claim

Facts, assumptions and unknowns stay distinct.

02
Test the decision

Costs, downside and scarce capacity stay visible.

03
Preserve the history

Revisions do not rewrite the approved baseline.

The case · Two evidence layers

What should management
do next?

The public record supports further diligence. The constructed exercise shows how the system challenges an operating proposal before anyone acts.

The public company

Progress Software · Issuer filings

Reported evidence

Separate acquisition-driven growth, accounting definitions and peer context before underwriting an improvement.

  • Financial statements reconcile to sourced rows and explicit units.
  • Unresolved amortization scope blocks dependent earnings measures.
  • Peer margins inform questions; they do not establish achievable savings.
Inspect the public evidence →Selected historical sources

The operating exercise

Constructed contracts, costs and observations

Revise the proposal

A positive forecast must survive contract eligibility, a real cost-release mechanism and implementation constraints.

The demonstrated source correction removes unsupported vendor savings while retaining committed costs. Changing the sequence alone does not repair the case.

Guided review · About 10 minutes

Follow one decision
from evidence to measurement.

Use this six-stop route for the primary case. Additional examples below are separate demonstrations, not successive stages of one company engagement.

  1. 1Decision

    Start with the recommendation

    See the current judgment, alternatives and the evidence that would reopen it.

    Read the executive memo →
  2. 2Evidence

    Trace the public baseline

    Inspect earnings definitions, acquisition effects and the limits of peer comparison.

    Open the filing analysis →
  3. 3Economics

    Separate the financial effects

    Follow monthly EBITDA, pre-tax cash, costs, downside and incremental value assumptions.

    Inspect constructed underwriting →
  4. 4Capacity

    Constrain the first 100 days

    See how dependencies and weekly resource limits change dates and modeled benefits.

    Review the proposed plan →
  5. 5Challenge

    Watch the case change

    Trace the source correction, retained costs and reopened decision against earlier versions.

    Review the correction →
  6. 6Measurement

    Challenge the claimed result

    Compare scoped KPIs, accounting differences, claims and residuals without rewriting history.

    Inspect the lifecycle →

All operating records, reviews and outcomes in this exercise are constructed. The presenter guide explains the period and example boundaries at each stop.

Additional financial and technical exhibits
Separate local application · Human approval

Try the approval workflow.

The fictional Beacon and Delta companies demonstrate authentication, approval, controlled pauses and KPI navigation. They are separate from the Progress research case.

01 · Diagnose

Establish the fact base

Review company diagnostics and evidence quality. Missing or suspicious inputs remain visible to the reviewer.

See a controlled pause →
02 · Underwrite

Challenge the value case

Inspect baseline, improvement, realization, cost and timing assumptions behind low, base and high scenarios.

Inspect the memo →
03 · Decide

Authorize the scope

A human approves, requests changes or rejects. The decision is recorded; model-callable tools cannot approve a plan.

Try a local decision →
04 · Monitor

Follow the approved plan

Review KPI definitions and observations in context. A target, a seeded observation and a realized return are different facts.

Inspect execution KPIs →

These application pages are read-only captures of the fictional demo. Start the local workspace for interactive decisions, evidence review and KPI navigation.

Technical diligence · Contracts and controls

The control system behind the investment case.

Optional models propose ideas and narrative. Typed tools own evidence and calculations. Durable state preserves decisions and recovery.

  1. 01 · InputImmutable evidence
  2. 02 · ContractScoped MCP tools
  3. 03 · Financial coreDeterministic sizing
  4. 04 · AuthorityHuman approval API
  5. 05 · ExecutionPersisted KPI state

Traceable financial claims

Server-issued quantity references bind numbers to company, period, unit and evidence. Model proposals and narrative are validated against that record.

Durable execution

PostgreSQL checkpoints, worker leases and idempotency support recovery. The approved plan and its decision remain inspectable.

Explicit access boundaries

Company scope, row-level security and a separate human approval audience keep authority outside the model's tool surface.

Behavior, beyond a screenshot

Unit and integration tests, adversarial evaluation cases, and a real Compose workflow. Exact commits and coverage scope are recorded.

Open the evidence index →

Reproducible distribution

Installed-package checks, synthetic fixtures and a deterministic demo let a reviewer inspect the work without paid inference.

Reproduce the showcase →

Acceptance with boundaries

The practitioner review is prepared but unperformed. Current limitations and remaining production gates are recorded alongside automated evidence.

Read the acceptance record →
Explore the workspace

Bring the operating review to your own screen.

Follow the Progress public case above, then use the separate fictional Beacon/Delta workspace for interactive decisions. The five-scenario CLI demonstration exercises approval, missing evidence, failure and recovery without Docker.

Python 3.12+ and uv. Docker Desktop with Linux containers for the browser workspace. No provider key is needed for the default rules-based showcase.

From a checkout of the reviewed commit
uv sync --frozen --extra dev
uv run pvc demo

# Browser workspace: Docker must be running
python scripts/showcase.py up

The setup command prints the local URL and approver token. Keep that token out of recordings and public artifacts.

What this showcase does and does not establish
  • The local operating demo uses synthetic businesses and outcomes. The separate Progress research case uses public filings and clearly labeled analyst assumptions. No customer savings or investment returns are claimed.
  • The default uses rules. Current live-model acceptance and real-source reconciliation require separate evaluation.
  • Core application/database checks and optional observability-image findings have separate evidence records.
  • AWS deployment, production identity, security review, operational readiness and launch decisions remain in the production roadmap.