> 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-robotics/project-instructions/1-discover-and-define-problem/1.6-value-proposition.md).

# 1.6 Value Proposition

{% tabs %}
{% tab title="✓ TASK" %}
Your team will discuss and create a [value proposition](https://docs.idew.org/principles-and-practices/practices/design-practices/value-proposition) for your team’s robot concept using this format:

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

Your team's value proposition is an “elevator pitch” that quickly communicates your robot concept to outside people and helps provide focus to your team as you design, build, and evaluate your robot prototype.

## **❏ Deliverable**

Submit a document with your team's value proposition for your robot concept.
{% endtab %}

{% tab title="➤ EXAMPLE" %}
**VALUE PROPOSITION:**

For busy people who want an easier way to keep their home clean, **FloorBot** is a cleaning robot that vacuums carpets and cleans floors, saving time and effort.
{% endtab %}

{% tab title="★ RUBRIC" %}

| **✓- Below Standard**                                                                         | **✓ Meets Standard**                                             | **✓+ Exceeds Standard**                                                                                                                                        |
| --------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Value proposition 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 users and other 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-robotics/project-instructions/1-discover-and-define-problem/1.6-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.