> For the complete documentation index, see [llms.txt](https://www.buildmvp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.buildmvp.com/problem/think-global-act-local.md).

# Think global, act local

You need to have a big vision you are passionate about but you should start with a small problem because startup journey is exhausting and you need to see wins along the way to get encouraged. Otherwise, you'll run out of gas and fail.

Though you want to solve a problem for many you should start working with a few (early adopters) and solve the problem for them.

### Big Vision, Small Start

1. Big Vision: Having a grand, global vision provides direction and motivation. It's the "north star" that guides the startup's overall mission.
2. Small Problem: Starting with a specific, manageable problem allows for focused effort and quicker results. This approach is more achievable and less overwhelming.

### Importance of Early Wins

1. Startup Journey: Acknowledging that building a startup is challenging and exhausting is realistic and important.
2. Encouragement through Progress: Small, frequent wins provide motivation and validation, helping founders and teams maintain momentum.
3. Avoiding Burnout: By focusing on achievable goals, startups can avoid the discouragement that comes from constantly chasing an distant, overambitious target.

### Narrow Focus, Broad Ambition

1. Solving for Many, Starting with Few: This aligns with the concept of finding a beachhead market - a small, specific group of customers that can be served exceptionally well.
2. Early Adopters: Focusing on early adopters allows startups to refine their product with highly engaged users before scaling.
3. Iterative Growth: This approach enables startups to perfect their solution in a controlled environment before expanding to larger markets.


---

# 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://www.buildmvp.com/problem/think-global-act-local.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.