Outcome. A revenue estimate field always lands as a clean rounded number, instead of mixing precise-looking decimals next to plain guesses that both claim a precision they do not have.
Workflow map
Enrollment, branches and actions at a glance
data-quality-038
flowchart TD
A[Annual revenue estimate known or changed] --> B[Format Data: round to nearest 10,000]
B --> C[Set Annual revenue estimate = rounded value]
When to use it, when not to
- UseUse it whenever a numeric estimate, revenue, employee count, deal size guess, comes from a source that returns more precision than the number is actually accurate to, and inconsistent precision across records makes sorting and reporting look noisier than the data really is.
- UseUse it as formatting only. It does not correct a wrong estimate, only standardizes how a given value displays and rounds.
- SkipDo not use it on a property where exact precision matters, an actual invoiced amount, a measured quantity. Rounding there destroys real information rather than cleaning up false precision.
- SkipDo not use it if your reporting tool already handles display-level rounding on its own. Adding a second rounding layer on the stored value itself is redundant and makes the raw and displayed numbers diverge from any other system reading the same property.
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.2 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.1 numbered action
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
or the data quality 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.
