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

# Founding Partner Programme

Use Eirin for free while we build it with you. 25 studios per group.

**25 studios per group.** Use Eirin for free while we build it with you.

{% columns %}
{% column %}
{% hint style="success" %}

### What you get

**Free until Dec 31, 2026**, or for 60 days, whichever is later

* A 20-minute setup call with our team
* A direct line to the founders
* A say in what we build next
* Founder pricing, kept for you later
  {% endhint %}
  {% endcolumn %}

{% column %}
{% hint style="info" %}

### What we ask

* 20 minutes of feedback every two weeks
* Your logo and a short case study
* If you like Eirin, tell others about it on X, LinkedIn or in your network
  {% endhint %}
  {% endcolumn %}
  {% endcolumns %}

## Your first 30 days

{% stepper %}
{% step %}

### Day 0

Replies go live on the setup call.
{% endstep %}

{% step %}

### Week 2

Your first weekly sentiment report.
{% endstep %}

{% step %}

### Week 4

We review together, then auto-reply switches on.
{% endstep %}
{% endstepper %}

## Get started

[Get started →](https://app.lysto.gg/eirin)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://eirin-ai.gitbook.io/eirin-ai-docs/founding-partner-programme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.