> For the complete documentation index, see [llms.txt](https://docs.fullforce.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fullforce.io/full-force-launchpad/sketching-the-problem.md).

# Sketching the Problem

Most crypto projects follow this pattern:

1. A development-oriented team creates a Telegram, Discord, and Twitter page
2. Their social strategy prioritizes user growth over sharing quality content
3. They use influencers to promote their presale and sell out
4. The project fails to cultivate engaged community members
5. The community members sell their investment, and reinvest into the next big thing!

This cycle plays out because large social followings often mean access to more capital, access to high-value partners, and higher-quality exchange listings. However, short-term gains lead to two long-term costs.

<table data-card-size="large" data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Low Engagement</strong></td><td>Low-quality campaigns like airdrops lead to a community full of low-engagement followers, not interactive members. Still, growing via other means (say, social media ads) is tricky due to challenges with compliance and high costs. Lower engaged users are also less likely to HODL the token.</td><td></td></tr><tr><td><strong>Launchpad-induced Sell Pressure</strong></td><td>When projects choose a launchpad, they submit themselves to a fundamentally flawed staking model that favors 'whales' holding the launchpad's token, rather than enabling the core community to invest in their project. The dynamic creates huge sell pressure, not a ground base of support.</td><td></td></tr></tbody></table>


---

# 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.fullforce.io/full-force-launchpad/sketching-the-problem.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.