Value Prop Statements

Documentation Index

Fetch the complete documentation index at: https://docs.getcore.me/llms.txt

Use this file to discover all available pages before exploring further.

Goal: Write clear, compelling value proposition statements that resonate with specific customer segments.

​

Tools Required

This skill runs using CORE memory only. No integrations required.

​

Trigger

Trigger: Run on demand when the user asks to craft a value proposition, articulate product positioning, or define unique value for a market.

​

Setup

Search memory for any previously stored positioning or value proposition work:

• “What is the product or service?”
• “Who is the target customer?”
• “What is the core value delivered?”

If nothing is found, ask once:

“To craft a strong value prop, I need to know: What is your product, and who is the customer you’re selling it to?”

Store the response in memory. Do not ask again in future runs.

​

Step 1: Identify Target Customer and Their Job-to-Be-Done

Define the specific customer segment and the job they’re trying to accomplish. Clarify:

• Target customer: Who is the buyer or end user? (Persona name, role, industry, company size)
• Job-to-be-done: What outcome does this customer want? Frame as a verb: “Reduce engineering time,” “Close sales faster,” “Sleep better”
• Current state: How are they doing this job today? What tools or processes do they use?
• Desired state: What would ideal look like? What would change for them if this job was easier?

If the user’s description is vague (e.g., “everyone”) → force a specific persona: “If you had to pick one person who needs this most, who would it be?” Output: Clear customer definition and their job-to-be-done.

​

Step 2: Identify Key Benefits (Outcomes, Not Features)

Translate product capabilities into customer outcomes. For the job defined in Step 1, list the top 3–5 benefits:

• Benefit: What does the customer gain? (save time, reduce cost, increase confidence, improve quality)
• Measurement: How would the customer measure success? (hours saved, revenue gained, error rate reduced, retention improved)
• Competitive context: Do competitors offer this? If yes, how are you better?

Avoid feature language. Bad: “Integrates with 500 apps.” Good: “Connects your entire tech stack so you’re not switching between tools.” If benefits are unclear → ask: “Why would a customer buy this?” Keep asking “why” until you reach an emotional or business outcome. Output: List of 3–5 customer benefits with measurable outcomes.

​

Step 3: Identify Barriers and Objections

Map the customer’s hesitations and objections to buying. For your target customer, what prevents them from solving their job-to-be-done with your product?

• Cost objection: “Our solution is expensive compared to their budget”
• Complexity objection: “Too much learning curve; they prefer simplicity”
• Trust objection: “They don’t know if it works; they want proof”
• Switching cost: “They have switching costs from their current solution”
• Unknown solution: “They don’t know a better solution exists”

For each objection, note what evidence or messaging would overcome it (e.g., free trial, case study, ROI calculator, proof of concept). If objections are unclear → ask: “Why would a customer NOT buy this?” Output: Map of top 2–3 objections and potential responses.

​

Step 4: Craft the Core Value Prop Statement

Write a concise, customer-centric value proposition using this formula:

[Product name] helps [target customer] [job-to-be-done] by [unique approach], so they can [primary benefit].

Example:

Notion helps product managers centralize requirements and feedback in a single workspace, so they can ship faster and reduce miscommunication across teams.

Refine the statement:

• Is the customer obvious? (Not “for busy people,” but “for marketing managers in mid-market B2B SaaS companies”)
• Is the job clear? (Specific verb: “reduce churn” not “manage customers”)
• Is the approach differentiated? (Why you, not a generic solution?)
• Is the benefit compelling? (Outcome the customer cares about)

If the statement feels generic → stress test it: “Could this apply to a competitor? If yes, it’s not differentiated enough.” Output: One-sentence core value proposition.

​

Step 5: Develop Supporting Value Prop Statements (By Segment)

Expand the core value prop into segment-specific variations. If you serve multiple customer segments (e.g., small teams vs. enterprises), write a tailored value prop for each: For Segment A:

[Product] helps [Segment A customer] [their job], so they can [their primary benefit].

For Segment B:

[Product] helps [Segment B customer] [their job], so they can [their primary benefit].

Order segments by priority (revenue potential, ease of reach, market size). If you have 5+ segments → pick the top 3 to tailor. For others, reference the core value prop. Output: 2–3 segment-specific value propositions.

​

Step 6: Create Supporting Evidence

Identify proof points that validate the value proposition. For each value prop statement, gather:

• Case studies: Customer stories showing the stated benefit
• Data: Metrics from customers (% of time saved, revenue increased, churn reduced)
• Third-party validation: Industry reports, analyst reviews, awards, certifications
• User testimonials: Direct customer quotes backing the value prop
• Free trial or POC: Opportunity for customers to experience the benefit firsthand

If proof is missing → flag it and recommend: “Conduct 5 customer interviews validating this benefit” or “Track this metric going forward.” Output: List of proof points per value prop statement.

​

Step 7: Test and Refine

Recommend testing the value propositions with real customers. Steps:

1. Share the value prop with 5–10 target customers (in conversation or on landing page)
2. Gather feedback: “Does this resonate?” “What would you change?” “Would you be interested?”
3. Measure engagement: Click-through rate, conversion rate, email opens, demo requests
4. Refine based on feedback: Update language, reorder benefits, shift segment focus

Establish a cadence: revisit value props quarterly or when product/market changes significantly. If testing shows low resonance → loop back to Step 2 and revisit benefits. The benefits may not match what customers actually value. Output: Refined value prop statements and validation plan.

​

Output Format

---

Value Proposition Statements Target Customer & Job

• Segment: [Customer role, industry, company size]
• Job-to-be-done: [Outcome in verb form]
• Current approach: [How they solve it today]
• Desired state: [What would ideal look like]

Core Value Proposition

[Product] helps [customer] [job] by [unique approach], so they can [benefit].

Key Benefits

1. [Benefit 1] — [Measurable outcome] (vs. competitor: [differentiation])
2. [Benefit 2] — [Measurable outcome] (vs. competitor: [differentiation])
3. [Benefit 3] — [Measurable outcome] (vs. competitor: [differentiation])

Segment-Specific Value Props

• For [Segment A]: [Segment-specific value prop]
• For [Segment B]: [Segment-specific value prop]

Customer Objections & Responses Supporting Evidence

• Case studies: [Customer names / industries]
• Data: [Quantified results: X% improvement, Y hours saved, etc.]
• Testimonials: “[Direct customer quote]” — [Customer name, role]
• Third-party: [Industry reports, analyst ratings, awards]

Testing Plan

• Audience: Test with [number] customers from [segment]
• Validation metrics: [Click-through %, conversion %, NPS, or engagement metric]
• Timeline: Test by [date]
• Success criteria: [Benchmark or threshold to validate resonance]

---

​

Edge Cases

• Multiple diverse use cases: If customers use the product for different jobs (e.g., analytics tool used for finance reporting and product analytics), create separate value props per use case, not one generic statement.
• B2B with multiple stakeholders: Different stakeholders (CFO vs. analyst vs. IT) care about different benefits. Create value props tailored to each (cost/ROI, speed/insight, implementation/security).
• Market saturation: If competitors use similar value props, emphasize the unique “how” (proprietary tech, approach, or customer success model that differentiates you).
• Unproven product: If the product is early-stage, build value props around the hypothesis you’re testing, not marketing claims. Acknowledge that benefits are “expected to deliver” and run experiments to validate.
• Shifting target customer: If the user is unsure which segment to prioritize, recommend testing the value prop with 2–3 segments simultaneously and picking the one with highest resonance.
• Feature-focused company culture: If the team naturally gravitates to features, reinforce the distinction: “Features explain the ‘what.’ Value props explain the ‘why customers care.’”