Hops for product teams
Standups, release notes, and retros, written for you.
@Hops turns your team's rituals into decisions, not more meetings.
- Postmortems drafted when things break
- Blockers and reviewers named, not waited on
- All inside Hops, where your team and one agent work together
On the team
Your eng rhythm, automated
Four standing routines. No prompting, no chasing — the work just shows up done.
Release notes
Merged PRs get categorized into features, fixes, and improvements and written as user-facing notes, handed to the PM for polish. Half a day becomes ten minutes.
sprint-14
53ChatDocs & TablesAutomations
Start meeting
AGENT9:02 AM
24 PRs merged since v2.13, categorized and written as user-facing notes. Ready for your polish, @Nina.
Release notes — v2.14
Draft · 24 merged PRs categorized
- Features 7 — realtime exports, saved views
- Fixes 12 — 4 reported by customers
- Improvements 5 — search latency, bulk actions
9:11 AM
Two wording changes and it ships. This used to be half a day of changelog archaeology.
APP9:14 AM
Release draft updated.
v2.14 — Release notes
Release · synced just now
StatusDraftReady to publish
Retro pack
Completion rate, rollovers, and re-estimated items by member land on the retro page before the meeting. Retros run grounded in data.
sprint-14
53ChatDocs & TablesAutomations
Start meeting
AGENT2:30 PM
Retro pack is on the page — completion, rollovers, and re-estimates by member. Nobody has to pull numbers in the meeting.
Retro pack — Sprint 14
Posted 30 minutes before retro
- Completion 84% — 42 of 50 points
- Rollovers 3 issues, all realtime exports
- Re-estimated 5 items, 4 on one workstream
2:38 PM
Rollovers all sitting in one workstream — that's the retro topic, not a round robin.
AGENT2:39 PM
Pinned it as the first agenda item and attached the pack to the retro doc.
Retro agenda — Sprint 14
Updated · 1 topic pinned
- 1. Realtime exports rollovers — owner Riley
- 2. Estimate drift on the same workstream
Postmortem drafter
The timeline compiles from Sentry errors and the incident channel into a postmortem skeleton, with responders tagged to annotate one shared timeline.
sprint-14
53ChatDocs & TablesAutomations
Start meeting
AGENT8:20 AM
Last night's incident timeline is drafted from Sentry and the incident channel. Responders are tagged to annotate their own steps.
Postmortem — API latency, Jul 14
Timeline drafted · 3 responders tagged
- 21:14 error rate 12× baseline
- 21:22 rollback started — Theo
- 21:41 recovered — 27 minutes of impact
8:33 AM
Annotating the rollback gap now — the deploy lock wasn't obvious to anyone outside the on-call rota.
APP8:35 AM
Incident status changed.
INC-118 — API latency
Incident · synced just now
StatusMitigatedPostmortem in review
Feedback miner
Intercom and Zendesk conversations get mined weekly for requests and bugs, deduped into the backlog with links and counts, with a PM triage invite per batch.
sprint-14
53ChatDocs & TablesAutomations
Start meeting
AGENT10:05 AM
This week's support mining — deduped into the backlog with links and counts. Triage invite is out for Thursday.
Feedback digest — week 28
217 conversations · 4 themes
- Bulk export 34 mentions across 9 accounts
- SSO on team plan 21 mentions
- Mobile session timeout 12 mentions — bug
10:19 AM
Bulk export goes to the sprint 15 candidates. Nine accounts isn't a hunch anymore.
APP10:21 AM
Issue created from digest.
Bulk export — customer request
Issue · created just now
BacklogUnsortedSprint 15 candidate
Beyond chat
Not just chat. The actual work.
@Hops works in the same surfaces your team does, and leaves a trail you can audit.
Collaborative Docs
Real collaborative documents. Hops drafts, edits, and comments next to your team. Every Hops edit labeled in version history.
Collaborative Threads
Conversations that carry the work. @Hops reads along, posts what it finds, and takes the next step right in the thread, next to your team.
Personal Assistant
Describe the job in plain language. @Hops runs it with everything it already knows: your context, your tools, your rules.
Integrations
Wired into your system of work
@Hops lives where product and eng live with a 2K+ connector catalog behind it for the rest of the stack.
Project tracking
Jira and Linear: shipped, in-progress, and blocked, read and written.
Dev & monitoring
GitHub and Sentry: PRs compiled into release notes, errors into postmortem timelines.
Team chat
Slack and Teams: standups posted, blockers surfaced, nudges sent where the team already is.
Support & knowledge
Intercom, Zendesk, Docs, Notion: feedback mined, backlogs built, decisions documented.
Security that's already answered
SOC 2 Type II
Audited controls for security, availability, and confidentiality.
ISO 27001
Certified information security management.
ISO 42001
Certified AI management. Governance for the agent itself.
Permissions from the space
Hops and teammates inherit access from the space and its owners. No shadow permissions.
One AI teammate for the whole team
Knows the work. Forgets nothing. Shares with everyone.