# Marketing 99.8% of projects launched daily are meme, and have 0 utility. 99.9% of projects launched daily are dead after the first month of life. Price of these projects is kept up only **by paid marketing &** **influencers**. **$ARMY is built different.** We have a *constantly evolving* product, a s*easoned & well-connected* team, and a *clear vision.* We focus on *building long-term value* and growing slowly through word of mouth. Instead of *chasing hype*, we’re creating a **high-quality product** that people will want to talk about. Our goal is simple: let the product speak for itself. By working hard every day, we’re making sure it reaches more people and builds a strong, lasting community. Still, we won't sit *down and wait* for the magic to happen * Daily we'll **post a tweet that showcases our platform**, with the goal of being retweeted and seen by most eyes possible. * Project taxes give us budget to buy paid marketing activities. Though, we'd prefer to use this budget when the platform has more products to showcase. * We're in constant research for opportunities. You think you have something juicy for us? \ DM one of our admins and send it our way! *Should you put your trust in us?* Your choice. But remember,[ top projects in the blockchain space](https://bc.army/clients/) have been paying us for content, tech and marketing for years. We will do the same for our project. Same trusted team. Same good intentions. Improved knowledge. You still don't believe us? **They do.** --- # Agent Instructions: 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: ``` GET https://docs.bc.army/usdarmy/marketing.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.