Use cases

Choose the job the model has to survive.

ModelxcelPro is one Excel add-in, but the use case changes by workflow: understand formulas, bind source inputs, explain version deltas, track review issues, or export proof. Every claim below maps to real commands, a visible result, an artifact, and a limit.

Join the waitlistSee the product tour

Private beta. Waitlist open. Windows desktop Excel add-in.

Workflow selector

Pick the workflow before the persona.

The strongest use-case page does not start with industry labels. It starts with the job the workbook must do, then shows which team reaches for that stack most often.

Review an inherited modelMap + Formula ToolsStart with structure and formula logic before editing: Worksheet Map, Risk Heatmap, TrustLens, Flow Diagram, and CalcScope.Explain an output moveCompare + ProofCompare versions, route material deltas into MCI, inspect the formula chain, then replay the changed drivers when a signed artifact is needed.Bind, sign, and verifyProofAttach source snapshots to inputs, sign reviewed formulas or blocks, verify drift, and export the right proof artifact.Hand off review evidenceArtifactsPackage a map export, comparison result, review issues, audit trail sidecars, certificate snapshot, or Replay Proof envelope.

Persona workflows

Four outcome cards. Each one is a stack, not a single feature.

Every persona gets the same product. The difference is the sequence: which commands start the review, what the user sees, and which artifact has to leave Excel.

Investment Banking & PE4 workflows

Move from inherited model review to client-ready handoff evidence.

Review the model, explain what moved, and hand off evidence without hiding inside the spreadsheet.

  1. TrustLens / Flow Diagram / CalcScope for formula review
  2. Sensitivity for key-driver testing
  3. Compare + MCI for version deltas
  4. Sign Block + Certificate + Evidence Pack + Replay Proof for handoff evidence
Handoff

A reviewed block, comparison/MCI explanation, signed certificate envelope, Evidence Pack, and optionally a signed replay envelope for a specific output delta.

Open workflow page
Project Finance & PPP4 workflows

Keep long-tenor infrastructure models navigable, source-bound, and change-aware.

Bind the source inputs, map the model structure, and isolate the changes that move debt-case outputs.

  1. Bind Source / Bind Vector for source integrity
  2. Trace Precedents / Dependents / Flow Diagram for navigation
  3. Worksheet Map + Risk Heatmap for structure and review triage
  4. Compare + MCI for version changes
Handoff

A source-bound input set, active-sheet map/export workbook, heatmap review lens, and comparison/MCI delta packet.

Open workflow page
Corporate FP&A4 workflows

Explain forecast changes, mark review status, and pressure-test close-cycle assumptions.

Know why the forecast moved before the close meeting starts.

  1. Compare Previous Version + MCI for forecast deltas
  2. Why This Number for the selected cell proof chain
  3. Audit Trail / Mark Cell for close-cycle review status
  4. Sensitivity + Model Health for driver testing and diagnostics
Handoff

A comparison/MCI explanation, audit-status sidecar, sensitivity output, signed certificate envelope or Evidence Pack for ledger state, and signed replay envelope when a changed output needs evidence.

Open workflow page
Audit & Assurance5 workflows

Define review scope, track issues, verify proof state, and export workpaper-ready evidence.

Turn model review into evidence: findings, status, proof coverage, and the right artifact for the claim.

  1. Model Health + Cell Search + Circular Refs for review scope
  2. Model Sentinel for adopted workbook checks, declared gap checks, and new-failure alarms
  3. Review Issues / Flag Cell + highlights for findings
  4. Audit Trail / Mark Cell + Highlight Audit for status
  5. Coverage / Verify Ledger / Seal Ledger / Certificate / Evidence Pack / Replay Proof for proof evidence
Handoff

A model-health scope, circular-reference findings, Sentinel check state, issue set, audit-status sidecar, proof coverage/ledger verdict, signed certificate envelope or Evidence Pack, and the correct replay artifact when the claim is output movement.

Open workflow page

Outputs

Outputs you can hand off.

No fake screenshots and no implied checkout. These are source-true artifacts ModelxcelPro can produce or persist today, each with a boundary attached.

Use the artifact that matches the claim you are making.
  • .mxreplay.signedExternally verifiable output-delta proofReplay Proof signs an output-movement certificate with an Ed25519 envelope. The verifier checks the envelope bytes and embedded public key signature; it does not prove the model or assumptions are correct.
  • Proof CertificateWorkbook proof snapshotCertificate JSON exports include a signed .mxcert.signed envelope for offline verification; PDF and branded Excel certificate formats remain SHA-256 self-hash only.
  • Evidence PackOffline audit handoffEvidence Pack bundles certificate JSON, the .mxcert.signed envelope, a .mxproof ledger snapshot with evidence seals, and Node.js verifiers. Replay Proof envelopes are verified separately.
  • Worksheet Maps - <timestamp>.xlsxStructure handoff workbookWorksheet Map exports map sheets, legend, summary, and formula details for selected sheets. The live analysis is active-sheet based; export is a reporting artifact, not a dependency proof.
  • .mxcmp / MCI reportVersion-delta review packetCompare results and Material Change Intelligence capture grouped cell changes, output attribution, paths, and review routes. Attribution depends on the chosen files, reachable drivers, and proof settings.
  • .mxaudit + .mxreviewSidecar review recordsAudit Trail and Review Issues persist reviewer status, issues, tags, comments, and exported review sets. The sidecars must travel with the workbook when that evidence matters.

Proof boundaries

What this does, and what it does not prove.

ModelxcelPro is strongest when the evidence is named precisely. The page says the quiet part out loud so reviewers do not over-read the artifact.

Format boundary
Certificate JSON and Replay Proof exports have signed envelopes; Certificate PDF and branded Excel formats remain SHA-256 self-hash only.
Ed25519 envelope
Certificate JSON writes .mxcert.signed and Replay Proof writes .mxreplay.signed. Verification confirms the envelope bytes and embedded public key signature, not the business correctness of the workbook.
Fingerprint check
Proof signer identity is self-asserted. Recipients should confirm the key fingerprint out of band; timestamping, identity binding, and revocation remain future work.
Heuristic lens
Risk Heatmap and Model Health identify review priorities. They do not prove formulas or assumptions are right.
Scope caveat
Worksheet Map analyzes an active worksheet and exports selected map sheets; Trace surfaces external references but does not turn closed workbooks into dependency graphs.
What you seeA red Risk Heatmap cluster or a low health score.
What it meansThe model has a concentration of formulas, errors, hardcodes, external links, or other review flags.
What to do nextOpen TrustLens, Worksheet Map, Cell Search, or Review Issues. Do not treat the color as a correctness verdict.
What you seeCoverage shows a percentage of inputs bound or formulas signed.
What it meansSome parts of the workbook have proof records and can be verified for drift.
What to do nextUse Verify Workbook and Verify Ledger, then review the unsigned or unbound areas deliberately.
What you seeCertificate and Replay Proof are both available.
What it meansCertificate JSON exports can include a signed .mxcert.signed proof-state envelope; Replay Proof signs a specific output-delta replay.
What to do nextUse Certificate for workbook-state handoff, .mxreplay.signed for output movement, or the Evidence Pack when reviewers need the certificate, sealed ledger, and offline verifiers together.