> For the complete documentation index, see [llms.txt](https://timpi.gitbook.io/timpi-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://timpi.gitbook.io/timpi-whitepaper/timpis-data-services/timpi-search/user-acquisition-strategy.md).
# User Acquisition Strategy
The Timpi search engine provides users with the first true alternative to Big Tech's control over what information we see and share on the web.
Our User Acquisition strategy focuses on initially capturing the market concerned with privacy and freedom. As the % of individuals who are actively seeking alternatives to Google grows rapidly, Timpi will be in a prime position as a viable alternative.
As regulation comes into place, we position ourselves as the number one alternative to Google, and we do this by demonstrating our value proposition.
Utilizing our decentralized architecture to maintain resilience and low operating costs. This allows us to expand and develop our platform rapidly.
Providing unique functionality appeals directly to our target audience supported with a marketing strategy that appeals to those personas.
Timpi is taking a comprehensive strategy to move into market segments based not only on solid marketing and PR but also on how we operate and our technology's functionality.
---
# 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://timpi.gitbook.io/timpi-whitepaper/timpis-data-services/timpi-search/user-acquisition-strategy.md?ask=&goal=
```
`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.