--- slug: value-proposition type: pattern summary: "The reason a specific customer should choose your product over doing nothing, building it themselves, or picking an alternative." created: 2026-04-04 updated: 2026-04-05 related: build-vs-dont-build-judgment: relation: used-by note: "Features should strengthen the proposition, not dilute it." competitive-landscape: relation: uses note: "Value is measured against alternatives." customer: relation: depends-on note: "A proposition must address a specific buyer." differentiation: relation: uses note: "Differentiation is what makes the proposition credible." distribution: relation: enables note: "The channel must convey the proposition effectively." go-to-market: relation: enables note: "The proposition is the core of your market message." monetization: relation: enables note: "Users convert when they've experienced the value." problem: relation: depends-on note: "Value only exists relative to a real problem." product-market-fit: relation: enables note: "Fit means the proposition resonates strongly enough that customers pull the product toward them." revenue-model: relation: enables note: "The model must reflect the value delivered." roadmap: relation: enables note: "The roadmap should reinforce and deepen the proposition." --- # Value Proposition > **Pattern** > > A named solution to a recurring problem. ## Understand This First - [Problem](problem.md) -- value only exists relative to a real problem. - [Customer](customer.md) -- a proposition must address a specific buyer. ## Context At the **strategic** level, once you've identified a [Problem](problem.md), a [Customer](customer.md), and a [User](user.md), you need to articulate *why* this customer should choose your product instead of doing nothing, building it themselves, or choosing an alternative from the [Competitive Landscape](competitive-landscape.md). The value proposition is that reason. It's the bridge between a real problem and a decision to act. A value proposition isn't a tagline or a marketing slogan. It's a clear statement of the benefit a specific customer receives, the problem it solves, and why this product delivers that benefit better than the alternatives. ## Problem Why should anyone care about your product? Most products compete not against other products but against *inaction*, the customer's default behavior of continuing to live with the problem. Overcoming inaction requires a value proposition strong enough to justify the cost of switching: the money, the time, the risk, and the organizational friction of adopting something new. ## Forces - **Inertia is the strongest competitor.** "Doing nothing" wins most of the time. - **Value is relative.** A feature only matters in comparison to what the customer has now. - **Different stakeholders value different things.** The [Customer](customer.md) may value risk reduction while the [User](user.md) values speed. - **Claimed value isn't credible value.** Everyone says their product saves time and money. - **Quantification helps** but not everything valuable is easily measured. ## Solution Write the value proposition as a simple statement that a specific customer can evaluate: "For \[customer segment\] who \[have this problem\], our product \[does this thing\] so they can \[achieve this outcome\], unlike \[the current alternative\] which \[has this limitation\]." This structure forces clarity. If you can't fill in every blank concretely, you have a gap in your product thinking. The hardest blank is usually the last one: articulating specifically what's wrong with the customer's current approach. If the current approach works well enough, your value proposition is weak regardless of how good your product is. Test the proposition by asking potential customers to rank their problems and evaluate your claimed benefit. If they rank your problem low, or if they don't believe your claimed benefit, no amount of engineering will help. In agentic coding, the value proposition often centers on speed, cost reduction, or capability expansion. "An AI agent can write your unit tests in minutes instead of hours" is a clear proposition, but only if the customer is currently spending hours writing tests and considers that time a problem worth solving. ## How It Plays Out A team builds a tool that uses AI agents to generate API documentation from source code. Their initial value proposition is "better documentation." This is vague and uncompelling; every documentation tool claims to be better. After talking to customers, they refine it: "For backend teams that ship APIs weekly, our tool generates accurate endpoint documentation from code in seconds, eliminating the two hours per sprint currently spent writing docs that go stale anyway." This version names the customer, the pain, the benefit, and the failing of the alternative. A solo developer builds a browser extension that reformats error messages into plain English using an LLM. The value proposition for senior developers is weak; they already read stack traces fluently. But for bootcamp graduates in their first job, the proposition is strong: "Understand your first error message without spending twenty minutes searching Stack Overflow." Same product, different customer, different strength of proposition. > **⚠️ Warning** > > A common trap is building a value proposition around a capability rather than an outcome. "We use GPT-4 to analyze your data" is a capability. "Find the three accounts most likely to churn this quarter" is an outcome. Customers pay for outcomes. ## Consequences A sharp value proposition aligns the entire team. Product knows what to prioritize. Marketing knows what to say. Sales knows which objections to anticipate. Engineering knows which performance characteristics matter. The liability is that a strong value proposition can become a cage. As the market evolves, the original proposition may weaken. Competitors copy your [Differentiation](differentiation.md). Customers' expectations rise. The proposition must evolve with the product and the market. A value proposition also creates accountability. If you promise "reduce onboarding time by 50%," someone will measure it. This is healthy pressure, but it means you must be honest in your claims. --- - [Next: Competitive Landscape](competitive-landscape.md) - [Previous: User](user.md)