Outcome. On a fixed schedule at the end of each quarter, every open deal gets its amount and stage frozen into snapshot properties, so quarter-over-quarter pipeline comparisons do not get overwritten by later edits to the live fields.
flowchart TD
A[Scheduled trigger: quarter end, 18:00] --> B[Enrollment: open deals across pipelines]
B --> C[Set snapshot_amount_q_end = current amount]
C --> D[Set snapshot_stage_q_end = current stage]
D --> E[Set snapshot_date = today]

When to use it, when not to
- UseUse it when finance or RevOps needs a point-in-time pipeline value that survives later amount or stage changes on the same deal.
- UseUse it to build a trend report of pipeline composition across quarters without exporting a manual snapshot each time.
- SkipDo not use it if the portal already exports pipeline snapshots through a data warehouse or BI tool on a schedule. That is a cleaner source of truth than CRM properties for historical trend analysis.
- SkipDo not use it on a portal with only one pipeline stage in active use. A quarter-end freeze adds little when the field barely changes.
or the reporting and alerts pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





