Customer
カスタマー
A customer is the person or organization that purchases an offering or holds the commercial relationship with the seller. The customer may differ from the user, buyer, approver, client contact, or beneficiary.
What it means
In everyday retail, purchaser, customer, and user may be one person. In business and institutional buying, they often separate. The customer is the commercial account or person recognized by the seller's stated rule—for example, the contracting organization, an active paying account, or a purchaser during a defined period. A buyer selects suppliers or arranges terms; a decider approves; a user consumes the product; a client often receives professional services or denotes a relationship style. Because these roles can overlap without being identical, customer counts, research, support, revenue, and retention decisions must name the entity, role, status, and time window being measured.
How to calculate it
Customer is a role or entity, not a formula. Operational counts require a grain and rule: unique customer people, customer accounts, or buying households during a stated period. For example, active customers may be defined as distinct paying accounts with an unexpired contract at period end. Never add users, contacts, and accounts into one total without deduplication and a declared unit.
What counts / what does not
Separate the entity counted as the customer from the other roles involved in buying, using, or benefiting from the offering. Include | the person or organization meeting the documented purchase or commercial-relationship rule for the product and reporting period. Exclude | prospects, leads, audience members, free users, partners, employees, and beneficiaries unless they independently satisfy the customer rule. Classify separately | buyer, decider, procurement contact, administrator, user, client contact, payer, and beneficiary so one account can contain several roles without double counting.
| Item | Treatment |
|---|---|
| Include | the person or organization meeting the documented purchase or commercial-relationship rule for the product and reporting period. |
| Exclude | prospects, leads, audience members, free users, partners, employees, and beneficiaries unless they independently satisfy the customer rule. |
| Classify separately | buyer, decider, procurement contact, administrator, user, client contact, payer, and beneficiary so one account can contain several roles without double counting. |
What moves the number
Identity | choose person, household, legal entity, or account as the customer grain and maintain stable identifiers. Lifecycle | distinguish prospect, new, active, dormant, churned, and former customer using dated status rules. Buying roles | map initiator, influencer, buyer, decider, gatekeeper, and user for complex purchases. Value and evidence | combine commercial records with user research while respecting consent, access controls, and the limits of each data source.
| Driver | Metric impact |
|---|---|
| Identity | choose person, household, legal entity, or account as the customer grain and maintain stable identifiers. |
| Lifecycle | distinguish prospect, new, active, dormant, churned, and former customer using dated status rules. |
| Buying roles | map initiator, influencer, buyer, decider, gatekeeper, and user for complex purchases. |
| Value and evidence | combine commercial records with user research while respecting consent, access controls, and the limits of each data source. |
When it helps
Revenue and retention metrics become comparable when finance, sales, product, and support count the same customer entity and lifecycle state. Product research improves when teams recruit the actual user for usability questions and the economic buyer or customer owner for purchase questions. Service ownership becomes clearer because contractual obligations attach to the customer account while permissions and experiences may attach to individual users.
- Revenue and retention metrics become comparable when finance, sales, product, and support count the same customer entity and lifecycle state.
- Product research improves when teams recruit the actual user for usability questions and the economic buyer or customer owner for purchase questions.
- Service ownership becomes clearer because contractual obligations attach to the customer account while permissions and experiences may attach to individual users.
How to use it
- Define the customer grain before counting acquisition, churn, retention, satisfaction, or lifetime value.
- A paying organization can be the customer even when many employees use the product and procurement placed the order.
- The user supplies usage evidence; the buyer supplies purchase evidence; neither role should automatically stand in for every customer need.
- Client is common in professional services but is not a universal legal or analytical substitute for customer.
- Potential customers belong to a market or pipeline until they satisfy the organization's explicit customer-status rule.
Decision cautions
Define a stable counting unit and time window before interpreting customer totals, retention, or segment comparisons. CRM records can contain several contacts for one account, so contact count should not be reported as customer count. The contractual customer may not experience the product directly; interviewing only executives can hide user friction. Status definitions that change between teams will distort conversion and churn even when each database query is technically correct.
- CRM records can contain several contacts for one account, so contact count should not be reported as customer count.
- The contractual customer may not experience the product directly; interviewing only executives can hide user friction.
- Status definitions that change between teams will distort conversion and churn even when each database query is technically correct.
Example
A company buys payroll software for 600 employees. The employer is the customer account and contracting party. Procurement is the buyer, the finance director is the decider, a payroll manager administers the service, and employees are users and beneficiaries. Five people appear as CRM contacts, but the seller counts one customer account for logo retention and 600 provisioned users for adoption. During discovery, payroll staff test workflow usability while finance discusses price and risk. If the employer ends the contract, the account churns even if one former employee keeps a free personal login. Recording these roles prevents inflated customer counts and makes the right participant answer each decision.
Compare with
Customer | purchases or holds the commercial relationship under the seller's stated entity and status rule. User | actually operates or consumes the offering and may have no purchasing authority or payment responsibility. Buyer | selects a supplier, negotiates, or arranges the purchase; in B2B this is one role inside a buying center. Client | often names the recipient of professional services or a relationship-oriented customer, but usage varies by profession and jurisdiction. Consumer or beneficiary | ultimately uses or benefits from an offering and may be different from both purchaser and customer account.
| Metric | Difference |
|---|---|
| Customer | purchases or holds the commercial relationship under the seller's stated entity and status rule. |
| User | actually operates or consumes the offering and may have no purchasing authority or payment responsibility. |
| Buyer | selects a supplier, negotiates, or arranges the purchase; in B2B this is one role inside a buying center. |
| Client | often names the recipient of professional services or a relationship-oriented customer, but usage varies by profession and jurisdiction. |
| Consumer or beneficiary | ultimately uses or benefits from an offering and may be different from both purchaser and customer account. |
Common mistakes
- Customer and user are not always the same; treating them as identical is especially risky in B2B, education, health, and family purchases.
- Every CRM contact is not a separate customer. Contacts, accounts, contracts, and legal entities represent different grains.
- The loudest stakeholder is not automatically the customer voice; purchase authority, daily use, administration, and benefit produce different evidence.
Frequently asked questions
Can a free user be a customer?
Only if the organization's declared customer definition includes a non-paying commercial relationship. Otherwise record the person as a user or prospect, not a paying customer.
In B2B, is the company or the contact the customer?
Usually the account or contracting organization is the customer for commercial metrics, while named people hold buyer, admin, or user roles. State the grain explicitly.
Is client a synonym for customer?
Sometimes in professional services, but not reliably. Use the term that matches the contract and operating model, then define it rather than assuming equivalence.
Who should be interviewed?
Match the participant to the question: users for workflow, buyers for selection, deciders for approval, administrators for operation, and account owners for relationship outcomes.