Account

Origin & evolution

Treating a company as the unit of account is old practice with a recent name. Salespeople worked large accounts for decades under the banner of key account management before anyone built a framework around it. The framework arrived in 2003, when Bev Burgess coined the term "account-based marketing" at ITSMA, the IT Services Marketing Association. ITSMA's move was to treat each strategic account as a market of one, with research, messaging✉️MessagingGo-To-MarketMessaging framework and key messagesView reference →, and sales coordinated around that single organisation.

The discipline split along the funnel⬇️FunnelGrowthA conversion funnel tracking user progressionView reference → as it matured. Marketing teams adopted account-based marketing to target named companies rather than scattered individuals, and sales teams adopted account-based selling to coordinate the multi-threaded pursuit inside each one. Vendors such as Demandbase and 6sense built platforms on the assumption🤔AssumptionStrategyA belief taken as true that underpins a strategyView reference → that the account, not the lead, is the right object to score and to measure.

The subscription🔂SubscriptionSales & RevenueA recurring subscriptionView reference → era then changed what an account is worth. When revenue recurs, an account's value becomes a relationship that can expand, contract, or churn over years, measured well beyond the first signing. That reframing made the account the natural home for the metrics🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference → that matter in recurring-revenue businesses: net revenue retention, expansion, and logo churn, each computed per account.

How it works in practice

A software firm pursues a 4,000-person logistics company. Inside that one account it tracks eleven contacts: a VP of operations who owns the budget, two analysts who will use the product daily, a security reviewer who can veto, and a procurement lead who controls timing. None of these people is the account. The account is the entity that survives any of them leaving.

The deal closes at 30 seats. A year on, the same account expands to 220 seats across three regions. In a per-deal view that would read as two unrelated wins. In an account view it reads as one relationship growing 7x, which is the number that predicts whether the business is healthy. Logos count the relationships; seats count the consumption within them; both are needed and they answer different questions.

Account vs. its neighbours

• Contact is a person inside the account. The account is the organisation; account_contains_contactAccountcontainsContacthierarchy is the edge that holds the many-to-one relationship. A contact can change jobs🔨JobUserJob To Be Done: what the user is trying to accomplishView reference → and vanish without the account changing at all.
• Lead is an unqualified individual signal, usually before any organisation has been confirmed as worth serving. The edge lead_becomes_accountLeadbecomesAccountcausal marks the promotion from a person of interest to a tracked company.
• Deal is a single opportunity🚪OpportunityDiscoveryA validated gap worth solvingView reference → to close revenue with an account. One account can carry many deals over time, which is why expansion and renewal are modelled as new deals against an existing account rather than as edits to the first one.
• Customer relationship🫶Customer RelationshipBusiness ModelA type of customer relationshipView reference → is the ongoing post-sale connection: support, success, renewal. The account is the structural unit; the relationship is the lived state of it, which is where retention and churn are actually felt.

In the graph

In the Unified Product Graph, an account is the organisational anchor of the sales region in any business that sells to companies. It connects downward to the people through account_contains_contactAccountcontainsContacthierarchy, sideways to revenue through account_negotiates_dealAccountnegotiatesDealhierarchy, and is delivered against through product_serves_accountProductservesAccounthierarchy and managed through pipeline_sales_manages_accountPipeline SalesmanagesAccounthierarchy. Modelling the company rather than the person as the unit means a product team can ask which kinds of organisations expand and which churn, and trace the answer through the contacts and deals that hang off each account, with the company kept whole where a flat contact list would scatter it.