If I could point to the one differentiating quality of those who can optimize work for scale, it's people who are able to think in workflows, versus others who think in isolated documents.
I was 22 years old, fresh out of college, when I first learned how to flowchart, and it changed the way I think about operations. It was just one year later when I had an anxiety attack as the COO of a 15-person startup company, trying to manage how my business worked through documents
Congrats on the launch@b_ragone!
I've been using Puzzle for quite some time now, both in my own business and with clients, and it's become a pretty essential part of how I approach operations.
One thing I especially love is how Puzzle helps connect the dots across an entire business. It's not just about documenting what happens in a process, but understanding the dependencies, assets, and costs between people, tools, and workflows. That's incredibly valuable when you're trying to make meaningful operational improvements without accidentally breaking something else. Also, MCP functionality makes mapping so much more efficient. I use it almost every day, and especially after client calls, to help identify (and make) updates in an existing process or start planning a new one.
But I also want to give Brian a huge shoutout. We've had several conversations about the product, including one just yesterday where I walked through a bunch of feedback, and what I appreciate most is how genuinely curious and receptive he is. He doesn't just listen to feedback. He asks thoughtful questions, explores solutions with you, and is clearly passionate about building something great.
It's been awesome working with you, Brian! Excited to see Puzzle continue to evolve and highly recommend folks try out Puzzle, especially if you're coming from the Whimsical/Miro/Lucidchart world. ✨
😍 @jessafterhours Thank you, Jesse! We feel blessed to have you and your deep expertise in this space working with us as a superuser to make the product better every day!
I'd been stuck in a rut for years superstacking tool after tool seeing the value in them all but drowning in confusion; then earlier this year I bumped into Puzzle and BOOM, it felt like somebody had thrown me a lifeline
Create a new workspace, hook up the MCP to Claude, add Brian and Kronda's super sauce (skills) and that's it, you're now officially a "Process Pro".
FULL DISCLOSURE: I am the least likely human on this entire planet who is, ever has been, or is ever likely to be a "Process Pro" but with Puzzle in my stack I genuinely have a new super power and finally I've levelled up! So if I can make it work, then anybody can.
And finally, a big shout out to the unsung hero baked in to the platform, that's the forever helpful "Jolly" who is always on in the background keeping the plates spinning while the nerds keep nerding.
What a product and what a team, thank you for all you do and the value you bring.
@thevikinggeneral Mark, thank you for your advocacy, it has been awesome to have you in the user community bringing your ideas re: tool templates, and organizing the endless tech stack that seems to keep growing! 🙌
See you in a future Office Hours!
maps like this usually die the week after setup cause nobody updates them, having the agents write back to it might actually fix that
@igorblink yes, I have a dedicated Documentation bot connected to Puzzle via MCP who keeps all my maps up-to-date as they evolve how they work.
Agents work fully autonomously while keeping me in the loop with their methods 👌
Which bots are you building with?
For a while Puzzle has been the way we plan and then manage our fleet of agents. It’s helps our whole team understand and maintain all things operations, and we can do it without breaking a sweat. Agents managing our docs for humans, amazing!!
@mike_roberts6 🙌 Top user right here. Thanks for the support, Mike!
Hey Product Hunters! 👋 I'm Brian, Founder of Puzzle.
In 2017 I ran ops for a 15-person startup and ended up in the hospital after an anxiety attack. Nobody could see how the operation fit together, so every process change turned into a multi-hour meeting. So I built Puzzle: one visual map of how the whole operation works.
Nine years later the problem is the same, but more of the work now runs through AI agents. A user just told me Claude feels like a "black box." He's right. Agents don't know how your business works, and your team can't see how the agents work.
Most teams pick one:
a diagram people can follow
Markdown files only agents read.
✅ Puzzle puts both on one map:
↳ Clear instructions your agents execute
↳ A clear visual your team can see
↳ A changelog of every decision
What part of your agents' work feels like a black box right now?
💭 Drop it below and I'll answer.
The tools listed next to each step are a detail I like. It helps with the very practical “where do I go to fix this?” question
@marianna_tymchuk Yes, great for debugging automations if you're responsible for workflows that spread across many systems!
Do you spend most of your time debuggin in a specific system (or many) in your company?