Zimbs Valetex

Workflow & finalization

A multi-week engagement as a controlled state machine

From fund setup to signed report, every step is validated, persisted, and gated. A finalized cap table is required before any valuation references it; finalization locks the inputs by design — turning methodological consistency from a hope into a guarantee.

Finalization-gatedServer-side validationRole-based review

The engagement, step by step

Ten gated stages, from fund to signed report

  1. 1

    Establish the fund

    Create the fund, with optional GP/LP aliases for branding across many entities.

  2. 2

    Create the company

    Public, private C-corp (INC), or private LLC — with type-aware terminology (shares vs. units) throughout.

  3. 3

    Build & finalize the cap table

    Securities → capitalization → option plan → warrant plan → shareholding → finalize. Each section is field-validated; finalization is irreversible and required before any valuation can reference it.

  4. 4

    Create the valuation

    Open a valuation against a finalized cap table on a specific valuation date.

  5. 5

    Populate financial statements

    Income statement and balance sheet for the relevant historical, forecast, and terminal periods.

  6. 6

    Configure valuation methods

    DCF, GPC, GTM, Backsolve, and Post-Money — each with its own inputs, comparable selection, and intermediate exhibits.

  7. 7

    Configure allocation methods

    OPM, CVM, and CSE — each producing per-class results, hybrid-weighted into a single blended conclusion.

  8. 8

    Apply DLOM

    Company-wide or per-share-class, via the analyst's selected methodology.

  9. 9

    Value shares

    Compute the final marketable and non-marketable per-class, per-share values.

  10. 10

    Finalize

    Lock all inputs and produce the signed PDF report and methodology-audit document.

What the gating guarantees

Consistency, enforced by the platform

Server-side validation

Every field is validated with FluentValidation on the server; the frontend mirrors it in real time via Yup, so a malformed payload never reaches the engine.

Irreversible finalization

Cap-table and valuation finalization lock the inputs by design — the foundation of a defensible tax and audit posture.

Re-openable sections

Until finalization, every section is independently re-openable, supporting iterative review cycles between analyst, reviewer, and partner.

Role-based review

Permission-gated access means analysts, reviewers, and partners each see and act on exactly what their role allows.

Frequently asked questions

How does the valuation workflow work?

The platform models an engagement as a finalization-gated state machine: establish the fund, create the company, build and finalize the cap table, create a valuation against it, populate financial statements, configure the valuation methods, configure the allocation engines, apply DLOM, value shares, and finalize — producing the signed report and methodology audit. Each stage is validated and persisted.

Why is finalization irreversible?

Irreversible finalization locks every input at a point in time, which is what makes the conclusion defensible to an IRS examiner or Big-4 reviewer. A finalized cap table is required before any valuation can reference it, guaranteeing the downstream math is built on a fixed, auditable foundation.

Can sections be revised during review?

Yes. Until finalization, every section is independently re-openable, supporting iterative analyst–reviewer–partner cycles. Once finalized, the engagement is locked and any further change is captured as a new versioned state in the audit trail.

How is validation enforced?

Every field is validated server-side with FluentValidation, and the frontend mirrors that validation in real time via Yup — so analysts never reach the server with a malformed payload, and inconsistent preference structures can't be saved.

Walk the workflow end to end

Book a walkthrough to see an engagement move from fund setup to a finalized, signed report.