The value delivered to customers
A value proposition is the specific value a product promises to deliver to a defined customer segment: the gains it creates and the pains it relieves, stated concretely enough that the customer recognises their own problem in it. The discipline lives in the matching. A proposition that is true for everyone is useful to no one, and the common failure is describing what the product does when the customer only cares what value they get.
The phrase entered management vocabulary through consulting in the late twentieth century, but its rigorous product-side form comes from Alexander Osterwalder and the Strategyzer team in Value Proposition Design (Wiley, 2014). They gave it a tool, the Value Proposition Canvas, with two halves that must align: a customer profile listing jobsJobUserJob To Be Done: what the user is trying to accomplishView reference →, pains, and gains, and a value map listing products and services, pain relievers, and gain creators. Fit is achieved when the relievers and creators actually address the customer's most pressing pains and gains. The canvas was built as the zoom-in companion to the earlier Business ModelBusiness ModelBusiness ModelThe business model canvas or definitionView reference → Canvas, where the value proposition is one of nine blocks.
The go-to-market lineage runs through Geoffrey Moore's Crossing the Chasm (1991). Moore supplied a fill-in-the-blanks positioningPositioningGo-To-MarketProduct positioning statementView reference → statement, naming the target customer, their needNeedUserA user need, pain, desire, or constraintView reference →, the product category, its key benefit, the competitive alternative, and the differentiator. His insightInsightUser ResearchA synthesised finding from researchView reference → was that a value proposition has to be aimed: the proposition that wins visionary early adopters is not the one that wins the pragmatic early majority, and a company stalls in the chasm when it forgets to re-aim.
Both threads converge on a single rule the field now treats as settled. A value proposition is grounded in the customer's world, the jobs and pains, before it describes the solutionSolutionDiscoveryA proposed approach to address an opportunityView reference →. The work is evidentiary, since a claimed gain that no customer ranks as important is a fit failure however elegant the featureFeatureProduct SpecificationA product capability or featureView reference → behind it.
A team building expense software for early-stage startups maps its target segment's profile. The pressing job is closing the monthly books fast; the sharpest pain is chasing receipts across Slack and email at month-end; the wanted gain is a defensible audit trail without hiring a bookkeeper. They draft their value map against exactly those entries. The pain reliever is automatic receipt capture from the inbox; the gain creator is an export an accountant accepts without rework.
Their proposition reads: "Close your books in a day, not a week, without hiring finance." They validate it against ten target customers and find the receipt-chasing pain resonates, while a feature they were proud of, multi-currency support, ranks near zero for this segment. That evidenceEvidenceValidationData supporting or refuting a hypothesisView reference → reshapes the roadmapRoadmapProduct SpecificationA strategic plan of features and milestonesView reference →. When they later face the early majority, the same underlying value is re-stated as reliability and compliance, because the pains that segment ranks highest are different ones.
In the Unified Product Graph the value proposition is the anchor of the Business, GTM & Growth region, the single entity that reaches across Users, Strategy, and Discovery. A business_modelbusiness_model_delivers_value_propositionvalue_proposition_targets_personavalue_proposition_addresses_jobvalue_proposition_solves_needvalue_proposition_evidenced_by_proof_pointvalue_proposition_challenged_by_objectionvalue_proposition_delivers_outcomepositioninggtm_strategy_positions_via_positioning
Type-specific fields on BaseNode
validation_statestringValidation maturity. Where it sits on the "is this real?" journey. Renamed from `confidence` because these values describe validation state, not subjective confidence. Use `Confidence` or `UPGAssessment` from primitives for per-rater confidence.
offering_typestringOffering shape
unique_selling_pointstringDifferentiation axis. Closed set so dashboards group propositions by differentiation strategy. For the narrative form, use `unique_selling_point_statement`.
unique_selling_point_statementstringNarrative differentiator copy. Pairs with `unique_selling_point` for messaging when the team needs the rhetorical sentence.
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
4 phases — initial: drafted
19 edge types connected to this entity.
business_model_delivers_value_propositionvalue_proposition_challenged_by_objectionvalue_proposition_evidenced_by_proof_pointvalue_proposition_targets_personavalue_proposition_delivers_outcomevalue_proposition_addresses_jobvalue_proposition_solves_needvalue_proposition_targets_persona_cross_domainkey_resource_enables_value_propositionpositioning_differentiates_via_value_propositioninsight_validates_value_propositionkey_activity_delivers_value_propositiondistribution_channel_delivers_value_propositionvalue_proposition_addresses_market_segmentvalue_proposition_yields_revenue_streamcustomer_relationship_supports_value_propositionpartnership_supports_value_propositioncapability_enables_value_propositioninitiative_realises_value_proposition1 framework use this entity type.