Sharing My Experience and a Few Ideas for the Next Steps
I rarely leave public comments, but this tool truly deserves recognition. The concept is incredibly powerful when well structured. I subscribed to the Tier 3 plan to support its development the project looks very promising and gave it the highest rating to help maintain momentum.
Here are a few improvements that would add significant value:
AI in the workflow: accelerate process modeling and enable automatic interpretation of Miro screenshots (extracting steps/connections).
Native webhook: an essential feature for integrations and automations.
Team section with photos: allow adding member images; because help with identification.
Configurable currency: make it possible to define the currency type in value fields.
Easy export: direct export to PPT (still the most used format in corporate presentations) and also to CSV or XLS.
Congratulations on the excellent work so far I’ll keep following and contributing wherever I can.
b_ragone
Nov 10, 2025Hey there! Thank you for your 5 star review, and feature suggestions. I'm thrilled to hear the value you're getting from the platform 🙏 I have a good news about your requests — many of your feature requests are on our roadmap with many upvotes, and planned:
↳ AI Agent — we'll be launching Nova, our agent, who will be able to take screenshots (any any text based input) from other systems and generate the diagram in Puzzle automatically). Estimated timeline: EOY 2025
↳ Webhooks — we have a spec for users to be able to send events to step cards. Is that what you're referring to re: Webhooks? Estimated timeline EOQ1 2026
↳ Team Section with Photos — user will be able to upload their photos to the *People cards*. Estimated timeline is EOM Jan 2026.
↳ Configurable currencies — users will be able to define the currency for an entire Workspace for Tool costs, and Role hourly rate costs. Estimated Timeline: TBD
↳ Export to PNG / PDF, and .xls — users will be able to one-click export a Section to PNG or PDF. Timeline EOQ1. .xls download timeline is TBD.