> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jinn.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Jinn for founders

> Every important meeting without going to it, answers from anything the company discussed, and knowledge that stays when people leave.

This page sets Jinn up for running a company: meetings, docs and the AI that reads them sit in
one workspace instead of a notetaker, a docs tool and a chat bot that don't know about each
other. Once it's set up, you get:

* Every important meeting without going to it — whoever is on the call records it, and you read
  or ask instead of sitting in ([step 4](#4-read-a-meeting-you-didnt-go-to))
* Answers about anything the company discussed, across every project, with a link to the moment
  it was said ([step 5](#5-ask-about-anything-the-company-discussed))
* Company knowledge that stays when people leave, and AI that runs on the account you choose
  ([step 3](#3-choose-whose-account-the-ai-runs-on))

Steps 1–3 you do once. Steps 4–6 are what you do every week.

A two-person startup and a 500-person company work with the same Jinn: the same meetings,
agents, chat and docs. What differs between workspaces is how much they record and how much AI
work they run, not which parts of the product they can open.

## 1. Set up the workspace

If nobody from your company is in Jinn yet, follow the [Quickstart](https://docs.jinn.so/getting-started/quickstart.md)
first. It creates the workspace and takes one real meeting from start to finish.

## 2. Make a project per stream of work

A [project](https://docs.jinn.so/projects/manage-projects.md) decides who sees what's in it and which agents read it.

1. Click **New project** in the left sidebar.
2. Name it after the work: *Product*, *Sales*, *Hiring — backend engineer*, *Series A*.
3. Choose **Private** for investor calls, hiring and anything you wouldn't put in front of the
   whole team — only the people you add can see it. Choose **Open** for the rest.

Search and chat find only what the person asking can already open, so a question in the
workspace chat doesn't surface a salary discussion to someone outside the hiring project.

## 3. Choose whose account the AI runs on

Transcribing, writing up and answering run on an AI provider account. Under **Settings** →
**AI Providers**, choose:

* **Jinn credits** — nothing to set up, everything runs on Jinn's accounts
* **Only my own keys** — everything runs on provider accounts your company already pays for and
  controls
* **My keys, with Jinn credits as backup** — your keys first, and Jinn credits for any provider whose key is missing or switched off

See [How your AI is powered](https://docs.jinn.so/workspace/ai-and-indexing.md).

## 4. Read a meeting you didn't go to

Whoever is on the call records it from the desktop app — see
[recording a meeting](https://docs.jinn.so/meetings/record-a-meeting.md). Upload old calls as files: open a project,
go to **Recordings** and click **Upload recordings**.

Every recorded meeting gets a write-up from AI [agents](https://docs.jinn.so/agents/add-an-agent.md) — each one reads
the meeting through a particular role. One of them, **Default**, is built into every project
and writes a summary and the action items on its own.

To read the same meeting the way you would have:

1. Open the recording.
2. Click **Add agent** at the end of the row of agents, and pick a role: **Product Manager**
   for decisions nobody made out loud, **Sales Rep** for which deals need attention,
   **Recruiter** for whether a candidate fits the role.
3. Read its write-up next to Default's.

## 5. Ask about anything the company discussed

1. Click **AI** in the left sidebar. The chat looks across the whole workspace.

2. Ask in plain words.

   > [!TIP]
   >
   > For example: *What did we tell customers about pricing this month, and did anyone push
   > back?*

3. Open the link under the answer to hear the moment it was said.

When a key hire leaves, this is what stays: the decisions are in the recordings, the write-ups
and the docs, and the chat answers from them for whoever comes next.

## 6. Bring in what you already have

* **Old calls.** Upload a Zoom export, a voice memo or a video to a project's **Recordings**.
  Jinn reads it as if it were recorded today. See [uploading a recording](https://docs.jinn.so/meetings/upload-a-recording.md).
* **Notes and specs.** Create a doc with **Add** → **New doc in project**, then open its **⋯**
  menu and choose **Import from Markdown** or **Import from HTML**. See
  [writing a doc](https://docs.jinn.so/docs/write-a-doc.md).

## Where to go next

> [card] [Jinn for your role](https://docs.jinn.so/for/overview.md)
>
> How Jinn helps each role on your team, and where each one starts.

> [card] [Jinn for managers](https://docs.jinn.so/for/managers.md)
>
> Notes for the whole team from one recording, and who owns what in one question.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.