> For the complete documentation index, see [llms.txt](https://astropad.gitbook.io/astropad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://astropad.gitbook.io/astropad/executive-summary.md).

# Executive Summary

Astropad is a next-generation presale launchpad aimed at overtaking legacy platforms such as PinkSale by
\
delivering a lower-cost, more transparent, and more secure experience for token projects and investors. The
\
platform is powered by the ASP utility token (100,000,000 supply) and features a 4% presale commission,
\
integrated paid services (audits, KYC, SAFU badges, AMA, marketing) paid in ASP, and a deflationary
\
mechanism where 10% of platform profit is used to buy back & burn ASP. This document expands the project
\
vision into a practical business model that includes market sizing, revenue scenarios, competitive analysis, and
\
quantified buyback examples to illustrate how platform success translates into token value for holders.

<figure><img src="/files/k6oMTVPe8Jyqs8HgwXnN" alt=""><figcaption></figcaption></figure>


---

# 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://astropad.gitbook.io/astropad/executive-summary.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.