Pilea
Agents for product management and customer research
How often do you communicate to your customers what you've shipped? 🔔📨Writing product updates was one of the tasks I always avoided, even though it's one of the most low-effort activities to show users and customers you're actually fixing the things they mention, and that you're actively improving your product.
Why I avoided it? 😌 It was probably one part forgetfulness (who can even remember the last 2 weeks?), one part imposter syndrome (have we really released anything cool enough to notify everyone?), one part tooling (it's "done" in Linear, but is it live in prod? (spoiler alert: no)) and one part laziness (how many people do I need to involve actually write this thing - from dev, ux, cs and marketing).
Starting two weeks ago, Lily - our assistant product manager agent in Pilea - writes them for us. And she does it in the format we want, in our tone of voice, on auto-pilot every two weeks and post the straight to Slack. She checks the codebase for what's actually made it prod, and has the context of each request so she can phrase it accordingly and check if multiple fixes are related to the same, customer facing thing.
A bonus outcome, that was very unexpected, Lily is always thrilled and excited about everything we've achieved (😅) and manage to show how much we actually get done. A friendly reminder to always celebrate our wins (though we do that every Thursday - something she's also contributing to) 🥳
We'll gradually give her agency to send them out herself, and maybe even notify the users who reported it (let us know if that would be of interest!).
Over the next weeks I'll be writing a "Dogfooding"-series on our blog, where I'll share how we use Pilea to build Pilea (dogfooding 🐶), which hopefully inspire you to start building your own agents to help deal with all the tedious task around product operations.
First up: Changelogs vs Product Updates!
👉 https://lnkd.in/eqRp8FGt
1 Comment
This is a strong dogfooding angle because it shows Pilea doing a real product-ops task, not just “AI agent helps with work.”
The sharper positioning might be less “Lily writes product updates” and more “Lily turns shipped work into customer-facing momentum automatically.”
That matters because changelogs are usually treated as internal hygiene, but for SaaS teams they can also reduce churn, close the feedback loop with users, and show customers the product is actively improving.
If you keep writing the dogfooding series, I’d make each post prove one product-ops workflow Pilea removes from the team: product updates, customer follow-ups, release summaries, internal celebration, feedback loop closure, etc.
That could make Pilea feel less like an assistant and more like an operating layer for product teams.