1
0 Comments

Show me your diagram workflow: How do founders/architects actually create client facing systems diagrams in 2025?

I'm doing some research on how technical professionals create systems diagrams, and I keep hearing the same story: "I use AI to get off the ground, then I draw in Figma"

That seems like a gap, no?

I'd love to understand your actual workflow:

  1. What do you start with? (whiteboard, AI, Visio, draw.io, Figma etc?)
  2. What tool do you finish with? i.e. what gets sent to clients?
  3. How long does it take to produce a satisfactory diagram?
    4 What is the most painful step in your workflow?

[Bonus question] If there was a tool that could go from "rough idea" to "client ready visual" in under 10 minutes, is this something you would value, and what would you be willing to pay?

I'm especially interested in hearing from:

  • Solutions architects
  • Technical consultants
  • Product managers who create technical documentation
  • Anyone who builds applications and uses diagrams to communicate their ideas

Comment with your workflow below. I'll compile the results and share back what I learn.

Many thanks,

posted to Icon for group Ideas and Validation
Ideas and Validation
on October 2, 2025
Trending on Indie Hackers
Why Most Startup Product Descriptions Fail (And How to Fix Yours) User Avatar 97 comments We just hit our first 35 users in week one of our beta User Avatar 43 comments From Ideas to a Content Factory: The Rise of SuperMaker AI User Avatar 27 comments AIgenerationtool — replacing hiring writers with 1 AI dashboard User Avatar 24 comments NanoBanana or Seedream4.0? Why Choose When You Can Have Both User Avatar 19 comments Why Early-Stage Founders Should Consider Skipping Prior Art Searches for Their Patent Applications User Avatar 18 comments