value-proposition

Design value propositions using a six-part JTBD template.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/omeragaakbas/zoyare --skill value-proposition-omeragaakbas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: value-proposition
Source: https://github.com/omeragaakbas/zoyare/tree/main/.claude/skills/value-proposition
Command: npx skills add https://github.com/omeragaakbas/zoyare --skill value-proposition-omeragaakbas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams, founders, and marketers turn product descriptions and customer insights into a clear, segment-specific value proposition using a six-part Jobs‑To‑Be‑Done (JTBD) structure so messaging and positioning directly reflect customer needs and competitive tradeoffs.

Core Features & Use Cases

  • 6-part JTBD template: Guides you through Who, Why (problem/JTBD), What before (current state), How (solution), What after (improved outcome), and Alternatives.
  • Structured outputs: Produces a customer profile, articulated JTBD, friction analysis, solution mapping, improved outcome description, competitor comparison, a concise 1–2 sentence value proposition, and a positioning statement for marketing.
  • Use Cases: Create go-to-market messaging for a new SaaS feature, refine value propositions for different customer segments, or test positioning against identified alternatives.

Quick Start

Draft a 6-part JTBD value proposition for a product that helps small marketing teams manage campaigns more efficiently, specifying the target customer, core problem, current solutions they use, key features that solve the problem, the improved outcome, and primary alternatives.

Frequently Asked Questions about value-proposition

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a value proposition using the Jobs-To-Be-Done framework?

To create a JTBD value proposition, you define the target customer, articulate the core problem, identify current solutions, map product features to the problem, describe improved outcomes, and list competitive alternatives. This structured approach ensures messaging reflects actual customer needs.

What is the best way to write segment-specific positioning for a SaaS feature?

Writing segment-specific positioning requires analyzing a single customer segment's friction points and mapping them against your product's solution and competitive alternatives. This generates a concise positioning statement tailored to that segment's specific tradeoffs.

How do I structure a value proposition for go-to-market messaging?

Structuring a value proposition for go-to-market messaging involves detailing who the customer is, why they need the product, what they used before, how your solution works, the improved outcome, and alternative competitors. This yields a concise one to two sentence value proposition.

Can I use a JTBD template for different customer segments?

Yes, you can use a JTBD template for different customer segments by processing one segment at a time. You provide the specific product description, target segment, competitive alternatives, and customer insights to generate a tailored value proposition and positioning statement for each.

What inputs do I need to generate a positioning statement for my product?

To generate a positioning statement, you need a product description, a defined target customer segment, identified competitive alternatives, and any available customer insights or market data. These inputs allow the framework to produce a concise value proposition.

Why does my value proposition not align with customer needs and competitive tradeoffs?

Your value proposition may not align with customer needs if it lacks a structured analysis of current solutions, competitive alternatives, and the specific job to be done. Articulating these six components ensures positioning directly reflects actual customer tradeoffs.