Launching today
WeProcess 1.0
The thinking layer between your team and the work
15 followers
The thinking layer between your team and the work
15 followers
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.
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 templates can actually earn money, that part feels really fresh. one thing that would make this way stickier for me is letting teams run retros and standups right inside the kanban view, with the notes auto linked to the cards they came from. would save a ton of tab switching during sprint reviews
@mermercise71555
This genuinely made me smile, Serdar 🙏 Bringing agile practices — retros, standups — right into the workspace is exactly what I've been planning as the next chapter for WeProcess, so having someone pick up on the agile angle unprompted means a lot. Running them inside the kanban view, with notes auto-linked back to the cards they came from, closes the exact tab-switching gap I built this to fix. Sprint reviews are where context leaks most. The auto-link-to-card detail is what makes it real instead of just another notes panel. Thank you for seeing where this is headed.
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.
Honestly the template marketplace idea is pretty smart, I poked around and liked that I could grab a kanban setup someone else made instead of building it from scratch. Also cool that it's all in one workspace, kind of wish more tools did that.
@seval441146
Thanks Seval 🙏 Grabbing a kanban setup someone else already figured out, instead of rebuilding it from scratch, is the exact loop I wanted to make normal — someone's already solved this problem three teams over, so why start from zero? And "wish more tools did that" is honestly the whole reason WeProcess exists as one workspace instead of five. Really appreciate you poking around and sharing this.
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.