WeProcess brings together the thinking tools your team already uses — whiteboard, kanban, mind map — and adds what most tools miss: a template marketplace where frameworks are shared, rated, and paid for. Publish your best process and earn every time it's used. Use what others have built and skip weeks of setup. Everything runs in one workspace, in 12 languages, with no vendor lock-in. Free plan available. Built by a solo founder from Japan.
No reviews yetBe the first to leave a review for WeProcess 1.0
Maker
📌
Hey Product Hunt! 👋 I'm TSUTSU, a solo founder from Yokohama, Japan.
For 15+ years I worked as a QA engineer across 100+ companies. Two things I saw everywhere eventually became WeProcess.
First: teams fiercely protect "our proprietary know-how" — but most of it isn't proprietary at all. The same framework, the same hard-won lesson, already exists three companies over. We guard knowledge that was never actually secret, and in doing so we keep everyone starting from zero.
Second: even when people want to share, the system doesn't reward it. You open-source code and get a thank-you, not a paycheck. You write the internal doc, give the thoughtful review, publish the blog post — real value, quietly consumed, never returned to you. So the rational move is to stop sharing. Knowledge stops flowing and dies inside one person's head.
WeProcess is my attempt to fix both.
It brings whiteboard, kanban, and mind map into one workspace, so your thinking doesn't get lost between tools. But the part I care about most is the template marketplace: publish a framework you've refined, and earn points every time someone uses it — points that convert to real money. The giver is rewarded, the receiver skips weeks of setup, and even the person who simply says "this is good" earns a little too.
Newton said we stand on the shoulders of giants. But someone has to lend the shoulder — and today, lending it pays nothing. I wanted to build a place where sharing knowledge is finally worth it.
WeProcess runs in 12 languages, free to start, no card required. This is 1.0, built solo.
Where does your team's knowledge get stuck today? I'm reading every comment 🙏
Report
The template marketplace idea is genuinely cool, and I like that you can monetize what you build. One thing I'd want before I commit is a real-time version history on the whiteboard view, so when a teammate edits a diagram I can scrub back and see exactly what they changed and when. Right now most tools either save full snapshots or just show an edit log, but neither lets you actually replay a brainstorm session. Would love to see that in a future release.
Thanks Betül — this is a sharp distinction, and one I've thought about a lot. You're right that most tools give you either snapshots or an edit log, but not a replayable session. The former loses the "why," the latter is unreadable. What you're describing — scrubbing back through a brainstorm as it actually unfolded — is exactly the kind of thing a CRDT-based history layer makes possible, and it's on my radar for the whiteboard. Genuinely useful framing for how to prioritize it. Really appreciate you taking the time.
Report
The template marketplace idea is genuinely interesting, especially paying creators for what gets used. One thing I'd love to see is a way to fork a template and tweak it for my own team while still crediting the original author, kind of like a GitHub branch for processes. That would make it way more natural to adapt someone's kanban setup or mind map without feeling like I'm starting from scratch every time.
You just described something that's been in my head for a while, Mihriban 🙏 Version-controlling templates — so you can fork one, adapt it for your team, and still trace it back to the original author — is exactly the direction I want the marketplace to grow. Right now templates are snapshot-based, but the branch model is the natural next layer. And the credit chain fits the point system perfectly: if a forked version gets used, the original author should still earn upstream. Really glad this resonated with someone else too.
Report
Love that the template marketplace is built in from day one — most tools bolt that on later. Spent a few minutes browsing frameworks and the rating system actually feels useful, not just filler.
Thank you Fatma 🙏 You noticed the thing I cared about most — the marketplace and rating system had to be built in from day one, not bolted on, because the whole point is that sharing knowledge should be rewarded, not an afterthought. "Not just filler" is exactly what I was aiming for: a like isn't just a vanity number here, it feeds real points back to the author. Really glad you actually browsed it — that means a lot.
Report
The kanban-to-mind-map handoff is way smoother than I expected, and having shared templates actually saved me a setup headache this morning.
This made my morning, Didem 🙏 Getting the mind-map-to-kanban flow to feel seamless — sketching the plan, then dropping it straight into execution without switching tools — was one of the hardest things to get right, so hearing it worked in real work means a lot. And templates cutting your setup time is exactly what I was going for. The community-shared template marketplace is still early, so if there's a framework you'd want to see there, I'd genuinely love to know.
Report
finally tried the mind map and kanban in the same view, and it actually clicked for me. the template marketplace idea is solid too, especially being able to publish my own and get paid when others use them.
"It clicked" is the best thing I could hear, Turan 🙏 The mind map and kanban living in the same view — planning and doing without the context switch — was the hardest thing to get right, so knowing it landed in real use means a lot. And you nailed the part I care about most: publishing your own and getting paid when others use it. That's the whole loop. If you do end up publishing one, I'd genuinely love to see what you build.
Report
the template marketplace idea is genuinely clever, especially letting people earn from frameworks they actually use at work. love that it's one workspace instead of juggling five tools
Thank you Necati 🙏 "Juggling five tools" is exactly the pain I built this around — every switch costs you context, and the thinking quietly leaks out in the gaps. And letting people earn from frameworks they already use at work is the part I care about most: the knowledge is already there, it just never gets rewarded. Really glad both halves landed for you.
The template marketplace idea is genuinely cool, and I like that you can monetize what you build. One thing I'd want before I commit is a real-time version history on the whiteboard view, so when a teammate edits a diagram I can scrub back and see exactly what they changed and when. Right now most tools either save full snapshots or just show an edit log, but neither lets you actually replay a brainstorm session. Would love to see that in a future release.
@betls8fo
Thanks Betül — this is a sharp distinction, and one I've thought about a lot. You're right that most tools give you either snapshots or an edit log, but not a replayable session. The former loses the "why," the latter is unreadable. What you're describing — scrubbing back through a brainstorm as it actually unfolded — is exactly the kind of thing a CRDT-based history layer makes possible, and it's on my radar for the whiteboard. Genuinely useful framing for how to prioritize it. Really appreciate you taking the time.
The template marketplace idea is genuinely interesting, especially paying creators for what gets used. One thing I'd love to see is a way to fork a template and tweak it for my own team while still crediting the original author, kind of like a GitHub branch for processes. That would make it way more natural to adapt someone's kanban setup or mind map without feeling like I'm starting from scratch every time.
@mihriban1537007
You just described something that's been in my head for a while, Mihriban 🙏 Version-controlling templates — so you can fork one, adapt it for your team, and still trace it back to the original author — is exactly the direction I want the marketplace to grow. Right now templates are snapshot-based, but the branch model is the natural next layer. And the credit chain fits the point system perfectly: if a forked version gets used, the original author should still earn upstream. Really glad this resonated with someone else too.
Love that the template marketplace is built in from day one — most tools bolt that on later. Spent a few minutes browsing frameworks and the rating system actually feels useful, not just filler.
@fatma147337
Thank you Fatma 🙏 You noticed the thing I cared about most — the marketplace and rating system had to be built in from day one, not bolted on, because the whole point is that sharing knowledge should be rewarded, not an afterthought. "Not just filler" is exactly what I was aiming for: a like isn't just a vanity number here, it feeds real points back to the author. Really glad you actually browsed it — that means a lot.
The kanban-to-mind-map handoff is way smoother than I expected, and having shared templates actually saved me a setup headache this morning.
@didemlhaa
This made my morning, Didem 🙏 Getting the mind-map-to-kanban flow to feel seamless — sketching the plan, then dropping it straight into execution without switching tools — was one of the hardest things to get right, so hearing it worked in real work means a lot. And templates cutting your setup time is exactly what I was going for. The community-shared template marketplace is still early, so if there's a framework you'd want to see there, I'd genuinely love to know.
finally tried the mind map and kanban in the same view, and it actually clicked for me. the template marketplace idea is solid too, especially being able to publish my own and get paid when others use them.
@turankto2
"It clicked" is the best thing I could hear, Turan 🙏 The mind map and kanban living in the same view — planning and doing without the context switch — was the hardest thing to get right, so knowing it landed in real use means a lot. And you nailed the part I care about most: publishing your own and getting paid when others use it. That's the whole loop. If you do end up publishing one, I'd genuinely love to see what you build.
the template marketplace idea is genuinely clever, especially letting people earn from frameworks they actually use at work. love that it's one workspace instead of juggling five tools
@necativgky
Thank you Necati 🙏 "Juggling five tools" is exactly the pain I built this around — every switch costs you context, and the thinking quietly leaks out in the gaps. And letting people earn from frameworks they already use at work is the part I care about most: the knowledge is already there, it just never gets rewarded. Really glad both halves landed for you.