Propane gives your product team and agents one connected, always-current view of your customers. Automatically collected from all your tools. Collaborate on a shared canvas. Commit straight to any coding or design agent. Secure, maintained, always on. You just build products people love.
Flame on! 🔥 So excited to finally launch this here on PH! 😽
We really put our blood, sweat and tokens into this one. the part i'm most excited about: for any PM, the days of context scattered across folders on your system are over — it now lives in one place you can actually work and collaborate in, a shared doc or prototype.
We built this for ourselves first, because we where drowning in scattered context, re-explaining the same stuff every time — so if that's you too, we'd genuinely love to hear your feedback! 💭
@greenlieber This feels like a real product team problem. Collecting feedback is not the hard part anymore; the hard part is turning scattered customer context into decisions without losing the reasoning behind them. I like the idea of giving both humans and agents the same shared context instead of forcing everything through separate docs and handoffs. Congratulations.
@alpertayfurr Thanks, ofc i 100% agree with your views here, and the strong point you have highlight is "reasoning" behind it. We often ignore that point.
@greenlieber Yes, I'm glad we're on the same page. I wish you success with your project :)
@harshchandgotia 100% its also a job that require taste & vision if we dont have that on the human side, we will just build slop on 10x so yes it's 100% a bigger impact even more now that execution is that fast.
And here we go!!!!
I watched product teams spend years deciding what to build based on whoever talked the loudest that week, while the real evidence of what customers needed sat scattered across support chats, sales calls, and notes nobody had time to read together.
With Propane, the reasoning behind a decision finally sits next to the feedback that shaped it, and an AI agent can use that same context to actually help instead of guessing.
It's been a pleasure building this for you all!
As a designer, the context layer is where I lose the most time. It takes loads of time pulling from research, support threads, and sales calls just to justify a direction. Love how you guys are solving this problem with Propane! Congrats on the launch.
@ben_shih I know that feeling 🫠 Though we're primarily serving PMs, I've been using Propane myself for design work — having the customer evidence already synthesized before I touch a frame changes how I think about a direction entirely. Especially the back-and-forth with your team (or agents) 🤖
When both suggest different directions simultaneously, how does Propane mediate those conflicts?
@crystalmei it really depends on how the user intent. A user can have a range of insights then some that are conflicting, then it up to the intent of the user to shaping the spec.
Let’s goo!!🚀 most excited to be part of building signals, my favourite part of propane, that gathers the most useful product context where I already work, and then makes that simple and accessible.
We really built this for ourselves as builders to actually build what matters - would love to speak to anyone building in the ai-era that feels limited by context, that was me!
@benfleming Too the mooooooooooooon! 🌝
@atherkildsen certainly on the way! with a great crew🚀🌕