> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/cxd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/cxd/project-chatbot/project-instructions/1-discover-and-define-problem/1.7-value-proposition.md).

# 1.7 Value Proposition & Features

{% tabs %}
{% tab title="✓  INSTRUCTIONS & DELIVERABLE" %}
Value propositions clearly define key aspects of your design that demonstrate it is a valuable and worthwhile product or service. It provides focus for the design of many types of services or products. Here is a template to get you started.

> **For** *\[describe target users]* **who** *\[describe problem or need], \[name of product/service]* **is a** *\[describe type of product/service]* **that** *\[describe benefit or value].*

As a team, review all of your work and discuss several possible design directions before settling in on one single value proposition. You will want this statement to be clear, concise, and compelling. It should be supported by your research and analysis up to this point.\
\
This is a good time to outline your intended features for the chatbot that you will be able to adapt as you move through your project. [Here is a template](https://docs.google.com/drawings/d/1oL9Wdbm0lDgp38PGO_dnXa47X32P92EbYNgvauZeF98/edit?usp=sharing) to get you started.

**❏ Deliverable**\
A document or slide deck with your team's value proposition in large font, and a copy of your draft feature mapping.
{% endtab %}

{% tab title="★  RUBRIC" %}

| ✓-  Below Standard                                                                                                | ✓  At Standard                                                   | ✓+  Above Standard                                                                                                                             |
| ----------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| **Value proposition** is provided but is not clear or does not offer a compelling need for the proposed solution. | Value proposition is clear and supported by the team's research. | Value proposition is especially convincing and generates anticipation to see the rest of the project. The value to stakeholders is compelling. |
| {% endtab %}                                                                                                      |                                                                  |                                                                                                                                                |
| {% endtabs %}                                                                                                     |                                                                  |                                                                                                                                                |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.launchboard.app/cxd/project-chatbot/project-instructions/1-discover-and-define-problem/1.7-value-proposition.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.