> For the complete documentation index, see [llms.txt](https://docs.theoutcomeminds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theoutcomeminds.com/foundation/quickstart.md).

# Start Here

See what a map reveals and make better strategy decisions.

The Outcome Mindsᵀᴹ is built for entrepreneurs, founders, executives, and leaders.

Use it when you need to choose focus, explain strategy, or cut waste.

### What a map shows

A useful map shows two things at once.

* How close each capability is to the customer outcome.
* How mature each capability is in the market.

That view changes the quality of your decisions.

You stop treating every problem as if it needs custom work.

### What entrepreneurs use it for

* Choosing where to differentiate
* Deciding what to buy or partner for
* Seeing hidden dependencies
* Aligning product, ops, and go-to-market
* Spotting bottlenecks before scaling

### Ground rules

1. Name one user.
2. Define one clear outcome.
3. Map capabilities, not teams.
4. Place items using evidence.
5. Separate visible work from supporting work.
6. Update the map when conditions change.

### Good output

By the end of a first session, you should have:

* One user
* One outcome
* 8 to 15 capabilities
* A maturity position for each capability
* Three strategic moves
* One review cadence

{% hint style="info" %}
If the map feels crowded, you are mixing multiple outcomes. Split them and redraw.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.theoutcomeminds.com/foundation/quickstart.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.