zamski.

Independent operating diligence and intelligence for private equity

Know what the evidence supports before the numbers make it obvious.

Zamski tests thesis-critical claims against the records a company created while doing the work. Start with a diligence question, then revisit the same evidence through ownership to see what strengthened, weakened, was contradicted, or remains unproven.

Discuss a portfolio companySee an illustrative finding
Claim“Enterprise rollout is on track.”EvidenceSupportsSupportsContradictsNot observedFindingAt risk

Management reporting tells you the story.Zamski tests what the operating record supports.

Financial reporting, board materials, and the data room are necessary views of the business. They are prepared for review. Zamski tests the claims that matter to the investment against the record the company created while doing the work.

Prepared evidence has never been easier to produce.

A capable AI coding agent can turn supplied facts into a polished diligence package in minutes. Those documents may be completely accurate. But several documents derived from the same supplied narrative are not independent corroboration.

Prepared for review

Illustrative AI agent workflow

/goal Build a diligence data room for the synthetic company Acme Software from the supplied company facts and source documents.

Keep the documents internally consistent and cite the supplied materials.

One supplied narrative

  1. Product architecture overview
  2. Implementation history
  3. AI adoption summary
  4. Scalability narrative
  5. Delivery-risk register
  6. Value-creation progress report
  7. Diligence Q&A

Created while operating

  1. RepositoryChange merged to the shared implementation path
  2. Work trackingRollout ticket reopened
  3. Work trackingInternal deadline moved
  4. RepositoryCustomer-specific exception path changed
  5. Team communicationDelivery concern raised
  6. RepositoryShared component reused by a second team
  7. Work trackingBlocking dependency still open

Each record was made for the work itself, not for review. That is what makes them independent of one another and of the documents.

Seven polished documents.One underlying narrative.

Zamski asks a different question: does the historical operating record independently support the claims those documents make?

The issue is not whether the prepared material is true. It is whether independent evidence supports it.

Quality of earnings tests the numbers.Zamski tests the operating claims behind them.

A claim that survives the evidence test is valuable too. It becomes evidence the investor can defend.

What Zamski does.

Illustrative. Synthetic company and evidence.The structure is the product. The company is not real.

Claim

“Enterprise rollout is on track.”

Management update to the board

  1. Work trackingSupportsCore rollout work advanced toward the committed milestones.
  2. Repository historySupportsShared implementation components continued to move toward closure.
  3. Team communicationContradictsDelivery discussion still refers to an unresolved dependency and a customer-specific exception.
  4. Expected evidenceNot observedNo closure record appeared for the blocking dependency. Within the reviewed coverage, where one would be expected.

Finding

Enterprise rollout

At riskWeakened since the prior review

Support and contradiction from independent records. One expected record missing within coverage.

View the evidence
  • Supported. Independent records agree with the claim.
  • Contradicted. The record disagrees, and says where.
  • Unresolved. Examined and not settled either way.
  • Expected evidence not observed. Only within stated coverage; otherwise the report draws no conclusion from absence.

Every finding resolves to the source records behind it.

What changed. Why it matters. What supports it.

A report opens with the consequence, not the mechanics. The evidence behind every line is one click away, and it is the same evidence management can check.

Illustrative operating report

The readoutWhat changed this period, in the order it needs attention. The consequence comes first.

Why it mattersThe business condition, what the record directly shows, and what that could affect, kept apart and labelled as such.

What to askOne question for management, and the evidence basis the finding rests on.

The evidenceThe claim as management made it, then support and contradiction side by side, each from a named type of record.

What was missingA record that should exist and does not. It counts only where coverage was sufficient to expect it.

How it movedThe same claim at the prior review and now, so the direction is visible rather than argued.

The limitWhat the evidence does not establish, stated rather than filled in with narrative.

Full reportThe whole artifact, as it is delivered.

Illustrative. Synthetic company and evidence.The structure is representative of the product. The company is not real.

Operating readout, this period

The investment thesis remains supported, but execution around the largest customer rollout weakened this period. The commitment is less credible and the evidence for repeatable delivery has weakened. Platform reuse elsewhere continues to improve.

What needs attention

Enterprise rollout

At riskWeakened this period

Customer commitment, revenue timing

Opened below

Delivery economics

WatchUnchanged this period

Margin and scalability

Platform reuse

On trackStrengthened this period

Value-creation plan

Key-person dependency

WatchUnchanged this period

Execution continuity

Finding

Enterprise rollout

At risk/Weakened this period

Why it matters

The operating record is becoming less consistent with the committed rollout schedule. Dependencies remain unresolved and delivery still takes customer-specific paths, so the evidence for repeatable implementation is weaker than the plan assumes.

What the record shows

Directly observed

  • A dependency the rollout requires remained open past the internal commitment.
  • Delivery work continued on a customer-specific path, not the reusable one.
  • The planned closure work did not appear in the reviewed operating record.

What this could affect

Possible consequence, not observed

  • Customer commitmentGo-live timing
  • Value creationRepeatable delivery
  • Margin thesisAmount of custom implementation work
  • Exit readinessEvidence the business scales without proportional engineering effort

Question for management

What has to be resolved for this rollout to meet the customer commitment without adding more custom work?

Evidence basis

  • Several independent records
  • Coverage sufficient for this finding
  • Contradiction unresolved
The evidence behind this finding

Management claim

“The enterprise rollout is on track for the committed go-live, and the implementation is moving onto the repeatable platform model.”

AssessmentContradicted

Support

  • Work tracking

    Core rollout work advanced and the reusable implementation path was partially adopted.

  • Repository

    Shared implementation components continued to move toward closure.

Contradiction

  • Work tracking

    A critical dependency remained open beyond the internal commitment.

  • Repository

    The customer-specific exception path continued to receive production changes.

  • Team communication

    Delivery discussion continued to reference the unresolved dependency.

Expected evidence not observed

Within the reviewed coverage, no closure record appeared for the blocking dependency. A rollout tracking to the committed date would be expected to produce one.

Zamski separates evidence it did not find from evidence it had the coverage to expect. Only the second can support a finding. Where coverage is not sufficient to expect the record, the report says so and draws no conclusion from its absence.

Change through time

  1. Earlier

    The rollout plan and the reusable delivery path were still aligned.

  2. This period

    The dependency remained open and exception-path work continued.

  3. Current finding

    The evidence supporting the committed rollout weakened.

Limit

The evidence establishes what the operating record shows about the rollout path. It does not observe the customer contract, the revenue schedule, or the commercial relationship. Everything under “what this could affect” is an inference from operating evidence, not an observed commercial fact.

It does not establish why the dependency remains open, and it does not predict whether the committed date will be met. A system not included in this review could hold relevant evidence. Where that is the case the report states it rather than filling the gap with narrative.

Every finding is source-linked. A finding that supports management is reported with the same evidence discipline as one that contradicts it. Source markers are categories of operating record rather than named systems; the sources for a review are confirmed at scoping and printed in the report as its coverage.

Better evidence, earlier, so there is more time to act.

Underwrite

Protect the underwriting thesis.

Know whether the assumptions behind the investment are appearing in the operating record.

Hold

Double down with evidence.

Where an initiative is demonstrably working, support additional resources or capital with evidence rather than anecdote.

Intervene earlier.

Surface blockers and deteriorating execution while they are operationally correctable, before they become a financial surprise.

Reunderwrite when the evidence changes.

Repeated contradiction and unresolved gaps give investment and operating teams evidence to re-examine the plan.

Exit

Reduce exit surprises.

Find likely buyer questions while there is still time to remediate, narrow a claim, or document what changed.

Preserve proof of value creation.

Where the record supports management, preserve that evidence for the board, the investment committee, and the eventual exit story.

How Zamski works.

  1. Frame the investment questions.

    Identify the claims and the decisions that matter.

  2. Define the evidence coverage.

    Confirm the operating records available for review, and state that coverage in the report.

  3. Test the operating record.

    Read independent records against the claims, preserving support, contradiction, absence where it is meaningful, and uncertainty.

  4. Deliver the findings.

    Show what the evidence supports, what it contradicts, what remains unresolved, and why it matters.

  5. Revisit the baseline.

    Follow-on reviews show what changed without rewriting the evidence behind the earlier finding.

Independent evidence at every stage of the investment.

A point-in-time review tells you what appears true today. Zamski preserves the baseline and shows what strengthened, weakened, appeared, disappeared, or was resolved through ownership.

ClaimUnderwriteFirst 100 daysHoldReunderwriteExit
Enterprise rolloutOn trackOn trackAt riskAt riskResolved
Reusable deliveryNot sufficientWatchOn trackWatchOn track
Key-person dependencyNot sufficientWatchWatchOn trackOn track
Underwrite

Are we buying what we think we are buying?

The baseline. Rollout evidence supported the plan. Reusable delivery and the concentration of critical work could not be established from the evidence in scope, so both are named as unresolved rather than assumed.
First 100 days
The same claims, read again. Shared implementation work began to appear in the record. Concentration of ownership was visible enough to watch.
Hold

Is the value-creation plan becoming real?

Rollout evidence weakened: a dependency stayed open and customer-specific work continued. Reuse strengthened elsewhere in the business.
Reunderwrite
The plan is re-examined against what the record now shows. The rollout remains at risk, reuse has plateaued, and critical work is spread across more people than before.
Exit

What will the next buyer find?

What the next buyer will find, with the evidence preserved from the baseline onward: the rollout resolved, reuse supported, and the earlier concentration reduced.

Built to be trusted with access.

AccessZamski does not modify source-system business records.
Access is granted by the company and scoped to the engagement. The permissions requested for each source are disclosed before connection.
TraceabilityEvery finding resolves to the source records behind it.
Management can check the same evidence, which is what makes a finding usable at a board or an investment committee.
PreservationFindings are preserved with the evidence they were made from.
A later review shows what changed. It does not rewrite the earlier finding.
LimitsWhere the evidence is not sufficient to conclude, the report says so.
Absence within stated coverage can support a finding. Absence without it does not, and Zamski draws no conclusion from it.

Security and trust

Who it is for.

Investment teams

Underwriting the business and deciding which claims require deeper evidence.

Operating partners

Responsible for the value-creation plan becoming real.

Boards and investment committees

Who need conclusions they can inspect and defend.

Discuss a portfolio company.

Tell us the company and the claim you would most want tested. Zamski will follow up to discuss the operating evidence required for a review.

Discuss a portfolio company