A distinct group within the target market
A market segment is a group of buyers similar enough on the attributes that drive purchasing that one strategy can serve them all. The premise is that a market is heterogeneous, so treating it as one undifferentiated mass wastes effort, while slicing it too finely produces segments too small to be worth a strategy. A segment is the unit at which targeting, sizing, and positioningPositioningGo-To-MarketProduct positioning statementView reference → decisionsDecisionStrategyA recorded decision with context, rationale, and consequencesView reference → are made.
The modern concept was named by Wendell R. Smith in Product Differentiation and Market Segmentation as Alternative Marketing Strategies, published in the Journal of Marketing in 1956. Smith argued that demand is diverse, not homogeneous, and that a firm faces a choice: differentiate the product to bend demand toward a single offering, or segment the market and tailor offerings to its natural divisions. He framed segmentation as a deliberate response to heterogeneity rather than an accident of it. That paper is the citation every later treatment traces back to.
Practice then split segmentation into bases. Demographic and, for business markets, firmographic bases describe buyers by observable attributes such as age, income, company size, or industry. They are cheap to measure and easy to act on, which is also their weakness: two companies of identical size can want completely different things. NeedsNeedUserA user need, pain, desire, or constraintView reference →-based and behavioural segmentation cut instead by what buyers are trying to do and how they act, which predicts purchasing better but costs more research to build. The field's working consensus is that observable bases are useful proxies, and needs-based bases are the ones that actually explain why someone buys.
Clayton Christensen's JobsJobUserJob To Be Done: what the user is trying to accomplishView reference →-to-Be-Done argument in Competing Against Luck pushes this further: the relevant unit of demand is not a demographic cohortCohortGrowthA group of users sharing a common characteristicView reference → but a functional, emotional, and social job a buyer is trying to get done, with demographic and firmographic attributes serving only as circumstantial context. By that reading, a segment built on observable proxies may cluster the wrong buyers together — two companies of identical size and industry may be hiring for entirely different jobs — while a needs-based segment that groups buyers by the job they share will more reliably predict who buys and why.
Segmentation also acquired a sizing discipline. The TAM, SAM, SOM hierarchy nests three figures: the total addressable market is all demand for the category, the serviceable available market is the slice your offering and reach can actually serve, and the serviceable obtainable market is the share you can realistically win near term. Segmentation is how a credible SAM gets drawn, because a SAM is a TAM filtered down to the segments you have chosen to serve.
A company selling expense-management software starts with a TAM of every business that processes expenses, a number in the millions. That figure is too coarse to plan with. They segment firmographically by headcount and find three groups behave differently: sole traders want zero setup, mid-market finance teams want approval workflows, and enterprises want procurement integration. The mid-market segment, firms of 50 to 500 staff, has roughly 80,000 companies in their geography, an average contract value that supports a sales-assisted motion, and the least competition. That becomes the SAM.
Naming that segment forces honest trade-offs. The approval-workflow featuresFeatureProduct SpecificationA product capability or featureView reference → that win mid-market deals add friction the sole trader hates, so the team cannot serve both well with one product. Positioning sharpens immediately, because "expense software for growing finance teams" is a claim a buyer can place themselves inside, and the sole trader self-selects out without a wasted sales call.
Geoffrey Moore's Crossing the Chasm makes segment choice a survival decision rather than a targeting preference. Moore argues that technology products face a structural gap between early adopters, who tolerate incompleteness for the promise of an advantage, and the pragmatist early majority, who want a complete solutionSolutionDiscoveryA proposed approach to address an opportunityView reference → and buy from market leaders. Crossing that gap requires concentrating on a single beachhead segment — one specific, bounded group — winning it completely enough to become a reference customer before expanding. The implication for sizing is that a plausible SAM must be a segment you can dominate, not merely enter; diffuse targeting across several segments at once typically fails to build the reference base that the early majority demands.
In the Unified Product Graph, a market segment anchors the market intelligence region and acts as the join between sizing and design. Personas live inside it (Market SegmentincludesPersonacross-domain, market_segment_includes_personaPersonabelongs toMarket Segmentcross-domain), business modelsBusiness ModelBusiness ModelThe business model canvas or definitionView reference → point at it (persona_belongs_to_market_segmentBusiness ModeltargetsMarket Segmentcross-domain), positioning is scoped to it (business_model_targets_market_segmentPositioningwithinMarket Segmentcross-domain), an ideal customer profile sharpens it (positioning_within_market_segmentIdeal Customer ProfiletargetsMarket Segmentcross-domain), and competitive analysisCompetitive AnalysisMarket IntelligenceA structured analysis of the competitive landscapeView reference → bounds its study to it (ideal_customer_profile_targets_market_segmentCompetitive AnalysisscopesMarket Segmenthierarchy). Holding the segment as a node keeps the "who we sell to" decision queryable, so a persona with no segment, or a segment no business model targets, shows up as an unfinished link rather than an assumptionAssumptionStrategyA belief taken as true that underpins a strategyView reference → nobody wrote down.competitive_analysis_scopes_market_segment
Worked example: Trellis
Trellis targets 50-to-500-person, operations-heavy B2B companies: AI-curious but wary after ungoverned AI experimentsAI ExperimentAI & Machine LearningAn AI-focused experimentView reference →, already paying for a spreadsheet-plus-glue stack. This market segment is precise enough to anchor an ideal customer profileIdeal Customer ProfileGo-To-MarketThe ideal customer profile (ICP)View reference → and a positioningPositioningGo-To-MarketProduct positioning statementView reference → statement, and it maps directly to the director personaPersonaUserAn archetype representing a user segmentView reference → and economic buyer the product is shaped around.
Type-specific fields on BaseNode
segment_sizenumberPotential customers in this segment
growth_ratenumberYoY growth rate as a decimal. @example 0.15 represents 15%
tamnumberTotal Addressable Market (currency units)
samnumberServiceable Addressable Market (currency units)
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
14 edge types connected to this entity.
product_addresses_market_segmentcompetitive_analysis_scopes_market_segmentbusiness_model_targets_market_segmentmarket_segment_includes_personapersona_belongs_to_market_segmentpositioning_within_market_segmentideal_customer_profile_targets_market_segmentdocument_describes_market_segmentcultural_adaptation_targets_market_segmentcustomer_relationship_with_market_segmentdistribution_channel_reaches_market_segmentvalue_proposition_addresses_market_segmentrevenue_stream_captured_from_market_segmentinitiative_enters_market_segmentIn a portfolio document, Market Segment entities can participate in cross-product edges, the typed relationships that link entities across different products. These edges are declared in UPGPortfolioDocument.cross_edges.
instance_ofarea_targets_market_segment{product_id}/{node_id}. They are declared in the cross_edges array of a UPGPortfolioDocument, not inside individual product graphs. See Portfolio for the full model.1 framework use this entity type.