Company size bucket property from employee count

Outcome. Every company with a known employee count gets sorted into one of a handful of standard size buckets, so segmentation and reporting group accounts consistently instead of everyone picking their own number ranges in each report.

Workflow map Enrollment, branches and actions at a glance data-quality-026

flowchart TD
    A[Number of employees known or changed] --> B{Employee count range}
    B -->|<= 10| C[Bucket: 1-10]
    B -->|<= 50| D[Bucket: 11-50]
    B -->|<= 200| E[Bucket: 51-200]
    B -->|<= 1000| F[Bucket: 201-1000]
    B -->|> 1000| G[Bucket: 1000+]

When to use it, when not to

• UseUse it when reports, lists, or lead routing need to group companies by size bucket, such as "SMB", "Mid-market", "Enterprise", rather than filtering on a raw number every time.
• UseUse it once your team has agreed on the actual bucket boundaries; building this before that conversation just encodes someone's guess.
• SkipDo not use it if Number of employees is rarely populated on your company records; a bucket built on mostly-blank data adds a property without adding real segmentation value. Consider data-quality-023's enrichment fallback pattern first.
• SkipDo not use it as a replacement for the raw Number of employees value in reports that need precision; keep both properties, the bucket is a convenience layer on top.