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.
I had the pleasure of giving Propane a spin with @atherkildsen and I have to say that I believe they're really onto solving "the real" headache for product managers and anyone else working with qualitative (plus quantitative) data collection. Distilling insights from phone calls, emails, usage patterns and shower-thoughts used to be an art form. Propane helps make the process transparent and solid from insight to deployment. Junior PMs get a nudge towards quality and senior PMs get speed and collaboration on the artefacts that matter.
Excited to see where the team will take this!
What are you looking at next @greenlieber ? I suppose with launch on product hunt there will be a lot of insights for you to capture now, and distill? ;)
Propane
@atherkildsen @stian_nm Take over the world haha... I want to enable all Product teams to build amazing products based on context, this values them and their customer, fighting AI slop products.
@atherkildsen @greenlieber amazing, looking forward to seeing where you'll go with this! ✨
Propane
@atherkildsen @stian_nm so do we :)
Propane
@greenlieber @stian_nm 💚 A lot happened since our chat (a month ago 🤪), so you should go check it out!
Mailwarm
What does that handoff look like, generating a spec or directly creating tasks in a tracker?
Propane
@thamibenjelloun Its a spec with attachment to signals files etc, we have not focused on created tasks in tools like @Linear or @Jira if thats what you mean? How would you like that work out?
Work from context in Canvas -> Spec + context -> Tasks then agents work from that vs direct handover?
Jinna.ai
Congrats on the launch! Good stuff for teams, but how does it compare to Claude Cowork + like 1 team/knowledge directory?
Propane
@nikitaeverywhere Hey Nikita big thanks for the support means a lot!!🤝
Genuinely great question that we have thought a great deal about ourselves..
Having built some pretty comprehensive internal claude code/markdown/obsidian based setups we thought this was quite overcomplicated: managing state, coordinating across team (engineers and non-engineers), felt quite single player - you still need to set up schedules infra etc.
Fundamentally we wanted to make gathering important product context: simple, accessible and ready out of the box - you plug your tools in, where you work already, then we ensure the signals come in filtered from the noise, so you (or your agents) can easily work with product context and collaborate with your team in a multiplayer setup
Would be super down to get your deeper feedback!
The canonical context idea is the right problem. The release risk is provenance: if an agent is going to commit from customer context, the team needs to see which source changed the recommendation and how stale that source is. Otherwise the shared brain quietly turns into another untrusted doc pile.
Propane
@krekeltronics Spot on, but is also an hard problem to get right, all while that part of the market is in a mindset of "let it ship on it own" BTW. a massive fan of the product you have been part of, Teenage Engineering. wow a beautiful product and fun to play.
Propane
@krekeltronics @greenlieber also a big teenage engineering fan... 🙋 now that is how you build an exceptional product!
agree for sure with your point, that's why we built the full trail in. for example, we have the full map from conversation -> insight -> signal in our platform so you can see exactly what is informing your signals:)
ConnectMachine
how does Propane decide what counts as “new context” for billing??
Propane
@syed_shayanur_rahman If we fin a new insight on a company from e.g a support ticket its new context, and within that month if we find 20 new insight for that company you only pay once.
Would love to see integrations with Gong, HubSpot, and Intercom if those aren’t already on the roadmap.
Propane
@ankur_jeswani We support hubspot, intercom and gong i coming but we do support @Granola
I've burned through a lot of tools trying to solve the same problem, keeping design decisions grounded in actual customer reality instead of internal assumptions.
What I like about Propane is that I went in thinking "this is for PMs." It's not. As a design lead, the context layer is where I spend a disproportionate amount of time, pulling from research, support threads, sales calls, Slack, just to make a case for a direction. Propane collapses that. When you're committing context directly to a design agent, you're starting from signal instead of noise.
This is the right problem to solve. ❤️💪
Propane
@madshensel Thanks for being a supporter day 1