.png){kind=small}
The Value Proposition as Marriage Proposal (Part 1): The Courtship
- Feb 10
- 11 min read
Updated: Feb 22
Written By Mark Evans MBA, CMgr FCMI
Proposing to Strangers and Other Business Failures
Every business is essentially making a marriage proposal to the market. Yet most do so blindly through building products, burning capital, and wondering why customers don’t say “yes.” The fundamental error isn’t in execution; it’s in assuming you can propose without courtship, without truly knowing the person you’re asking to commit.
In relationship terms, this is proposing to a stranger. In business terms, it’s launching without validating your value proposition. Both are forms of Russian roulette, and the barrel is loaded with inevitable failure. According to CB Insights’ analysis of startup failures, 42% failed because there was “no market need” the business equivalent of proposing marriage to someone who doesn’t want to get married. These weren’t businesses that lacked talent, ambition or funding; they simply never understood what they were proposing or to whom.
From what I've seen over time, here’s what most business literature misses: the value proposition isn’t just a marketing statement. It’s not a tagline for your website or a slide in your pitch deck. A properly understood value proposition is the beating heart of your entire organisation, the central pulse that coordinates every function both external and internal, every decision, every interaction towards delivering what customers actually need.
Like a biological heart that circulates oxygenated blood to every organ, the value proposition circulates clarity and purpose through recruiting, culture, values, vision, sales, service, brand, operations, and product development. When it beats clearly and strongly as one with the team, the business lives. When it’s weak, generic, or misaligned with actual customer needs, the organisation suffers systemic failure, often fragmenting into disconnected functions that pursue their own objectives without connection to customer value.
"Without a fully grounded and tested value proposition, your business is just a loose idea, a mere concept to gamble everything on."
This two-part series sets out that effective value proposition development mirrors the structure of a successful marriage proposal. Part 1 explores the courtship phase, understanding who you’re proposing to and what they actually need. Part 2 will examine the marriage itself, delivering on your promise daily and making the value proposition the organising principle for your entire business.
The Dual Nature: Value AND Proposition
Understanding the Words We Use
The term “value proposition” contains two words that deserve equal weight, yet most businesses fixate on the first and ignore the second. They obsess over value, namely features, benefits, competitive advantages, while forgetting they’re making a proposition. And propositions, by definition, require someone to say yes.
Value: What You Offer
Anderson, Narus, and Van Rossum (2006) define customer value propositions in business markets as answering the question: “Why should our firm purchase your offering instead of your competitor’s?” They emphasise that value is always relative to the next-best alternative and must be demonstrable, not merely claimed.
Rather, notice what’s essential: the recipient. Value doesn’t exist in isolation; it exists only in relationship to someone who values it. A holiday home in Barbados has tremendous value to someone who loves Caribbean travel and has leisure time. It has zero value (possibly negative value) to someone who doesn’t travel, fears flying, or has mobility constraints.
Zeithaml (1988) demonstrated this in her foundational research on consumer perceptions of value: “Perceived value is the consumer’s overall assessment of the utility of a product based on perceptions of what is received and what is given” (p. 14). Value is always perceived, always contextual, always relative to the specific individual’s needs, preferences, and circumstances.
Proposition: The Ask
The word “proposition” transforms value from attribute to offer. A proposition is fundamentally relational and it requires a proposer and a proposee, an offer and a response, alignment between what’s offered and what’s needed.
The marriage proposal metaphor illuminates this perfectly. When someone proposes marriage, they’re not simply listing their attributes (“I’m employed, healthy (i have my own teeth), educated”). They’re making a specific offer to a specific person: “Given who you are and what you need, I believe we can build something together that serves us both better than being apart. Will you commit to that with me?”
The proposition succeeds when both parties take a journey to believe the exchange creates mutual value. It fails when needs are mismatched, misunderstood, or unmet.
Why Value Proposition Development Matters Beyond Marketing
Most executives treat the value proposition as something the marketing team crafts after the business model is set. This is catastrophically backwards.
The value proposition should be the organising principle for every business function. A properly constructed value proposition, one that genuinely proposes specific value to specific customers based on validated understanding of their needs, should become the foundation upon which all organisational activities and growth strategies are built.
Traditional marketing treats customers as fixed entities with stable preferences. However, as I explore in my work on quantum marketing and the “if” economy customer behaviour is far more contextual and probabilistic than traditional personas suggest. Rather than proposing to fixed demographics, we must understand how context shapes which version of a customer emerges at the moment of decision.
The marriage metaphor extends here as well. A successful marriage isn’t just the wedding day (the marketing moment). It’s the entire relationship structure and how you make decisions together, how you allocate resources, how you communicate, how you resolve conflicts, how you grow together over time. The proposal establishes the foundation; the marriage is the ongoing commitment to deliver on that proposal daily.
Your value proposition is the same. It’s not what you say; it’s what you are. It’s not marketing; it’s strategy. It’s not communication; it’s organisational coordination.
The Courtship Phase: Knowing Who You’re Proposing To
The Foundation: Understanding Before Offering
In personal relationships, proposing marriage without knowing your partner’s values, goals, and non-negotiables would be absurd. Yet businesses routinely develop products based on assumptions about customer needs rather than validated understanding.
Christensen et al.‘s (2016) Jobs-to-be-Done (JTBD) theory provides the theoretical foundation for this customer-centric approach. In Competing Against Luck, they argue that customers don’t buy products; they “hire” them to accomplish specific jobs in specific contexts. As Christensen writes, “When we buy a product, we essentially ‘hire’ something to get a job done. If it does the job well, when we are confronted with the same job, we hire that same product again” (p. 26).
This reframes value proposition development entirely. The question isn’t “What features should our product have?” but “What job is the customer trying to accomplish, and what would make them ‘hire’ us to do it?” This is the courtship - understanding the customer’s world before proposing your solution.
Furthermore, Osterwalder et al. (2014) describe the value proposition at the heart of their business model canvas. They provide a vital business tool desined to extract and examine the value creation side of the idea, before mapping into the wider business model and ultimatley how the value is created and then delivered to the customer.
The Three Dimensions: Functional, Emotional, and Social Needs
Just as someone seeking a life partner has functional needs (shared life goals, compatible lifestyles), emotional needs (security, excitement, affection), and social needs (family approval, peer perception, cultural alignment), customers hiring products have needs across the same three dimensions.
Christensen et al. (2016) make this explicit in their framework:
Functional Jobs: The practical tasks customers need to accomplish. “I need to get from point A to point B.” “I need to track my expenses.” “I need to communicate with my team.”
Emotional Jobs: How customers want to feel or avoid feeling. “I need to feel secure.” “I need to avoid embarrassment.” “I need to feel competent.”
Social Jobs: How customers want to be perceived by others. “I need to signal status.” “I need to demonstrate belonging.” “I need to project professionalism.”
As Christensen emphasises, customers don’t want more features; they want solutions to their problems. This insight is revolutionary for value propositions. You’re not proposing features; you’re proposing solutions to jobs across all three dimensions. And crucially, the relative importance of each dimension varies by individual and context.
The Varying Degrees of Importance: Why Generic Propositions Fail
This is where most value propositions fail catastrophically: they assume everyone weights functional, emotional, and social needs identically.
Consider someone seeking a romantic partner. Person A might prioritise functional compatibility (shared life goals, compatible lifestyles) at 70%, emotional connection at 20%, and social factors (partner’s status, family approval) at 10%. Person B might weight these completely differently: 30% functional, 60% emotional, 10% social. Person C might prioritise social factors at 50% because they’re in a culture or profession where partner choice affects career prospects.
None of these weightings is “correct.” They’re individual. And any proposition that ignores these weightings and assumes everyone values the same things equally, will fail for most people.
The business parallel is exact. Different customers within the same market segment weight functional, emotional, and social factors dramatically differently. A value proposition that speaks only to functional needs will resonate with some customers and completely miss others. Unless you know which customers you’re talking to and what they prioritise.
Griffin and Hauser (1993) demonstrated in their research on the voice of the customer that understanding these variations is essential: “Customer needs are not all of equal importance. Understanding the relative importance customers attach to the satisfaction of different needs is critical” (p. 2). Their work established methodologies for discovering not just what customers need but how much each need matters.
The implication is stark: these weightings aren’t even stable within individuals. The same person may prioritise differently depending on context, recent experiences, time pressure, and who else is involved in the decision. This means your value proposition must be validated not just for what customers need, but for when and why those needs become paramount.
The Homework: Discovery Before Declaration
Before you can propose, you must understand. Not assume. Not guess. Not project your own preferences onto customers. Actually discover what they need and how much each dimension matters to them. You would be amazed at how many business leaders i've met or advised, who test their assumptions with colleagues and freiends rather than the target customer(s).
Steve Blank’s customer development methodology, detailed in The Startup Owner’s Manual (2012), provides the practical framework. His approach emphasises getting out of the building and conducting deep, qualitative interviews structured around understanding:
- What jobs are you trying to accomplish?
- How do you accomplish them today?
- What’s inadequate about current solutions?
- What would success look like?
- How would that success make you feel?
- Who else would know or care about this decision?
Notice: these questions discover needs and weighting. They don’t ask “Would you buy our product?” They don’t pitch solutions. They excavate the customer’s actual job structure.
To understand weighting and context, add questions like:
- Under what conditions does this job become urgent?
- What situations make different solutions more or less appealing?
- When have you prioritised differently than you expected?
- What factors change which needs matter most to you?
These questions reveal not just what customers need, but when, why, and under what conditions different needs become paramount.
Blank’s research across thousands of startups demonstrates that teams conducting extensive customer discovery before building products have dramatically higher success rates than those who build first and validate later. The homework isn’t optional; it’s existential.
This is the courtship. You’re learning who this person is and not who you hope they are, not who would be convenient for your product roadmap but, who they actually are. What keeps them up at night. What they’ve tried before. What worked. What didn’t. Why. And critically, how context shifts what they need from you.
Without this homework, you’re not making a proposition. You’re making an expensive guess. And the market, like a prospective spouse, doesn’t reward guessing.
Conclusion: Ready to Propose?
The courtship phase is where most businesses fail. They rush to build products, craft messaging, and launch campaigns without truly understanding who they’re proposing to or what those customers actually need across functional, emotional, and social dimensions.
The hard truth: if you cannot articulate your customer’s jobs, pains, and gains in their own words, if you don’t know how they weight different needs across different contexts then you’re not ready to propose. You’re gambling..
In Part 2, we’ll explore what happens after the proposal: how to deliver basics before delight, how to test your proposition before committing resources, and most critically, how to make your validated value proposition the beating heart of your business, circulating through every function from recruiting to operations to service.
Because getting them to say “yes” is just the beginning. The marriage, it's the daily delivery of your promise, and where value propositions are proven or broken.
Discover your business Value Proposition and book a free 15 minute clarity call or contact us
Frequently Asked Questions
1. What is a value proposition?
A value proposition is a clear statement explaining why a customer should choose your product over alternatives. It answers: "What specific value do you offer to specific customers that solves their specific problems?"
2. Why do most startups fail?
42% of startups fail because there's "no market need" (CB Insights, 2021). They build products without understanding what customers actually want or need.
3. What is Jobs-to-be-Done (JTBD) theory?
JTBD theory states that customers don't buy products—they "hire" them to accomplish specific jobs. Understanding the job, not just product features, is key to creating value propositions that resonate.
4. What are the three dimensions of customer needs?
Customer needs fall into three categories:
Functional: Tasks to accomplish (e.g., "get from A to B")
Emotional: How they want to feel (e.g., "feel secure")
Social: How they want to be perceived (e.g., "appear professional")
5. What is customer discovery?
Customer discovery is the process of conducting in-depth interviews (typically 30-50) to understand customer problems, current solutions, and unmet needs before building your product. It validates the problem, not your solution.
6. How do you validate a value proposition?
Validate through progressive stages:
Discovery interviews (understand the problem)
Landing page tests (measure behavioral interest)
Concierge MVPs (manually deliver the service)
Pilot programs (test willingness-to-pay)
7. What's the difference between personas and contextual customer understanding?
Traditional personas treat customers as fixed ("John is a tech enthusiast"). Contextual understanding recognises that the same person has different priorities in different situations (John values innovation at work, reliability for his parents).
8. How many customer interviews should you conduct?
Aim for 30-50 customer discovery interviews. Stop when you start hearing the same problems, needs, and contexts repeatedly - this indicates you've found clear patterns.
9. What questions should you ask in customer discovery interviews?
Focus on understanding their world:
What jobs are you trying to accomplish?
How do you accomplish them today?
What's inadequate about current solutions?
What would success look like?
How would that make you feel?
Who else cares about this decision?
10. Should you test your solution or the problem first?
Always test the problem first. Customers can accurately describe their problems but often can't articulate what solution they'd want. Validate that the problem exists and matters before proposing your solution.
References
Anderson, J. C., Narus, J. A., & Van Rossum, W. (2006). Customer value propositions in business markets. Harvard Business Review, 84(3), 90-99. (Accessed 6th February 2026)
Blank, S., & Dorf, B. (2012). The startup owner’s manual: The step-by-step guide for building a great company. K&S Ranch. (Accessed 6th February 2026)
Christensen, C. M., Hall, T., Dillon, K., & Duncan, D. S. (2016). Competing against luck: The story of innovation and customer choice. Harper Business.
Eric Ries (2011) complements Blank's methodology with rapid experimentation principles in The Lean Startup, providing the 'Build-Measure-Learn' feedback loop now used by startups worldwide.
Griffin, A., & Hauser, J. R. (1993). The voice of the customer. Marketing Science, 12(1), 1-27.
Osterwalder et al. (2014) provide the practical framework in Value Proposition Design that hasbecome the de facto tool for startups validating product-market fit.
Zeithaml, V. A. (1988). Consumer perceptions of price, quality, and value: A means-end model and synthesis of evidence. Journal of Marketing, 52(3), 2-22.
Comments