Glossary
Account: The Company-Level Foundation of B2B Sales
An account is the organized company, institution, or business-unit record around which a B2B team coordinates contacts, relationships, activities, opportunities, contracts, and customer history.
Quick definition
An account is the organized company, institution, or business-unit record around which a B2B team coordinates contacts, relationships, activities, opportunities, contracts, and customer history.
Key points
Define whether an account represents a legal entity, corporate family, location, or buying unit.
Link contacts, opportunities, activities, contracts, and product usage to a canonical account identity.
Preserve hierarchy and lifecycle distinctions across prospects, customers, partners, and former customers.
Assign ownership and data stewardship rules to prevent duplicates and conflicting engagement.
An account may represent a global parent, a legal subsidiary, a regional division, a franchise, a public institution, or a specific business unit. The correct level depends on how the organization buys, contracts, deploys, and manages budgets. Revenue teams should define the unit deliberately rather than using a website domain as the only identity rule. One domain can cover many buying units, and one company can use several domains.
A canonical account record typically stores names, identifiers, domains, locations, industry, size, ownership, hierarchy, territory, lifecycle, assigned team, and relationship status. It also connects the people who work there, marketing engagement, sales activities, opportunities, contracts, support history, product usage, and partner involvement. Sensitive or uncertain data should be limited, sourced, and governed according to a valid business purpose.
Contacts represent people, while accounts represent the organizations or buying units around them. Leads may be unqualified people or companies that have not yet been matched and reviewed. Opportunities represent specific potential transactions, often with products, value, stage, timing, and decision participants. An account can therefore contain many contacts and several opportunities across time without losing the wider relationship context.
Good systems perform lead-to-account matching early enough to reveal existing ownership and activity. A new form submission from a current customer should not be treated like an unknown acquisition lead, and a contact at a company with an active opportunity should reach the relevant owner. Matching should combine domains, company names, locations, and trusted identifiers, with human review for ambiguous corporate structures.
Hierarchy captures relationships among parent companies, subsidiaries, branches, and buying units. This supports global negotiation, local selling, territory assignment, risk review, and aggregated reporting. Teams should state which attributes roll up, such as total revenue or pipeline, and which remain local, such as owner, contract, consent status, or product deployment. Blind rollups can erase real operational differences.
Lifecycle labels should distinguish target, prospect, active opportunity, customer, former customer, partner, competitor, and disqualified states where relevant. Because one company can hold several relationships, a single field may be insufficient; a customer can also be an expansion target or technology partner. Preserve status history and effective dates so reporting reflects what was true when activity occurred.
Account data degrades through acquisitions, rebrands, office changes, domain migrations, and inconsistent entry. Establish creation rules, duplicate checks, required identifiers, merge procedures, hierarchy review, and a responsible data steward. Automated enrichment can fill gaps, but changes to ownership, legal identity, or customer status should not be overwritten without controlled logic and an audit trail.
Measure completeness on fields that enable actual decisions rather than pursuing perfect data everywhere. Monitor duplicates, unmatched contacts, hierarchy gaps, stale ownership, invalid domains, and records without a next action. Give sellers a simple correction path and feed common errors into validation rules. A trustworthy account layer improves routing, personalization, forecasting, customer handoffs, and privacy response handling across the revenue organization.
Practical examples
Global parent with regional accounts
A software vendor keeps a parent record for consolidated reporting and separate regional accounts because each region signs its own contract and has distinct data requirements. Contacts and opportunities remain linked at the buying level.
Lead matched to a customer account
A product manager submits a webinar form using a subsidiary domain. Matching rules connect the person to an existing customer hierarchy and route the request to the account team instead of placing it in a new-business sequence.
Acquisition and account history
After one customer acquires another, operations links both accounts under the new parent but retains historical contracts, activities, and ownership. The team can report the combined relationship without erasing what occurred before the acquisition.
Frequently asked questions
What is an account in a CRM?
An account is the organization-level record that groups people, activities, opportunities, contracts, and relationship data. Its exact scope should reflect how the business sells and serves, whether at parent, subsidiary, location, or buying-unit level.
Can one company have multiple accounts?
Yes. Separate accounts can be appropriate when subsidiaries, regions, franchises, or business units buy independently. They should be connected through a hierarchy so teams retain enterprise visibility and avoid uncoordinated engagement.
Who should own account data quality?
Revenue operations or a designated data steward usually defines standards and controls, while sales, marketing, success, finance, and systems teams contribute corrections and source expertise. Clear decision rights are more effective than assigning vague responsibility to everyone.
Related terms
Target account
A target account is a named organization selected for deliberate go-to-market attention because it matches priority criteria and justifies coordinated marketing, sales, partner, or customer engagement.
Prospect
A prospect is a person or organization that has been identified as a plausible buyer because it meets meaningful targeting or qualification criteria and can reasonably progress through a sales process.
Potential customer
A potential customer is an organization or buyer that could plausibly purchase and receive value from an offering, based on market eligibility, likely needs, and the ability to enter a commercial relationship.
Account-Based Marketing
Account-based marketing (ABM) is a B2B go-to-market approach that concentrates sales and marketing resources on a defined set of high-value target accounts instead of casting a wide net across an entire market.
Lead qualification
Lead qualification is the evidence-based process of deciding whether a person and associated account fit the intended market, have a relevant problem or objective, and merit a defined next step in the sales process.
Keep exploring
Browse the full technographic glossary or follow the B2B prospecting playbook to search by stack and unlock leads.