# Who We Serve

SEED is built for projects at different stages of their lifecycle. It is not limited to pre launch teams.

#### Pre launch projects

Teams preparing to go live need:

* Clear positioning and narrative
* A high intent community ready at TGE
* Sensible allocation and access design
* Launch architecture and trading support
* Awareness that turns interest into day one users<br>

SEED helps pre launch teams:

* Define their story in language real users understand
* Warm up wallets and communities before the first trade
* Plan liquidity and market structure for confidence at launch
* Execute campaigns that tie directly into on chain actions from day one

#### Post launch projects

These are tokens already trading that need a stronger growth engine. Common needs include:

* Higher daily activity and user participation
* Better trading performance and deeper liquidity
* Campaigns that create new demand
* Stronger utility activation and product adoption<br>

SEED supports post launch projects by:

* Designing new activation loops and product campaigns
* Optimising liquidity and market structure for healthier charts
* Using JuicedBot and Academy to guide holders into usage
* Running coordinated pushes around product releases and milestones

#### Revivals and turnarounds

Some projects have strong ideas and real technology but have lost momentum. These teams often need:

* Rebuilt liquidity and market structure
* Fresh positioning and story
* Community re engagement
* New commercial and ecosystem partnerships<br>

SEED works with these projects to:

* Reset how the market sees the token and product
* Rebuild confidence in the chart and liquidity
* Reignite community participation through clear plans and campaigns
* Reconnect the project with opportunities inside the Pineapple network<br>

Across all stages, SEED is flexible. Teams can engage at the point that fits their current needs, then scale support as they grow.

<br>


---

# 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://seed-4.gitbook.io/launch-with-seed/gitbook/whoweserve.md?ask=<question>
```

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.