Skip to main content
Operations teams are the connective tissue of a company, and also the team that deals with the most fragmented context. Hops gives ops teams one place where the full picture is always in view.

​
What ops teams use Hops for

  • Process documentation: keep SOPs, runbooks, and playbooks up to date without the manual overhead
  • Decision tracking: every decision logged in a thread, with context attached
  • Vendor and partner management: account context, contract summaries, and follow-up prep
  • Reporting: draft weekly ops reports from your connected tools without reformatting everything manually
  • Onboarding: new hire context, checklists, and recurring orientation flows via automations
Spaces: One Space per major ops function or ongoing process. Think vendor management, internal operations, team onboarding. Agents to add: The default agent handles most ops tasks. Build a custom agent if your team has a specialized workflow (for example, a dedicated vendor-management agent). Tools to connect: Google Drive or Notion (SOPs, docs), Linear or Jira (ops projects), Slack (team communication), your HR tool (onboarding context).

​
Example workflows

Weekly ops report
Set up an automation: every Friday, your ops agent pulls updates from your project tracker and connected docs, drafts the week’s ops summary, and posts it to the Ops Space. Review and send.
New vendor onboarding
Create a Space for each vendor. Pin the contract summary, SLA, and contact list. When anyone asks about this vendor, the agent answers from what’s already there. No digging through email.
Decision log
After each ops meeting, paste or summarize the decision in the Space thread. Tag the agent to format it as a decision record (what was decided, who owns it, next step). The log builds automatically.