Q: Please explain to me how this system is useful at Tier 1 & 2 ...
It really seems like the value proposition of Puzzle is in the ability to track and calculate costs and tell clients a very clear narrative in a visual way that demonstrates 'my' value to them. It also seems like those features are restricted to Tier 3. So, how are these things accomplished in Tiers 1 & 2?
b_ragone
Nov 4, 2025A: Hey Superdang, there are a collection of features included in Tier 1 and Tier 2 that you won’t find in any other diagramming tool. Here’s a quick rundown of what makes each of them special:
1️⃣ Connected Team Designer — Most diagram tools stop at showing what happens. Puzzle goes further by showing who does it. With the Team Designer, you can assign roles, visualize ownership, and instantly see where handoffs happen. It’s perfect for agencies and ops teams mapping out accountability or redesigning org structures.
2️⃣ Tool Canvas — Instead of just naming the apps you use, the Tool Canvas lets you map where each tool connects to your processes. You can see your stack in context—how HubSpot feeds into Zapier, or how Airtable connects to your client portal—so you understand exactly how your systems talk to each other.
3️⃣ Combining Written and Visual Documentation — Most platforms force you to choose between a diagram or a doc. Puzzle merges both. Each step in your process holds its own written context, links, and Loom or Scribe recordings—so your visuals stay readable while your details stay accessible.
4️⃣ Public Views — Instead of exporting screenshots or rebuilding your diagram elsewhere, you can share a live view of your map directly with clients or stakeholders. They get to explore your processes interactively—without editing rights—so you maintain clarity and control while sharing your work beautifully.
5️⃣ Consistent diagramming — many teams need to train their teams on 'how to diagram' to follow a 'visual language' of color keys, shapes, and formatting. With Puzzle, you're guaranteed to get a consistently beautiful and easy-to-understand diagram no matter who is diagramming. You can throw your 'diagram formatting' SOP out the window with Puzzle.
Is there a way to restrict specific information from being viewable based on who is looking at it?
Scenario: I build my process diagram and show how/where different tools connect via API. That’s all the info a client, or VA, needs to see in public view but my CTO and I should also be able to store things like and API key for each of the connected tools and have them be secure from anyone else.
Verified purchaser
Hey Superdang, the best way to parse out which processes & informations are seen by who is to use the Public Share Views. It allows you to select which Sections of the map a client can see.
If you wanted to have sensitive information excluded, you'd just not include those steps of the process in the Public View.