Every HubSpot account starts with a set of company properties already built in — and most teams either ignore them or pile custom fields on top before understanding what they already have. HubSpot's default company properties cover the fundamentals of segmentation and reporting, and using them well — clean, consistent, and complete — beats adding a dozen custom fields you'll never maintain. Here's the practitioner's read on the defaults that matter and how to get value from them.
What are HubSpot's default company properties?
They're the standard, pre-built fields on every company record — the basics HubSpot assumes any business will want to track. Out of the box you get fields like company name, domain, industry, number of employees, annual revenue, location (city, state, country), lifecycle stage, and owner, among others. Some you fill in; some HubSpot can populate or infer. The point of having them as defaults is consistency: every company record speaks the same language, so you can segment, filter, and report across your whole database without inventing structure from scratch. Before you ever create a custom property, it's worth knowing what these cover — because they handle more than most teams realize.
Which default properties matter most for B2B?
Domain, industry, employee count, revenue, lifecycle stage, and owner — these are the fields that drive segmentation and routing. Domain is the quiet hero: it's the unique identifier HubSpot uses to dedupe companies and to associate contacts automatically, so keeping it clean prevents duplicate company records. Industry, employee count, and revenue are your core firmographics — the fields you segment and target on, the ones that tell you whether a company fits your ideal customer profile. Lifecycle stage tracks where the company sits in your funnel. Owner assigns accountability. Worked example: a clean set of these six fields lets you build a list of "mid-size SaaS companies in our target region at the opportunity stage" in seconds — without a single custom property. That's the payoff of using the defaults well.
How do you keep these properties clean and useful?
Standardize how each field is filled, keep the key ones required, and don't let free text creep into fields that should be picklists. The most common failure isn't missing properties — it's inconsistent ones. Industry entered ten different ways, revenue in some records and not others, domains with typos. A property is only useful if it's populated consistently across records, because segmentation breaks the moment the same thing is recorded two different ways. Make the fields that drive your reporting required on creation, use dropdown values instead of free text where you can, and run periodic checks for blanks and inconsistencies. Worked example: a company list segmented by industry is useless if half the records say "Software" and half say "SaaS" — agreeing on one set of values, and enforcing it, is what makes the property actually work.
When should you add custom properties instead?
Only after the defaults are clean and you've hit a real gap they can't fill. Custom properties earn their place when you need to track something specific to your business that no default covers — a product line, a tier, a renewal date. But every custom property is a field someone has to populate and maintain, so the discipline is to exhaust the defaults first. Teams that add custom fields early often end up with a sprawl of half-filled properties that make the record harder to read, not easier. Worked example: a team adds five custom firmographic fields, then realizes HubSpot's default industry and revenue fields already covered four of them — they created maintenance work for nothing. Start with the defaults, keep them clean, and add custom only where there's a genuine, well-defined need. Getting that property strategy right is central to a clean HubSpot setup.
The IV-Lead take
The default company properties are more capable than most teams give them credit for. Used well — consistently filled, standardized, and complete — they handle the segmentation, routing, and reporting that B2B teams actually need, without a single custom field. The mistake is reaching for custom properties before mastering the defaults, which leaves you with a cluttered record and a maintenance burden. Clean the basics first: a tidy domain, consistent firmographics, a reliable lifecycle stage. Then, and only then, add what's genuinely missing.
Drowning in custom properties that should have been defaults? Book a 30-minute portal audit — we'll review your company properties and show you what to clean up, standardize, or retire. For the bigger picture, see how we approach HubSpot implementation and optimization.
Frequently asked questions
What are HubSpot's default company properties?
They're the standard fields built into every company record — name, domain, industry, employee count, annual revenue, location, lifecycle stage, owner, and more. They give you consistent structure for segmentation and reporting without creating any custom fields.
Why is the company domain property so important?
Domain is the unique identifier HubSpot uses to deduplicate company records and to associate contacts automatically. Keeping domains clean and consistent prevents duplicate companies and keeps contacts linked to the right accounts.
Should I create custom properties or use the defaults?
Start with the defaults and keep them clean. Add custom properties only when you hit a genuine gap they can't fill, since every custom field is something to populate and maintain. Many teams recreate fields that already exist by default.
How do I keep company properties consistent across records?
Use dropdown values instead of free text for fields you segment on, make the key fields required on creation, and review periodically for blanks and inconsistencies. A property only works if the same thing is recorded the same way everywhere.
