An account in CRM is a record that represents a company or organisation you do business with – or want to. It’s the central object in most B2B CRM systems, and almost everything else (contacts, deals, activities, notes) connects back to it.

That might sound simple. But here’s what most CRM onboarding guides skip over: the account isn’t just a place to store a company’s phone number. It’s the unit of commercial truth. When your sales team asks “what’s our relationship with Acme Corp?”, the account record is supposed to answer that question completely – history, revenue, open opportunities, the lot.

If you’re just getting started with CRM software, understanding accounts is the single most important concept to get right before you touch anything else. Get this wrong and your entire database becomes unreliable. Get it right and everything from sales forecasting to renewal tracking becomes dramatically easier.

Account vs Contact: What’s the Difference?

People confuse these two constantly. An account is the company. A contact is the person who works there. They’re separate records, but they’re linked.

So in your CRM, “Meridian Software Ltd” is an account. Sarah Chen, the Head of Procurement at Meridian Software Ltd, is a contact associated with that account. You might have five contacts at Meridian: Sarah, the CFO, the IT manager, and two other stakeholders you’ve been emailing. All five sit under the same account record.

This separation matters more than it sounds. People move jobs. If Sarah leaves Meridian and joins a competitor, you update her contact record and re-associate it with the new company’s account. The Meridian account keeps its history and nothing gets lost. That’s the whole point of the structure.

If you want a deeper look at how contacts work on their own terms, this guide to contacts, leads and customers covers the full picture.

What Information Lives on an Account Record?

The exact fields vary by CRM platform, but most account records hold a consistent core set of data. Think of it as the permanent dossier on a company – not just contact details, but the full commercial context.

• Company name and legal entity – the primary identifier
• Industry and company size – useful for segmenting by Ideal Customer Profile (ICP)
• Account owner – the rep or team responsible for this relationship
• Associated contacts – every person at the company you’ve interacted with
• Open and closed deals (opportunities) – linked directly to the account
• Annual contract value or Annual Recurring Revenue (ARR) – what the account is worth commercially
• Activity history – calls, emails, meetings, all timestamped
• Account status – prospect, active customer, churned, on hold

Some teams also track custom fields specific to their business – things like preferred communication channel, contract renewal date, or which product tier the account is on. The CRM is flexible enough to hold whatever you actually need to manage the relationship.

A Concrete Example: Selling to Thornfield Group

Let’s make this real. Say you work in sales at a B2B software company and you’ve been pursuing a mid-market logistics firm called Thornfield Group for three months.

In your CRM, Thornfield Group is a single account record. Attached to it are four contacts: James, the operations director who initiated the conversation; Priya, the IT lead who evaluated your product; Marcus, the CFO who signed off on budget; and Claire, the procurement manager who handled the contract. Each of those people has their own contact record with their own email history, job title, and notes – but they all roll up under Thornfield Group.

There’s also one open opportunity (the deal you’re trying to close), two past discovery call activities, a proposal document, and a note from three weeks ago reminding you that James is on holiday until mid-October. All of it sits in one place. When your manager asks for a status update on Thornfield, you pull up the account and the answer is right there – no digging through email threads.

That’s what a well-maintained account record actually does for you day to day. It’s not administrative overhead; it’s how you stop dropping the ball on complex, multi-stakeholder deals.

What Is Account Hierarchy and Why Does It Matter?

Account hierarchy is how CRMs handle the fact that large companies aren’t flat. A global enterprise might have a parent company, multiple regional subsidiaries, and dozens of local business units – and your team might be selling to several of them simultaneously.

Without hierarchy, that’s a mess. You’d have five separate Acme Corp accounts with no connection between them, no consolidated view of total revenue, and no way of knowing that the deal your colleague is chasing in Germany involves the same parent company you already work with in the UK.

With account hierarchy, you can set up a parent account (the top-level entity) and link child accounts (subsidiaries or divisions) beneath it. This gives you two views at once: the granular detail of each individual entity, and a rolled-up picture of the entire relationship.

For teams tracking Net Revenue Retention (NRR) or managing enterprise renewals, that consolidated view isn’t optional – it’s essential. You can’t accurately report on an account’s total value if the revenue is scattered across five disconnected records.

Most major CRM platforms support parent-child account relationships. Salesforce calls them Account Hierarchies directly. HubSpot handles it through company associations. The mechanics differ slightly, but the underlying concept is the same.

How Accounts Fit Into the Broader CRM Data Model

Accounts don’t exist in isolation. They sit at the centre of a web of related objects, and understanding those relationships helps you use your CRM more effectively.

Here’s the basic structure in most B2B CRMs:

• Accounts are linked to Contacts (the people)
• Accounts are linked to Deals / Opportunities (the revenue potential)
• Deals move through a sales pipeline with defined stages
• Activities (calls, emails, meetings) are logged against both contacts and accounts
• Parent Accounts can contain multiple Child Accounts

This structure is what makes CRM so much more useful than a shared spreadsheet. The relationships between objects let you ask questions you couldn’t otherwise answer – like “which accounts have had no activity in 90 days?” or “what’s the total pipeline value across all subsidiaries of this parent company?” For teams doing serious RevOps work, those queries drive real decisions.

If you want to understand how all the core objects fit together, our CRM database explainer maps out the full data model clearly.

Common Mistakes Teams Make With Account Records

Most CRM data quality problems trace back to how accounts were set up in the first place. A few patterns come up again and again.

Duplicate accounts are the most common issue. Someone creates “Thornfield Group” and a colleague later creates “Thornfield Group Ltd” – now the data is split. Contacts, deals, and activity history are scattered across both. The fix is to establish naming conventions early and enforce them, ideally with duplicate detection turned on in your CRM.

Contacts stored without account associations is the second big one. If a contact record isn’t linked to an account, it becomes an orphan – nobody knows which company they work for, and you lose the aggregated view entirely. Every contact should be associated with an account on creation.

Stale account owners cause friction too. If a rep leaves and their accounts aren’t reassigned, those accounts effectively go dark with no one responsible for them. Regular account ownership audits – quarterly at minimum – prevent this from silently eroding your churn rate.

Getting these basics right matters more than any advanced feature. A clean account structure is the foundation, and everything built on top of it – reporting, forecasting, territory management – depends on it being accurate.

How to Think About Accounts When You’re Just Starting Out

If you’re new to CRM and feeling overwhelmed, here’s the most useful mental shift: stop thinking about CRM as a place to log things that already happened, and start thinking about accounts as living records of an ongoing relationship.

Every interaction you log against an account makes the next interaction better. Your manager can cover for you when you’re out. Your successor can pick up where you left off. The account becomes institutional knowledge rather than personal memory that walks out the door.

Start small. Pick five accounts you own and make sure each one has the correct contacts linked, an accurate account owner, and at least one recent activity logged. That’s it – that’s the foundation. Once you’ve got five accounts in good shape, scaling to fifty or five hundred follows the same logic.

For a broader introduction to how CRM software works as a whole, our CRM software overview is worth reading alongside this one. And if you want to compare platforms to find one that handles account hierarchy well, the CRM Tools Directory is a good starting point.

One concrete action to take today: open your CRM, search for accounts with no associated contacts, and start cleaning those up. Linking orphaned contacts to the right account will immediately improve the reliability of every report your team runs. It’s not glamorous work. But it’s the work that makes everything else function properly.

Want more practical CRM fundamentals delivered weekly? The CRM Daily Newsletter covers exactly this kind of ground, without the jargon.