Flows accumulate. People leave. Chalky reads every one of them and tells you which are risky, which are quietly broken, and which nobody needs any more. Read-only throughout.
Nothing is asserted on our say-so. Each rule names the Salesforce documentation or practitioner guidance it comes from, and the rules stay public whether or not you buy anything.
The failures that surface months later: DML with no fault path, queries whose empty result is never checked, update triggers that fire on every save because nothing gates them on a real change.
Queries and actions inside loops, record-triggered flows with no entry criteria running on every save of every record, unfiltered queries that work in a sandbox and fail at real data volumes.
Flows elevated to system context without sharing where nothing justifies it, and credential material sitting in plain sight in assignments, formulas or action inputs.
Hardcoded record Ids and business values, missing descriptions, unreachable elements left behind by an unfinished change, and automation with no way to switch it off during a data load.
Not "this rule exists". The element, the value, and where it sits, so your admin can open the flow and see the same thing we did.
What breaks if it is left, written in business terms, then the remediation and a link to the published source the rule came from.
A plain-English read of each flow rather than a list of codes, so the report is usable by someone who did not build it.
Flows found, flows evaluated, and any we could not read are all stated. Rules that did not apply are named as such, because a rule that did not apply is not a pass.
A read-only connection to a sandbox. Chalky reads flow metadata and changes nothing, and there is no production option to choose by mistake.
We count the flows and elements in the org and quote against them before anything is charged, so the price is known rather than estimated.
Every flow is evaluated against the full ruleset and written up, worst first, with a contents index and the numbers behind every percentage.
Flow analysis is the scan that runs on its own. The revenue scans run inside a consulting engagement, where the answer depends on what your business actually agreed.
What finance signed off, checked against what the org is configured to charge. Every difference listed with the record to check, across Revenue Cloud Advanced and CPQ.
Catalogue, pricing procedures, bundles, amendments and renewals read as built, then compared against the behaviour the programme was signed off to deliver.
Alongside the audit, Chalky counts what has built up: obsolete flow versions, drafts that were never activated, flows with no active version at all, and interviews left paused waiting on something that never came.
On a real org we found over nine hundred obsolete versions across three hundred flows, and several hundred paused interviews, the oldest by some months. None of it was doing harm that day. All of it was noise between an admin and the flow they needed to change.
Thirty minutes with an expert who has done it before.
