Skip to main content
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

Company AI brain

Every decision, doc and thread, answerable in one question. Connect your docs, threads and decisions once, then ask anything.

​
Browse by team

​
Leadership

Founders & Executives

Monday company snapshot, Board meeting and fundraise prep, Investor update, and 6 more.

VC & PE

Investment memo, Founder pipeline and partner meeting, Quarterly LP update, and 1 more.

​
Go-to-market

Sales

Pre-call prep, Post-call follow-up, Deal rooms, and 8 more.

RevOps

Handoff watch, Renewal watch, Pipeline review, and 5 more.

Marketing

Campaign launch, Content repurposing, Copy review and approval, and 7 more.

Support

Response drafting, Weekly patterns report, Escalation brief, and 4 more.

​
Product & Engineering

Product & Engineering

Spec review, Release notes, Sprint retro prep, and 7 more.

​
Back office

Finance

Monthly close, Board prep, Spend anomaly alert, and 3 more.

Operations & Project Management

Monday trading brief, Vendors and purchase orders, Decision log, and 3 more.

HR & People Ops

New hire onboarding, Job description draft, Policy Q&A, and 5 more.

Legal

Contract redlines, NDA prep, Compliance question, and 2 more.

​
Services

Agencies & Consulting

Client onboarding and kickoff, Deck review with the partner, Client status and dashboard, and 7 more.

​
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.

1. Ask Hops

Copy a prompt into any chat, or mention @Hops in a Space. Many use cases need nothing more.

2. Connections

The apps Hops reads from and writes to. Each page links to the ones it needs.

3. Skill (optional)

Saved instructions, so Hops answers in the same format every time.

4. Automation (optional)

Runs the work on a schedule or when something happens, so nobody has to ask.
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 to create your first Space, then come back and pick a use case.