Core concept · Layer 3

Entities

Markets can increasingly be understood as systems of entities and relationships.

Definition

Entities are the organisations, people, products, services, problems, categories, concepts and technologies whose explicit relationships define meaning in a market.

Frontier Marketing defines entity architecture as the deliberate design of those entities and their relationships so that both humans and machines arrive at the same understanding of the organisation.

Entity types

Organisations
Companies, institutions, agencies and other collective actors that can be named and distinguished.
People
Named individuals with roles, authorship and affiliations — founders, authors, researchers, practitioners.
Products
Named things that can be bought, licensed or used, with versions and capabilities.
Services
Named forms of work delivered to a buyer, with scope and outcomes.
Problems
The buyer conditions that create demand, stated specifically enough to be recognised.
Categories
The classes used by buyers and systems to group comparable offerings.
Concepts
Named ideas, frameworks and disciplines — Frontier Marketing itself is a concept entity.
Technologies
Named technical capabilities, standards and platforms that shape what is possible.

Why relationships matter

An entity in isolation carries little meaning. A product becomes understandable through the problem it addresses, the category it belongs to, the organisation that makes it and the people associated with it. Frontier Marketing holds that meaning is produced by relationships, and that relationships left implicit are relationships that retrieval systems must guess.

Explicit relationships improve human and machine understanding for the same reason: they remove the need for inference. A reader who has to deduce what a company does will sometimes deduce wrongly; a system doing the same at scale will do so consistently.

A worked example of an entity graph

This website is itself structured as an entity graph. Its principal relationships are stated in plain language here and expressed in structured data on every page:

Designing an entity architecture

Give each entity one canonical page and one canonical name. Use a stable identifier for it. State its relationships as ordinary crawlable links in the body text, not only in navigation. Keep structured data consistent with the visible wording. Where two entities could be confused, disambiguate explicitly rather than hoping context resolves it.

Published: 2026-09-20

Last updated: 2026-09-20

Framework version: 1.0