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

# Explore use cases

> Ready-to-run playbooks for every team. Pick your team, copy the setup, and have Hops working in your Space today.

Most use cases start with a question. Connect the apps Hops needs, then copy a prompt from the page and ask. Add a skill when you want Hops to follow the same format every time, and an automation when you want it to run without being asked. Pick the team closest to yours and start from there.

## Start here

<Card title="Company AI brain" icon="brain" href="/docs/use-cases/company-ai-brain" horizontal>
  Every decision, doc and thread, answerable in one question. Connect your docs, threads and decisions once, then ask anything.
</Card>

## Browse by team

### Leadership

<CardGroup cols={3}>
  <Card title="Founders & Executives" icon="briefcase" href="/docs/teams/founders-executives">
    Monday company snapshot, Board meeting and fundraise prep, Investor update, and 6 more.
  </Card>

  <Card title="VC & PE" icon="money-bill-trend-up" href="/docs/teams/vc-pe">
    Investment memo, Founder pipeline and partner meeting, Quarterly LP update, and 1 more.
  </Card>
</CardGroup>

### Go-to-market

<CardGroup cols={3}>
  <Card title="Sales" icon="handshake" href="/docs/teams/sales">
    Pre-call prep, Post-call follow-up, Deal rooms, and 8 more.
  </Card>

  <Card title="RevOps" icon="arrows-rotate" href="/docs/teams/revops">
    Handoff watch, Renewal watch, Pipeline review, and 5 more.
  </Card>

  <Card title="Marketing" icon="bullhorn" href="/docs/teams/marketing/overview">
    Campaign launch, Content repurposing, Copy review and approval, and 7 more.
  </Card>

  <Card title="Support" icon="headset" href="/docs/teams/support">
    Response drafting, Weekly patterns report, Escalation brief, and 4 more.
  </Card>
</CardGroup>

### Product & Engineering

<CardGroup cols={3}>
  <Card title="Product & Engineering" icon="code" href="/docs/teams/product-engineering">
    Spec review, Release notes, Sprint retro prep, and 7 more.
  </Card>
</CardGroup>

### Back office

<CardGroup cols={3}>
  <Card title="Finance" icon="chart-line" href="/docs/teams/finance">
    Monthly close, Board prep, Spend anomaly alert, and 3 more.
  </Card>

  <Card title="Operations & Project Management" icon="gears" href="/docs/teams/operations">
    Monday trading brief, Vendors and purchase orders, Decision log, and 3 more.
  </Card>

  <Card title="HR & People Ops" icon="users" href="/docs/teams/hr-people-ops">
    New hire onboarding, Job description draft, Policy Q\&A, and 5 more.
  </Card>

  <Card title="Legal" icon="scale-balanced" href="/docs/teams/legal">
    Contract redlines, NDA prep, Compliance question, and 2 more.
  </Card>
</CardGroup>

### Services

<CardGroup cols={3}>
  <Card title="Agencies & Consulting" icon="building" href="/docs/teams/professional-services">
    Client onboarding and kickoff, Deck review with the partner, Client status and dashboard, and 7 more.
  </Card>
</CardGroup>

## How every use case is built

Every use case page has copyable prompts, the connections it needs, and only the setup steps that apply. You build up in this order, and stop as soon as you have what you need.

<CardGroup cols={2}>
  <Card title="1. Ask Hops" icon="comments" href="/docs/quickstart">
    Copy a prompt into any chat, or mention `@Hops` in a Space. Many use cases need nothing more.
  </Card>

  <Card title="2. Connections" icon="plug" href="/docs/connections/overview">
    The apps Hops reads from and writes to. Each page links to the ones it needs.
  </Card>

  <Card title="3. Skill (optional)" icon="robot" href="/docs/agents/build-a-skill">
    Saved instructions, so Hops answers in the same format every time.
  </Card>

  <Card title="4. Automation (optional)" icon="clock" href="/docs/spaces/automation">
    Runs the work on a schedule or when something happens, so nobody has to ask.
  </Card>
</CardGroup>

Each page opens with a **How it runs** note that tells you which of these it uses:

* **Ask Hops:** ask in chat whenever you need it. No skill or automation.
* **Ask Hops + skill:** ask in chat, with a skill that keeps the output consistent.
* **Scheduled:** an automation runs on a schedule, posts an alert to Slack or the Space, and saves a Doc or Table.
* **Triggered:** an automation runs when something happens, like a new deal, ticket or form.
* **Space per client or deal:** one Space per account, project or deal, with its own context and automations.

## New to Hops?

Start with the [Quickstart](/docs/quickstart) to create your first Space, then come back and pick a use case.


## Related topics

- [Company AI brain](/use-cases/company-ai-brain.md)
- [Welcome](/welcome.md)
- [Get started](/quickstart.md)


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