Launching today
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.
Propane
Hey Product Hunt 👋
Our founding team has been building products for 10+ years at scalable SaaS and deep learning AI companies. We wanted to fix our own problems. The way product teams work has not changed much in a long time, and we think it is time for that to change.
Over the last several months we went very deep with hundreds of product teams. Two camps: stuck in legacy tooling or building everything from scratch. What surprised us is that both are doing 90% of the same work. Collecting customer feedback. Shaping and evaluating ideas. Handing off to coding agents. Every team. Every time.
The same shift Cursor brought to engineering is coming for product.
How you understand your customers at scale, how you operate and strategize, how you collect and make sense of everything. All of that should just be provided for you. Automatically, with your context, your intent, and your personalization built in.No one should be rebuilding that infrastructure individually, at every company, every time.
We are building Propane for the people who want to focus on the primary work. To think, strategize, and shape the future of software. To have time to talk to customers, look at the market, and build products that everyone loves ❤️
How Propane works
Collect: we pull everything into one shareable context. Your customer and market brain, for your entire team and agents.
Collaborate: you and your agents work together in one shared workspace. No copy-pasting, no context switching.
Commit: from that same context, hand over to your coding and design agents with a canonical data set built for meaningful outcomes.
Everyone has access to the same context. No more sharing documents across other systems. Everything compounds and stays in one place where humans and agents can work together.
We think pricing should be different.
We want to make this more accessible and more valuable. That is why we are introducing one price, as many users and tools as you need. You only pay for the new context we find and index each month. Capped. No surprises.
Our offer to the Product Hunt community: use code PH001 for three months free on the base plan.
That is $150 in value, on us.
If you want to know more:
Pricing: https://www.usepropane.ai/pricing
Changelog: https://www.usepropane.ai/changelog
Try it: https://app.usepropane.ai/auth/signup
Sign up, try it, and help us shape the future. We are reading everything.
Best,
The Propane team ❤️ 🚀
@greenlieber im so excited for this launch. The multiplayer part and how we can accelerate our decision making in Product and cross functionally is critical to get right to actually save time and to get the decisions right
Propane
@michaelauchenberg Me to! We see over and over that this is hard and the multiple player part is just not there , or now it is... :)
Looks very interesting - is there a minimum of data (maturity of company / product) that is needed in order for these insights to be valuable / actionable?
Propane
@simonsylvest What's up simon thanks for the support!🤝
I would say for a decently established team (small/startup fine for sure) but probably not solopreneurs. One good rule of thumb could be if you have a stack of tools that are capturing customer context already but it is scattered across your team.
Then signals will flow in seamlessly from those tools, filtering out the noise, and you can collaborate with your team with them in canvases!
Propane
@simonsylvest hey man, besides from Ben's answer there is also the difference between a signal and a insight on our platform.
Enough insights about the same subject turns into a signal, which as you said, becomes actionable. Hope that covered all the angles! Say if you have more questions
Persuasive Patterns Card Deck (4th gen)
I've been watching what you've been building for a while now and is genuinely excited for this.
With the teams you've been testing with, where do teams typically see the biggest lift first: support speed, product discovery, or better handoffs between teams?
And how do you see your tool stack up against, for instance, harvestr?
Propane
Hej @toxboe 👋 Thanks for following along!
I'd say the biggest lift is actually increase alignment, because they have a shared context and understanding from the get go.
Discovery comes second, and something that sneaks up on the teams, as they get more and more invested in the platform.
I haven't used Harvestr, but did a quick background check, and I'd say it's a different tool, for a different problem. They look like they are more focused downstream, with collecting and organizing feedback, and pushing that to a roadmap, right? We're focusing more upstream, and signals come before feedback, and the context is there for the agents, when you want to dig in. So we overlap, but we've taken a different approach to it.
Happy to show you what we're seeing.
Introducing one flat price for unlimited users and tools is a huge win for lean startups that are sick of seat-licensing fatigue, Congrats 👏 for shipping. qq does the base plan track historical context storage limits, or are we literally only billed on the net-new data ingested during the billing cycle?
Propane
@vikramp7470 Good question. Historical context is included in the base plan, no extra charge. You only get billed when we index a new customer or competitor for the first time in a billing cycle. After that, every update, signal, or data point we pull on that same customer counts as one index event, not one per update. So 30 signals on a customer in a month still equals one billing unit for that customer that month.
@greenlieber Thanks for clarifying, super fair pricing model, appreciate the breakdown.
Think this space is very exciting, but there is also a lot of "build-it-yourself" going on and most often a pretty heavy legacy stack. How do you see the space and your vision in this regard?
Propane
@thomas_kjolhede The way we see the market is that legacy systems were built for records, not reasoning. Someone always had to manage the context manually, and that's still true today.
The DIY wave makes sense, but what we're seeing is that 90% of teams are building the same thing: the same prompts, the same skills, the same local context stores. That's just a new silo.
We're building with the 90% already done. The 10% is your data, your team, your intent. You get the same power as building it yourself, but shared infrastructure means compound value across your team and agents, less time to value, and lower cost on tokens, infra, and time.
Why should every team build this alone when we can scale it together?
How do you see it?
Great work and congrats on the launch. Am I correct to assume the always-current, auto-collected part is the hardest element? Wondering what happens when two tools disagree about the same customer (ex. - sales notes say one thing, support tickets another) - what do you treat as truth before committing that to an agent?
Propane
@artstavenka1 Yes, you're right, that's the hardest part. Think of it like a data warehouse problem: deduplication, matching, conflict resolution across sources. That's real infrastructure work and most teams have no business spending cycles on it.
Our view is that teams shouldn't have to deal with that layer at all. You connect your tools, you get access to clean, enriched context. We handle the hard job underneath. The goal is that when two sources disagree, that's our problem to resolve, not yours.
Vivaldi
Looks very polished! What vendor did you use for document processing/multiplayer text editors?
Propane
@uladzislau_rasliak Thanks for the praise. We landed on @Tiptap to handle that layer. Great product with great offerings. Shout out to them :)