The Close Cycle Lab sizes one process. The team calculator is a broader, lower ballpark — about 3% of loaded labor. They are not the same model. How to read the numbers. Every figure here is illustrative. The free Snapshot replaces it with your own work.
Process estimate. Task-level Monte Carlo of the close — P10/P50/P90 days, tornado, bottlenecks, and capacity returned.
Cash leakage, not labor. Expected catch from duplicates, overpays, missed credits, and discount leakage.
About 3% of loaded labor for the people in scope. A wide, low band — not the close lab.
Lead with carry on close lag at your WACC. CCC is an ops scenario, not the automation thesis.
Days off the close for one portco, plus an illustrative exit-equity translation.
ARR leakage model for SaaS. Not a labor calibration.
Three ranked processes on the team-ballpark band.
Statement match, exceptions, intercompany clears — hours returned.
Hours by entity × automatable share for FP&A packs.
Remittance match, deductions, collections drafts.
Notes, fields, forecast cleanup — hours your reps get back.
Provisional vs actual wrap and true-up exposure for GovCon.
How to read our numbers: illustrative vs measured ›
No. Labs are illustrative capacity bands with uncertainty. The free Snapshot replaces every figure with a measured process on your own work.
Most finance teams: Close Cycle Lab. Controllers sizing AP leakage: AP Leak. A wide team ballpark: the recovery calculator. Everything else is optional.
Yes. Snapshot and Book CTAs preserve the lab estimate so Opswell sees the same figure you just sized.
Labs are illustrative. The Snapshot replaces every figure with a measured process on your own work — free, yours to keep.