Skip to content

Company size bucket property from employee count

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

Company6 stepsUpdated for HubSpot seat pricing
OutcomeEvery 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 mapdata-quality-026
Number of employees known or changed leads to Employee count range. Employee count range leads to <= 10: Bucket: 1-10; <= 50: Bucket: 11-50; <= 200: Bucket: 51-200; <= 1000: Bucket: 201-1000; > 1000: Bucket: 1000+. Number of employees known or changed Employee count range <= 10 Bucket: 1-10 <= 50 Bucket: 11-50 <= 200 Bucket: 51-200 <= 1000 Bucket: 201-1000 > 1000 Bucket: 1000+
Number of employees known or changed leads to Employee count range. Employee count range leads to <= 10: Bucket: 1-10; <= 50: Bucket: 11-50; <= 200: Bucket: 51-200; <= 1000: Bucket: 201-1000; > 1000: Bucket: 1000+. Number of employees known or changed Employee count range <= 10 Bucket: 1-10 <= 50 Bucket: 11-50 <= 200 Bucket: 51-200 <= 1000 Bucket: 201-1000 > 1000 Bucket: 1000+

When to use it, when not to

Use it

  • Use 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.
  • Use it once your team has agreed on the actual bucket boundaries; building this before that conversation just encodes someone's guess.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 6 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 7 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Data quality spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library