# Product Ops Coordinator

Help software and ecommerce teams hear customers clearly, write better issues, and tell customers what changed, without a dedicated product operations hire.

Works for: [SaaS companies](https://www.generalinput.com/templates/saas-companies)

## What it handles

- A weekly feedback report: the top requests and pain points, how often each came up, and from which customers.
- Issue drafts for bugs and requests, with steps to reproduce, expected and actual behavior, and acceptance criteria.
- Release notes drafted from merged work, in plain language for customers.

## What to bring

- Your help desk (Intercom or Zendesk), call recorder (Gong), issue tracker (Linear or Jira), and GitHub.
- Your product areas, how issues should be written, and who approves release notes.

## What it can set up for you

- **Issue Writing Method** (skill): Turns a report or request into a clear issue with acceptance criteria.
- **Weekly Feedback Themes** (workflow, Every Monday morning): Reports the top requests and pain points from tickets and calls.
- **Release Notes Draft** (workflow, When a release is tagged): Drafts customer-facing release notes from merged work.

## A fictional example

### You provide

Fictional week: 9 tickets asked to export reports to a spreadsheet, 4 said the mobile app signs them out every day, and 2 sales calls asked for single sign-on. Merged this week: 'Add CSV export to reports' and 'Fix daily sign-out on iOS'.

### Illustrative result

# Feedback, week of 2026-10-13

1. Export reports to a spreadsheet: 9 tickets. CSV export shipped this week; tell those customers.
2. Daily sign-out on mobile: 4 tickets. Fixed for iOS this week; the fix does not mention Android.
3. Single sign-on: 2 sales calls.

## Release notes (draft)
- Export any report to CSV.
- The iOS app no longer signs you out every day.

Nothing was published.

## How setup works

1. Add the specialist. It arrives with its role and starter memory, and nothing is built or connected yet.
2. It asks what you want it to handle, which tools your team uses, how often, and where results should go.
3. It proposes the workflows, apps, and skills that fit, builds the ones you approve, and tests them with you before anything runs on its own.

## Where its job ends

- It drafts and files issues. It never changes priorities, closes issues, merges code, or publishes release notes.
- Themes show the conversations behind them. It never names a customer outside the team.

Use this specialist: https://www.generalinput.com/templates/specialists/product-ops-coordinator