🦉 feedback for people who ship
Blog
Latest posts.
-
Product
we send one email a day
every status change used to be an email. triage twenty cards, someone gets twenty mails. now hoot sends one digest a day, with where each card ended up.
Jessé Cruz 3 min read
-
Playbook
what to write when you say no
hoot won't let you reject a card without a reason, and the reason gets emailed. three shapes that work, and the one that doesn't.
-
Playbook
let your agent do the monday triage
one prompt in claude code or cursor. the agent reads the board over mcp, finds duplicates, lines up tradeoffs, and stops before it moves anything.
-
Blog
we forgot the basics
the landing sold the agent, the mcp, the triage. it never said how feedback gets in. now it does: a board, a widget, an api. then the loop.
-
Product
we ask one question
the widget asked for a title, a description, an email and a name. now it asks what's on your mind. a category chip, one box, a screenshot. email only if we don't already know it.
-
Playbook
why hoot has no ai button
no summarize button. no ai triage. the agent you already use reads the board through mcp. a button inside hoot would be a smaller version of that.
-
Product
we let your app talk
the widget was web only. now an ios or android app gets a key that can only create posts, and a prompt you paste into your agent. no webview.
-
Product
we pick a shape
the widget used to live in your bottom-right. now it's a tab, an owl, a pill, or nothing. you pick. the snippet stays two lines.
-
Product
we work the board
pending was a number. now every card flags what's waiting, and you move it from a menu. no drag required.
-
Product
we killed the $5 plan
$5 was a tax. hoot is free now — one board, just you, mcp included. pro is $19 when the team shows up.
-
Product
we post to your url
new card? status change? pro can now POST a signed json payload to your endpoint. hmac. retries. no slack-or-nothing.
-
Product
we closed the loop
people asked. we shipped. now they get an email. comments on the card, a note for the team, and a ping when it actually goes out.
-
Product
Triage your product feedback from your AI coding tool
Hoot now ships an MCP server. Connect Claude Code, Cursor, or Codex to a project and let your agent read, search, triage, and ship feedback — without ever leaving your editor.
.png)
-
Blog
Why you should use Public Roadmaps
A public roadmap does more than showcase upcoming features. It reduces uncertainty, shows users you’re listening, and helps build long-term trust in your product.
.png)
-
Blog
The Problem With Collecting Feedback in Slack, Email, and DMs
Customer feedback is valuable, but when it's spread across Slack, email, DMs, and support chats, important insights get lost. Here's why scattered feedback leads to poor product decisions and how to fix it.
.png)
-
Blog
The Biggest Mistake Founders Make With Feature Requests
Most founders treat feature requests as instructions. The best founders treat them as signals. Learn how to uncover the real problem behind user feedback and avoid turning your product into a bloated mess.
-
Blog
Why I built hoot?
Hoot started as an internal tool to solve a problem I had across my own apps: feedback scattered everywhere. This is the story of how a simple need for a centralized, easy-to-integrate feedback system became a SaaS.
