A single undetected Salesforce regression can cost days of lost revenue, customer trust, and engineering scramble. Release Assurance costs a fraction of one incident.
See plansWe don't charge for clicks or test steps. You pick a coverage package, we allocate Coverage Units to the workflows you want protected, and those workflows run daily by default. Subscription billing starts when your initial protected workflows are ready for review — not before.
Coverage Units are our internal way to estimate the build effort, run complexity, and maintenance risk behind each protected workflow. You don't size them — we do, with you.
1 Salesforce object, 1 record create/update, short action path, limited fields, 1 primary assertion.
2–3 Salesforce objects, more fields and data setup, more screens, waits, related-record checks, multiple assertions.
Longer action path, more engineering build time, conditional logic, branching outcomes, status changes, validation rules, deeper verification.
LWC / shadow DOM traversal, approvals, multiple roles, permission-dependent steps, integrations, many assertions.
This is only a directional estimate. We confirm the actual Coverage Units during scoping — before any billing changes.
“I know what we're paying, I know which workflows are protected, and I know Release Assurance will maintain the coverage as Salesforce changes.”